ECS Container (AWS) Inputs

George Alpizar
George Alpizar
  • Updated

AWS ECS (ECS Containers)

Overview

This input type allows you to specify a set of ECS assets (tasks, containers, etc.) for Edge Delta to monitor.


Review Sample Configuration

Review the following sample configuration:

  ecs:
    - labels: "errorcheck"
      include:
        - "container-name=myecho,task-family=test-task,task-version=2"
      exclude:
        - "container-name=.*xray.*"

Review Parameters

Review the following parameters that you can configure in the Edge Delta App. 


labels

Required

Enter a descriptive label for this input. 

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

errorcheck is the default label.

Review the following example: 

- labels: "errorcheck" 

include

Optional 

Enter the ECS assets 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 ECS Exclude field takes precedence over the ECS Include field. 
  • For the ECS Include and ECS Exclude parameters, note that if the value you provide after container-name= or task-family= is contained anywhere in the pod or namespace name, then the value will match.

Review the following example: 

include:
  - "container-name=myecho,task-family=test-task,task-version=2"

exclude

Optional 

Enter the ECS assets 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 ECS Exclude field takes precedence over the ECS Include field.
  • For the ECS Include and ECS Exclude parameters, note that if the value you provide after container-name= or task-family= is contained anywhere in the pod or namespace name, then the value will match.

Review the following example: 

exclude:
  - "container-name=.*xray.*"

auto_line_detection

Optional

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

Review the following example: 

auto_detect_line_pattern: true

boost_stracktrace_detection

Optional

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

Review the following example: 

boost_stacktrace_detection: true

filters

Optional 

Enter an existing filter to add to this input. 

To learn how to create a filter, see Filters.

Review the following example: 

filters: 
- info
- not_trace
- mask_card
- mask_password

late_arrival_handling

Optional

You can use this parameter to configure how to accommodate delayed data. 

Specifically, you can use the ignore_after parameter to configure when to ignore metrics or pattern logs.

For example, for ignore_after, if you enter 15m, then the input will ignore logs whose timestamp is older than 15 minutes. 

Review the following example:  

late_arrival_handling:
  rule_metrics:
    ignore_after: 15m
  patterns:
    ignore_after: 4h
    report_with_original_timestamp: true

 

Share this document