One platform for Azure, AWS, and GCP.
Ingest D4 telemetry from Microsoft Azure, Amazon Web Services, and Google Cloud with full CSP provenance. Same provenance model across all three — you choose by cloud, not by vendor lock-in.
Supported cloud providers
Real exporters for each provider. Install, configure resource and org/project IDs, run on a schedule — no JSON editing. The exporter stamps every signal with provenance; the API and storage expose it for filtering and querying.
Microsoft Azure
Azure Monitor metrics
afterai-export-azure-monitor — resource-id, subscription-id, tenant-id. source.csp_telemetry: azure.monitor.metrics
Amazon Web Services
AWS CloudWatch metrics
afterai-export-cloudwatch — region, resource-id, account-id. source.csp_telemetry: aws.cloudwatch.metrics
Google Cloud
GCP Cloud Monitoring
afterai-export-gcp-monitoring — project-id, resource-id. source.csp_telemetry: gcp.monitoring.metrics
Why multi-cloud provenance matters
No lock-in
The same provenance model across Azure, AWS, and GCP. Same source shape: csp, csp_telemetry, csp_org_id, csp_project_id, resource_id. Your queries and filters work the same no matter which cloud produced the signal.
Out-of-band ingestion
Exporters run on a schedule (cron, CI). They pull metrics from each provider's API and write artifacts with source already filled. The runner POSTs to the AfterAI API. No hot-path instrumentation — zero impact on your inference path.
Trustable attribution
Every signal carries source so you know which cloud resource produced it. The API and Azure Table Storage store these as first-class columns — filter and query by CSP, org, project, or resource_id in the portal and via the API (e.g. GET /signals/debug).
Simple flow
- Install the exporter for your CSP (Azure, AWS, or GCP).
- Configure with resource ID and tenant/subscription/project IDs — no JSON editing.
- Exporter writes artifacts + manifest with source; runner POSTs to the AfterAI API.
- See and filter by CSP provenance in the console and API.
Documented in the CSP quickstart (who fills source, runner vs exporter) and csp-provenance.md (canonical source schema and examples). providers.md lists Azure Monitor, AWS CloudWatch, and GCP Monitoring as implemented with links to each package README.