Events 🗓️


In this article, we delve into the diverse spectrum of events that Komodor captures within Kubernetes clusters. From availability issues to deployments, changes, node management, service discovery, audits, and custom events, each event type is thoroughly explored. Komodor's ability to correlate related events offers invaluable insights into their causes and impacts, facilitated by the Komodor Timeline visualization. Whether it's troubleshooting, resolution guidance, or gaining a deeper understanding of your Kubernetes environment, this article serves as a comprehensive guide to navigating and leveraging the rich event data provided by Komodor.

Event Types

Availability issue

Exposes occasions where Services run into capacity issues, the impact of those issues, how common they are, when they occurred in the past, and correlating key insights to expose what might’ve caused the issue.

The Availability issue event allows you to dive deeper into the issue with a unique and substantial guided investigation experience.

Deploy event

Komodor automatically tracks changes applied to workloads on your cluster.

Whenever a new version is deployed or a configuration is changed, Komodor will generate a deploy event that will provide information for both successful and unsuccessful deployments.

When a deployment fails, Komodor correlates critical information to understand the cause for this failure, including the failure reason, container logs, recent changes to the workload, and supporting resources (such as ConfigMaps).

In addition to that, Komodor prompts suggested actions that might help with getting to a resolution.

Change events

Capture Kubernetes resources creation, modifications, and deletion. Those events uncover what changed and when.

Supported resources 

ConfigMap, Secret, HPA, Service, Ingress, ResourceQouta

Job run

Track Job runs and their status.

Node creation/deletion

Get an indication for nodes added/removed from your clusters.

Node issue

Captures events where nodes suffered from pressure for an extended period of time and the impact it had on the workloads running on the cluster.

Node termination

Captures node terminations, what caused it (scale down/spot interruption) as well as uncovering impacted workloads and the impact on their health.

Service discovery

Identifying newly deployed Services/Workloads 

Audit events

Tracking changes implemented through Komodor, uncovering what was the change, when it occurred, and who initiated it.

Custom events

Komodor also supports sending custom events to enrich the timeline.


Komodor correlates between related events to expose critical information on what happened and what it impacted. 

The Komodor Timeline provides visualization that allows users to easily correlate between events.

Was this article helpful?

0 out of 0 found this helpful



Please sign in to leave a comment.