Need advice about which tool to choose?Ask the StackShare community!
Observium vs Prometheus: What are the differences?
Key Differences between Observium and Prometheus
Observium and Prometheus are two popular monitoring tools used in IT infrastructure management. While both provide valuable insights into system performance, there are key differences that set them apart.
Architecture: Observium is built using a traditional client-server architecture model. It relies on a centralized server that collects data from various devices and agents. On the other hand, Prometheus follows a decentralized architecture where each target device exposes metrics directly to the Prometheus server, allowing for a more flexible and scalable monitoring approach.
Data Collection: Observium primarily focuses on collecting data via SNMP (Simple Network Management Protocol) and utilizes polling techniques to gather information from monitored devices. Prometheus, on the other hand, adopts a pull-based model where it scrapes metrics from specific endpoints exposed by each target device. This approach ensures more efficient data collection and reduces network overhead.
Data Storage: Observium uses a MySQL or MariaDB database to store and manage collected data. It organizes information in a predefined schema, allowing for easy querying and analysis. In contrast, Prometheus operates on its proprietary time-series database capable of handling vast amounts of metrics and timestamps efficiently. This database is optimized for storing and querying time-series data, offering advanced querying capabilities like label-based filtering.
Alerting and Notification: Observium provides a useful alerting system that allows users to define threshold alerts and receive notifications when specific conditions are met. Its notification system supports various methods such as email, SMS, and SNMP traps. Prometheus, on the other hand, comes with a more extensive alerting system known as Prometheus Alertmanager. It offers advanced features like deduplication, grouping, and silencing of alerts, empowering users to manage and process alerts more efficiently.
Ecosystem and Integration: Observium is a feature-rich tool with out-of-the-box support for a wide range of network devices and vendors. It offers an extensive set of integrations enabling monitoring across different technologies. Prometheus, on the other hand, has a thriving community-driven ecosystem. It offers a vast collection of exporters that can gather metrics from various sources, making it highly versatile and suitable for monitoring diverse applications and systems.
Scalability: Observium is designed to handle small to medium-sized networks and can efficiently collect and process data within that range. However, scaling Observium for large-scale deployments can be challenging due to its architecture and database limitations. Prometheus, on the other hand, is highly scalable and can handle monitoring requirements at any scale. Its distributed architecture and efficient data storage make it suitable for monitoring large deployments and high-traffic environments.
In Summary, Observium and Prometheus differ in terms of architecture, data collection methods, data storage, alerting capabilities, ecosystem and integration support, and scalability. Choose Observium for its centralized approach, support for SNMP, and easy setup, while Prometheus offers a decentralized architecture, pull-based model, and scalability for monitoring diverse systems and applications.
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.
Pros of Observium
- Modern Graphs1
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 Observium
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