Code generation
graph -> generated observabilityDashboards and monitoring assets
Observability assets are generated per service and provisioned consistently in Compose and Kubernetes.
When to use
Use this reference when generating, reviewing or operating a Service Architect project.
Behavior
- Every service receives Jsonnet dashboard sources for the runtime capabilities represented by the graph.
- generate.generated.sh compiles dashboards for provisioning.
- Project-level grafana/provisioning connects generated dashboards and data sources.
- prometheus.yml defines the local Compose scrape topology.
- Helm ServiceMonitor or OTLP collector wiring supplies the equivalent Kubernetes metrics path.
Dashboard and monitoring files
Generated observability sources and provisioning.
FileDashboardDescription
<service>/grafana/dashboards/01_service.jsonnetServiceLifecycle, health and request overview.
02_streams.jsonnetStreamsStream throughput, latency and errors.
03_datasource.jsonnet + 04_datasink.jsonnetConnectorsInbound and outbound connector behavior.
05_pools.jsonnetExecutionTask pool utilization and queue behavior.
06_storage.jsonnetStateStorage-related runtime metrics.
07_http_server.jsonnet + 08_http_client.jsonnetHTTPServer/client request metrics.
09_grpc_server.jsonnet + 10_grpc_client.jsonnetgRPCServer/client RPC metrics.
11_runtime.jsonnetRuntimeLanguage/runtime process metrics.
12_kafka_client.jsonnetKafkaProducer and consumer metrics when Kafka is selected.
_lib.libsonnetShared dashboard libraryCanonical labels, panels and queries.
grafana/generate.generated.shGenerated executableCompile the service dashboard set.
grafana/provisioning/Project provisioningLoad dashboards and data sources into local Grafana.
prometheus.ymlManagedCompose scrape and remote telemetry configuration.
Dashboard generation
make grafana-dashboards
make docker-up
# or deploy the same service identity
make kubernetes-up