The benefits that IT teams can expect out of this:
1. Reduce noise - Group similar alerts from the same server together under a single work item(incident).
2. Full context of the issue from a single view - Freshservice will automatically associate the asset to the incident so that the agent can get the whole context from one view.
3. Automatic Routing and prioritization - Set up rules based on which the tickets created through these alerts will be prioritized correctly and routed to the right agent groups.
4. Auto closure of tickets - The ticket will be automatically resolved based on the status of the latest alert for that ticket. ex. If an alert was triggered due to a sudden spike, a new ticket is created and then the utilization might go back to normal, in this case this ticket will be auto-closed by Freshservice.
Below: a ticket created through an alert. You can also see the recent alerts grouped together under the same ticket.
PS: this is version 1 and we will continue to build on top of this.
If you are interested to know more, please feel free to comment below and I will reach out to you.
+1 interested here !
I am interested too.
we would be interested in learning more.
Having just started with freshservice, I am desperately lacking this Feature as I send our Nagios notifications to the Helpdesk. If the email processing would be able to do some regexp, that would be a good start.
Agreed, we use PRTG and would have a great use for aggregating our alerts and taking action. Please let us know how we can get involved.
Interested to hear how this progresses. We need to bring in network devices to the Freshservice database for asset management purposes.
would LOVE this, when's the beta??
I am also keen on this feature, when will this go live?
We are also very interested in this functionality. When could it be available?