Skip to main content

FAQ & Troubleshooting

I instrumented my service, but nothing shows up in the dashboard​

Work through these in order:

  1. Check your API key. Make sure it hasn't been disabled or deleted under API Keys, and that you copied the full secret.
  2. Check where telemetry is going. If you're using the event runtime's automatic wiring, confirm MIDIL_TELEMETRY_SINK is set to http (it defaults to stdout, which only logs locally). See Configuration.
  3. Check network reachability. Your service needs outbound access to Observatory's API URL.
  4. Give it a moment. New events usually appear within seconds, but a slow network or a large backlog can add a short delay.

Do I have to instrument every service at once?​

No. Start with one consumer or producer and you'll see it immediately in Overview. Add more services over time. The Trace Graph shows exactly where a trace passes through a service that isn't instrumented yet, so you always know what to add next.

What brokers are supported?​

For the zero-refactor path (ConsumerObserver/ProducerObserver), any broker works. The broker name is just a label you choose, so it fits Kafka, RabbitMQ, SQS, SNS, Redis, or a webhook. The built-in event runtime ships first-class SQS and Redis support directly. See Installation.

Why is a consumer showing as "down"?​

A consumer is marked down when Observatory hasn't seen any activity from it recently. Check that the service is actually running and that it can still reach Observatory. A temporarily unreachable service will recover on its own once it reports again.

A duplicate event wasn't caught, why not?​

Idempotency only catches a duplicate if the same idempotency key is used across every delivery of that logical event. If your key is derived from something that changes per delivery (a fresh message ID, a timestamp), two deliveries of "the same" event won't look identical to the store. See Idempotency & duplicates for how to pick a key, and the Idempotency Center to check current coverage.

Can I replay dead-lettered events?​

Not yet, this is coming soon. In the meantime, use the DLQ Center to see what's failing and fix the underlying issue. A fixed consumer will process new deliveries normally.

My API key leaked. What's the blast radius?​

Rotate or disable it immediately from API Keys. A key can only write telemetry and read consumer control state for your organization. It has no access to the dashboard, billing, members, or settings, so a leaked key can't be used to change anything about your account.

Is there a Node.js / Go / other language SDK?​

Not yet. Python (pymidil) is the only SDK available today. More languages are planned. See SDKs for what's coming.

How do I get my team into my organization?​

See Members & Invitations to invite people directly, or Single Sign-On to have your team join automatically through your identity provider.