Closed
Add events-to-logs feature leveraging the k8s_events receiver#215
Conversation
Copilot
AI
changed the title
[WIP] Add events-to-logs feature leveraging k8s_events receiver
Add events-to-logs feature leveraging the k8s_events receiver
Jul 17, 2026
csatib02
marked this pull request as ready for review
July 17, 2026 17:07
csatib02
reviewed
Jul 17, 2026
- Move eventsToLogs from Tenant to Collector CRD as a struct exposing kube_api_qps, kube_api_burst and dedup_interval; wire storage into the k8s_events receiver like the filelog receiver - Grant the collector (and the operator, for RBAC escalation) get/list/watch on core events; propagate to generated ClusterRole, config/rbac and helm chart - Fix copyright headers to 2026 - Document that events are read cluster-wide regardless of tenant scoping Signed-off-by: Bence Csati <bence.csati@axoflow.com>
Signed-off-by: Bence Csati <bence.csati@axoflow.com>
Signed-off-by: Bence Csati <bence.csati@axoflow.com>
Member
|
Folded into #216 as the 'feature' commit. |
csatib02
added a commit
that referenced
this pull request
Aug 7, 2026
Squash-merges the events-to-logs feature (PR #215): adds the k8s_events receiver wiring, EventsToLogs API field, CRD/RBAC, and docs. Adapted to the snake_case component names introduced in the preceding commit. Signed-off-by: Bence Csati <bence.csati@axoflow.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an events-to-logs feature (#199) that collects Kubernetes events as log records using the OpenTelemetry k8s_events receiver and routes them through a tenant's existing subscription/output pipelines.
API
eventsToLogsboolean onTenantSpec. Events are scoped to the namespaces resolved bylogSourceNamespaceSelectors, or all namespaces whenselectFromAllNamespaces: true, preserving tenant isolation.make generate.Config generation
GenerateKubernetesEventsReceiveremits ak8s_events/<tenant>receiver withnamespacesset to the tenant's log source namespaces (omitted when selecting from all namespaces).generateReceiversadds the receiver per tenant when enabled;GenerateRootPipelinenow takes a receiver list so the tenant root log pipeline includesk8s_events/<tenant>alongsidefilelog/<tenant>.RBAC
ClusterRolegrantsget/watch/liston coreeventsso the receiver can watch them.Tests
eventsToLogs-enabled tenant, covering receiver and pipeline wiring end-to-end.Caveat
Since the collector runs as a DaemonSet, each collector pod receives the events, so they are duplicated once per node (same behavior as running multiple replicas of the upstream receiver). This is documented on the API field.