Send the actual alertID back via the alert message for API usage
Yeah, that sounds suboptimal for what we are publishing now in our APIs. Well figure out a better solution....
Forum Discussion
Currently, the alert ID sent through with the alert is the LM... one, which apparently is not the one used to acknowledge the alert via the API. Instead, you have to call the API method to get the list of alerts for that particular host, then use the alertID which comes back with this response to ack the alert. This is an unnecessary overhead, and I still do not have an answer on how you work out which of the alerts you want to ack if more than one datasource is currently alerting on a host.
Please could the alert just include the actual alertId, which can then be used directly to acknowledge via the API.
Many thanks
