Data processing agreement in Monitoring and observability
Without a published DPA you cannot review the contract before you talk to sales.
- 6Published
- 28Vendors measured
- 21%Of those measured
- 2026-08-31Checked
21% here against 26% across every category we measure. Monitoring and observability sits below the overall share for this criterion.
Back to Data processing agreement across all categories, or to Monitoring and observability.
Published
Published and readable without a login.
No data processing agreement found.
We reached at least one address for each of these vendors and none of them carried it. That is what we found at the addresses we checked, on the date we checked them, and not a statement about what the vendor has.
| Vendor | What we found |
|---|---|
| Bugsnag | 8 addresses checked |
| Checkly | 8 addresses checked |
| Chronosphere | 8 addresses checked |
| Dynatrace | 8 addresses checked |
| Elastic | 8 addresses checked |
| Grafana Labs | 8 addresses checked |
| Highlight | 8 addresses checked |
| Last9 | 8 addresses checked |
| Logz.io | 8 addresses checked |
| Middleware | 8 addresses checked |
| Netdata | 8 addresses checked |
| New Relic | 8 addresses checked |
| Pingdom | 8 addresses checked |
| Raygun | 8 addresses checked |
| Rollbar | 8 addresses checked |
| Sematext | 8 addresses checked |
| SigNoz | 8 addresses checked |
| Site24x7 | 8 addresses checked |
| Splunk | 8 addresses checked |
| StatusCake | 8 addresses checked |
| Sumo Logic | 8 addresses checked |
| Zabbix | 8 addresses checked |
Not measured
We could not look at these, or their robots.txt asks us not to. That says something about our measurement, not about them, and they are left out of the percentage above.
| Vendor | What we found |
|---|---|
| Cronitor | The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured. |
| Graylog | The vendor’s server blocked or rate-limited our crawler, so this was not measured. |
Found something we missed? Tell us and the next run picks it up.