Case study · Travel and aviation · Datadog LaunchPad
An airport's monitoring, held as code its own teams run
An Irish airport operator now runs its Datadog configuration as code through its own pipeline, within about ten weeks of kick-off.
At a glance
About 10 weeks
from kick-off to its own pipeline
Every service
with a named owning team
Around 70%
of logs linked to traces
AviationIrelandAzureTerraformDatadogProfessional services
01
The challenge
The challenge
Observability platforms are often adopted fast and configured by hand, with no clear owner for each service and spend that moves with every new service. For an airport, where passenger-facing services are time-critical and alerts have to be trusted, that does not scale. The operator, which runs on Microsoft Azure, chose to bring in Datadog specialists and decided its configuration should live as code, so its own teams could run and extend it.
02
What we did
What we did
- Assessed the Datadog environment and turned it into a prioritised 30/60/90 day plan.
- Built the monitoring as code, tuned to the operator's own baselines to cut false alarms.
- Registered every service in Datadog's Software Catalog with a named owner.
- Set up cost monitoring and a dashboard that forecasts spend against commitment.
- Moved the configuration into the operator's own repository and pipeline, with templates and guidance for its engineers.
03
The outcome
The outcome
- Datadog configuration now runs through the operator's own pipeline, and Datadog's own health check found low alert noise.
- Its engineers have templates and guidance to create their own monitors, dashboards and runbooks.
- Every service has a named owning team.
- Datadog spend is visible by product and forecast against commitment.
This case study is anonymised, so the customer is not named.
Talk to us about Datadog LaunchPad.
Tell us what you run today and what you need from it. We’ll recommend the simplest first step.