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
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.
The form for creating a new dashboard shows the account id. Would be a cleaner user experience if the account display name was shown.
Widgets imported with the same widget Id will share data. Reloading one widget will update both with the same results regardless of whether the queries are different.
A request has come in from a customer to have a funnel chart type which included drill down capability. I have explained to the customer that it is not current functionality but have submitted it as feedback in this topic.
I imagine the intended functionality would display a metric at the top of the funnel i.e. total errors -> then funnel down to say total 500 errors -> then say to total 500 errors in NSW -> then clicking on that would display the grid view of all the 500 errors for NSW users.
This functionality I Imagine would work somewhat like the summarize function does https://docs.microsoft.com/en-us/azure/data-explorer/kusto/query/summarizeoperator by taking total data and aggregating it to a simpler metric
Having a hard limit on the number of results returned in a query preview (or, as a dropdown) would reduce load on the UNIFYMonitor service while people are building dashboards. Currently there's no limit, so if people don't set one in their query then it will return all rows available to that query.
Alongside that, having the ability to display a count of displayed records & how many would have returned (IE Displaying 1000 records of 50,000 possible) would allow people to ensure their queries are returning expected results, without needing to return all possible rows.
Customer support service by UserEcho