Skip to main content

Log files

Instrument and system logs are the evidence Chipper uses to reconstruct activity. Chipper reads those logs without changing the instrument or its control software, then parses the original text into structured fields.

How files reach Chipper​

  • A Chipper Log Collector can watch logs on an instrument PC.
  • Chipper can read from customer-owned AWS S3, Azure Blob Storage, or Google Cloud Storage.
  • You can manually upload representative or historical files from Investigate → Log Files.

See Instruments and log sources to choose a connection pattern.

What processing creates​

A processed file can contribute:

  • One or more runs, including runs that span several files.
  • Method attribution.
  • Events from enabled monitoring rules.
  • Derived numeric values for analysis and SPC.
  • Alerts when an event breaches an alerting condition.

Chipper keeps the original file available for investigation. Open Log Files to filter by file name, status, source, instrument, type, method, run, or upload time. Select Details to review the file's relationships, or open the viewer to search and inspect the original text.

File status​

The normal manual-upload path moves from Received to Processing and then Processed. A file can instead show an error or a held state when Chipper cannot safely complete ingestion or attribute the data.

A processed file with zero events is not necessarily empty or broken. It may contain valid activity that no enabled rule currently matches. Check the instrument type, open the Rules Library, and confirm that the relevant rules are enabled.

Manual-upload limits​

The upload dialog accepts multiple files, but every file must:

  • Be assigned to an instrument.
  • Use an extension permitted for that instrument type.
  • Be no larger than 48 MiB.

For actively growing or large files, use a continuous source so Chipper can process new content incrementally.