Pranay Prateek
Maintainer, SigNoz
San Francisco, California, United States
Actions
Pranay is one of the maintainers at SigNoz, an open source APM. He loves working on open source and
observability, and has deep interest in philosophy esp. around Existentialism
He is one of the organisers of OpenTelemetry APAC discussion group meetings & has been speaker in events hosted by Github, Kubernetes Community Days, etc.
Area of Expertise
Topics
OpAMP in Action: User configurable observability pipelines
The current observability pipelines using OpenTelemetry Collector cannot be configured dynamically. This means that the user cannot change the pipeline configuration without restarting the collector. This is a problem for users who want to change the pipeline configuration based on the data they are receiving. For example, a user might want to change the sampling rate of a trace exporter based on the number of traces they are receiving or they might want to parse unstructured logs into structured logs for further processing. This is not possible with the current static pipelines.
In this talk, we'll discuss
- How we use OpAMP to build user configurable observability pipelines.
- The problems we faced with the existing static pipelines and how we leveraged OpAMP to solve them.
- How we exploited the flexibility of OTEL Collector components to build a preview pipeline that allows users to preview their pipeline configuration before deploying it.
- Show all of this in action with a demo
Is OpenTelemetry too complicated to get started?
In this talk I will highlight some of the key issues end users face getting started with OpenTelemetry, and some possible ways to solve for this.
Some common questions we see are:
1. What is the right way to deploy otel collectors for my scale?
2. I have instrumented my applications but I don't see my telemetry data data ( esp. around tracing)
3. Questions around manual instrumentation or any use cases which are not covered by auto instrumentation are tough to get help and guidance on
This is more of an introspective talk on what we can do better as a community and derives from our experience of helping 1000s of users get started with OpenTelemetry.
Observability Diet: Your 5-Step Plan to Trim the Data Fat
Many organizations drown in terabytes of telemetry data but often use only 20% of it.
In this lightning talk, we'll sprint through battle-tested strategies in OpenTelemetry to trim your observability costs without compromising visibility. From intelligent sampling to SDK optimization, learn how to implement a lean observability practice that focuses on signal over noise.
Key Takeaways:
- Sampling : Tail based sampling, head based sampling for traces, probabilistic sampler processor for logs
- Using processors in the Otel collector with granular filtering/dropping of irrelevant attributes - to control volume going out of collector
- Reduce the volumes at the SDKs by controlling what attributes are sent - e.g.control what http.headers are sent
- Visibility on cardinality in time series (and suggestions on what attributes to drop)
- Use `Views` in SDKs to customise aggregation or which attributed are reported in metrics
- Using granular retention settings to reduce observability costs
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top