View lifecycle events

Lifecycle events help you understand how an infrastructure resource changes over time. View the resource lifecycle events received by Coralogix to track creation, updates, keep-alive signals, and removal.

Lifecycle events provide visibility into resource state changes that are separate from Kubernetes events for the resource. Use them to track resource activity, investigate changes, and understand resource behavior.

Why this matters

Unexpected behavior in infrastructure often results from resource changes. Without visibility into the events received for a resource, troubleshooting becomes slow and unclear.

Lifecycle events help you:

• Identify resource lifecycle changes: See the exact time of resource creation, updates, or deletion, and understand state transitions.
• Understand the nature of changes: Determine whether an update reflects a meaningful configuration change or routine metadata activity.
• Confirm resource availability: Verify that a resource remains active through periodic keep-alive signals, helping you rule out availability issues.
• Trace issues using a clear activity timeline: Correlate system behavior with resource changes to understand what happened before, during, and after an incident.

This visibility helps you diagnose problems faster and understand resource state with confidence.

What you can do

Use lifecycle events to:

• Track resource lifecycle changes: See the time of resource creation, updates, or deletion to understand state transitions and recent activity.
• Monitor resource availability over time: View periodic signals that confirm the resource remains active and responsive.
• Investigate configuration or metadata changes: Identify updates that might explain unexpected behavior, performance issues, or system instability.
• Narrow investigations using filters: Filter events by source or event type to focus on relevant changes and speed up analysis.

Lifecycle events versus K8s events

The Lifecycle Events section shows the resource events received and processed by Coralogix.

The K8s Events section shows Kubernetes system and runtime events generated by the cluster.

Use lifecycle events to understand how Coralogix detects and tracks resource state. Use K8s events to investigate cluster or runtime activity.

Example use case

A service starts failing or behaving unexpectedly. You open the resource's lifecycle events and notice an Update event shortly before the issue began. This indicates that the resource configuration or metadata changed around the same time, helping you quickly trace the cause and validate recent changes.

In another scenario, an application stops responding and you suspect the underlying resource might be down. Lifecycle events show regular Keep-alive activity, confirming the resource is still running. This helps you rule out availability issues and focus your investigation on other potential causes, such as configuration or application errors.

View lifecycle events for a resource

1. Select Infrastructure, then Infrastructure Explorer.
2. Select a resource.
3. Open the Lifecycle Events section.

The table displays lifecycle signals received for the selected resource, ordered from most recent to oldest.

Understand lifecycle event fields

Each event includes the following fields:

Timestamp: The date and time when Coralogix received the lifecycle event.

Source: The system or integration that reported the event.

Event type: The lifecycle action reported for the resource. Use this field to understand what changed and how the resource state evolved over time.

• Create: Indicates when Coralogix first detected and registered the resource. Use this to identify when a resource was first created.
• Update: Shows that the resource's metadata or configuration changed. Use this to investigate behavioral changes, configuration drift, or unexpected updates.
• Keep-alive: Represents a periodic signal confirming the resource is still active and monitored. Use this to verify ongoing availability and connectivity.
• Delete: Records the removal of the resource. Use this to track when a resource ends or stops reporting.

Filter lifecycle events

Use filters to narrow the events displayed in the table:

• Search: Locate specific lifecycle events by entering keywords, such as resource names, event details, or identifiers, to quickly find relevant activity.
• Select source: Filter events by the monitoring source that reported them to understand where the lifecycle signal originated.
• Select event type: Filter events by lifecycle action (Create, Update, Keep-alive, or Delete) to focus on specific types of resource activity or changes.

Filters help you focus on relevant lifecycle activity when investigating resource changes.

Time range behavior

Lifecycle events reflect the selected time range. Adjust the time range picker to view lifecycle activity for a specific period.