Alternatives to Splunk
Other Monitoring and observability vendors we measure, sorted by how much they publish that Splunk does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 27 that differ from Splunk on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Splunk has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “publishes and Splunk does not” is the one that closes them.
| Vendor | Score | Publishes, and Splunk does not | Splunk publishes, and they do not | |
|---|---|---|---|---|
| Sentrysentry.io | 83/100 | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | nothing | Compare |
| Datadogdatadoghq.com | 74/100 | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | 1 security.txt (RFC 9116) | Compare |
| Sumo Logicsumologic.com | 57/100 | 4 Subprocessor list, Status page with history, Notice before subprocessors change, +1 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Honeycombhoneycomb.io | 80/100 | 3 Data processing agreement, Subprocessor list, Status page with history | 1 security.txt (RFC 9116) | Compare |
| Rollbarrollbar.com | 68/100 | 2 Subprocessor list, Status page with history | 1 security.txt (RFC 9116) | Compare |
| New Relicnewrelic.com | 65/100 | 2 Subprocessor list, Status page with history | 1 Certifications named | Compare |
| UptimeRobotuptimerobot.com | 65/100 | 2 Data processing agreement, Status page with history | 1 security.txt (RFC 9116) | Compare |
| Better Stackbetterstack.com | 57/100 | 2 Data processing agreement, Notice before subprocessors change | 1 security.txt (RFC 9116) | Compare |
| Chronospherechronosphere.io | 40/100 | 2 Subprocessor list, Uptime SLA with a figure | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Sematextsematext.com | 35/100 | 2 Uptime SLA with a figure, No third-party tracking before consent | 3 Data location stated, Certifications named, security.txt (RFC 9116) | Compare |
| Pingdompingdom.com | 30/100 | 2 Uptime SLA with a figure, Named privacy contact | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Grafana Labsgrafana.com | 50/100 | 1 Status page with history | 1 security.txt (RFC 9116) | 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.