JonathanD Posted April 27, 2017 Posted April 27, 2017 Hi - I'm trying to automate creation of an incident upon receipt of an email from our monitoring system. I've looked at the webinar, created a routing rule that looks for a particular text string and have emailed in a few test emails containing said string but I can't get it to work. We do have a bit of customized setup in that we add customers as linked connections upon logging a call so I'm a bit worried that our particular config is inhibiting this functionality ? Thanks for any help, Jonathan
Steve Giller Posted April 27, 2017 Posted April 27, 2017 I think you need body LIKE '%Transaction Failure%' in the Rule Expression
Victor Posted April 27, 2017 Posted April 27, 2017 @JonathanD as @DeadMeatGF suggested, you would need a different operator (the LIKE operator) if you want to match a specified pattern in a string (text). Using equal (=) in the rule expression means that you instruct the routing rule to "hard" match, in other words match the field with the whole value, rather than searching for that value in the field you specified (body, subject, etc...). Alos make sure the syntax is correct, for example "bodysubject" is an invalid field, it needs to be either "body" or "subject"...
JonathanD Posted April 27, 2017 Author Posted April 27, 2017 ah great - thanks guys for the responses.. I've changed the string as recommended but still can't see an incident being raised.. is there a log file or something I can access to try and figure out where this might be stuck ?
James Ainsworth Posted April 28, 2017 Posted April 28, 2017 Hi @JonathanD, I just wanted to check that you have the routing rules enabled. There are also some logs that can be looked at in Administration under System->Monitor->Log Files Have a look at the EspMailService.log and the EspServerService.log. There are some filters when viewing the logs and you will want to select to show Emergency, Alert, Critical, and Error. A lot goes through these logs so you will want to monitor this as an email arrives. For testing purposes you can create a very simple Rule Expression to match something basic in an incoming test email. This way you can eliminate if the rules expression is causing the issue or not. Regards, James
JonathanD Posted May 2, 2017 Author Posted May 2, 2017 Thanks James - surprise, surprise, having switched it on.. that rule now works !! (Doh).. How can I ensure that the text of the email is automatically included in the incident description ? I can't seem to see it in there at the moment.. Cheers, Jonathan
Victor Posted May 2, 2017 Posted May 2, 2017 @JonathanD when autoresponder raises a request, the email subject is put as incident summary and email body as incident details... This is not working for you? (I had a look in the logs, I can't see any request where this failed)... Btw, the logs screenshot you posted are not relevant for this, the autoresponder actions are recorded into server service logs...
JonathanD Posted May 2, 2017 Author Posted May 2, 2017 Hi Victor.. ok, so I have the subject line inserted properly into the incident description, however I can't see the message body anywhere.. Is there a config option I'm missing here somewhere ? Cheers, Jonathan
Victor Posted May 2, 2017 Posted May 2, 2017 @JonathanD it's stored in the details section. Click on the Details bar and it should expand. You also have a pin you can enable to have the detail section expanded by default...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now