Connect logs to Chipper
Chipper passively ingests instrument and system logs. It does not change instrument control software or validated records.
Every continuous log source is linked to one instrument so files, runs, methods, events, and alerts keep the right context.
Choose a connection path
| Path | Best for | Start in Chipper |
|---|---|---|
| Agent → Chipper cloud | A Windows instrument PC and the simplest managed route. | Configure → Log Sources → New log source |
| Existing cloud storage | Logs already in AWS S3, Azure Blob Storage, or Google Cloud Storage. | Configure → Log Sources → New log source |
| Standalone agent → your cloud | A collector writing to customer-owned AWS, Azure, or Google Cloud storage. | Configure → Log Sources → New log source |
| Manual upload | Historical analysis, a format check, or a one-time test. | Investigate → Log Files → Upload Files |
The in-app wizard guides the selected route and keeps a draft if you leave before finishing.
Agent → Chipper cloud
Use the Chipper Log Collector to watch specific local file patterns on a Windows PC. The wizard creates an enrollment command, waits for the collector to check in, and then asks which local logs to watch.
This route uses a Chipper-managed landing path, so the normal setup does not require customer cloud credentials.
Existing cloud storage
Choose the provider, location, prefix, and read credentials. The wizard tests access where an automated check is available.
Then choose:
- Instant import: the bucket or container sends an event when a file changes, so ingestion begins promptly.
- Scheduled import: Chipper checks the source once per hour.
Use a prefix that identifies one instrument and does not overlap another source in the same location.
Provider guides:
Standalone agent → your cloud
This route uses the same Windows collector, but its local configuration writes into customer-owned storage. Chipper then reads the logs from that location using the credentials and import mode configured in the wizard.
Use this route when data-governance policy requires the first cloud copy to land in infrastructure your organization owns.
Manual upload
Use Manual Log Upload for representative or historical files. Each file must use an extension permitted for the selected instrument type and be no larger than 48 MiB.
Verify the connection
- Open Configure → Log Sources and confirm the source is active.
- Open the source to review its last import and recent failures.
- Open Investigate → Log Files and wait for a new file to reach Processed.
- Review the file's instrument, methods, runs, events, and alerts.