SAService Architect Back to designer
SAService ArchitectDocumentation
Code GenerationKubernetes and Helm
Code generation Prometheus + Grafana + OTEL + Jaeger + Loki

Observability and Temporal

The generated local cluster verifies metrics, dashboards, traces and logs against the same service identity used by Compose.

When to use

Use this reference when generating, reviewing or operating a Service Architect project.

Behavior

  • The project orchestration installs pinned Prometheus, Grafana, OpenTelemetry Collector, Jaeger and Loki releases.
  • Generated Grafana dashboards cover services, streams, sources, sinks, pools, storage, HTTP, gRPC, Kafka and runtime metrics.
  • ServiceMonitor scrapes C++ and TypeScript metrics endpoints; Go and Rust export OTLP metrics through the collector.
  • Collector relabeling normalizes service and job labels so dashboards work in both Compose and Kubernetes.
  • When the graph contains Temporal, the local stack installs the official Temporal chart and PostgreSQL persistence.
  • Temporal Server metrics, SDK/Worker metrics and ServiceLib graph metrics remain separate metric owners.

Port forwards

# Grafana
docker compose -f docker-compose.kubernetes.yml exec kubernetes \
  kubectl -n <namespace> port-forward service/monitoring-grafana 3000:80
# Prometheus: service/monitoring-kube-prometheus-prometheus 9090:9090
# Jaeger: service/jaeger 16686:16686