An event source is a component that produces events and exposes them for delivery to consumers. In a metrics pipeline, sources provide CloudEvents that can be stored, transformed into CDEvents, and processed into measurements. section 9.2.2 section 9.2
Common event sources include:
- Knative Eventing sources such as APIServerSource, PingSource, GitHubSource, GitLabSource, RabbitMQSource, and KafkaSource. section 9.2.4
- Tool-specific producers from Tekton, Knative Eventing, and Argo Events, including sources for pipelines, tasks, Git providers, Slack, and Stripe. section 9.2
- Custom sources for systems that already produce events but do not emit CloudEvents. section 9.2.4
Sources should be normalized to CloudEvents before entering the collection pipeline. An event endpoint stores incoming events, while later routing, transformation, and calculation stages decide which events to process. Persistent storage separates collection from downstream processing and supports extensible mappings to CDEvents. section 9.2.2 section 9.2.7
Kubernetes deployment events
An ApiServerSource watches Kubernetes Event resources and sends matching CloudEvents to a service such as cloudevents-raw-service. Those events can be stored, filtered, transformed into CDEvents, and used to calculate deployment frequency. section 9.2.4 section 9.2.7
Listing 9.1 Knative Source APIServerSource definition
apiVersion: sources.knative.dev/v1
kind: ApiServerSource #1
metadata:
name: main-api-server-source #2
spec:
serviceAccountName: api-server-source-sa #3
mode: Resource
resources:
- apiVersion: v1
kind: Event #4
sink: #5
ref:
apiVersion: v1
kind: Service
name: cloudevents-raw-service
namespace: dora-cloudevents
Inspect the declarative ApiServerSource definition, including its service account, watched Kubernetes resource, and event sink. section 9.2.4
