Skip to Content

GlassFlow Observability

This guide explains how to export GlassFlow’s logs and metrics for monitoring and observability purposes.

  • Metrics are enabled by default in the Helm chart and available at the OTEL collector endpoint
  • Logs can be enabled by configuring an OTLP exporter endpoint
  • The OTEL collector service is available at {release-name}-otel-collector.{namespace}.svc.cluster.local:9090

Metrics Export

GlassFlow includes an OpenTelemetry (OTEL) collector that exposes metrics by default via a Prometheus exporter. The metrics are available at the /metrics endpoint.

Accessing Metrics

The OTEL collector service exposes metrics at:

{release-name}-otel-collector.{namespace}.svc.cluster.local:9090/metrics

For example, if you installed GlassFlow with the release name glassflow-chart in the glassflow namespace:

glassflow-chart-otel-collector.glassflow.svc.cluster.local:9090/metrics

Prometheus Scraping

To scrape metrics with Prometheus, add the following configuration to your Prometheus config:

# GlassFlow OTEL Collector metrics - job_name: 'glassflow-otel-collector' static_configs: - targets: ['glassflow-chart-otel-collector.glassflow.svc.cluster.local:9090'] metrics_path: /metrics scrape_interval: 15s
💡

Replace glassflow-chart and glassflow with your actual release name and namespace if different.

Logs Export

To enable log export, you need to configure an OTLP exporter endpoint in your Helm values.

Configure OTLP Exporter

Update your values.yaml file to include the OTLP exporter configuration:

# OTLP exporter configuration for logs otel: exporter: endpoint: your-otel-endpoint.com:4317 # Replace with your OTLP endpoint tls: insecure: true
💡

Endpoint Protocol:

  • For HTTP (often port 4318): Use http://your-endpoint:4318
  • For gRPC (often port 4317): Use your-endpoint:4317 (no http prefix)

Supported OTLP Endpoints

GlassFlow supports standard OTLP exporters. You can configure it to send logs to:

  • Jaeger: http://jaeger-collector:14250
  • Zipkin: http://zipkin:9411/api/v2/spans
  • Custom OTLP endpoint: Any endpoint that accepts OTLP format
ℹ️

The OTLP exporter configuration follows the standard OpenTelemetry format. Refer to the OpenTelemetry Collector OTLP Exporter documentation  for detailed configuration options.

Last updated on