Question 1

Which Datadog region does Ana use?

Accepted Answer

The connector supports all Datadog regions including US1, US3, US5, EU, and government clouds. Admins whitelist the corresponding API endpoint domain (api.datadoghq.com, api.datadoghq.eu, etc.) in the TextQL admin console based on where your Datadog account is hosted.

Question 2

Can Ana correlate traces with logs?

Accepted Answer

Yes. Ana can follow Datadog trace IDs across metrics, APM, and logs to build a complete picture of a request or incident. This is especially powerful when joined with warehouse data for root-cause analysis of customer-reported issues.

Question 3

How are Datadog keys secured?

Accepted Answer

API key and application key are encrypted in TextQL's credential vault and injected by our egress proxy at the network layer. Ana's Python sandbox never sees the raw values. Both keys can be rotated any time from the TextQL admin console.

Question 4

Does Ana respect Datadog RBAC?

Accepted Answer

Yes. The application key is created under a specific Datadog user, and Ana inherits that user's permissions. We recommend creating a dedicated TextQL service user with exactly the read permissions you want Ana to have for clean audit separation.

Question 5

Can Ana create Datadog monitors?

Accepted Answer

Yes with write permissions. By default the connector is read-only. Admins can grant write permissions to let Ana create or update monitors, SLOs, and dashboards based on analysis results. Writes are audit-logged separately from reads.