Datadog
Inventory Datadog users, roles and MFA, the API and application keys that can act on the account and who owns them, where monitors send alerts, every outside service and cloud account Datadog is connected to, where log data is copied, monthly usage, and the Audit Trail of who changed what.
Questions you can answer 18
Each one is a saved query that ships with ConfigView, reading your Datadog data on your own server. Ask it in plain English, SQL, Slack or the API.
- Who has admin rights in Datadog?
- Which Datadog admins do not have MFA turned on?
- List privileged Datadog users and service accounts
- Where does Datadog send alerts?
- Which Slack channels, PagerDuty services and webhooks do Datadog monitors notify?
- Which outside systems receive Datadog alerts?
- Who changed what in Datadog in the last 30 days?
- Show recent Datadog monitor and dashboard changes
- Which Datadog keys or users were created or changed this month?
- Which Datadog API keys haven't been used in 90 days?
- Are there Datadog API keys created by people who have left?
- List stale or orphaned Datadog application keys
- Where does Datadog send our logs?
- Which S3 buckets and outside hosts receive Datadog log data?
- Is Datadog forwarding logs to a third party?
- Which Datadog monitors notify nobody?
- Are any Datadog monitors sending to a webhook that no longer exists?
- Find Datadog alerts that reach no one
No Datadog questions match that yet. Try a shorter word.
What ConfigView collects from Datadog 9
-
API Keys
Datadog API keys: name, last four characters, who created each one and when it was last used. The keys themselves are never stored.
-
Application Keys
Datadog application keys across the organization: name, last four characters, what each one is allowed to do, its owner and when it was last used. The keys themselves are never stored.
-
Audit Trail
Who changed what in Datadog: each Audit Trail event's time, person, action, the dashboard, monitor, key or setting it touched, and the IP it came from. Kept as a growing history. Needs Audit Trail enabled on the Datadog plan.
-
Connected Services
Outside services Datadog is connected to: Slack, Microsoft Teams, PagerDuty, Opsgenie, webhooks, Jira, ServiceNow, Okta, Cloudflare, Fastly, Confluent, AWS, Google Cloud and Azure accounts, with the host each one points at. No credentials are stored.
-
Log Destinations
Where Datadog copies log data outside itself: log archives in S3, Google Cloud Storage or Azure, and log forwarding to Splunk, Elasticsearch, Microsoft Sentinel or any HTTP endpoint, with the bucket or host and which logs go there.
-
Alert Recipients
Where each Datadog monitor sends its alerts: the Slack channel, webhook, PagerDuty service, Teams channel, Opsgenie service or email address named in it. The alert text itself is not stored.
-
Roles
Datadog roles, built-in and custom: how many users hold each one and the permissions it grants.
-
Monthly Usage
This month's and last month's Datadog usage per product (hosts, containers, log volume, custom metrics and so on): the monthly total, the busiest hour and how many hours reported.
-
Users
Every Datadog user and service account: email, status (active, invited, disabled), whether MFA is on, last login, and the roles each one holds.