agent
opentelemetry-collector
agent | opentelemetry-collector | |
---|---|---|
21 | 16 | |
1,545 | 3,892 | |
2.3% | 2.1% | |
9.9 | 9.9 | |
6 days ago | 2 days ago | |
Go | 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.
agent
-
Ask HN: Best solution for homelab service monitoring?
And has an agent that can be run on the host to monitor it: https://github.com/grafana/agent
- Grafana to sumologic pricing
-
Best unicorn monitoring system?
For example, there are things like https://github.com/grafana/agent
-
Grafana agent JSON Schema
Hey, I would like to lint my agent config in vscode. Did someone know where I can find the agent config JSON schema ? I've searched on https://github.com/grafana/agent and https://grafana.com/docs/agent/latest/ but cant find anything like this ...
-
Monitoring Internet Quality and Speed
Grafana Agent can stream data back to you.
-
Distributed tracing with Envoy, Kuma, Grafana Agent, and Jaeger
At the time, Jaeger did not support OTEL format, which meant we needed our telemetry collector to export spans in Jaeger format. We were able to push this small fix to add a Jaeger exporter on the Agent.
-
Those of you using prometheus as part of your observability stack, what approach did you take to scaling to scrape 25+ clusters, and why? Is Thanos the answer to my problems?
Furthermore, would recommend Grafana Agent OR Prometheus Agent in this case since you probably don't need the Prometheus UI in each Cluster as well as the Alerting stuff that is inside Prometheus. (Mimir will do the ruling stuff for you). Grafana Agent also has an Operator mode if you want to use ServiceMonitor and PodMonitor CustomResources.
- Promtail on windows as service
-
Prometheus Agent Mode, for Metric Forwarding
There were a bunch of alternatives to solve this before, like grafana agent [0], vm agent [1] or opentelemetry collector [2].
[0] - https://github.com/grafana/agent
[1] - https://github.com/VictoriaMetrics/VictoriaMetrics/tree/mast...
[2] - https://github.com/open-telemetry/opentelemetry-collector
-
Shell script to monitor remote VPS?
This might be a reasonable use case for the Grafana Agent. It's basically a Prometheus instance, but without the local storage. Just forwards the data.
opentelemetry-collector
-
OpenTelemetry Collector Anti-Patterns
But how does one monitor a Collector? The OTel Collector already emits metrics for the purposes of its own monitoring. These can then be sent to your Observability backend for monitoring.
-
OpenTelemetry Journey #00 - Introduction to OpenTelemetry
Maybe, you are asking yourself: "But I already had instrumented my applications with vendor-specific libraries and I'm using their agents and monitoring tools, why should I change to OpenTelemetry?". The answer is: maybe you're right and I don't want to encourage you to update the way how you are doing observability in your applications, that's a hard and complex task. But, if you are starting from scratch or you are not happy with your current observability infrastructure, OpenTelemetry is the best choice, independently of the backend telemetry tool that you are using. I would like to invite you to take a look at the number of exporters available in the collector contrib section, if your backend tracing tool is not there, probably it's already using the Open Telemetry Protocol (OTLP) and you will be able to use the core collector. Otherwise, you should consider changing your backend telemetry tool or contributing to the project creating a new exporter.
-
Building an Observability Stack with Docker
To receive OTLP data, you set up the standard otlp receiver to receive data in HTTP or gRPC format. To forward traces and metrics, a batch processor was defined to accumulate data and send it every 100 milliseconds. Then set up a connection to Tempo (in otlp/tempo exporter, with a standard top exporter) and to Prometheus (in prometheus exporter, with a control exporter). A debug exporter also was added to log info on container standard I/O and see how the collector is working.
-
Amazon EKS Monitoring with OpenTelemetry [Step By Step Guide]
You can find more details on advanced configurations here.
-
Go 1.21
> opentelemetry is basically a house of antipatterns
"Look on My Works Ye Mighty and Despair!"
https://github.com/open-telemetry/opentelemetry-collector/tr... -> https://github.com/open-telemetry/opentelemetry-collector-re... ... and then a reasonable person trying to load that mess into their head may ask 'err, what's the difference between go.opentelemetry.io/collector and github.com/open-telemetry/opentelemetry-collector-contrib?'
$ curl -fsS go.opentelemetry.io/collector | grep go-import
-
Options Pattern in Golang
open-telemetry/opentelemetry-collector: OpenTelemetry Collector (github.com)
-
Display CockroachDB metrics in Splunk Dashboards
There are 2 collector types: the core and the contrib. I have used the contrib as it features the splunk_hec exporter.
-
OpenTelemetry Collector on Kubernetes – Part 1
We are setting the deployment to have exactly 1 replica and setting the container CPU and memory limits according to the minimum that was checked for performance in their docs.
-
Observability Mythbusters: How hard is it to get started with OpenTelemetry?
Lightstep ingests data in native OpenTelemetry Protocol (OTLP) format, so we will use the OTLP Exporter. The exporter can be called either otlp or follow the naming format otlp/. We could call it otlp/bob if we wanted to. We're calling our exporter otlp/ls to signal to us that we are using the OTLP exporter to send the data to Lightstep.
-
OpenTelemetry Collector: A Friendly Guide for Devs
Then, we set up a batch processor that batches up the spans together and every 1 second sends the batch forward. In production, you would want more than 1 second, but I set this here to 1 second for instant feedback in Jaeger.
What are some alternatives?
vector - A high-performance observability data pipeline.
go-sql-driver/mysql - Go MySQL Driver is a MySQL driver for Go's (golang) database/sql package
loki - Like Prometheus, but for logs.
GORM - The fantastic ORM library for Golang, aims to be developer friendly
PushProx - Proxy to allow Prometheus to scrape through NAT etc.
jaeger - CNCF Jaeger, a Distributed Tracing Platform
operator - Kubernetes operator for Victoria Metrics
go-ethereum - Go implementation of the Ethereum protocol
thanos - Highly available Prometheus setup with long term storage capabilities. A CNCF Incubating project.
argo-cd - Declarative Continuous Deployment for Kubernetes
helm-charts - Helm charts for VictoriaMetrics, VictoriaLogs and ecosystem
prometheus - The Prometheus monitoring system and time series database.