Need advice about which tool to choose?Ask the StackShare community!
Jaeger vs Prometheus: What are the differences?
Key Differences between Jaeger and Prometheus
Jaeger and Prometheus are both popular monitoring tools used in the field of observability. While they serve similar purposes, there are several key differences between the two:
Data Model: Jaeger focuses on distributed tracing, capturing and analyzing traces of requests as they propagate throughout a distributed system. On the other hand, Prometheus is a time-series-based monitoring system, collecting and storing metrics data over time.
Monitoring Approach: Jaeger provides a more detailed view of request flow in a distributed system, enabling deep performance analysis and troubleshooting. Prometheus, on the other hand, offers a broader scope of monitoring, focusing on metrics and alerting based on thresholds and rules.
Instrumentation: Jaeger requires explicit instrumentation in the code to capture and propagate trace information. Prometheus, on the other hand, relies on a pull-based model where it scrapes metrics from instrumented endpoints.
Data Storage: Jaeger uses a distributed storage backend like Elasticsearch or Cassandra to store highly detailed trace information. Prometheus comes with its own built-in time-series database designed for efficient storage and querying of metrics data.
Query Language: Jaeger provides a query language called Jaeger Query Language (JQL) for retrieving and analyzing trace data. Prometheus uses its own query language called PromQL, specifically designed for querying time-series metrics.
Alerting: Jaeger does not provide built-in support for alerting. Prometheus, on the other hand, has extensive alerting capabilities, supporting alert rules and notifications based on metric thresholds.
In Summary, Jaeger focuses on distributed tracing and provides in-depth analysis of request flow, while Prometheus is a more general monitoring system that collects and stores metrics data over time, with built-in alerting capabilities.
Looking for a tool which can be used for mainly dashboard purposes, but here are the main requirements:
- Must be able to get custom data from AS400,
- Able to display automation test results,
- System monitoring / Nginx API,
- Able to get data from 3rd parties DB.
Grafana is almost solving all the problems, except AS400 and no database to get automation test results.
You can look out for Prometheus Instrumentation (https://prometheus.io/docs/practices/instrumentation/) Client Library available in various languages https://prometheus.io/docs/instrumenting/clientlibs/ to create the custom metric you need for AS4000 and then Grafana can query the newly instrumented metric to show on the dashboard.
Hi, We have a situation, where we are using Prometheus to get system metrics from PCF (Pivotal Cloud Foundry) platform. We send that as time-series data to Cortex via a Prometheus server and built a dashboard using Grafana. There is another pipeline where we need to read metrics from a Linux server using Metricbeat, CPU, memory, and Disk. That will be sent to Elasticsearch and Grafana will pull and show the data in a dashboard.
Is it OK to use Metricbeat for Linux server or can we use Prometheus?
What is the difference in system metrics sent by Metricbeat and Prometheus node exporters?
Regards, Sunil.
If you're already using Prometheus for your system metrics, then it seems like standing up Elasticsearch just for Linux host monitoring is excessive. The node_exporter is probably sufficient if you'e looking for standard system metrics.
Another thing to consider is that Metricbeat / ELK use a push model for metrics delivery, whereas Prometheus pulls metrics from each node it is monitoring. Depending on how you manage your network security, opting for one solution over two may make things simpler.
Hi Sunil! Unfortunately, I don´t have much experience with Metricbeat so I can´t advise on the diffs with Prometheus...for Linux server, I encourage you to use Prometheus node exporter and for PCF, I would recommend using the instana tile (https://www.instana.com/supported-technologies/pivotal-cloud-foundry/). Let me know if you have further questions! Regards Jose
We're looking for a Monitoring and Logging tool. It has to support AWS (mostly 100% serverless, Lambdas, SNS, SQS, API GW, CloudFront, Autora, etc.), as well as Azure and GCP (for now mostly used as pure IaaS, with a lot of cognitive services, and mostly managed DB). Hopefully, something not as expensive as Datadog or New relic, as our SRE team could support the tool inhouse. At the moment, we primarily use CloudWatch for AWS and Pandora for most on-prem.
this is quite affordable and provides what you seem to be looking for. you can see a whole thing about the APM space here https://www.apmexperts.com/observability/ranking-the-observability-offerings/
I worked with Datadog at least one year and my position is that commercial tools like Datadog are the best option to consolidate and analyze your metrics. Obviously, if you can't pay the tool, the best free options are the mix of Prometheus with their Alert Manager and Grafana to visualize (that are complementary not substitutable). But I think that no use a good tool it's finally more expensive that use a not really good implementation of free tools and you will pay also to maintain its.
The objective of this work was to develop a system to monitor the materials of a production line using IoT technology. Currently, the process of monitoring and replacing parts depends on manual services. For this, load cells, microcontroller, Broker MQTT, Telegraf, InfluxDB, and Grafana were used. It was implemented in a workflow that had the function of collecting sensor data, storing it in a database, and visualizing it in the form of weight and quantity. With these developed solutions, he hopes to contribute to the logistics area, in the replacement and control of materials.
Pros of Jaeger
- Easy to install6
- Open Source6
- Feature Rich UI5
- CNCF Project4
Pros of Prometheus
- Powerful easy to use monitoring47
- Flexible query language38
- Dimensional data model32
- Alerts27
- Active and responsive community23
- Extensive integrations22
- Easy to setup19
- Beautiful Model and Query language12
- Easy to extend7
- Nice6
- Written in Go3
- Good for experimentation2
- Easy for monitoring1
Sign up to add or upvote prosMake informed product decisions
Cons of Jaeger
Cons of Prometheus
- Just for metrics12
- Bad UI6
- Needs monitoring to access metrics endpoints6
- Not easy to configure and use4
- Supports only active agents3
- Written in Go2
- TLS is quite difficult to understand2
- Requires multiple applications and tools2
- Single point of failure1
Sign up to add or upvote consMake informed product decisions
What is Jaeger?
What is Prometheus?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Jaeger?
What companies use Prometheus?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Jaeger?
What tools integrate with Prometheus?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+11
+12
+14
+6
+42+26