Integrations
Goliash on the dashboards and in the tools you already use. The settings below are filled in for this server.
Prometheus and Grafana
scrape /metrics, import the dashboard1. A token
An admin creates a viewer token under Users and API tokens, or with goliash token create -name prometheus -role viewer.
2. Scrape
scrape_configs:
- job_name: goliash
scrape_interval: 60s
scheme: https
authorization:
credentials_file: /etc/prometheus/goliash-token
static_configs:
- targets: [demo.goliash.dev]3. Dashboard
Grafana → Dashboards → New → Import, upload the file and pick the Prometheus data source. Versions, drift, delivery, image hygiene and Goliash's own health, with deploys marked on the graphs. The alert rules go into Prometheus' rule_files. On Kubernetes, the Helm chart creates all three: --set metrics.serviceMonitor.enabled=true,metrics.prometheusRule.enabled=true,metrics.grafanaDashboard.enabled=true.
SigNoz
the OpenTelemetry Collector reads /metrics1. A token
An admin creates a viewer token under Users and API tokens, or with goliash token create -name signoz -role viewer.
2. Add to the collector
receivers:
prometheus/goliash:
config:
scrape_configs:
- job_name: goliash
scrape_interval: 60s
scheme: https
authorization:
credentials_file: /etc/otelcol/goliash-token
static_configs:
- targets: [demo.goliash.dev]
service:
pipelines:
metrics/goliash:
receivers: [prometheus/goliash]
processors: [batch]
exporters: [otlp] # the exporter that already sends to SigNoz3. Dashboard
SigNoz → Dashboards → New dashboard → Import JSON. Metrics show up about a minute after the collector restarts.
AI assistants
Claude, Cursor and others ask Goliash over MCP1. A token
An admin creates a viewer token under Users and API tokens, or with goliash token create -name mcp -role viewer.
2. Add the server
claude mcp add --transport http goliash https://demo.goliash.dev/mcp \ --header "Authorization: Bearer glsh_api_…"