It reports into the tools you already run.
A control layer that only reports into its own dashboard is a second system for your team to watch, and it will be the one they forget.
A service you deploy.
Two streams, two destinations
| What | How | Where |
|---|---|---|
| Metrics and logs | OpenTelemetry: metrics over OTLP gRPC or HTTP, logs over OTLP HTTP; a Prometheus exporter for teams that scrape | your collector |
| A decision a rule sends | syslog, or webhooks for anything else | your SIEM |
Application logs go through the OpenTelemetry log bridge, so a decision, the rule version behind it and the request that carried it correlate in your own tooling rather than in ours.
Nothing leaves your network to get there
These are pushes into systems you own. No endpoint of ours collects anything about your traffic.