In this use case, the customer has a a very long application log event message that does not have a clear column definition (meaning the column separators such as , . or space cannot be used reliably), and needs to extract some crucial information to use in variables to put these into a meaningful alarm message.
To further explain the use case, a sample of the event structure:
" Alert:Data Protection, Job <status> CommCell: <system> Client: <hostname> Application:<application with spaces> Subclient: <system> Backup set: <name> Instance: <hostname> MediaAgent: <name with spaces> Storage Policy: <name> Library: <name> User:<username> DA Description:<status> Criteria: <result> , Client: <hostname> , Agent Type: <application>, Instance: <hostname>, Backup Set: <name> , Subclient: <system> , Status: <status>, Job ID: <INT>, Error Code: <error>, Failure Reason: <message> "
Due to the nature of some of the values, you cannot use the column function to set your variable value. Instead, you would need to use a regex to find the value (s) you need and then be able to put these into a meaningful alarm message.