Skip to main content
Enterprise only. A dedicated Prometheus endpoint is available to enterprise customers who want to route Turbo pipeline metrics into their own observability stack. If you would like access, contact support@goldsky.com or reach out to your account manager.

​
Overview

If you already run your own observability stack (Datadog, Grafana Cloud, New Relic, etc.), you don’t need to build dashboards twice. Every enterprise Turbo project can be provisioned with a scrape-ready Prometheus endpoint that exposes the same streamling_* metrics that power the health dashboard — letting your existing alerting, dashboarding, and incident-response tools see Turbo pipeline health. 
Goldsky  ──HTTPS /metrics──▶  your Prometheus-compatible agent  ──▶  Datadog / Grafana / New Relic / PagerDuty / …

​
Getting access

Contact support@goldsky.com to request the integration. You will receive:
  • A project-scoped scrape URL.
  • Credentials for scraping (bearer token or basic auth).
  • The list of metric names and label conventions available for your project.
All metrics are scoped to your project — you only see metrics for pipelines in the project associated with your credentials.

​
Where the metrics can go

The endpoint uses the standard Prometheus exposition format, so it works with anything that speaks Prometheus. Common destinations fall into three categories:

​
Observability platforms (push-based)

These ingest the metrics and give you dashboards, monitors, and alerting on top.
  • Datadog — use the OpenMetrics / Prometheus check on the Datadog Agent. Metrics appear as Datadog metrics and can be used in monitors, dashboards, and SLOs.
  • New Relic — forward via the Prometheus OpenMetrics integration.
  • Splunk Observability Cloud / SignalFx — use the Splunk OpenTelemetry Collector with the Prometheus receiver.
  • AWS CloudWatch / Managed Prometheus — use the AWS Distro for OpenTelemetry to send metrics to Amazon Managed Service for Prometheus or CloudWatch.

​
Prometheus-compatible storage

If you already run Prometheus or a long-term-storage backend, point it at the endpoint as another scrape target.
  • Grafana Cloud — scrape via Grafana Alloy or a Grafana Agent.
  • Self-hosted Prometheus — add the endpoint as a scrape target in prometheus.yml.
  • VictoriaMetrics, Thanos, Cortex, Mimir — any Prometheus-compatible store can scrape the endpoint directly.

​
Alerting destinations (indirect)

Paging tools like PagerDuty, Opsgenie, or VictorOps don’t scrape metrics directly. Instead, define alert rules in whatever system is scraping the endpoint (Datadog monitors, Prometheus Alertmanager, Grafana alerts) and route those alerts into your paging tool via its native integration.

​
Example scrape config

A minimal Prometheus scrape configuration looks like this: 
scrape_configs:
  - job_name: goldsky-turbo
    scrape_interval: 30s
    metrics_path: /metrics
    scheme: https
    static_configs:
      - targets:
          - metrics.goldsky.com # provided by support
    authorization:
      type: Bearer
      credentials: ${GOLDSKY_METRICS_TOKEN}
Exact host, path, and auth method will be confirmed when the endpoint is provisioned for your project.

​
Available metrics

The endpoint exposes the same streamling_* metrics used in the health dashboard. Each metric is labelled with at least project_id and service_instance_id (the pipeline identifier). For concrete query examples and the most commonly alerted metrics, see the starter PromQL queries on the custom alerts page.

​
Next steps

  • Browse the available metrics inside the Goldsky-hosted Grafana workspace first — see the health dashboard guide.
  • If you don’t need to bring your own stack, use custom alerts in the Goldsky Grafana workspace for Slack or email notifications without additional setup.