3 ms·
Yes, this what the people who will curse you out and judge you for not using wide events omits: it will greatly increase storage costs compared to the normal me
by henning 1y ago
Yes, this what the people who will curse you out and judge you for not using wide events omits: it will greatly increase storage costs compared to the normal metrics + traces + sample based logging that is conventional. It has both a benefit and a cost, and the cost part is always omitted.
- valyala 1y agoProperly implemented wide events usually reduce storage costs comparing to typical chaotic logging of everything. It is expected that a single external request leads to exactly one wide event with all the information about this request, which may be needed for further debugging and analytics. See https://jeremymorrell.dev/blog/a-practitioners-guide-to-wide-events/ https://jeremymorrell.dev/blog/a-practitioners-guide-to-wide... .
- edzhelyov 1y agoHow would you add an outgoing request you make to external system in the wide event? For example, I receive a request, in that request I make a HTTP call to http://example.com http://example.com. In tracing that will be a separate span, but how you manage that in a single wide event?
- behemot 1y agoClickHouse is pretty good at compressing the wide events, so it's not that dramatic compared to the benefits of having high-cardinality telemetry. check this out: https://clickhouse.com/blog/optimize-clickhouse-codecs-compression-schema https://clickhouse.com/blog/optimize-clickhouse-codecs-compr...