prom_ex
agent
Our great sponsors
prom_ex | agent | |
---|---|---|
1 | 21 | |
566 | 1,543 | |
- | 4.6% | |
5.1 | 9.9 | |
about 1 month ago | 7 days ago | |
Elixir | Go | |
MIT License | 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.
prom_ex
-
Monitoring Elixir Apps on Fly.io With Prometheus and PromEx
This post is about another cool Fly.io feature --- built-in Prometheus metrics --- and how easy it is to take advantage of them in an Elixir application. I wrote and maintain an Elixir library, PromEx, that makes it a snap to export all sorts of metrics from your Elixir applications and get them on dashboards in Grafana. Let's explore some of the concepts surrounding Prometheus and see how we can leverage the Fly.io monitoring tools in an Elixir application to get slick looking dashboards like this one:
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.
What are some alternatives?
prometheus.ex - Prometheus.io Elixir client
vector - A high-performance observability data pipeline.
elixir_prom_ex_example
loki - Like Prometheus, but for logs.
prometheus-ecto - Prometheus.io collector for Elixir.Ecto
PushProx - Proxy to allow Prometheus to scrape through NAT etc.
Alchemetrics - Elixir metrics reporter and collector
operator - Kubernetes operator for Victoria Metrics
grafana - Run Grafana on Fly
thanos - Highly available Prometheus setup with long term storage capabilities. A CNCF Incubating project.
instruments - Simple and Fast metrics for Elixir
helm-charts - Helm charts for VictoriaMetrics, VictoriaLogs and ecosystem