Connect your stack
27 native integrations. 3,200+ tools via managed connectors. Most are one-click OAuth, some use API keys - Viktor handles auth and starts working. No webhooks, no Zapier zaps.
Loading
Viktor is an AI employee that connects to Datadog with a scoped API key and helps you monitor application errors and incidents, running 13 Datadog actions for you like List Logs, Search Logs, and Search Hosts. Ask in plain English in Slack or Microsoft Teams; Viktor does the work in Datadog and reports back. Setup takes about two minutes.
Free to start · No credit card · SOC 2 Type 1 · Works in Slack & Microsoft Teams
Messages you'd actually send. Paste one into Slack or Microsoft Teams, swap in your specifics, and Viktor takes it from there.
“Summarize the new errors in Datadog from the last 24 hours and flag any regressions.”
— you, in Slack or Teams
“Check Datadog for the root cause of last night's incident and report back.”
— you, in Slack or Teams
“Watch Datadog for a new critical alert and page me immediately.”
— you, in Slack or Teams
“Post a summary of this week's Datadog incident count to #eng every Friday.”
— you, in Slack or Teams
Ask in plain English in Slack or Microsoft Teams. Viktor picks the right Datadog actions, runs the work, and reports back. No workflows to build.
List services from Datadog's Service Catalog with ownership, metadata, and team info. Use to discover service names for filtering in Search Logs (service:my-app) or finding monitors via Search Monitors (tag:service:my-app). Returns service definitions including links, docs, and on-call.
Search Datadog monitors (alerting rules) including status, thresholds, and conditions. Query syntax: tag:env:production, type:metric, status:Alert. Tags filter: comma-separated (e.g. env:prod,team:backend). After finding a monitor, use Search Events to see recent state changes, or Get Metric Data to query the underlying metric it tracks. Returns monitor ID, name, type, query, status, and tags.
Discovery tool: list available Datadog metric names, optionally filtered by host. Returns metric name strings (e.g. system.cpu.user, aws.ec2.cpuutilization) for use in Get Metric Data queries with the syntax aggregation:metric.name{tags}. Use Search Hosts to find valid host names for the host filter.
Search Datadog logs matching a query with support for facets and time ranges. Uses log search syntax: service:web-app status:error, @http.statuscode:>=400, boolean operators (AND, OR, NOT), and wildcards. Set from to now-1h for recent logs. Use Search Metrics to discover metric names or Search Hosts to find host names for filtering. To investigate an incident, use Search Incidents first, then search logs for that time window and service.
Search Datadog incidents by state, severity, and metadata. Query syntax: state:active, state:resolved, severity:SEV-1. After finding an incident, investigate with: Search Logs for the incident time window, Get Metric Data for relevant metrics, Search Events for related monitor alerts, and Search Services for ownership info.
Search monitored infrastructure hosts. Filter by tag (env:production), name (host:web-01), or partial match. Sort by cpu, iowait, load, status, or apps. Host names from results can scope queries in Get Metric Data (e.g. avg:system.cpu.user{host:web-01}), filter logs in Search Logs (host:web-01), or filter metrics in Search Metrics. Max 1000 results.
Search Datadog events: monitor state changes, deployment markers, error spikes, and infrastructure events. Filter by sources (e.g. nagios,docker), tags (e.g. env:prod,service:web), and priority (normal or low). Time range defaults to last 24h (POSIX timestamps in seconds). To investigate a monitor alert, use Search Monitors first, then search events for the relevant time range. Follow up with Search Logs for deeper investigation.
List and search Datadog dashboards. Returns dashboard IDs, titles, URLs, and metadata. Dashboard URL: where region comes from Get Account Info. Use alongside Search Services to find dashboards related to a specific service.
Post custom time-series metric data points to Datadog. Data appears in dashboards, monitors, and can be queried via Get Metric Data. Points: JSON object where keys are Unix timestamps (seconds) and values are numeric, e.g. {"1640995200": 1.0}. Use Search Metrics to verify a metric name exists, or post to a new name to create it. This is a WRITE operation that creates or appends data to a metric time series.
Query time-series metric data for analyzing trends and system performance. Query syntax: avg:system.cpu.user{}, sum:requests.count{env:prod} by {host}, max:system.mem.used{service:web}. Both from and to are POSIX timestamps in seconds. Use Search Metrics first to discover available metric names. Use Search Hosts to find valid host tags for scoping. After finding anomalies, use Search Logs to investigate related entries.
Detect the Datadog region for the connected account. Call this FIRST before any other Datadog tool if you do not already know the region. Returns the region domain (e.g. datadoghq.com) which must be passed as the region parameter to Search Logs, Search Monitors, Get Metric Data, and all other Datadog tools.
Get a list of logs matching a filter query. Uses the GET endpoint with a higher rate limit (3600/hr vs 300/hr).
Detect the Datadog region for the connected account by validating the API key against each regional endpoint. Use this to discover the correct region before calling other Datadog actions.
27 native integrations. 3,200+ tools via managed connectors. Most are one-click OAuth, some use API keys - Viktor handles auth and starts working. No webhooks, no Zapier zaps.
Message Viktor in Slack like you'd message a teammate. "Summarize the new errors in Datadog from the last 24 hours and flag any regressions." "Check Datadog for the root cause of last night's incident and report back." Plain English, any tool.
Viktor opens Datadog, runs the work, and posts back what changed. Sensitive actions wait for your approval. Everything is logged. You stop doing the work and start reviewing it.
A Datadog AI agent is an AI that connects to your Datadog account and completes work in it - it doesn't just answer questions about Datadog, it takes the actions. Viktor is that agent: an AI employee that works in Datadog on your behalf and delivers the finished result in Slack or Microsoft Teams.
Unlike workflow builders such as Zapier or Make, there is nothing to configure - no triggers to map, no workflows to maintain. You describe the outcome in plain English, and Viktor picks the right Datadog actions, chains them with the other 3,200+ tools it connects to, and asks for approval before anything sensitive runs.
Cloud monitoring as a service
Scoped API keys - Viktor stores your key securely, uses only the scopes you grant, and you can revoke it at any time.
Review-first approvals: sensitive Datadog actions wait for your sign-off before they run.
Isolated compute per team, encrypted in transit and at rest - and your data is never used to train models.
SOC 2 Type 1 compliant, with Type 2 and ISO 27001 in progress.
Yes. Datadog is one of the 3,200+ tools Viktor connects to, via a managed connector. Once connected, anyone on your team can put Viktor to work in Datadog from Slack or Microsoft Teams - no workflow builder, no code.
Ask for outcomes that span tools — Viktor pulls from Datadog, cross-references the rest of your stack, and delivers one finished result.
Viktor connects to 3,200+ tools and works across them in a single run.
