Issue:
The Datadog integration is properly configured with the correct permissions, but no services are being discovered for import into Cortex.
Explanation:
Service discovery relies on properly configured environment values within the Datadog integration settings. These values must match the raw env tag values used in Datadog, for example: dev, stg, or prd. They should not include prefixes like env: or any additional formatting.
If no environments are configured, Cortex defaults to searching for services where env:none, which only matches services that do not have an environment tag.
Solution:
To fix this, update the Datadog integration settings so that the Environments field contains the tag values (e.g., dev, stg, prd).:
- In Cortex, navigate to Integrations, then go to your Datadog configuration.
- Click the edit icon next to the configuration
- Add your environment tags to the Environments field
- After adding or correcting these values, trigger a re-sync to allow Cortex to properly discover and import services from Datadog.
Resources: