Connect Datadog to Leanmote to count your production deployments in DORA, and to see in Context's SRE tabs what Datadog records: transactions, SLOs, incidents, cases, dashboards, and what your Datadog account itself uses and costs. Every permission is read-only: Leanmote never changes anything in your Datadog.
What Leanmote reads from Datadog
Leanmote reads Datadog with a token from a service account. Only the deployments permission is needed to connect; each permission you add opens one more tab of the SRE group.
Deployments (DORA) —
dora_metrics_read, the only required one. How often you deploy to production, how many changes fail and how long you take to recover.Transactions —
timeseries_query,monitors_read,events_read. Transaction volume, how many are rejected, the peaks and each product's latency.Availability —
slos_read,apm_service_catalog_read,metrics_read,apm_read,logs_read_data. Whether your services meet their SLOs and whether they send logs, traces and metrics. Leanmote only counts logs: it does not read their content.Incidents and tickets —
incident_read,cases_read,teams_read. Incidents and cases, and who in your team handled them.Datadog dashboards —
dashboards_read. The widgets of the Datadog dashboards you choose to show. Computing them also needstimeseries_query.Datadog usage —
usage_read, andbilling_readfor the cost. What your Datadog account uses of each product and what it costs, month by month. The cost is only read when the token's role has access to billing in Datadog.
Connect Datadog
In Datadog, go to Organization Settings › Service Accounts and open a service account, or create a new one.
In that account, go to Access Tokens and click + New Token. Tick
dora_metrics_readand the permissions of the tabs you want to see. You can add the rest to the same token later, without connecting again.In Leanmote, go to Integrations, open Datadog, choose your Region (the address you use to sign in to Datadog, for example US5 if you sign in at us5.datadoghq.com), paste the token and click Connect. Leanmote checks it with Datadog before saving it.
Supported regions: US1, US3, US5, EU1, AP1, AP2 and UK1.
Mark your production environments
Datadog does not say which environment is production, so right after connecting Leanmote lists the environments of your Datadog deployments and you mark the production ones. Only deployments to those environments count for Deployment Frequency, Change Failure Rate and Time to Restore. If Datadog has no deployments in the last 90 days yet, the environments show up when the first one arrives; the other SRE tabs do not need this step.
In Integrations › Datadog › Manage you also see what Leanmote reads for each SRE tab. When a tab is missing a permission or something to choose, click its status to see which.
Count DORA from Datadog
If your organization had not chosen where deployments are counted, saving the production environments makes DORA count Datadog deployments. If it had already chosen another source, that choice stays, and you can switch to Datadog deployments in Settings → Organization Settings → Tabs → Metrics, under Where deployments are counted.
With Datadog deployments:
Deployment Frequency counts the production deployments, on the day each one finished.
Change Failure Rate counts as failures the deployments Datadog marks as failed, the deployments that get rolled back (when a service goes back to an earlier version in the same environment, the first deployment it undid counts as failed) and the incidents Datadog records in production.
Time to Restore is the time from each failure to its recovery: until the deployment that rolled it back finished, or the time to restore Datadog records for an incident.
Lead Time for Changes keeps coming from your pull requests.
A deployment is tied to its repository in Leanmote when the repository Datadog records matches one of yours; otherwise it still counts for the organization. The SRE › Deployments tab always counts Datadog deployments, whatever is chosen in Metrics, so its figures can differ from the DORA tab.
Settings for the SRE tabs
In Settings → Organization Settings → Tabs → SRE you choose your transactions metric and its tags, the latency metrics, the dashboards to show, the services that should be observed, and how Datadog teams and people match Leanmote's. See SRE tabs in Context.
If the token stops working
If Datadog stops accepting the token (it expired or was revoked), Leanmote marks the connection to be reconnected and lets your admins know, as with any other integration. Connect again from Integrations › Datadog with a new token; the production environments you chose stay. Leanmote also checks the saved token again on its own, so the warning clears if it works again — for example, after you add a missing permission to the same token.
Related articles
