Learn · Integrations
OpenTelemetry
Send traces from the collector you already run.
Checked against the product on · written for people writing code
Point an existing collector at the platform and every span becomes an event about a watched thing. Your rules then weigh those events the way they weigh any other feed.
Set up the exporter
Add a feed of the OpenTelemetry kind and copy its token.
Point your collector at the platform’s signal paths.
The standard paths are used. No feed id appears in the URL.
Send the token in the Authorization header.
The token resolves which feed the signals belong to.
Add two resource attributes with your collector’s attribute processor.
One names the division that owns the data. The other names the watched-thing type, when the default of sensor is wrong.
Open the feed and read the live tail.
Spans appear within seconds of the collector flushing.
| Attribute | Value | Default |
|---|---|---|
| division id | The slug of the division that owns the data. | The division on the feed. |
| subject type | One of chat, sensor, lead, ticket, or journey. | sensor |
What a span becomes
One span becomes one event. The event carries the span name, its attributes, its timings, and its status. Events about one service group into a story by time window, which is what a rule then reads.
- Does the platform replace my observability tool?
- No. The collector keeps sending to your existing backends. This is one more exporter target.
- What names the watched thing?
- The service name on the span, prefixed by the division and the type.
- What happens to metrics and logs today?
- They are accepted and stored. Processing them the way traces are processed is in build.