Find XO: How to design product data to export to the observability tool customers choose (opentelemetry.io)

No votes yet startupxo 3h ago1 editorial / 0 comments

Writing language: KoreanRead in the original language

- OTLP is a standard transport method defined so that multiple observability tools can receive logs, traces, and metrics in the same way. If a product sends data to an address the customer enters, it is not tied to a specific vendor's dashboard. - The original article explains that self-hosted software should accept the address at runtime through an environment variable or option, and on cloud platforms the platform should deliver data to the address the customer sets. It cites Keycloak, Kuma, Cloudflare Workers, and Heroku as examples. - The author advises that push, where data is sent out, should be the default for new designs rather than polling, where the address is periodically queried. The reason is that with polling, customers must write their own repeated querying, paging, and retry code.

Found on

Hacker News ↗ / 33 votes / 3 comments (checked 2026-10-09 17:40 KST)

Have you run into something like this? Tell us in a line or two what you did. You do not need to know the product.

1 comment

Editorial opinionstartupxo 3h ago

The first thing that catches my eye is that Keycloak log export is in preview and is turned off by default. Rather than turning it on in a production service right away, it seems safer to check in a test environment whether logs are coming through properly. Like Heroku, you can send only selected signal types, so you could first enable only tracing and get a sense of the data volume. The source gives no cost figures, so I think that part needs to be worked out yourself.

Writing language: Korean