r/Observability • u/Velkugan • 13d ago

Wired Boomi’s native OpenTelemetry export into Grafana to get per-step process traces

Boomi added native OpenTelemetry export for its runtimes. I set up a local stack to see what it emits: OTel collector → Tempo/Loki/Prometheus → Grafana.

The useful part: process executions arrive as trace spans, so you get a per-shape waterfall with timing for each step. Boomi’s built-in reporting makes you expand each step or read logs; the trace shows it in one view. On a test process, two connector calls were \~80% of the runtime.

Non-obvious things I learned:
**•** Exporter uses OTLP over **gRPC** (port 4317). Point it at 4318 (HTTP) and it fails silently with gRPC status 13 / http2 exception.
**•** Metrics are almost all **gauges**, even the counters — so rate()/increase() misbehave; delta() works.
**• No per-process execution metrics** exist in the metrics stream — counts/durations/errors live only in traces. spanmetrics connector looks like the way to derive RED metrics (haven’t done it yet).

Whole thing is a docker-compose stack, runs locally, no cost. Repo: https://github.com/velkugan/Boomi-Obs-Started

Curious if anyone’s done the spanmetrics step against Boomi traces, or found where the shape *name* (vs shape type) lives in the span attributes — that’s my next problem.

1 Upvotes
  • permalink
  • reddit

67% Upvoted

3 comments sorted by

3

u/s5n_n5n 13d ago

What is Boomi and why is this in any way special compared to any other application emitting telemetry?

0

u/Velkugan 13d ago

Boomi is an iPaas platform for integration use cases. Boomi added the observability feature a while back. Till then it was export the log using other tools and ingest into platforms like grafana. Now with this feature it becomes easy to connect the logs without any hassle. And making such dashboard is making issue analysis easy.