Edge Delta Kubernetes Trace Input

Overview

You can use the Kubernetes Trace source node to ingest eBPF traces for specific resources from the Linux kernel.

• outgoing_data_types: trace

Example Configuration

nodes:
  - name: Kubernetes_Trace_Input
    type: k8s_trace_input

Required Parameters

name

A descriptive name for the node. This is the name that will appear in Visual Pipelines 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_trace_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

exclude

The exclude parameter is used to excluded traces from certain namespaces from being ingested by the agent. It is specified in OTEL format with Golang regex or full text. If exclude is specified it drops traces that match its Golang regex rules. Exclude is optional.

• If include is specified as well as exclude, then traces matching in include are passed unless they are dropped by exclude.

nodes:
  - name: <node name>
    type: k8s_trace_input
    include:
    - k8s.namespace.name=.*
    exclude:
    - k8s.namespace.name=test

include

The include parameter is used to specify namespaces from which traces should be ingested by the agent. It is specified in OTEL format with Golang regex or full text. If exclude is also specified, then traces matching in include are ingested unless they are dropped by exclude. Include is optional.

nodes:
  - name: <node name>
    type: k8s_trace_input
    include:
    - k8s.namespace.name=.*