Hyper for Datadog

What Hyper reads

Hyper does not keep a copy of your Datadog data. It reads Datadog each time you ask. It works only with Datadog organizations on the US1 site. It can search logs, traces and spans, real user monitoring, events, and metrics. It can read monitors, downtimes, SLOs, incidents, cases, error tracking issues, dashboards, notebooks, services, hosts, and the users in your organization.

What Hyper can do

Create and change monitors, cases, dashboards, and notebooks. Comment on cases, attach files to them, and link them to each other and to Jira issues. Change, comment on, and file Jira or Linear tickets for error tracking issues. Hyper cannot delete monitors, cases, dashboards, or notebooks. Datadog allows these actions only after an admin of your organization turns on write access for its MCP server. Hyper asks you before each action. You cannot choose to always allow these actions.

Before you connect

Hyper can read all the logs, traces, and metrics that your Datadog user can see, and logs and traces often contain customer data, emails, and internal details. A change to a monitor takes effect at once. Datadog records each read and change in its Audit Trail and limits how many reads you can do each month. A Datadog admin can turn off this kind of access. Anyone whose text gets into your logs, such as the users of your app, can add text that hides instructions that try to trick an assistant, so check each action that Hyper asks you to approve.