Need advice about which tool to choose?Ask the StackShare community!
Prometheus vs osquery: What are the differences?
Key Differences between Prometheus and osquery
1. Data Collection and Monitoring Capabilities: Prometheus is primarily designed for monitoring and alerting in a time-series manner, collecting data via pull-based model where clients periodically scrape metrics from service endpoints. On the other hand, osquery is an agent-based tool that enables querying of the underlying operating system, collecting information about system configuration, security settings, and other operational data.
2. Purpose and Scope: Prometheus is specifically built for monitoring distributed systems and microservices, providing robust support for metrics, alerts, and recording rules. In contrast, osquery is more focused on providing visibility and monitoring of individual hosts or machines, allowing detailed querying capabilities for system-level information and threat hunting.
3. Use Case and Flexibility: Prometheus excels in monitoring dynamic environments with auto-discovery capabilities, making it well-suited for cloud-native applications and containerized infrastructures. It offers extensive support for scaling and handling high cardinality data. Conversely, osquery's strength lies in its ability to inspect and monitor a wide range of system attributes across different operating systems, making it more adaptable to varied host-based use cases.
4. Query Language and Data Models: Prometheus Query Language (PromQL) is specifically tailored for time-series data, allowing aggregation, filtering, and transformation of metrics over time. It provides functions to analyze and visualize data for monitoring purposes. In contrast, osquery employs SQL-like syntax with a schema, enabling users to query the system state and log data efficiently, facilitating security investigations and operational insights.
5. Ecosystem and Integrations: Prometheus has a vast ecosystem, with numerous exporters, dashboards, and alerting solutions available, making it easy to integrate with different frameworks and platforms. It also supports exporters that collect data from third-party systems. On the contrary, osquery offers a smaller but growing ecosystem of extensions and integrations, primarily focusing on security-related tools and use cases.
6. Operational Overhead and Resource Consumption: Prometheus requires dedicated resources for data storage and retention, as it keeps a compact, on-disk, and efficient time-series database. It also requires periodic maintenance and management for data compaction and purging. Conversely, osquery's resource consumption is comparatively lower, as it leverages system resources for data collection and presents a smaller operational footprint.
In summary, Prometheus is a powerful monitoring tool designed for time-series data collection in dynamic environments, while osquery specializes in querying and monitoring the state of individual hosts across different operating systems, offering extensive visibility and threat-hunting 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.
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 osquery
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 osquery
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