Skip to content
Case study · Healthcare · Datadog HyperCare

A lean team takes control of Datadog spend in its first weeks

A UK health and social care software group now has filtered logs, a tagging standard and early warning of unexpected Datadog spend.

At a glance
2 weeks
of hands-on Datadog engineering
Log noise
cut by the team itself
Early warning
of unexpected spend
Health and social care softwareUKAzureDatadogDatadog HyperCare
01
The challenge

The challenge

Datadog makes it easy to switch everything on, and in a busy Azure estate every log source and every host flows in by default, long before anyone has decided what is worth keeping. The group was bringing several acquired businesses onto one observability platform. It chose Datadog and decided to spend its first weeks getting the foundations right, so its lean team could run the platform on its own.

02
What we did

What we did

  • Ran a Datadog HealthScan and walked the team through the recommendations.
  • Agreed a single tagging standard, so data can be filtered, grouped and costed consistently.
  • Showed the team how to filter logs, keeping what matters and dropping the noise.
  • Set out a simple way to choose which Azure hosts Datadog monitors, by decision rather than by default.
  • Helped the team create cost monitors that warn of unexpected spend, product by product.
03
The outcome

The outcome

  • Log noise cut by the team's own engineers, keeping the logs from their own services.
  • A clear set of next steps from the HealthScan, which the team now owns.
  • A tagging standard and tag-based host selection, both ready to roll out.
  • A cost monitoring approach that gives early warning of unexpected spend.

This case study is anonymised, so the customer is not named.

Talk to us about Datadog HyperCare.

Tell us what you run today and what you need from it. We’ll recommend the simplest first step.