odigos
b3-propagation
odigos | b3-propagation | |
---|---|---|
40 | 3 | |
3,024 | 517 | |
1.2% | 0.8% | |
9.8 | 2.7 | |
5 days ago | 3 months ago | |
Go | ||
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
odigos
-
Setup odigos in Ubuntu
Welcome 👋 to this blog. Did you want to use odigos on your Ubuntu machine but don't know how to start? Then this blog will definitely help you and it also helps you to understand the basic aspect of the odigos project.
- Open Source Distributed Tracing Through eBPF
- Odigos v0.1.82 - Open-source instant distributed tracing without code changes
- Odigos – Language Agnostic Auto-Instrumentation
-
OpenTelemetry in 2023
Disclaimer: I am one of the maintainers
Many comments complain about the complexity of using OpenTelemetry, I recommend checking out Odigos, an open-source project which makes working with OpenTelemetry much easier: https://github.com/keyval-dev/odigos
We combine OpenTelemetry and eBPF to instantly generate distributed traces without any code changes.
-
OpenObserve: Elasticsearch/Datadog alternative in Rust.. 140x lower storage cost
Check it out here: https://github.com/keyval-dev/odigos
- Odigos v0.1.5 - Managing OpenTelemetry using Kubernetes labels
-
Instantly Generate and Send OpenTelemetry data to AWS S3
Hi, sure here is the link to Odigos: https://github.com/keyval-dev/odigos We do not replace Grafana or any other monitoring vendor. We build them a better pipeline with higher quality signals (distributed tracing). They still do the visualization, it will just display better information.
-
Automatic Instrumentation As A Kubernetes Virtual Device
Check out mor about Odigos, our open source project at https://github.com/keyval-dev/odigos
- Extending Containers with Kubernetes Device Plugin
b3-propagation
-
OpenTelemetry in 2023
I've been playing with OTEL for a while, with a few backends like Jaeger and Zipkin, and am trying to figure out a way to perform end to end timing measurements across a graph of services triggered by any of several events.
Consider this scenario: There is a collection of services that talk to one another, and not all use HTTP. Say agent A0 makes a connection to agent A1, this is observed by service S0 which triggers service S1 to make calls to S2 and S3, which propagate elsewhere and return answers.
If we limit the scope of this problem to services explicitly making HTTP calls to other services, we can easily use the Propagators API [1] and use X-B3 headers [2] to propagate the trace context (trace ID, span ID, parent span ID) across this graph, from the origin through to the destination and back. This allows me to query the metrics collector (Jaeger or Zipkin) using this trace ID, look at the timestamps originating at the various services and do a T_end - T_start to determine the overall time taken by one call for a round trip across all the related services.
However, this breaks when a subset of these functions cannot propagate the B3 trace IDs for various reasons (e.g., a service is watching a specific state and acts when the state changes). I've been looking into OTEL and other related non-OTEL ways to capture metrics, but it appears there's not much research into this area though it does not seem like a unique or new problem.
Has anyone here looked at this scenario, and have you had any luck with OTEL or other mechanisms to get results?
[1] https://opentelemetry.io/docs/specs/otel/context/api-propaga...
[2] https://github.com/openzipkin/b3-propagation
[3] https://www.w3.org/TR/trace-context/
-
OpenTelemetry and Istio: Everything you need to know
(Note that OpenTelemetry uses, by default, the W3C context propagation specification, while Istio uses the B3 context propagation specification – this can be modified).
-
Spring Cloud Sleuth in action
The default format for context propagation is B3 so we use headers X-B3-TraceId and X-B3-SpanId
What are some alternatives?
opentelemetry-js - OpenTelemetry JavaScript Client
trace-context-w3c - W3C Trace Context purpose of and what kind of problem it came to solve.
openobserve-chart - Simplified Helm chart for single-node OpenObserve
zipkin - Zipkin is a distributed tracing system
openobserve - 🚀 10x easier, 🚀 140x lower storage cost, 🚀 high performance, 🚀 petabyte scale - Elasticsearch/Splunk/Datadog alternative for 🚀 (logs, metrics, traces, RUM, Error tracking, Session replay).
spring-cloud-sleuth-in-action - 🍀 Spring Cloud Sleuth in Action
opentelemetry-java-instrumentation - OpenTelemetry auto-instrumentation and instrumentation libraries for Java
community - OpenTelemetry community content
opentelemetry-proto - OpenTelemetry protocol (OTLP) specification and Protobuf definitions
oteps - OpenTelemetry Enhancement Proposals
skywalking - APM, Application Performance Monitoring System
terraform-aws-jaeger - Terraform module for Jeager