docs
zipkin-api-example
| docs | zipkin-api-example | |
|---|---|---|
| 6 | 1 | |
| 625 | 9 | |
| 0.3% | - | |
| 8.4 | 10.0 | |
| 16 days ago | over 6 years ago | |
| SCSS | 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.
docs
-
OpenTelemetry in 2023
Prometheus text exposition format is de-facto standard used in monitoring. It would be great building an official observability standard on top it. This format is much easier to debug and understand than OpenTelemetry for metrics. It is also more efficient, e.g. it requires less network bandwidth and less CPU for transfer than Otel for metrics.
[1] https://github.com/prometheus/docs/blob/main/content/docs/in...
-
Kubernetes prometheus metrics for running pods and nodes?
I've set up prometheus to monitor kubernetes metrics by following the prometheus documentation.
-
Minimal, allocation-free OpenMetrics implementation for no-std/embedded Rust
It was added back to Prometheus.
https://github.com/prometheus/docs/blob/main/content/docs/in...
-
What is promeetheus monitoring?
Exporters are third-party tools that send metrics to the Prometheus server. When Prometheus cannot access metrics, it uses exporters. These exporters export metrics from systems and send the metrics to the Prometheus server. There are official and non-official exporters in Prometheus' GitHub organization.
-
Energy monitor exporter?
Now I'm looking for another energy monitor and I'm really struggling to find one! https://github.com/prometheus/docs/blob/main/content/docs/instrumenting/exporters.md
-
Monitoring Rust web application with Prometheus and Grafana
Metrics are exposed in a simple text-based format.
zipkin-api-example
-
OpenTelemetry in 2023
Yes, I really agree, and I've gone through the same pain, but try using the alternatives that claim to be better because they have OpenAPI specifications [1]
The example shows you how to use the swagger tool, parse the OpenAPI spec [2], auto-generate GoLang glue code, call __one__ of those auto-generated functions and log a trace.
However, there is zero documentation, zero other examples, and I'm left scratching my head whether there's even one person in the world using this approach. I eventually ended up just directly using the service APIs [3] via REST calls.
OTEL is painful, but the alternatives are no better :( I really wish there's some interest in this space, since SLO's and SLI measurements are becoming increasingly important.
[1] https://github.com/openzipkin/zipkin-api-example
[2] https://github.com/openzipkin/zipkin-api/blob/master/zipkin2...
[3] https://zipkin.io/zipkin-api/#/
What are some alternatives?
flight-manual.atom.io - 📖 Documentation for Atom, generated by nanoc, hosted by GitHub Pages
aws-otel-lambda - AWS Distro for OpenTelemetry - AWS Lambda
community - OpenTelemetry community content
odigos - Distributed tracing without code changes. 🚀 Instantly monitor any application using OpenTelemetry and eBPF
windows_exporter - Prometheus exporter for Windows machines
opentelemetry-lambda - Create your own Lambda Layer in each OTel language using this starter code. Add the Lambda Layer to your Lamdba Function to get tracing with OpenTelemetry.
rust-prometheus - Prometheus instrumentation library for Rust applications
openobserve - 🚀 10x easier, 🚀 140x lower storage cost, 🚀 high performance, 🚀 petabyte scale - Elasticsearch/Splunk/Datadog alternative for 🚀 (logs, metrics, traces, RUM, Error tracking, Session replay).
terraform-aws-jaeger - Terraform module for Jeager
opentelemetry-js-contrib - OpenTelemetry instrumentation for JavaScript modules
prometheus - The Prometheus monitoring system and time series database.
proposal-explicit-resource-managemen