Configure Events

You can use the appdynamics-collectors Helm chart (collectors-values.yaml) to modify the events configuration and exclude any specific type of event. The event types that are excluded are not monitored.

The events are enabled by default. If you require to exclude events so that the collector does not collect the specific type of events, configure the required parameter in the collector configuration (collectors-values.yaml) file, then upgrade the helm release with the updated values:

clustermonConfig:
  events:
    enabled: true
    severityToExclude: []
    reasonToExclude: []
    severeGroupByReason: []

YML

To choose which events you require to exclude, configure the following parameters:

Parameter	Value	Result
severityToExclude	You can specify any of the following values: Normal Warning Severe	This excludes the specified type of events. For example, if you specify Normal, all the events of the normal (informational) type are not displayed on the UI.
reasonToExclude	You can specify the list of Kubernetes event reasons. For the list of some of the reasons, see Events Reason Reference.	This excludes the events that have the specified event reasons.
severeGroupByReason	You can specify the list of Kubernetes reasons that you want to observe as critical or severe. This value can be customized by using the required reason. For the list of some of the reasons, see Events Reason Reference.	This displays the events as severe when the event includes the specified event reasons.
Example `events: enabled: true severityToExclude: [Normal] reasonToExclude: [BackOff, Started] severeGroupByReason: [Failed, Evicted]` YML

For details about configuring the collectors-values.yaml file, see Cisco AppDynamics Collectors Settings.