This input will return the configuration information for each alert that exists in the specified environment.
Note: to get the information of any alerts that have actually been triggered, check out the ‘triggeredalerts‘ input.

Splunk events

Sourcetype: mulesoft:mulesoftalerts

Timestamp: time that data was received by Splunk

Sample event:

{"id": "094ea754-c359-4768-afe2-ff7bdcbfc346", "name": "deployment", "severity": "INFO", "enabled": true, "organizationId": "b02e9361-b9f6-4fa6-9054-62e52526543d", "environmentId": "7345beef-70cb-4387-b26d-2534486a5b98", "lastModified": 1622111811340, "createdAt": 1622111811340, "isSystem": false, "productName": "runtime-manager", "condition": {"resources": ["*"], "type": "deployment-success", "resourceType": "cloudhub-application"}, "actions": [{"subject": "${severity}: Deployment Success", "userIds": ["b7a0b83f-8b8a-4c3c-ae30-0a07ee11d928"], "type": "email", "content": "Hello,\nYou are receiving this alert because:\nThe deployment of the application ${resource} has succeeded.\nPlease see${resource} for more details."}], "conditionType": "deployment-success"}

About this input

This input calls the URL:

Using the parameters:

One event will be created for each alert represented in the returned JSON object

Learn more: Mulesoft documentation

Posted by:Andrew MacLeod

Andrew is a certified Splunk Admin and has worked for iDelta for over two years. Previously, he worked as an actuarial analyst in the life and pensions industry - a role that he was in for over 7 years before deciding to embark on a career change into the IT industry. He holds an MPhys degree in theoretical physics from the University of Edinburgh. Outside of work he is a big puzzle fan, with a particular penchant for things cruciverbal and mathematical.