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.

Have the pie graph widget display the number within the segments of the graph without having to hover over it.

AMS should incorporate the FIM/MIM reporting currently used for health checks on support contracts.

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 

I believe that the dropdowns on Monitor could do with some minor changes, in particular:

1. user-select: none;
2. cursor: pointer;

Before:

After:

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..  

Various Reports should be available as part of AMS which would be targetting users in different levels:

1. Business Users
2. Operational Support
3. Management
4. etc.

Please consider creating a data agent that performs http get(s) and pipes the json response to ingress api.

Use case I'm looking at is Azure DevOps, retrieving repositories; then for each repository retrieving the most recent commit date.

If a query returns a large dataset, the whole dashboard will freeze in an attempt to render the widgets.