Since Solr is a Java application, you can instrument it using the Application Insights Java Agent, following these steps:
Download the Application Insights Java agent from the official GitHub repository releases page.
Copy the downloaded agent on the Azure VM where your Solr instance is hosted.
Add the -javaagent to your Solr application's JVM arguments, ...
This is also a bug in Sitecore 9.1 update 1. I have raised it as a ticket with Sitecore support and they have provided a bug reference 291373. Development of the hotfix is in progress.
I note that in the hotfix mentioned above, 2 of the files are not present in the /bin folder of 9.1.1. The missing files are:
We have raise this problem to the Sitecore Support which generated a ticket #527731 (Please use this ticket# if you have the same issue)
IMPORTANT: The following approach does not work without the hotfix provided by Sitecore, don't give a shot by simply changing the files specified in the step"after the hotfix has been installed"
Accordingly to the ...
According to the official documentation:
There are two ways to enable application monitoring for Azure App Services hosted applications:
Agent-based application monitoring (ApplicationInsightsAgent).
Manually instrumenting the application through code
For Sitecore 8.0 your only option is Agent-based application monitoring (...
The setting MaxTelemetryItemsPerSecond is not setting the sampling interval to 5 seconds, but it is telling how many items to check in 1 second, so you cannot set it to 5 minutes.
In more details
Sampling is a feature in Azure Application Insights. It is the recommended way to reduce telemetry traffic and storage, while preserving a statistically ...
When Sitecore is deployed to Azure PaaS, XM and XP packages for app services contain additional config files for Application Insights in the folder \App_Config\Sitecore\Azure. The file \App_Config\Sitecore\Azure\Sitecore.Cloud.ApplicationInsights.config replaces default log file appenders with Application Insights appenders for standard Sitecore log files.
/solr/admin/info/system?wt=json is a well-known exploit that allows to get access to system information of a Solr instance.
This is not a standard behaviour of Sitecore or Solr, so these requests must be sent by an external bot or script.
Consider enabling IP restriction for your Solr app service so that only known servers and locations can access it. You ...
The Application Insights telemetry initializers are triggered before the Session_OnStart event occurs, so you need to register your custom telemetry initializer in the Session_Start method in the Global.asax.cs of your application.
Custom Telemetry Initializer
You probably already created this, but I am sharing here an example. Mine is inheriting one of the ...
Log Stream reads from the trace on the local disk. In order to get the Sitecore log to log streams, you need two configurations in place: A log4net traceappender and application logging enabled.
The AI log4net appender in 9.0.x was actually just logging to trace. It seems they've updated it to log to AI directly (which is more right if they have but I haven'...
As long as I understood from Application Insights, I made the below assumption which can help here.
Insights Trace= Log.Info, Publish log, search log, crawling log
Insights Avail= Azure all resource availability logs.
Insights Exception= Sitecore and other exception logs.
Insights Event= Operational logs for internal Sitecore operation from xConnect, xdb ...
Found the issue. The direct cause is missing sections in web.config.
ApplicationInsights HttpModule is for capturing requests information in App Insights.
myAppInsightsListener in system.diagnostics is for capturing the traces.
The problem that caused this complicated and long process of troubleshooting is that when we thought it's exactly the same code ...