KloudStack Observability for Azure

KloudStack Observability for Azure connects a WordPress site to Azure Application Insights, so you can see request performance, errors and browser telemetry in Azure Monitor alongside the rest of your Azure estate. The plugin is built specifically for WordPress hosted on Azure. It reads its configuration from App Service application settings automatically, names telemetry using the Azure site, slot and region so one Application Insights resource can serve many sites, and produces a telemetry schema designed to work with Azure Monitor workbooks. Features

• Server-side request telemetry with normalised route names
• Uncaught exception and fatal error telemetry
• Browser telemetry via the official Application Insights JavaScript SDK
• Correlation between browser and server telemetry using W3C trace context
• Automatic Azure environment detection — App Service, Container Apps, AKS and Virtual Machines
• Cloud role naming from the Azure site and deployment slot
• Configurable sampling to control Azure ingestion cost
• Privacy controls: IP anonymisation, query-string redaction, consent gating
• Built-in diagnostics self-test and WordPress Site Health integration

Designed for Azure This plugin assumes Azure hosting. It will run elsewhere if you supply a connection string, but Azure environment enrichment will be unavailable and support is limited to Azure deployments. Performance Telemetry is buffered during the request and transmitted only after the response has been released to the visitor, so Application Insights latency or availability never affects your site's response time. A circuit breaker suspends transmission if the ingestion endpoint becomes unreachable. Trademarks Azure, Microsoft Azure and Application Insights are trademarks of the Microsoft group of companies. This is an independent plugin and is not affiliated with, endorsed by, or sponsored by Microsoft.

2.0.6

• The Debug log setting now says plainly that it does nothing on its own, and names the define( 'WP_DEBUG', true ); line that has to be added to wp-config.php for it to take effect.

2.0.5

• The plugin no longer writes a log file of its own. Debug output is handed to WordPress via error_log(), so WP_DEBUG_LOG decides where it lands. The setting itself is unchanged.

2.0.4

• The debug log filename now carries a per-site random suffix. The .htaccess written beside it denies direct access on Apache, but nginx ignores .htaccess entirely, so on those servers a fixed, identical-everywhere filename was guessable and the log fetchable. Both guards are kept.

2.0.3

• Hosting platform management API calls are excluded from request telemetry, alongside the health probe. These are the host calling the site rather than the site's own traffic, and being slow by nature they dominated the slowest-routes report.

2.0.2

• Health probe exclusion now also matches sites using plain permalinks, where the same route is reached as /?rest_route=/custom/v1/healthcheck rather than /wp-json/custom/v1/healthcheck.

2.0.1

• Telemetry is now OFF by default and must be enabled by the site owner. Nothing is transmitted until you turn it on, in line with WordPress.org guidelines 7 and 9.
• The settings screen now states plainly when telemetry is off and nothing is being sent.
• The debug log is written to a protected kloudstack-azure-observability folder inside the uploads directory, resolved with wp_upload_dir(), instead of the uploads root.
• The browser SDK snippet is registered through wp_add_inline_script() rather than emitted as a raw script tag.
• Hosting platform health probes are excluded from request telemetry. On a low-traffic site these could account for over 99% of recorded requests, hiding the site's real traffic and adding needless ingestion cost.

2.0.0

• Initial public release.