b3-propagation
community
b3-propagation | community | |
---|---|---|
3 | 7 | |
518 | 701 | |
1.0% | 2.3% | |
2.7 | 9.0 | |
3 months ago | 3 days ago | |
Python | ||
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.
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
community
-
All you need is Wide Events, not "Metrics, Logs and Traces"
otel is working on their events spec https://github.com/open-telemetry/community/issues/1688
- Open-Telemetry Donation Proposal: Continuous Profiling Agent
- Elastic offers donation of profiling agent to OpenTelemetry project
-
OpenTelemetry in 2023
1. Agreed. It's the sink and the house attached to it, and the docs are thin and confusing as a result.
2. I had a similar experience to you. I wanted to implement a simple heartbeat in our app to get an idea of usage numbers. This is surprisingly not possible, which greatly confuses me given the name of the project. The low engagement on my question put me off and I abandoned my OpenTelemetry planning completely. [1][2]
[1] https://github.com/open-telemetry/community/discussions/1598
- Decision about public video recordings
-
Frontend Overhaul of OTel Demo: Go to Next.js
One of the OpenTelemetry Project's many Special Interest Groups (SIG) is the OpenTelemetry Community Demo SIG which gives support to a set of instrumented backend microservices and a web frontend app that are primarily used to showcase how to instrument a distributed system using OpenTelemetry. The application's main focus is to demonstrate the implementation process to instrument an application no matter what programming language, platform, or operating system your team is using, as well as providing different approaching techniques (automatic and manual instrumentation, metrics, baggage). All of this while following the standards and conventions defined by the official OpenTelemetry Documentation. More about the specific requirements can be found here. At Tracetest, we have always focused on becoming part of and embracing the OpenTelemetry community. One of our goals this summer was to get more involved with a core OpenTelemetry project where we could provide a meaningful contribution. The OTel demo became the best match for achieving that goal as it would not only help the community, but we at Tracetest needed a good example to test and showcase what can be done with our tool. During the version 0.7 project cycle, we created two specific tickets to get us closer to the community and start looking for things to pick up:
- community/mission-vision-values.md at main ยท open-telemetry/community
What are some alternatives?
trace-context-w3c - W3C Trace Context purpose of and what kind of problem it came to solve.
Airline-Microservices - Airline Microservice is a simple Airline application for online reserving flight ticket. This application based on different software architecture and technologies like .Net Core, CQRS, DDD, Vertical Slice Architecture, Docker, kubernetes, tye, masstransit, RabbitMQ, Grpc, yarp reverse proxy, Identity Server, Redis, SqlServer, Entity Framework Core, Event Sourcing and different level of testing.
zipkin - Zipkin is a distributed tracing system
trouble-training - FullStack DDD/CQRS with GraphQL workshop including distributed tracing and monitoring. This shows the configuration from React frontend to .Net backend.
spring-cloud-sleuth-in-action - ๐ Spring Cloud Sleuth in Action
docs - Prometheus documentation: content and static site generator
odigos - Distributed tracing without code changes. ๐ Instantly monitor any application using OpenTelemetry and eBPF
tracetest - ๐ญ Tracetest - Build integration and end-to-end tests in minutes, instead of days, using OpenTelemetry and trace-based testing.
oteps - OpenTelemetry Enhancement Proposals
opentelemetry-proto - OpenTelemetry protocol (OTLP) specification and Protobuf definitions
terraform-aws-jaeger - Terraform module for Jeager