# Wetech Configured Datasource UID

<!-- auto-oncall-optimization-record
{
  "schemaVersion": "auto-oncall-optimization-record-v1",
  "optimizationId": "wetech-configured-datasource-uid-2026-08-12",
  "problems": [
    {
      "problemId": "configured-wetech-datasource-blocked-by-malformed-listing",
      "summary": "APID-29194 readiness resolved gosaas02 to SaaS02, but Prometheus queries failed because the Grafana datasource listing was returned as a JSON-encoded string even though the target had an exact configured datasource UID.",
      "status": "optimized_verified",
      "issueKeys": ["APID-29194", "APID-29259"],
      "sourceRefs": [],
      "signalTextIncludesAny": ["could not list Grafana datasources", "configured datasource UID", "provider_operation_failed"],
      "observedThrough": "2026-08-12",
      "effectiveAt": "2026-08-12T07:08:34Z",
      "verifiedAt": "2026-08-12T07:45:00Z",
      "attemptedAction": "Use the exact target inventory datasource UID directly and enumerate datasources only when no UID is configured.",
      "evidenceUrl": "https://github.com/tidbcloud/aisupport/tree/main/auto-oncall-services/docs/opts/2026-08-12-wetech-configured-datasource-uid.md"
    }
  ]
}
-->

- Owner: auto-oncall-services
- Source: APID-29194 staging replay `2c8613cb-3174-40f5-b720-96a2fb61a8b5`
- Status: optimized_verified

The exact inventory UID now bypasses a non-authoritative datasource listing;
the proxied Prometheus query itself still validates authentication and target
access. APID-29259 replay `669ba399-75a4-4818-bb54-739e5df24efc` then executed
many Prometheus queries successfully through the configured SaaS02 UID; the
prior malformed `/api/datasources` listing no longer blocked metrics.