Datadog Sync
2399 EUR / yearv1.1.9
Stop asking engineers whether an application still exists. Datadog Sync reads your Datadog Software Catalog, monitors, SLOs, teams, scorecards and deployment tracking and writes what it finds onto the matching cards as read-only fields — no manual curation, no second inventory. Services become Application cards (or attach to the ones you already have): registered or not, owning team, lifecycle and tier, worst monitor state with alert counts, SLO state with the remaining error budget, the version really running in production and when it last changed, the scorecard pass/fail score, and request volume over the last 30 days so a service nobody calls any more stands out as a retirement candidate. The whole landscape comes with it: Datadog systems become parent Applications, datastores and queues become IT Components the application runs on, APIs become Interfaces it provides or consumes, and teams become Organization cards that own their applications — each as core relations and hierarchy you can see in the dependency views, the matrix and every report. Services are matched by a `Datadog service` attribute you can fill in bulk, by name, or by an explicit link from the admin panel or the card's Datadog tab; unmatched services can optionally be created. Because the enrichment lands as ordinary attributes and relations, it shows up in the inventory grid, filters, reports and exports with nothing else to configure, and the Observability coverage report under Reports shows which applications Datadog knows, watches and holds to a standard, grouped by owner or capability. The sync is strictly Datadog → Turbo EA (nothing is ever written to Datadog), runs on a poll plus a nightly reconcile, never deletes a card or a relation, and stores your API and application keys encrypted on your instance. Datadog is a trademark of Datadog, Inc.; this extension is an independent product and is not endorsed by Datadog.
What’s new
1.1.92026-09-07
- The Datadog chips on a card now sit on the same line as other extensions' chips. They carried their own spacing underneath, which Turbo EA's card header — which now lays those chips out in one row itself — read as a request for extra room, leaving them a few pixels above their neighbours.
1.1.82026-09-05
- Housekeeping release — nothing changes in the product. A leftover pattern from an earlier version of the site-address check, which no longer did anything, has been removed from the code so a future reader cannot mistake it for a rule that is enforced. Your configuration, your cards and your sync behave exactly as before; there is no step to take on upgrade.
1.1.72026-09-05
- This extension now ships a changelog. Every release from here on documents what changed for you in this file, and it travels inside the signed bundle so it is on disk wherever the extension is installed.
1.1.62026-09-05
- The French interface calls a card «fiche» rather than «carte», matching Turbo EA's own vocabulary.
1.1.52026-09-03
- The settings panel says what the Datadog keys must be able to do, in Datadog's own words, in a block that stays on screen whether or not keys are already stored.
- A stored key is marked with a «Token stored» tag inside the field itself.
- A refused Datadog call now shows Datadog's own explanation instead of a bare error, and the line is written to the sync log.
1.1.42026-09-02
- Service level objectives are read correctly again. Datadog's SLO search returns each row wrapped in an envelope and pages differently from the other endpoints, so SLOs were being read as empty and only the first page was ever fetched. An SLO with no service tag is now attributed rather than dropped.
1.1.32026-09-02
- The sync is scoped to the services it actually discovered, so a name that merely resembles a service no longer pulls in unrelated monitors.
- A failed request names the request that failed.
- Service deep links open the Datadog service page.
1.1.22026-09-02
- The packaged wheel now carries the same version as the extension, so an install can no longer end up with mismatched halves.
1.1.12026-09-02
- Picking a Datadog site no longer blanks the field. Selecting a site stored the wrong thing internally, leaving the control empty and making the save fail — three of the settings dropdowns were affected.
1.1.02026-09-02
- The Datadog landscape lands on cards, not just on Applications. Hosts, containers and databases become IT Component cards and endpoints become Interface cards, nested by the hierarchy Datadog reports.
- Owner teams become Organization cards, linked to what they own.
- Deployments, scorecards and usage read through the same read-only client.
- A coverage report in the Reports menu, showing what Datadog knows about that Turbo EA does not.
1.0.02026-09-02
- First release. Bring the Datadog Software Catalog into Turbo EA: services become or match Application cards, and their monitors and service level objectives are mirrored onto the card so an architect can see an application's health without a Datadog seat. Read-only — nothing is ever written to Datadog.