opentelemetry-collector-co
tracing
opentelemetry-collector-co | tracing | |
---|---|---|
10 | 52 | |
- | 4,958 | |
- | 2.1% | |
- | 7.8 | |
- | 3 days ago | |
Rust | ||
- | MIT License |
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.
opentelemetry-collector-co
-
All you need is Wide Events, not "Metrics, Logs and Traces"
The open telemetry collector does just that. https://github.com/open-telemetry/opentelemetry-collector-co...
-
Migrating to OpenTelemetry
If you are using the prometheus exporter, you can use the transform processor to get specific resource attributes into metric labels.
With the advantage that you get only the specific attributes you want, thus avoiding a cardinality explosion.
https://github.com/open-telemetry/opentelemetry-collector-co...
-
Vendor lock-in is in the small details
The article seems to suggest https://github.com/open-telemetry/opentelemetry-collector-co... was silently killed, yet it appears to have been merged in January, am I missing something?
-
Ask HN: What's Your Opinion on Opentelemetry?
OpenTelemetry is a large suite of software, that supports many use cases. I think you got what you wanted but didn't realised it!
The dedicated executable that you are after is called the OpenTelemtry Collector.
The OpenTelemetry SDK for language of choice should include many exporters, which describe the format and transport mechanism for the traces. The OpenTelemetry Collector can then use an appropriate receiver to ingest those traces.
Here is a file based receiver for the collector:
https://github.com/open-telemetry/opentelemetry-collector-co...
-
OpenTelemetry at Scale: Using Kafka to handle bursty traffic
This arch is how the big players do it at scale (ie. datadog, new relic - the second it passes their edge it lands in a kafka queue). Also otel components lack rate limiting(1) meaning its super easy to overload your backend storage (s3).
Grafana has some posts how they softened the s3 blow with memcached(2,3).
1. https://github.com/open-telemetry/opentelemetry-collector-co...
-
Show HN: HyperDX – open-source dev-friendly Datadog alternative
Ah yeah the easiest way is probably using the OpenTelemetry collector to set up a process to pull your logs out of jounrnald and send them via otel logs to HyperDX (or anywhere else that speaks otel) - the docs might be a bit tricky to go around depending on your familiarity with OpenTelemetry but this is what you'd be looking for:
https://github.com/open-telemetry/opentelemetry-collector-co...
Happy to dive more into the discord too if you'd like!
-
DataDog asked OpenTelemetry contributor to kill pull request
Link to exact comment: https://github.com/open-telemetry/opentelemetry-collector-co...
-
Elastic, Loki and SigNoz – A Perf Benchmark of Open-Source Logging Platforms
What schema does SigNoz use with Clickhouse? The Open Telemetry Collector uses this schema https://github.com/open-telemetry/opentelemetry-collector-co... and I found out that accesing map attributes is much slower (10-50x) compared to regular columns. I expected some slow down but this is too much.
-
Podman: A tool for managing OCI containers and pods
Podman does support docker API so you can use something like the OpenTelemetry Collector to fetch metrics using the docker API and forward them to prometheus.
Collector: https://github.com/open-telemetry/opentelemetry-collector-co...
Docker receiver: https://github.com/open-telemetry/opentelemetry-collector-co...
Prometheus exporters: https://github.com/open-telemetry/opentelemetry-collector-co... and https://github.com/open-telemetry/opentelemetry-collector-co...
tracing
-
Decrusting the tracing crate [video] by Jon Gjengset
The video description is as follows:
In this stream, we peel back the crust on the tracing crate — https://github.com/tokio-rs/tracing/ — and explore its interface, structure, and mechanisms. We talk about spans, events, their attributes and fields, and how to think about them in async code. We also dig into what subscribers are, how they pick up events, and how you can construct your own subscribers through the layer abstraction. For more details about tracing, see https://docs.rs/tracing/latest/tracing/.
-
Vendor lock-in is in the small details
> What's been your biggest issues around ergonomics/amenities for OpenTelemetry?
I can't speak generally, but in the Rust ecosystem the various crates don't play well together. Here's one example: <https://github.com/tokio-rs/tracing/issues/2648> There are four crates involved (tracing-attributes, tracing-opentelemetry, opentelemetry, and opentelemetry-datadog) and none of them fit properly into any of the others.
-
Grimoire - A recipe management application.
The tracing (logging) mechanism in an asynchronous codebase (tracing).
-
How easy is it to swap out your async runtime?
Tracing is Tokio's alternative for async code.
-
Hey Rustaceans! Got a question? Ask here (27/2023)!
At a technical level, in Rust, both [tracing]https://crates.io/crates/tracing) and log are entire ecosystems (though for the latter at least there's also third party logging frameworks), and there's at least a bridge from log to tracing.
-
How can I write a tracing subscriber that saves to a database?
I am using https://github.com/tokio-rs/tracing for logging purposes in my application. I would like to develop a feature wherein logs should be saved to a database table (via sea-orm). Something similar is this, but it does not solve my needs fully.
-
A locking war story
I've used the tracing infrastructure with tracing_flame to profile some hot paths in async code: https://github.com/tokio-rs/tracing/tree/master/tracing-flame
-
I was wrong about rust
Oh nice! IIRC when I checked, it was the Unicode tables that smashed the code size. I recently hit the same issue with the tracing crate, where a crate feature (for env var filtering) pulled in regex and my binary was suddenly 1MB bigger.
-
Debugging and profiling embedded applications.
I know about tools such as tracing, jaeger or tracy. While having a complete tracing could be a potential solution, these tools don't work with no_std.
-
Custom Axum Logging for Routes?
tracing by itself only outputs log data, you need to consume them in a subscriber, the tracing-subscriber crate exists for this. (example)
What are some alternatives?
podman-compose - a script to run docker-compose.yml using podman
log4rs - A highly configurable logging framework for Rust
cockpit-podman - Cockpit UI for podman containers
slog - Structured, contextual, extensible, composable logging for Rust
traefik - The Cloud Native Application Proxy
env_logger - A logging implementation for `log` which is configured via an environment variable.
logs-benchmark - Logs performance benchmark repo: Comparing Elastic, Loki and SigNoz
log - Logging implementation for Rust
dd-trace-py - Datadog Python APM Client
opentelemetry-rust - The Rust OpenTelemetry implementation
opentelemetry-collector-contrib - Contrib repository for the OpenTelemetry Collector
vector - A high-performance observability data pipeline.