opentelemetry-semantic-conventions

Missing APM operations after an OpenTelemetry upgrade are typically caused by telemetry semantic mismatches, where attribute renames or scope breaks prevent Coralogix product surfaces from mapping the incoming data correctly.

To fix blank Database Monitoring rows, you must diagnose telemetry semantic mismatches by mapping your OpenTelemetry instrumentation attributes to the specific Coralogix-supported target fields required for database visibility.

The best way to align OpenTelemetry semantic conventions with Coralogix Infrastructure Explorer is to use a semantic triage checklist to map stable OTel attributes to Coralogix target fields and identify collection topology gaps.

You can identify bridge locations for OpenTelemetry collector pipelines by diagnosing telemetry semantic breaks, checking for incorrect attribute scopes, and mapping stable OTel attributes to Coralogix-supported target fields.

Yes, you can use this skill to troubleshoot empty Coralogix Infrastructure Explorer dashboards by diagnosing whether the issue is caused by attribute renames, scope mismatches, or collection topology gaps in your OpenTelemetry setup.