Skip to main content
New Idea

Making Alerts Better

Related products:Freshservice
  • March 28, 2025
  • 4 replies
  • 89 views

mbutler
Top Contributor ⭐
Forum|alt.badge.img+10

I hope it’s just a matter of time, but I’d rather document it here. I am working with alerts - bringing in more and more tools into the alerts, but I hit a major snag. I’d like to re-title the alert based on metrics that come in from the alert itself. While I could associate a ticket and then modify the ticket, I’d really like to modify the alert. I think the problem here might be the aggregation algorithm - that may be why this isn’t even an option.

Unfortunately, I haven’t found a way to do this. Moreover, it appears I cannot perform a PUT on an existing record. The API documentation doesn’t say it is possible, so I thought I would try, but it wouldn’t work. The only thing I can do is POST a new note to the alert.

Why?

They say a picture is worth a thousand words. Here’s an alert that I just setup. This is a notification of unmanaged assets in my environment. Here’s the problem, I would have to click on every one of these in order to find the asset I want to look at. I want to modify the subject so the alert is useful and makes it quicker for me to look at. Otherwise, it’s useless.

Workaround?

For right now, I could create a ticket for each alert. I’ll then be able to change the associated ticket with an HTTP PUT request via the API. This isn’t ideal - I shouldn’t have to hit the API to do such a thing - again, I think about the people coming after me. While this isn’t technically difficult, not everybody has API experience like I do. Many who will come behind me may not - it would be best if we could make this as user-friendly as possible in the Workflow Automator

4 replies

mbutler
Top Contributor ⭐
Forum|alt.badge.img+10
  • Author
  • Top Contributor ⭐
  • March 28, 2025

Shameless plugs: ​@Medic1334 ​@Daniel Söderlund ​@msconfig87 


Medic1334
Top Contributor ⭐
Forum|alt.badge.img+9
  • Top Contributor ⭐
  • March 28, 2025

All about updating the API to be able to do more but… why not just change your source email/notification method so that it is including information about the device, and then you are able to parse that out uniquely and pass it over to the ticket that is created?

The way I’ve built out alerts for our org is a way to minimize noise for agents, and allow for reruns of processes that fail to go into the same alert so that paging doesnt happen as the process is worked to resolution.


mbutler
Top Contributor ⭐
Forum|alt.badge.img+10
  • Author
  • Top Contributor ⭐
  • March 28, 2025

All about updating the API to be able to do more but… why not just change your source email/notification method so that it is including information about the device, and then you are able to parse that out uniquely and pass it over to the ticket that is created?

The way I’ve built out alerts for our org is a way to minimize noise for agents, and allow for reruns of processes that fail to go into the same alert so that paging doesnt happen as the process is worked to resolution.

I’m with you - unfortunately, this is a limitation of the application sending the alert to FreshService.  That application doesn’t have a way to substitute in fields, so I have a static subject line. There’s no way to substitute those fields.

The end user of this alert wants each alert turned into a ticket. So, this may actually work out to my favor. Earlier today, I configured it so it will create a ticket when the alert is received. I have aggregation setup, so it shouldn’t create multiple tickets for the same alert. I will be doing some additional testing today. I’ll keep you all posted.


Medic1334
Top Contributor ⭐
Forum|alt.badge.img+9
  • Top Contributor ⭐
  • March 28, 2025

If your source has you hamstrung for notification contents you can't do much more unfortunately.

We had a similar experience with our SQL agent job alerting process. The messages it sends on task failure apparently cannot be customized with SSMS/SSIS so we had to do our priority assignment based on job name as that and the job status were the only dynamic fields (and job status is only failed or completed :(). I am finding a way around this, but it's going to involve having to migrate our existing processes into our automation software (OpCon) which is probably for the better long term, just have to be able to convince the business we need the time to do that so we have better info.