Recently, you have added the feature to send a webhook as alert method. Great feature that enables us (as implementation partner who wants to monitor multiple environments) to gather and centralize failures into a dashboard.
We would like to build dynamics links to navigate to failures in Alumio. For outgoing failures we can build a link to the tasks with filters on “status” and “updatedAt” which works great. However, for the incoming we are missing two elements:
In the logs of an incoming we would like to be able to filter on the status “failed”. Actually, this filter is usefull for all configurations that contains logs, so this might be implemented on a more generatic way and not only for incoming configurations.
In the data that is send via the webhook we are missing a timestamp of the “startedAt”. The logs do contain a timestamp:
Thank you very much for sharing your detailed feedback and feature request regarding the incoming logs.
We have forwarded your request to our Production team and asked them to assess the feasibility of including these enhancements in our backlog. We’ll be happy to update you once we have more information on the next steps or timeline.
If the team has any follow-up questions or requires further clarification, we’ll be sure to reach out.
Thank you for your patience. We’ve received confirmation from our development team that they’ve agreed to include the first point as a feature request.
The second point is a lot trickier due to the logic of our current alerts. We perform a query, and if there are results, we send an alert. If we include the logs that include the start date, we always get results, even if there are no errors.
Unfortunately, we can’t yet confirm when the mentioned feature request will be released. For your convenience, you can stay updated on new features and improvements through our Release Notes page.
