Data collection
MultiTool only collects data that is actively required to power product functionality. We do not collect data speculatively for future use cases.
- Every field collected has a defined purpose.
- We do not resell or repurpose your telemetry data.
- All data can be permanently deleted.
- We do not perform soft deletes.
Data we collect
MultiTool currently ingests a minimal subset of OpenTelemetry trace fields to power intelligent alerting.
| Field name | Source | Used for | Why it's needed |
|---|---|---|---|
deployment.environment | OpenTelemetry traces | Intelligent alerting | Segment analysis by environment (e.g. production vs. staging). |
service.version | OpenTelemetry traces | Intelligent alerting | Compare deployed versions to detect regressions. |
service.name | OpenTelemetry traces | Intelligent alerting | Associate telemetry with the correct service. |
http.response.status_code | OpenTelemetry traces | Intelligent alerting | Detect shifts in error rates and response distribution. |
end_time_unix_nano | OpenTelemetry traces | Intelligent alerting | Order requests and evaluate behavior within analysis windows. |
What we do not collect
If it is not required to evaluate deployment health, we do not ingest or store it. We do not collect:
- Request or response bodies
- Headers
- User identifiers
- IP addresses
- Database contents
- Unnecessary infrastructure metadata
- Logs or source-maps
Deletion
All collected data can be permanently deleted upon request. Deleted data is fully removed from our systems.