Visualization in Azure Monitor needs improvement. Adding more features to it would also make the solution better.

We are sometimes confused about the details. We would like to have a flow in terms of how a new application should engage with Azure Monitor. We must understand: what is the most crucial part of our monitoring or support? We are not very good at it yet. 

Currently, it seems it's complicated to get the correct information in terms of what to do and how things work. Maybe it would help if they offered some guidance or written guides. For example, we say that project manager should follow their quality issues before putting the application into production. It's so complicated from their side for the project managers. Some kind of simplification is required for people engaged in the platform. 

Still, it's very new, and we will be gaining experience, and we may see much more substantial things in the future as we uncover more capabilities.

Azure Monitor could improve the visualization aspect and integrate better with other third-party services.

They need to work with other cloud providers - not just Azure. We'd like them to work with clouds such as GCP, AWS, and Alibaba, for example. 

Azure Monitor is a complex product because you can use it to monitor different things, and that could be an area for improvement. Having templates by Microsoft added to it is another area for improvement.

What I'd like to be added in the next release of Azure Monitor is an overview of best practices from Microsoft and what they'd recommend users to monitor.

Assigning an alert is another feature I'd like to see in the next release of the solution. Currently, you can't assign an alert to anyone, if a server crashed and you need to assign that alert to a specific team, it's not possible.

If Azure Monitor wants to compete with other APM products in the industry, it has to stitch together the information and user flow. It also needs to provide all the information, as you get with Stock Trace, including details related to where the call came from and where the problem lies. That's what we'd like to see. With a solution like Dynatrace, you have a clear path and you know which calls were made before and after the problem, and where the issue occurred. That feature is lacking in Azure Monitor.

If it is configured incorrectly, you can end up with a huge bill. Sometimes, a lot of data is collected and stored, and we may get charged for that kind of storage which is an issue.

I'd like the solution to do more around vulnerability assessment. It's lacking in the product right now.

It's difficult to say as I only use a small part of this solution; however, It can be quite difficult to use at times. I think there are better solutions available. 

In my opinion, they should improve the overall user experience, especially when it comes to indexing and searching collective logs. The search language they've developed is quite difficult to understand. 

Azure Monitor could improve network performance monitoring and make it more advanced.

This solution could be improved with more out-of-the-box functionalities and artificial intelligence to complete event correlation.

The solution should have cross-connection or cross-communication between tech partners. For example, it should be able to read the logs in the database and GCP environment by enabling a couple of hooks to collect information from cloud vendors to Azure Insights.