Page Comparison

Introduction

The tags beginning with {2-level parser name} dmp.commvault identify events generated by {product type} belonging to {Company-site} Commvault.

Valid tags and data tables 

The full tag must have {X} 4 levels. The first two are fixed as {2-level parser name}dmp.commvault. The third level identifies the type of events sent. The fourth level indicates the event subtype.

These are the valid tags and corresponding data tables that will receive the parsers' data:

For more information, read more About Devo tags.

How is the data sent to Devo?

Logs generated by Commvault must be sent to the Devo platform via the Devo Relay to secure communication. See the required relay rules below:

Rule for events with "AuditTrail: message"

• Source port - Any available port

• Source data - AuditTrail:

• Target tag - dmp.commvault.audit.event

• Target message - \\\\d0

• Stop processing - ✓

Rule for events with "Alerts: message"

• Source port - Any available port

• Source data - Alerts:

• Target tag - dmp.commvault.alert.event

• Target message - \\\\d0

• Stop processing - ✓

Table structure

These are the fields displayed in this table:these tables:

dmp.commvault.audit.event

timestamp(int(utc_timestamp_str, +"000"))

dmp.commvault.alert.event

ifthenelse(isnotnull(job_id_main), job_id_main, job_id_description)

ifthenelse(isnotnull(alert_name_main), alert_name_main, alert_name_description)

timestamp(int(utc_timestamp_str, +"000"))

join(msg_tok_sep, ", ")