Observability
Operational dashboards, application traces, monitoring and alerting.
21 listings, including 21 from other publishers. Entries cover the deployment options documented on their individual pages.
Read this page as JSON or Markdown.
Watch this category with RSS · Build a requirements shortlist
Deployment comparison
| Listing | Documented clouds | Deployment and infrastructure | Licensing | Installation | Operations and limitations |
|---|---|---|---|---|---|
| AVEVA PI System (BYOL) | AWS | Customer-operated Servers / containers | Commercial Only Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. | Package / binary installer | Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.Scope and evidenceThe reviewed AWS Guidance includes Outposts for core collection/historian components; it is not a region-only VM installation. PI component versions and licences are separate. Industrial telemetry does not itself supply environmental-compliance document management.
Cloud evidence reviewed 2026-11-19 |
| Cloud Carbon Footprint | Google Cloud | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. | Application platform deployment | Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.Scope and evidenceThe named hosting path is Google App Engine; reading AWS/Azure billing does not establish app deployment there. Estimates and dashboards are not audited emissions or regulatory-compliance certifications. The moving latest release tag is not an immutable application version.
Cloud evidence reviewed 2026-11-19 |
| Coroot Community Edition | AWS, Azure, Google Cloud, Oracle Cloud | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0 for Coroot Community Edition. Enterprise Edition has separate subscription terms. | Install the Coroot Operator and Community Edition Helm chart on the customer's Kubernetes cluster. | The customer manages the operator, image versions, privileged node-agent permissions, storage capacity, telemetry retention, backup and recovery, and access to the UI.Scope and evidenceThe node agent requires privileged access for eBPF and host inspection, and upstream describes AWS Fargate support as basic. Anonymous usage statistics are enabled by default and can be disabled. The operator updates unpinned Coroot component images automatically. Native SAML/OIDC SSO is Enterprise-only. The Coroot server v1.29.4, Community chart 0.3.3 and operator chart 0.10.8 are separate version tracks; inspect and pin each required image.
Cloud evidence reviewed 2026-11-20 |
| Datadog BYOC Logs | AWS, Azure, Google Cloud | Customer-operated · vendor control plane Servers / containers | Commercial Only Commercial Datadog software and service. Confirm BYOC Logs activation and commercial terms with the account team. | Install the BYOC Logs engine and Observability Pipelines Worker with Helm. An operator-managed installation is documented on Amazon EKS. | The customer provisions and sizes the cluster, manages storage, database, IAM and network connectivity, and applies validated engine and Worker version pairs. Datadog maintains the hosted UI.Scope and evidenceLog ingestion, indexing and storage run in the customer's account. Matching query results travel to Datadog for display. The default connection is outbound from searcher pods to Datadog. Confirm service-site availability and account activation. A Docker path is documented for local evaluation. Docker is evaluation-only, and the Operator path is EKS-only. Engine v0.1.36/chart 0.6.0 needs the documented StatefulSet policy migration on existing clusters. Hosted Datadog SSO/SCIM and compliance boundaries remain distinct from the customer engine.
Cloud evidence reviewed 2026-11-20 |
| Elastic Cloud Enterprise | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial Elastic Cloud Enterprise license required after the trial. | Official ECE installation script on prepared AWS, Azure or Google Cloud Linux hosts | Customer manages cloud instances, Linux and container runtime compatibility, XFS storage, networking, DNS, certificates, host maintenance, capacity, backups, upgrades and licensing.Scope and evidenceThis entry covers Elastic Cloud Enterprise, not Elastic Cloud Hosted or Elastic Cloud Serverless. ECE requires supported Linux and container-engine combinations, dedicated storage planning and coordinated host maintenance; automatic cloud VM patching can disrupt the platform. Elastic Cloud Enterprise 3.8.6 and 4.2.1 fix seven platform-role, retained credential and CA key, cross-deployment symlink, role-token, and platform-setting issues. Certificate-rotation users must complete the documented cleanup after upgrade, and operators should review or revoke persistent role tokens. Elastic's CVE-2026-114938 advisory states Elasticsearch 7.17.3 and later can be affected on x86-64 AVX512_VBMI CPUs. Authenticated read access can permit RCE and unauthenticated access can cause denial of service. Planned ECE 4.2.2 and 3.8.7 were not yet released at review time; until fixed images are available, apply -XX:-UseBASE64Intrinsics, restart every deployment and follow Elastic's rollout guidance.
Cloud evidence reviewed 2026-11-15 |
| Elastic Cloud on Kubernetes | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Source Available Elastic License 2.0 distribution with free Basic capabilities; Enterprise licensing unlocks additional features and support. | Official ECK Helm chart or Kubernetes manifests on EKS, AKS or GKE | Customer manages Kubernetes, storage, resource sizing, security, snapshots, upgrades and availability; Elastic licensing controls advanced features and support.Scope and evidenceThis entry covers self-managed Elastic Cloud on Kubernetes, not Elastic Cloud Hosted or Elastic Cloud Enterprise. ECK automates application lifecycle but does not transfer cluster, storage, backup or upgrade responsibility to Elastic. The free Basic license and paid Enterprise feature set differ; optional Cloud Connect services create separate external dependencies. ECK 3.5.0 fixes service-token exposure, cross-namespace certificate injection, and retained cross-namespace credentials. CVE-2026-72648 has no workaround; after upgrading, rotate the affected service token as Elastic directs.
Cloud evidence reviewed 2026-11-17 |
| Grafana OSS Self-Hosted | AWS | Customer-operated Servers / containers | Open Source / Open Core AGPL-3.0 OSS; Enterprise distribution/plugins have separate licensing | Official Linux packages, Docker image or Kubernetes Helm deployment. | Customer maintains the Grafana server, database, plugins, access controls and data-source integrations.Scope and evidenceThis entry covers Grafana OSS, not Grafana Cloud. The Enterprise Docker image and plugins can have different terms and entitlements. Grafana queries configured data sources; it is not by itself a complete logs/metrics storage backend. Grafana 13.3.1 fixes multiple authorization, impersonation, path-traversal, and denial-of-service CVEs; coordinated patches were also published for maintained 13.2, 13.1, 13.0, and 12.4 branches. Upgrade to a patched release for the deployed branch and review plugin compatibility.
Cloud evidence reviewed 2026-11-12 |
| Langfuse Self-Hosted | AWS, Azure, Google Cloud, Railway, Render | Customer-operated Servers / containers | Open Source / Open Core MIT core; designated enterprise directories and add-on capabilities use separate license terms or keys. | Docker Compose for a single VM; Helm/Kubernetes and official AWS, Azure and Google Cloud Terraform modules. | Customer operates the deployment, persistence, access policies, retention, backups and scaling.Scope and evidenceTraces can contain prompts, outputs and other sensitive application data, so configure capture and retention deliberately. Self-hosted trace storage does not move the underlying application model into the same account. Optional model-based evaluators or the gateway use configured providers, which may be external. The single-VM Compose example does not provide production high availability or backups. Langfuse v4.82.0 fixes an SSRF path in GitHub Enterprise SSO and moves audit logs to ClickHouse. Review outbound SSO connectivity and audit-log storage during upgrade.
Cloud evidence reviewed 2026-11-12 |
| MLflow Tracking Server Self-Hosted | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Open Source / Open Core Apache 2.0 for upstream MLflow; connected model providers and managed distributions have separate terms. | Python MLflow server command, official Docker Compose bundle or Kubernetes Helm deployment. | Customer operates server access, metadata and artifact stores, retention, backups, scaling and version upgrades.Scope and evidenceTraces can capture model inputs, outputs and intermediate metadata. Point clients at the customer-hosted server and review recording/redaction settings. Applications, evaluators and optional model integrations may still call external providers; hosting the tracking server does not host all training or inference runtimes. Production database, storage and security configuration differ from a local quickstart.
Cloud evidence reviewed 2026-11-12 |
| Nagios XI | AWS | Customer-operated Servers / containers | Commercial Only Commercial perpetual node-based license; limited free and 30-day trial modes are available. | Official Nagios XI Amazon EC2 AMI or package installation on a supported Linux server | Customer manages compute, plugins, credentials, monitored endpoints, upgrades, backups, availability and notification delivery.Scope and evidenceNagios Core is open source, but the XI interface and system frameworks are commercially licensed. The AWS badge covers the official EC2 AMI, not a managed Nagios service. The cloud guide installs and compiles the application at first boot, so the AMI is not a durable application-version snapshot. The current reviewed upstream release is 2026R2, with command/SQL injection fixes; verify the actual build and change initial database/system credentials.
Cloud evidence reviewed 2026-11-19 |
| OpenObserve Enterprise Self-Hosted | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Enterprise End User License Agreement. The vendor publishes a free tier through 50 GB/day of ingestion, with a license required above that threshold. | Install the Enterprise Helm chart and CloudNativePG operator, then configure the cluster, object storage and application settings for the selected provider. | The customer runs the cluster, configures storage credentials and ingestion endpoints, sizes components, manages backups and retention, and applies chart and application upgrades.Scope and evidenceThe documented paths cover Enterprise Edition. Feature access depends on the enterprise entitlement. OpenObserve documents outbound product usage reporting and a ZO_TELEMETRY opt-out. Plan for separate recovery of telemetry objects and PostgreSQL metadata. The reviewed chart 1.1.7 pins Enterprise image v1.1.2; do not substitute an OSS or release-candidate tag by name alone. Dex is optional and must be configured. The EKS node example is a sizing starting point, not an HA workload benchmark. The linked EKS cluster example pins Kubernetes 1.30, which is absent from AWS’s currently available EKS versions; select an available version compatible with the application before using the example.
Cloud evidence reviewed 2026-11-20 |
| OpenSearch | Railway | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0 for upstream OpenSearch. Separately operated managed services and connected model or data services have their own terms. | Run official Docker images and customize the documented Docker Compose examples; native package and tarball installations are also documented. | Customer manages cluster sizing, storage, shard and replica layout, TLS, users and roles, ingestion, snapshots, monitoring and upgrades.Scope and evidenceSample deployments and demo security settings require production configuration. Official images distributed through Amazon ECR are not evidence of an AWS-specific deployment. The listing covers self-operated OpenSearch; Amazon OpenSearch Service and other managed services are separate delivery models. Embeddings and AI connectors can involve external models or services. OpenSearch 3.10.0 removes experimental Views and macOS x64 archives and fixes remote-store data-loss or stall paths, bulk-index corruption, heap leaks, snapshot queue stalls, remote-translog issues, and OOM behavior. Validate plugins, Dashboards, and storage recovery before upgrading.
Cloud evidence reviewed 2026-11-12 |
| Parseable OSS | AWS, Railway | Customer-operated Servers / containers | Open Source / Open Core AGPL-3.0 for the OSS project. Standalone and distributed OSS deployment guides are available; Enterprise software/support has separate terms. | Install OSS with Helm in standalone or distributed mode on the documented AWS path, or use the Railway standalone template. Pin application/chart versions and review the migration requirements for older charts. | The customer manages credentials, data ingestion, persistent staging, object storage, access configuration, retention, backups and upgrades.Scope and evidenceThe standalone example is a single pod; distributed OSS has a separate vendor guide and is not automatically an HA guarantee. Chart 3.2.4 defaults to application v3.2.3, whereas the reviewed upstream release is v3.2.7. Existing standalone charts through 3.0.2 need a new 3.1.0+ installation and verified data migration. Railway uses a moving edge image, paid Buckets and a persistent staging volume. Disable optional usage statistics with P_SEND_ANONYMOUS_USAGE_DATA=false when required; this alone does not establish air-gapped operation.
Cloud evidence reviewed 2026-11-20 |
| Prometheus | AWS | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0 for upstream Prometheus components. | Run official server binaries or the documented Prometheus container with persistent storage and a configured scrape file. | Customer manages scrape targets, storage retention, alerting, access controls, exporters, backups and upgrades.Scope and evidenceThe sample Docker configuration is not a complete production monitoring deployment. Exporters, remote-write destinations and alert integrations may be outside the account; capacity and retention remain operational choices.
Cloud evidence reviewed 2026-11-12 |
| SigNoz Self-Hosted | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Open Source / Open Core MIT Expat for core code; ee/ enterprise code has its own separate license. | Use the supported Foundry workflow to generate and run the Docker Compose stack; the older bundled install script/deploy files are deprecated. | Customer manages collectors, storage capacity, retention, authentication, backups, alert API and operator migrations, and platform upgrades.Scope and evidenceThe reviewed guide is explicitly for self-hosted Community without a license. Commercial features require their stated terms. Instrumentation can capture sensitive payloads, so configure capture and retention according to the data being monitored. SigNoz v0.150.0 automatically migrates stored alert rules to v2alpha1 but removes the v1 rule APIs and GET /api/v2/rules. Update API scripts, move Terraform configurations from signoz_alert to signoz_rule, use SigNoz Operator v0.0.5 or newer, and back up the metastore before upgrading. The release also begins dual-ingesting log bodies into native JSON storage; plan additional collector, ClickHouse, and log-disk capacity before rollout.
Cloud evidence reviewed 2026-11-12 |
| Splunk Enterprise | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial end-user license based on data volume or infrastructure; limited trial, developer and Free licenses have separate restrictions. | Splunk Enterprise installation package on supported Linux or Windows hosts; Docker is limited to supported standalone and single-server topologies. | Customer manages compute, networking, storage, data inputs, certificates, clustering, capacity, backups, license configuration, monitoring and upgrades.Scope and evidenceThis entry covers customer-managed Splunk Enterprise, not Splunk Cloud Platform. Splunk documents customer-managed BYOL architectures on AWS, Azure and Google Cloud. Current installation documentation limits supported container deployments to standalone and single-server topologies, so distributed production deployments should follow supported package-based validated architectures. Confirm supported operating systems, instance types, object-store throughput, cache sizing and clustering requirements. Splunk advance notice SVD-2026-1101 says forthcoming November disclosures are fixed in Enterprise 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 and strongly recommends those or later releases. Final CVE-specific disclosures were not live during this review; 10.6.0 Universal Forwarder users should move to 10.6.1 or later.
Cloud evidence reviewed 2026-11-16 |
| SUSE Observability Self-Hosted | AWS, Azure, Google Cloud, Alibaba Cloud | Customer-operated Servers / containers | Commercial Only Commercial SUSE Observability self-hosted subscription and license key required. | SUSE Observability server Helm chart on EKS, AKS, GKE or Alibaba ACK, with provider-specific storage configuration | Customer manages the Kubernetes cluster, persistent storage, sizing, ingress, certificates, backups, upgrades and monitored-system access.Scope and evidenceThis entry covers the self-hosted server product, not SUSE Cloud Observability SaaS. Installation requires a license key, compatible Helm and Kubernetes versions, persistent storage and dedicated sizing. High-availability and non-high-availability profiles are not interchangeable after installation, so choose the production topology before deployment. SUSE Observability 2.13.0 includes authentication, disk, and backup fixes and requires the documented sequential upgrade path. Version 2.10 reached end of support on November 12, 2026; move through supported intermediate releases as required.
Cloud evidence reviewed 2026-11-17 |
| SUSE Security (NeuVector) | AWS, Azure, Google Cloud, IBM Cloud, Alibaba Cloud, Oracle Cloud | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0 for NeuVector; Rancher Prime delivery and commercial support have separate subscription terms. | SUSE Security Helm chart or manifests on public-cloud Kubernetes | Customer manages Kubernetes, registry access, Helm values, storage, certificates, policies, upgrades, monitoring and cluster privileges.Scope and evidenceThis entry covers upstream NeuVector/SUSE Security deployment; subscription images/support can require commercial entitlements. SUSE names six public-cloud Kubernetes targets. Resolve the conflicting manager-redundancy guidance before HA design, and apply GKE Autopilot allowlists where required. Scan-policy/compliance functions do not certify the customer installation.
Cloud evidence reviewed 2026-11-18 |
| ThingsBoard Self-Hosted | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Source Available Business Source License 1.1 for ThingsBoard 4.4+; production grants and a licence key are subject to device, server and attribution conditions. | Kubernetes manifests | Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.Scope and evidenceCurrent 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.
Cloud evidence reviewed 2026-11-19 |
| Wazuh Self-Hosted | AWS | Customer-operated Servers / containers | Open Source / Open Core Open-source Wazuh components under GPL-2.0 and Apache-2.0 licenses. | Official Wazuh All-In-One AMI from AWS Marketplace | Customer manages EC2, networking, storage, agents, TLS, backups, retention, upgrades and capacity.Scope and evidenceThe vendor’s all-in-one AMI is explicitly single-node/testing oriented and does not provide HA or professional support. A production design should evaluate distributed server/indexer/dashboard components and match supported versions. Cloud-monitoring integrations alone do not establish hosting on additional providers.
Cloud evidence reviewed 2026-11-18 |
| Zabbix Server | AWS, Azure, Google Cloud, DigitalOcean | Customer-operated Servers / containers | Open Source / Open Core AGPLv3 for Zabbix 7.0+; older releases such as the reviewed DigitalOcean 6.x packages use GPLv2. Provider images/support can be separately charged. | Official Zabbix VM images from AWS, Azure, Google Cloud or DigitalOcean marketplaces | Customer manages VM, database, storage, agents, networking, TLS, retention, backups, upgrades and monitoring capacity.Scope and evidenceProvider packages differ: the reviewed AWS AMI is v7.4.16, the Azure guide uses a 7.4 example, and DigitalOcean lists older 6.x images. Upstream 8.0.0 does not make those images current. Recheck supported branches/OS and patch before use; single appliances do not establish HA or retention sizing.
Cloud evidence reviewed 2026-11-18 |
Choose 2–4 listings to compare
Browse listing cards
Data & analytics +1 more
AVEVA PI System (BYOL)
Commercial industrial data collection, historian and visualization system with an AWS architecture.
- AWS
Buyer facts and open questions →
6 sources checked
Data & analytics +1 more
Cloud Carbon Footprint
Open-source cloud-usage, energy and carbon-estimation application.
- Google Cloud
Buyer facts and open questions →
5 sources checked
Coroot Community Edition
Self-hosted application observability with service maps, logs, metrics, traces and continuous profiling.
- AWS
- Azure
- Google Cloud
- Oracle Cloud
Buyer facts and open questions →
14 sources checked
Datadog BYOC Logs
Datadog log processing, indexing and storage in the customer's cloud, with search through Datadog Log Explorer.
- AWS
- Azure
- Google Cloud
Buyer facts and open questions →
14 sources checked
Data & analytics +2 more
Elastic Cloud Enterprise
Commercial self-managed orchestration platform for Elastic Stack deployments across customer cloud hosts.
- AWS
- Azure
- Google Cloud
Buyer facts and open questions →
6 sources checked
Databases & vector +3 more
Elastic Cloud on Kubernetes
Elastic's Kubernetes operator for deploying and operating Elasticsearch, Kibana and related Elastic Stack resources in customer clusters.
- AWS
- Azure
- Google Cloud
Buyer facts and open questions →
7 sources checked
Grafana OSS Self-Hosted
Self-hosted dashboards, visualization and alerting for operational data.
- AWS
Buyer facts and open questions →
6 sources checked
AI observability & LLMOps +2 more
Langfuse Self-Hosted
Self-hosted LLM observability, evaluations and prompt-management platform.
- AWS
- Azure
- Google Cloud
- Railway
- Render
Buyer facts and open questions →
10 sources checked
AI observability & LLMOps +2 more
MLflow Tracking Server Self-Hosted
Self-hosted experiment tracking and LLM/agent observability with customer-controlled metadata and artifacts.
- AWS
- Azure
- Google Cloud
Buyer facts and open questions →
3 sources checked
Nagios XI
Commercial infrastructure and network monitoring server deployed on customer-controlled Linux infrastructure.
- AWS
Buyer facts and open questions →
7 sources checked
OpenObserve Enterprise Self-Hosted
Self-hosted observability platform for ingesting, searching and analyzing logs, metrics and traces.
- AWS
- Azure
- Google Cloud
Buyer facts and open questions →
15 sources checked
Databases & vector +3 more
OpenSearch
Distributed search and analytics engine with vector retrieval, operational-data analysis and OpenSearch Dashboards visualizations.
- Railway
Buyer facts and open questions →
7 sources checked
Parseable OSS
Self-hosted telemetry data lake for querying logs, metrics and traces stored in columnar files.
- AWS
- Railway
Buyer facts and open questions →
16 sources checked
Prometheus
Metrics monitoring and time-series database for instrumented services and infrastructure.
- AWS
Buyer facts and open questions →
3 sources checked
SigNoz Self-Hosted
OpenTelemetry-based application observability platform for traces, metrics and logs.
- AWS
- Azure
- Google Cloud
Buyer facts and open questions →
6 sources checked
Observability +1 more
Splunk Enterprise
Customer-managed platform for ingesting, indexing, searching and visualizing machine data.
- AWS
- Azure
- Google Cloud
Buyer facts and open questions →
6 sources checked
SUSE Observability Self-Hosted
Commercial observability platform installed by Helm into a dedicated customer Kubernetes cluster.
- AWS
- Azure
- Google Cloud
- Alibaba Cloud
Buyer facts and open questions →
6 sources checked
DevOps +1 more
SUSE Security (NeuVector)
Open-source Kubernetes security platform with documented customer-operated deployment on AWS, Azure, Google Cloud, IBM Cloud, Alibaba Cloud and OCI.
- AWS
- Azure
- Google Cloud
- Oracle Cloud
- Alibaba Cloud
- IBM Cloud
Buyer facts and open questions →
4 sources checked
Data & analytics +1 more
ThingsBoard Self-Hosted
Source-available IoT device, telemetry and dashboard platform.
- AWS
- Azure
- Google Cloud
Buyer facts and open questions →
7 sources checked
Wazuh Self-Hosted
Open-source security monitoring platform launched from Wazuh's official all-in-one AWS image.
- AWS
Buyer facts and open questions →
3 sources checked
Zabbix Server
Open-source monitoring platform deployed from official Zabbix cloud images into customer accounts.
- AWS
- Azure
- Google Cloud
- DigitalOcean
Buyer facts and open questions →
6 sources checked
How these listings fit
- AVEVA PI System (BYOL)
- Commercial industrial data collection, historian and visualization system with an AWS architecture.
- Cloud Carbon Footprint
- Open-source cloud-usage, energy and carbon-estimation application.
- Coroot Community Edition
- Node and cluster agents collect operational telemetry for application monitoring and troubleshooting.
- Datadog BYOC Logs
- The customer-cloud Logs engine ingests, indexes, stores and queries operational logs. Datadog hosts the Log Explorer and pipeline configuration UI.
- Elastic Cloud Enterprise
- Operates Elastic Stack deployments used to ingest, search and analyze logs, metrics, traces and security telemetry.
- Elastic Cloud on Kubernetes
- Elastic Stack collects and analyzes logs, metrics and traces; exact integrations and features depend on the selected license.
- Grafana OSS Self-Hosted
- Visualization, dashboards and alerting over connected telemetry and other data sources; storage backends are configured separately.
- Langfuse Self-Hosted
- Application/model traces and experiment visibility for AI workloads. Infrastructure metrics and broader application monitoring require separately selected tooling.
- MLflow Tracking Server Self-Hosted
- Application/model traces and experiment visibility for AI workloads. Infrastructure metrics and broader application monitoring require separately selected tooling.
- Nagios XI
- Provides self-hosted infrastructure, network and service monitoring with checks, alerts, dashboards, reporting and an API.
- OpenObserve Enterprise Self-Hosted
- Collects and analyzes application and infrastructure telemetry, with dashboards and alerts for operational monitoring.
- OpenSearch
- Search and analytics over ingested operational data, including log analysis and monitoring; collection, ingestion and dashboard configuration remain deployment work.
- Parseable OSS
- The application ingests and queries operational telemetry and provides dashboards and alerting.
- Prometheus
- Metrics collection, time-series storage and PromQL analysis/alert evaluation. Log storage and distributed tracing require other components.
- SigNoz Self-Hosted
- Application observability over OpenTelemetry traces, metrics and logs; applications must be instrumented and collection configured.
- Splunk Enterprise
- Ingests, indexes and searches machine data for operational monitoring, troubleshooting, dashboards and alerting.
- SUSE Observability Self-Hosted
- Collects, correlates and visualizes Kubernetes topology, metrics, events and related operational signals in a customer-operated deployment.
- SUSE Security (NeuVector)
- Provides workload, network and security-event visibility for Kubernetes clusters.
- ThingsBoard Self-Hosted
- Source-available IoT device, telemetry and dashboard platform.
- Wazuh Self-Hosted
- Collects and analyzes security telemetry, events, file integrity, vulnerabilities and alerts through customer-operated central services.
- Zabbix Server
- Monitors infrastructure, networks, applications, logs and service availability through a customer-operated server and agents.
Review dates and sources appear on each listing. Functionality, edition, deployment and licensing must be checked together. Filter this category with cloud and deployment controls →