Wording only \u2014 the Debug log setting now explains that WP_DEBUG must be enabled separately.<\/p>","2.0.5":"
Debug output now goes to the WordPress debug log instead of a file in uploads. Any log left by an\nearlier version can be deleted.<\/p>","2.0.4":"
Hardens the debug log against direct access on servers that ignore .htaccess, such as nginx.<\/p>","2.0.3":"
Excludes hosting platform management API calls from telemetry.<\/p>","2.0.2":"
Fixes health probe exclusion on sites using plain permalinks.<\/p>","2.0.1":"
Telemetry is now off by default. After updating, enable it on the settings screen if you want data\nsent to Azure. Existing sites that already had it enabled keep their setting.<\/p>","2.0.0":"
Initial public release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3646533,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3646533,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3646533,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3646533,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["2.0.6"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3646533,"resolution":"1","location":"assets","locale":"","width":1742,"height":1703},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3646533,"resolution":"2","location":"assets","locale":"","width":1750,"height":2552}},"screenshots":{"1":"Settings \u2014 connection, telemetry, privacy and advanced controls in one screen. On Azure the connection string is read from the hosting environment and shown read-only.","2":"The built-in diagnostics self-test \u2014 checks configuration, the Azure environment, outbound connectivity and a live round-trip to Azure through the real transport path, with a copy-paste report for support."}},"plugin_section":[],"plugin_tags":[8093,13289,5603,248562,32683],"plugin_category":[54],"plugin_contributors":[275618],"plugin_business_model":[],"class_list":["post-350328","plugin","type-plugin","status-publish","hentry","plugin_tags-application-insights","plugin_tags-azure","plugin_tags-monitoring","plugin_tags-observability","plugin_tags-telemetry","plugin_category-security-and-spam-protection","plugin_contributors-kloudstack","plugin_committers-kloudstack","plugin_support_reps-pauljohnstone"],"banners":{"banner":"https:\/\/ps.w.org\/kloudstack-azure-observability\/assets\/banner-772x250.png?rev=3646533","banner_2x":"https:\/\/ps.w.org\/kloudstack-azure-observability\/assets\/banner-1544x500.png?rev=3646533","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/kloudstack-azure-observability\/assets\/icon-128x128.png?rev=3646533","icon_2x":"https:\/\/ps.w.org\/kloudstack-azure-observability\/assets\/icon-256x256.png?rev=3646533","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/kloudstack-azure-observability\/assets\/screenshot-1.png?rev=3646533","caption":"Settings \u2014 connection, telemetry, privacy and advanced controls in one screen. On Azure the connection string is read from the hosting environment and shown read-only."},{"src":"https:\/\/ps.w.org\/kloudstack-azure-observability\/assets\/screenshot-2.png?rev=3646533","caption":"The built-in diagnostics self-test \u2014 checks configuration, the Azure environment, outbound connectivity and a live round-trip to Azure through the real transport path, with a copy-paste report for support."}],"raw_content":"\n
KloudStack Observability for Azure connects a WordPress site to Azure Application Insights, so\nyou can see request performance, errors and browser telemetry in Azure Monitor alongside the\nrest of your Azure estate.<\/p>\n\n
The plugin is built specifically for WordPress hosted on Azure. It reads its configuration from\nApp Service application settings automatically, names telemetry using the Azure site, slot and\nregion so one Application Insights resource can serve many sites, and produces a telemetry\nschema designed to work with Azure Monitor workbooks.<\/p>\n\n
This plugin assumes Azure hosting. It will run elsewhere if you supply a connection string, but\nAzure environment enrichment will be unavailable and support is limited to Azure deployments.<\/p>\n\n
Telemetry is buffered during the request and transmitted only after the response has been\nreleased to the visitor, so Application Insights latency or availability never affects your\nsite's response time. A circuit breaker suspends transmission if the ingestion endpoint becomes\nunreachable.<\/p>\n\n
Azure, Microsoft Azure and Application Insights are trademarks of the Microsoft group of\ncompanies. This is an independent plugin and is not affiliated with, endorsed by, or sponsored\nby Microsoft.<\/p>\n\n
This plugin sends data to Microsoft Azure Application Insights, a third-party service operated\nby Microsoft. It does this so that telemetry collected from your site can be stored, queried and\nvisualised in Azure Monitor.<\/p>\n\n
What is sent, and when:<\/strong> on each non-excluded page request, the plugin transmits the request\nroute, duration, HTTP response code, and contextual data about the WordPress installation\n(WordPress version, PHP version, active theme, plugin count, memory usage, query count) to the\nApplication Insights ingestion endpoint configured for your Azure resource. Uncaught exceptions\nand fatal errors are transmitted with their message, type and stack trace. If browser telemetry\nis enabled, the Application Insights JavaScript SDK is loaded in visitors' browsers and sends\npage views, AJAX calls and JavaScript errors directly to the same endpoint.<\/p>\n\n Nothing is sent until you turn it on.<\/strong> All telemetry is off by default. On a fresh install the\nplugin transmits nothing at all \u2014 not server-side request data, and not browser data \u2014 until you\nenable it on the settings screen. Browser telemetry is a second, separate opt-in: no JavaScript\nSDK is loaded and no visitor data is collected in the browser unless you enable that as well.\nServer-side telemetry additionally requires an Application Insights connection string; without\none, nothing leaves your site regardless of the settings.<\/p>\n\n Visitor data:<\/strong> client IP addresses are anonymised before transmission by default. Query\nstrings are redacted against an allowlist by default. Request and response headers, which may\ncontain cookies and authorization data, are not<\/strong> transmitted unless you explicitly enable\nthat option.<\/p>\n\n Cookies are off by default.<\/strong> When you enable browser telemetry it runs in cookie-less mode,\nso the SDK sets no The trade-off: without those cookies Application Insights cannot group requests into sessions or\ndistinguish returning visitors, so reports show page and dependency timings but not<\/strong> \"users\"\nor \"sessions\". If you need that aggregation, turn cookie-less mode off in Settings \u2014 but the\ncookies then require visitor consent in most jurisdictions, and obtaining it becomes your\nresponsibility. A Endpoints contacted:<\/strong> the Application Insights ingestion endpoint from your connection string\n(typically Microsoft terms of use: https:\/\/azure.microsoft.com\/support\/legal\/\nMicrosoft privacy statement: https:\/\/privacy.microsoft.com\/privacystatement<\/p>\n\n No data is sent to KloudStack. The plugin does not phone home.<\/p>\n\n\n Yes. The plugin sends telemetry to an Application Insights resource in your own Azure\nsubscription. Azure charges for telemetry ingestion and retention apply under your Azure\nagreement.<\/p><\/dd>\n No. Telemetry is transmitted after the response has been released to the visitor, so Azure\nlatency does not affect page load time.<\/p><\/dd>\n If you use full-page caching, cached responses are served without running PHP, so no server-side\nrequest telemetry is produced \u2014 while the browser SDK still fires. This is expected.<\/p><\/dd>\n Yes. Each site reports a distinct cloud role name, derived from the Azure site name or set\nmanually in settings.<\/p><\/dd>\n\n<\/dl>\n\n\nai_user<\/code> or ai_session<\/code> cookies and, in most jurisdictions, no visitor\nconsent obligation arises from using it.<\/p>\n\nkloudstack_obs_has_consent<\/code> filter is provided so a consent management\nplatform can gate injection.<\/p>\n\nhttps:\/\/<region>.in.applicationinsights.azure.com<\/code> or\n https:\/\/dc.services.visualstudio.com), and https:\/\/js.monitor.azure.com<\/code> for the JavaScript\nSDK unless the bundled local copy is selected in settings.<\/p>\n\n\n
APPLICATIONINSIGHTS_CONNECTION_STRING<\/code> to your\napplication settings. The plugin will detect it automatically.<\/li>\n\n
Do I need an Azure subscription?<\/h3><\/dt>\n
Does this slow down my site?<\/h3><\/dt>\n
Why do my browser page views outnumber my server requests?<\/h3><\/dt>\n
Can I use one Application Insights resource for several sites?<\/h3><\/dt>\n
2.0.6<\/h4>\n\n
\n
2.0.5<\/h4>\n\n
\n
2.0.4<\/h4>\n\n
\n
2.0.3<\/h4>\n\n
\n
2.0.2<\/h4>\n\n
\n
2.0.1<\/h4>\n\n
\n
kloudstack-azure-observability<\/code> folder inside the\nuploads directory, resolved with wp_upload_dir(), instead of the uploads root.<\/li>\n2.0.0<\/h4>\n\n
\n