Improve web app user happiness by optimizing database speed with Microsoft Azure logs.

Improve customer satisfaction for web apps by optimizing database performance using logs from Microsoft Azure

Owners of web apps should always prioritize customer pleasure. A fast and highly responsive user interface is crucial for consumer happiness. The databases that support these apps are now frequently run as managed services by cloud providers, as cloud applications have become the norm. Because logs, analytics, and traces aren’t always put together in context, and you don’t have access to the underlying hosts, optimizing cloud services can be difficult.

Optimize database performance

A database’s most fundamental feature is that it’s continually busy with user requests—not only do stored datasets change, but so do the queries used in web applications. Small database changes can have a significant influence on overall application performance. Analyzing the sluggish query log is a basic yet practical approach to testing high-performance databases. This log file keeps track of all queries that have surpassed a pre-determined (manually) time limit.

It’s simple in on-premises settings, but when SQL is run as a managed service in the cloud, access to the underlying host is usually impossible. Despite this, logs are typically available on cloud consoles, albeit records alone are insufficient for helpful analysis.

​​

One place to rule them all

All data required for a particular study should ideally be available in one location: all relevant logs should already be established in context with related telemetry. Having all of this information extracted and accessible saves time and gives sense to unstructured data.

Enable agentless log ingestion

You must create additional resources in your Microsoft Azure account to enable agentless log ingestion. All you have to do now is run the script we’ve created. Everything on GitHub is open-sourced, making it transparent and safe to use.

You can choose which logs to forward after installing the forwarding components. You may increase the threshold for slow query logging in the Azure Database for MySQL, and you can add an option to send MySqlSlowLogs to an event hub in the Diagnostics settings of your database instance.

Use custom metrics based on logs for constant optimization

To demonstrate the value of custom metrics based on logs, assume your web application is increasing slowly over time. This drop in performance is recognized, and an automatic root cause analysis is run, exposing some queries on a managed cloud service database that are running slower than expected.

The sluggish query log is required for the subsequent analysis.

You can use facets and the timeframe during which the incident happened to filter for sluggish query log entries in your database in the Dynatrace log viewer. Can rapidly recognize faulty queries and can take corrective actions.

You may also develop a measure that collects information about your slow queries to figure out which ones need to be improved.

Log monitoring beyond cloud platform databases

For most Microsoft Azure platform services, you can send resource-specific logs and audit logs via the EventHub. For easy troubleshooting, records are linked to the entities you’re watching. For example, if your App Service has a high Failure rate, you can go straight to the log viewer by selecting the Logs icon. The log viewer automatically creates filters for your resource, allowing you to diagnose the issue quickly.

Enteros

About Enteros

IT organizations routinely spend days and weeks troubleshooting production database performance issues across multitudes of critical business systems. Fast and reliable resolution of database performance problems by Enteros enables businesses to generate and save millions of direct revenue, minimize waste of employees’ productivity, reduce the number of licenses, servers, and cloud resources and maximize the productivity of the application, database, and IT operations teams.