docs
community
docs | community | |
---|---|---|
6 | 7 | |
625 | 700 | |
0.3% | 1.4% | |
8.4 | 9.0 | |
16 days ago | about 12 hours ago | |
SCSS | 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.
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.
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?
flight-manual.atom.io - ๐ Documentation for Atom, generated by nanoc, hosted by GitHub Pages
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.
windows_exporter - Prometheus exporter for Windows machines
trouble-training - FullStack DDD/CQRS with GraphQL workshop including distributed tracing and monitoring. This shows the configuration from React frontend to .Net backend.
rust-prometheus - Prometheus instrumentation library for Rust applications
b3-propagation - Repository that describes and sometimes implements B3 propagation
terraform-aws-jaeger - Terraform module for Jeager
tracetest - ๐ญ Tracetest - Build integration and end-to-end tests in minutes, instead of days, using OpenTelemetry and trace-based testing.
prometheus - The Prometheus monitoring system and time series database.
opentelemetry-proto - OpenTelemetry protocol (OTLP) specification and Protobuf definitions
Grafana - The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
odigos - Distributed tracing without code changes. ๐ Instantly monitor any application using OpenTelemetry and eBPF