Transparency alternatives to OpenObserve
Other Monitoring and observability vendors we measure, sorted by how much they publish that OpenObserve does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 46 that differ from OpenObserve on at least one criterion we measured for both. Public transparency score, not a product or security rating.
OpenObserve has 5 gaps in what we could measure: Data location stated, Status page with history, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “publishes and OpenObserve does not” is the one that closes them.
| Vendor | Score | Publishes, and OpenObserve does not | OpenObserve publishes, and they do not | |
|---|---|---|---|---|
| Sentrysentry.io | 74/100 | 3 Data location stated, Status page with history, security.txt (RFC 9116) | 2 Uptime SLA with a figure, HTTPS enforced with HSTS | Compare |
| Rollbarrollbar.com | 70/100 | 3 Data location stated, Status page with history, Named privacy contact | 2 Data processing agreement, Uptime SLA with a figure | Compare |
| Pulseticpulsetic.com | 65/100 | 3 Data location stated, Status page with history, Named privacy contact | 3 Subprocessor list, Certifications named, Uptime SLA with a figure | Compare |
| New Relicnewrelic.com | 57/100 | 3 Status page with history, security.txt (RFC 9116), Named privacy contact | 3 Data processing agreement, Certifications named, Uptime SLA with a figure | Compare |
| Netdatanetdata.cloud | 43/100 | 3 Data location stated, Status page with history, Named privacy contact | 5 Data processing agreement, Subprocessor list, Certifications named, +2 | Compare |
| Honeycombhoneycomb.io | 70/100 | 2 Status page with history, Named privacy contact | 1 Uptime SLA with a figure | Compare |
| Datadogdatadoghq.com | 61/100 | 2 Status page with history, Named privacy contact | 2 Uptime SLA with a figure, Notice before subprocessors change | Compare |
| Sumo Logicsumologic.com | 57/100 | 2 Status page with history, Named privacy contact | 2 Data processing agreement, Uptime SLA with a figure | Compare |
| Coralogixcoralogix.com | 48/100 | 2 Data location stated, Status page with history | 4 Subprocessor list, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | Compare |
| Dash0dash0.com | 39/100 | 2 Data location stated, security.txt (RFC 9116) | 4 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +1 | Compare |
| Splunksplunk.com | 39/100 | 2 Data location stated, security.txt (RFC 9116) | 4 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +1 | Compare |
| Grafana Labsgrafana.com | 35/100 | 2 Status page with history, Named privacy contact | 4 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +1 | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.