web stats
Mirth Community - View Single Post - New here! Question about alerts.
View Single Post
  #2  
Old 10-31-2017, 08:26 AM
narupley's Avatar
narupley narupley is offline
Mirth Employee
 
Join Date: Oct 2010
Posts: 7,124
narupley is on a distinguished road
Default

One thing to check out if you haven't already is the User Guide, which was recently overhauled.

In case you weren't aware, our business model is a core product that is open source, supplemented with a commercial license that includes helpdesk support, monthly Q&A webinars with the Mirth Connect dev team, and access to commercial extensions among other things.

One of those extensions is Advanced Alerting, which goes beyond the simple error-based alerts and adds metric-based threshold and "sliding window" type alerts that allow you to create complex trigger conditions.

For example, an alert that triggers when the number of incoming messages is 100 or less for an hour would look like this:



There are other advanced trigger types too like Threshold (alert when certain stat is greater than some amount for some period), Deployed State (alert when a channel state is, say, Stopped for X amount of time), and the recently added SSL Certificate Validation trigger type which works in conjunction with the SSL Manager extension to trigger when a certificate has expired or has been revoked / rejected.

In addition to the advanced trigger types, Advanced Alerting allows you to set various Escalation Levels and Action Groups so you can choose to alert different groups of people based on different periods in the alert lifecycle. Maybe alert Tier 1 support at first, but escalate to Tier 2 if the issue hasn't been resolved for an hour, etc. You can set Do Not Disturb periods for each group too... maybe some groups you only want to be alerted during business hours for example.
__________________
Step 1: JAVA CACHE...DID YOU CLEAR ...wait, ding dong the witch is dead?

Nicholas Rupley
Work: 949-237-6069
Always include what Mirth Connect version you're working with. Also include (if applicable) the code you're using and full stacktraces for errors (use CODE tags). Posting your entire channel is helpful as well; make sure to scrub any PHI/passwords first.


- How do I foo?
- You just bar.
Reply With Quote