Azure - Logs loading slow

When loading logs in Azure, especially over a longer time span like one month, there are several factors that can affect performance and loading times. Here are some considerations and steps you can take to improve the situation:

1. Time Span of the Query: When querying logs for a longer duration, the system may need to process more data, which can lead to slower load times. Azure's system might scan more than the specified time range due to how it partitions data. For example, if you request logs for 30 days, the system may scan additional days to ensure all relevant records are included.
2. Query Optimization: Ensure that your queries are optimized. Avoid querying excessively large datasets without filters. If possible, break down your queries into smaller time ranges to reduce the load on the system.
3. Data Latency: Be aware that there can be latency in log data ingestion. Depending on the Azure service, logs may take time to become available for querying. For activity logs, they are typically available for analysis within 3 to 20 minutes after they are generated.
4. Resource Logs: If you are also querying resource logs, be aware that they can add additional latency. Some services report logs at intervals which may affect how quickly you can retrieve them.
5. Check for Errors: If logs are not loading as expected, check for any error messages or indications that might suggest issues with the query or the service itself.

By considering these factors and possibly adjusting your query strategy, you should be able to improve the loading times for your logs in Azure.

References:

• Log data ingestion time in Azure Monitor
• Optimize log queries in Azure Monitor