Edge Delta Kubernetes Event Source

Monitor Kubernetes Events.

  2 minute read  

Overview

You can use the Kubernetes Event Source node to ingest Kubernetes events from the cluster when there is a state change in a cluster resource. If there is more than one agent in the cluster, a leader election process selects an agent to collect all the events. Events have the item.type=event attribute. If you connect the Kubernetes Event Source node to the ed_archive_output node, the events are searchable on the Event Explorer or using the Search tab on the Logs page with the search string: @item.type:event.

  • outgoing_data_types: log

Example Configuration

nodes:
  - name: my_k8s_event_input
    type: k8s_event_input
    report_interval: 1m

Required Parameters

name

A descriptive name for the node. This is the name that will appear in pipeline builder and you can reference this node in the YAML using the name. It must be unique across all nodes. It is a YAML list element so it begins with a - and a space followed by the string. It is a required parameter for all nodes.

nodes:
  - name: <node name>
    type: <node type>

type: k8s_event_input

The type parameter specifies the type of node being configured. It is specified as a string from a closed list of node types. It is a required parameter.

nodes:
  - name: <node name>
    type: <node type>

Optional Parameters

report_interval

The report_interval parameter defines the interval at which to report events. It is specified as a duration and the default value is 1m. The report_interval parameter is optional.

nodes:
  - name: ed_k8s_events
    type: k8s_event_input
    report_interval: 1m

source_metadata

The source_metadata parameter is used to define which detected resources and attributes to add to each data item as it is ingested by the Edge Delta agent. In the GUI you can select:

  • Required Only: This option includes the minimum required resources and attributes for Edge Delta to operate.
  • Default: This option includes the required resources and attributes plus those selected by Edge Delta
  • High: This option includes the required resources and attributes along with a larger selection of common optional fields.
  • Custom: With this option selected, you can choose which attributes and resources to include. The required fields are selected by default and can’t be unchecked.

Based on your selection in the GUI, the source_metadata YAML is populated as two dictionaries (resource_attributes and attributes) with Boolean values.

See Choose Data Item Metadata for more information on selecting metadata.