Datadog
Observability for metrics, logs, and traces across services
Polygrade integrates with Datadog for reliability visibility into Polygrade itself, not claims data. Datadog is an observability platform for metrics, logs, and traces, used by engineering and operations teams to monitor the software they depend on. This governs how your team runs Polygrade as enterprise software.
Datadog is an observability platform for metrics, logs, and traces, used by engineering and operations teams to monitor the software they depend on. This isn’t a claims integration, Datadog is about how your organization runs Polygrade itself as procured enterprise software: reliability visibility into Polygrade itself.
What Polygrade does with Datadog
For enterprise clients who want visibility into Polygrade’s own uptime and performance, Polygrade can expose status and performance metrics your team already monitors in Datadog alongside everything else in your stack.
This sits apart from Polygrade’s claim-handling integrations entirely. Datadog doesn’t touch claim data, parts sourcing, or payment execution, it’s the layer that governs how your team accesses and monitors Polygrade as a system, the same way it governs every other vendor you run Datadog against.
How the Datadog connection works
Polygrade’s status and performance data can be exported to a Datadog integration configured during enterprise onboarding.
This is configured during enterprise onboarding rather than left to a self-serve setup, since it touches how your team authenticates or how your operations team gets alerted.
What stays in Datadog
Datadog continues to manage identity, observability, or incident routing exactly as it does for every other tool in your stack. Polygrade is one more system governed by the rules you already have in Datadog, not a special case.
Data handling and security
Polygrade is SOC 2 compliant, with both Type I and Type II audits complete, and each client runs on a company-specific instance, a property directly relevant to how access through Datadog is scoped, since there’s no shared environment to accidentally expose.
Every claim recommendation Polygrade makes is logged with a confidence level and its supporting inputs, independent of whatever visibility Datadog is configured to provide, Datadog adds a second layer of oversight on top of an already-audited system, not a replacement for it.
Setting this up
A dedicated Forward Deployed Engineer configures the Datadog connection as part of enterprise onboarding, working with whoever owns identity or operations tooling on your side.
Frequently asked questions about Polygrade and Datadog
Is Datadog used for claims data, like Polygrade’s other integrations?
No. Datadog governs how your organization accesses or monitors Polygrade itself; claim, parts, and payment data move through Polygrade’s separate category-specific integrations.
How does Polygrade connect to Datadog?
Polygrade’s status and performance data can be exported to a Datadog integration configured during enterprise onboarding.
Is Datadog required to use Polygrade?
No. Datadog is available for enterprise clients who want Polygrade to run under their existing identity, observability, or incident management setup, it isn’t required for Polygrade’s core claims functionality.
