Re:OpenTelemetry at Scale: Using Kafka to handle bursty traffic
by ankitnayan on Monday October 23, 2023 @01:19AM
(#37981908)
Caching is to improve read performance whereas Kafka is used to handle ingest volume. I couldn't correlate the Grafana articles shared
Re:OpenTelemetry at Scale: Using Kafka to handle bursty traffic
by blinded on Monday October 23, 2023 @11:42AM
(#37987316)
Yep! Should have made that more clear. Brought it up as an example of other parts of the system that require scaling.
Re:OpenTelemetry at Scale: Using Kafka to handle bursty traffic
by wardb on Monday October 23, 2023 @01:59AM
(#37982093)
Grafana Labs employee here => On the linked articles: I'm not aware of any caching being used in the writing data to S3 part of the pipeline other then some time based/volume based buffering at the ingester microservices before writing the chunks of data to object storage.
The linked Loki caching docs/articles are for optimising the read access patterns of S3/object storage, not for writes.
Re:OpenTelemetry at Scale: Using Kafka to handle bursty traffic
by blinded on Monday October 23, 2023 @02:49PM
(#37989921)
Yes. Thanks for the reply!
Grafana has some posts how they softened the s3 blow with memcached(2,3).
1. https://github.com/open-telemetry/opentelemetry-collector-co... 2. https://grafana.com/docs/loki/latest/operations/caching/ 3. https://grafana.com/blog/2023/08/23/how-we-scaled-grafana-cl...
I know the post is about telemetry data and my comments on grafana are logs, but the arch bits still apply.