Kubernetes Inputs

Enter a descriptive label for this input. 

When you create a workflow, you will use this label to enter your input into the workflow. 

apache,errorcheck is the default label.

This parameter is required.

Review the following example: 

labels: "apache,errorcheck"

Enter the Kubernetes attributes to include.

To specify which input to add, you must provide include/exclude regex filters.

• All rules in the same line with a comma(",") separated means AND:

   include:
     - "rule-1,rule-2"
  

• All rules under the same part (include/exclude) means OR:

   include:
     - "rule-1"
     - "rule-2"
  

• The Kubernetes Exclude field takes precedence over the Kubernetes Include field.
• If the value you provide after pod=, namespace=, or kind= is contained anywhere in the pod or namespace name, then the value will match.

This parameter is optional.

Review the following example: 

include:
  - "pod=^apache.*$,namespace=.*web*"

Enter the Kubernetes attributes to exclude.

To specify which input to add, you must provide include/exclude regex filters.

• All rules in the same line with a comma(",") separated means AND:

   exclude:
     - "rule-1,rule-2"
  

• All rules under the same part (include/exclude) means OR:

   exclude:
     - "rule-1"
     - "rule-2"
  

• The Kubernetes Exclude field takes precedence over the Kubernetes Include field.
• If the value you provide after pod=, namespace=, or kind= is contained anywhere in the pod or namespace name, then the value will match.

This parameter is optional.

Review the following example: 

exclude: 
  - "namespace=^kube-nginx$"
  - "pod=.*nginx*,kind=StatefulSet"

Enter true or false to enable auto line detection for log messages with multiple lines.

This parameter is optional.

Review the following example: 

auto_detect_line_pattern: true

Enter true or false to enhance (or troubleshoot missed patterns) the Auto Line Detection parameter. 

This parameter is optional.

Review the following example: 

boost_stacktrace_detection: true

Select an existing filter to add to this input. 

Note

In addition to the Kubernetes-specific filters that you can configure, you can also use universal filters, such as regex, that are applicable to most inputs.

You can use a filter to discard unnecessary logs or protect sensitive data. As a result, filters can help reduce the agent's resource load because of the reduced log ingestion.

To use a universal filter, you must: 

1. Create a filter
2. Add the filter to the input
3. Review the following example of how to add the regex-error-doc-example filter into a YAML file:

   filters:
   - name: regex-error-doc-example
     type: regex
     pattern: error|ERROR|ERR|Err

To learn more about universal filters, see Filters.

This parameter is optional.

Review the following example: 

filters: 
  - info 
  - not_trace 
  - mask_card 
  - mask_password

enrichments

You can use this parameter to enrich data with specified extracted fields. 

To learn how to enrich data from inputs, see Enrich Input Data.

This parameter is optional. 

Review the following example: 

enrichments:
        dynamic:
          field_mappings:
            # if the field value starts with "aws-instance" then instance metadata is get from aws ec2 instance.
            # for more info ref: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-data-retrieval.html
            - field_name: "instance_id"
              value: '{{".aws-instance.instance-id"}}'
            - field_name: "instance_type"
              value: '{{".aws-instance.instance-type"}}'