Digital Sierra

Telemetry Sources

Detailed guides for each telemetry source integration.

Kubernetes

The collector watches the Kubernetes API for workload, node, namespace, service, ingress, and secret events. It uses a read-only service account and never modifies cluster resources.

Event types:
  • k8s.workload.upsert — Deployments, StatefulSets, DaemonSets, Pods
  • k8s.node.upsert — Node capacity, labels, taints
  • k8s.namespace.upsert — Namespace labels, annotations, status
  • k8s.service.upsert — Service types, ports, selectors
  • k8s.ingress.upsert — TLS coverage, routing rules
  • k8s.secret.upsert — Metadata only (data never collected)

OpenTelemetry

The collector exposes an OTLP gRPC endpoint that accepts spans and metrics. Telemetry is enriched with compliance metadata — no raw spans are stored.

Event types:
  • otel.service.upsert — Service discovery from OTLP resource attributes
  • otel.alert.error_rate — Error rate threshold alerts

GitHub

The collector accepts GitHub webhooks for repository events, pull requests, releases, and branch protection changes.

Event types:
  • github.repo.upsert — Repository metadata and visibility
  • github.pr.merged — PR merge records with reviewer list
  • github.branch_protection.changed — Rule changes
  • github.release.published — Release change records

AI / GenAI

Collects model inventory and usage telemetry via OpenTelemetry GenAI semantic conventions. Supports ISO 42001 AI management system compliance.

Event types:
  • ai.model.upsert — Model registration and configuration
  • ai.model_call.aggregate — Usage aggregates (tokens, users, errors)