Bài viết mới chia sẻ 3 mẫu triển khai OpenTelemetry Collector ở quy mô lớn: Load balancer, Multi-cluster và Per-signal. Kèm theo lời khuyên hữu ích để chọn mẫu phù hợp với kiến trúc của bạn!
#OpenTelemetry #OTelCollector #Deployment #Scalability #CôngNghệ #TriểnKhai
⏳ Haven’t shared your experience with the OpenTelemetry Collector yet? There’s still time!
Our follow-up survey is still open, and we’re inviting all Collector users to help us understand:
- What’s improved
- What still needs work
- How we can better support your use cases
Even if you responded to the first survey, we’d love your updated perspective.
📝 Take 5 minutes and tell us what’s up → https://buff.ly/Ghoh5H9
Exposing #OTelCollector in #Kubernetes with #GatewayAPI & #mTLS
https://opentelemetry.io/blog/2025/expose-otel-collector-gateway-api/
The goal of this blog post is to demonstrate how you can expose an OpenTelemetry (OTel) Collector running inside Kubernetes to the outside world securely, using the Kubernetes Gateway API and mutual TLS (mTLS) for authentication and encryption. As observability becomes increasingly critical in modern distributed systems, centralizing telemetry data via OTel Collectors deployed in one or many Kubernetes clusters is common practice. Often, services or agents running outside your Kubernetes cluster need to send data to these Collectors. Exposing internal services requires careful consideration of security and standardization. This is where the Kubernetes Gateway API and mTLS shine.
Last week's #OTelCollector user feedback session is now available on the #OTel YouTube channel, featuring Iris Dyrmishi, Greg Eales, Juraj Michálek, and Joel Verezhak. Moderated by Yours Truly. 👇
My latest post on the #OTel blog. If you're using the #OTelCollector or are looking into using it, then this post is for you!
https://opentelemetry.io/blog/2024/otel-collector-anti-patterns/
The OpenTelemetry Collector is one of my favorite OpenTelemetry (OTel) components. It’s a flexible and powerful data pipeline which allows you to ingest OTel data from one or more sources, transform it (including batching, filtering, and masking), and export it to one or more observability backends for analysis. It’s vendor-neutral. It’s extensible, meaning that you can create your own custom components for it. What’s there not to like? Unfortunately, as it happens with many tools out there, it is also very easy to fall into some bad habits.
Are you using the #OTelCollector or are considering using it in your organization? Then check out the latest post on the #OTel blog on OTel Collector Anti Patterns!
The OpenTelemetry Collector is one of my favorite OpenTelemetry (OTel) components. It’s a flexible and powerful data pipeline which allows you to ingest OTel data from one or more sources, transform it (including batching, filtering, and masking), and export it to one or more observability backends for analysis. It’s vendor-neutral. It’s extensible, meaning that you can create your own custom components for it. What’s there not to like? Unfortunately, as it happens with many tools out there, it is also very easy to fall into some bad habits.
Want to learn about how other end users implement and use #OTelCollector? Then check out this week's #OTel Collector End User feedback panel. The goal is to help us inform project priorities for the Collector – we'll be asking our four panelists questions such as, how are you primarily using the Collector? What are your pain points, and what capabilities would you like to see?
When: Thursday, Feb 29 13:00 EST/10:00 PST
Calendar Link: https://buff.ly/49sQjSm
Does anyone know how the #otelcollector httpsetterextension works?
I am trying to forward a header I send with my logs from #csharp
https://stackoverflow.com/questions/77943760/forwarding-a-http-header
Reddit Tech VN Bot
Tomas Ekeli
OpenTelemetry
Nicolas Fränkel 🇪🇺🇺🇦🇬🇪
Adriana Villela 🇧🇷🇨🇦
Morten Toudahl
C S