Troubleshooting

Tip

Opening a support request? File it in the OpenSight Customer Portal and attach a support bundle — a redacted ZIP of your server’s state and recent logs — so support can diagnose without a round of follow-up questions. LinkMesh support has the hours and first-response times.

By symptom

Collectors

• A collector won’t connect or won’t enrol — TLS/SAN mismatches, rejected or reused tokens, proxy handshake failures → Enrollment troubleshooting
• A collector shows 0 throughput / 0 CPU / 0 memory / 0 uptime, but data is arriving at your destination → Self-telemetry troubleshooting. If every collector reads zero, start at Check 0: is externalUrl set?

Configuration

• You saved a change and the collector is still running the old config — pipeline edits that never get pushed, rejected configs, silent generation failures → Config not applying after save
• The dry-run panel rejects your OTTL expression — reading the parse error, the six shapes it takes, and what each one means → Dry-run rejected my OTTL expression

Data flow

• A destination receives nothing, or an edge on the canvas reads zero — check whether the numbers are wrong or the data is: is throughput working on only some edges? and numbers are zero but data is arriving
• A processor is in the chain but nothing changes — verify the rule against a realistic record in the preview workspace, then see the config applied but the behaviour didn’t change

Before you file a support request

1. Generate a support bundle — it carries the server state and recent logs, already redacted.
2. Note the collector’s Events tab around the time of the problem. config_rejected, config_rolled_back, config_drift_detected, and config_applied carry the collector’s own error text, which is usually the diagnosis.
3. Check Compatibility & supported versions — a runtime outside the supported range is worth ruling out first.