DEV Community

Sumit Vohra
Sumit Vohra

Posted on

OTEL-COLLECTOR ( issues over short and long term )

Hey community,
I have been using otel-collector for my org ( x Tbs/day ) observability in k8s setup for sometime. Following is my experience. Do you had the same or was it different and how did you overcome it?

Long Term ( 6 months + of using ) :

  1. Poor data-loss detecting capabilities. I have been loosing data but no good way to see that. Agent/collector pods prints error logs but since pipeline doesn't work so it doesn't reach the log-system

  2. No UI to view/monitor my existing connections and pick and drop functionalities

  3. No easy way to inject transformers, for example i need to change format of some data for SIEM/snowflake, drop some log data like cribl, i should be able to do it within otel itself.

Short term ( while setup ) :

  1. No grpc-native load balancer in otel. Horizontal scaling became an issue, as the agent runs on grpc and owing to no native grpc-load balancer directly operating over otel, resulted in oversizing my clusters unnecessarily.

  2. Distributed tracing needs more automation, i had to manually stitch at various places.

Anyone else faced similar issues or others???

Sentry image

See why 4M developers consider Sentry, “not bad.”

Fixing code doesn’t have to be the worst part of your day. Learn how Sentry can help.

Learn more

Top comments (0)

A Workflow Copilot. Tailored to You.

Pieces.app image

Our desktop app, with its intelligent copilot, streamlines coding by generating snippets, extracting code from screenshots, and accelerating problem-solving.

Read the docs

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay