I have a request from a customer that asks "Really want to stress that time range should be configurable so that we can make the changes without needing any modification to actual report/dashboard"
In conversations what was described was a slider where by you can select the time range which updates the associated dashboard metrics.
This would differ from the existing functionality where by you select the drop down and choose a pre-configured time range.
UNIFYMonitor was developed to act as a branded portal to host content driven by PowerBI and Azure. While working on a client who has requirements for alert monitoring through UNIFYMonitor it was raised that the alerts we deliver to the client are branded and sent from Microsoft Azure. It would be preferable if the alerts, like our dashboards, are branded as UNIFY products.
The Log Analytics team have stated (here) that they plan on incorporating email/sms templates into the platform; however, there is no stated timeline or information on what level of customisation will be available.
Alerts have several forwarding options when triggered, including the ability to send json to Azure Functions, making it relatively easy to send data to any forwarding service we may configure/develop.
In the case of this project work we plan on using Ivanti as a tool to reformat and forward the alerts we send via Azure Log Analytics.
This item has been roadmapped for the current project.
The following error us displayed when attempting to add a new email notification to an alert trigger:
[UAR-400]Error occurred while attempting to update alert trigger '131'
The notification is not added as a result.
The same error is shown when copying or importing an alert trigger which has at least one existing email notification.
This has been fixed and released to production.
AMS should incorporate the FIM/MIM reporting currently used for health checks on support contracts.
UNIFYMonitor will provide an SDK for end services to integrate.
When testing login/logout functionality in applications, there should be a low level verification that the login was as expected such as checking SAML messages, id tokens etc
Thanks for the suggestion, Ravneel. I've added this to the backlog.
The ability to import updated dashboard configuration over the top of an existing dashboard. This will allow the user to modify the dashboard JSON and upload it over the existing config rather than creating a new dashboard with the updates and deleting the old dashboard.
I believe that the dropdowns on Monitor could do with some minor changes, in particular:
- user-select: none;
- cursor: pointer;
This item will likely be not applicable with the new project, and is not worth fixing for the current solution.
Currently the clients logo is presented in the dashboard. There is an undefined issues where-by the logo sometimes doesn't appear. To remove this issue altogether it would be best to remove the logo element from the dashboard granting more real estate for other metrics. The logo is still a nicety so It would be good to show it near the name of the client dashboard at the top of the screen or perhaps in place of the name..
This functionality has been added and is now live in the production site of monitor. There is now an action on the operations team to remove the logo tiles from the dashboards to create space for other more useful metrics
Customer support service by UserEcho