Need advice about which tool to choose?Ask the StackShare community!
Prometheus vs SignalFx: What are the differences?
1. Scalability and Performance:
Prometheus is specifically designed to handle high volumes of time series data, making it a highly scalable and efficient monitoring solution. It uses a pull-based model where each Prometheus server individually collects data from various targets. In contrast, SignalFx employs a push-based model, where agents send data to SignalFx's collectors. This approach allows Prometheus to handle larger data volumes and ensures better performance for scaling up monitoring infrastructure.
2. Data Collection and Query Language:
Prometheus uses a flexible and powerful query language called PromQL, which allows users to perform complex aggregations and analysis on the collected data. It provides advanced functions for filtering, grouping, and transforming time series data. On the other hand, SignalFx utilizes a query language called SignalFlow, which enables real-time analysis and anomaly detection. It includes features like real-time aggregations and anomaly detection functions, making it suitable for complex streaming data analysis.
3. Alerting and Notification:
Prometheus offers built-in alerting capabilities, allowing users to define alert rules based on specified conditions. When triggered, Prometheus can send alerts to various notification channels like email, webhook, or integration with third-party systems like PagerDuty. SignalFx also provides alerting functionality with real-time, dynamic thresholds and anomaly detection. It supports various notification channels for sending alerts, including integrations with collaboration platforms like Slack and PagerDuty.
4. Integrations and Ecosystem:
Prometheus has a vast ecosystem with a wide range of integrations available for monitoring various systems and service providers. It provides extensive support for exporters, ensuring compatibility with various technologies. SignalFx also offers a range of integrations, providing monitoring capabilities for different services and platforms. However, Prometheus has a larger community and an extensive ecosystem of exporters, making it more versatile and adaptable to different environments.
5. Architecture and Storage:
Prometheus follows a single-server architecture, where each Prometheus server stores its time series data locally. This approach simplifies deployment and reduces complexity. SignalFx, on the other hand, uses a distributed architecture, with data collected and stored in a cloud-based service. It offers a more scalable and fault-tolerant solution for large-scale deployments but may require additional configuration and setup.
6. Pricing and Cost:
Prometheus provides an open-source monitoring solution without any licensing costs, making it highly cost-effective for organizations. However, it requires self-hosting and maintenance. SignalFx, being a commercial solution, offers additional features and support options but comes with a subscription-based pricing model. The pricing depends on the data volume and the level of support desired.
In Summary, Prometheus excels in scalability and performance, offers a flexible query language (PromQL), provides built-in alerting, has a vast integrations ecosystem, follows a simple single-server architecture, and is a cost-effective, open-source solution. SignalFx offers real-time analysis with SignalFlow, utilizes a push-based data collection approach, provides enterprise-level alerting with multiple notification channels, has a range of integrations, follows a distributed architecture, and offers a subscription-based pricing model.
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.
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.
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/
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
Pros of SignalFx
- High cardinality5
- Scalability5
- World class customer support4
- Easy to install4
- Fastest alerts4
Sign up to add or upvote prosMake informed product decisions
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