insights-core | Insights Core is a data collection

The name of Azure App Services are required to be globally unique. Presumably, someone else has already created a web app with the name 'azuredemo'. Try making the name more unique and publishing again.

You may try "Remote Development" in VS code as a quicker and easier option. Please refer to the tutorial here

Here is one example of java dev environment You will have to install Remote Development extension and would suggest Remote-Container. Try sample for Java.

https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers&WT.mc_id=azurespringcloud-github-judubois

https://github.com/microsoft/azure-spring-cloud-training/blob/master/00-setup-your-environment/AlternateSetup.md#preparing-visual-studio-code

https://code.visualstudio.com/docs/remote/faq#_remote-containers

According to this documentation

Telemetry is not sent instantly. Telemetry items are batched and sent by the ApplicationInsights SDK. In Console apps, which exits right after calling Track() methods, telemetry may not be sent unless Flush() and Sleep/Delay is done before the app exits as shown in full example later in this article.

You can add a flush() and sleep() method to have a try.It can be your application is over,but telemetry haven't sent.

Hope this can help you.

I did a some googling and little research. I foud following:

1. The missing class com.azure.data.cosmos.internal.directconnectivity.rntbd.RntbdConstants$RntbdContextRequestHeader is a part of azure-cosmosdb-direct, pls see pom.xml, class is located here.
2. azure-cosmosdb-direct is missing from your dependency list. I assume it's incomplete or hidden for some reason(?)
3. Looking at exception stacktrace it's clear that at com.azure.data.cosmos.internal.directconnectivity.rntbd.RntbdContextRequest$Headers.(RntbdContextRequest.java:126) is a place where exceptiom occurs. So that means RntbdContextRequest class actually existsts (it's also is a part of azure-cosmosdb-direct). Therefore you have needed dependency, but it probably has wrong version.

I propose you to look a bit deeper into how azure-cosmosdb-direct dependency is injected in your project and fix its version. Just try to declare it directly in your pom.xml with the latest version.

Hope I helped you.

My java version is "1.8.0_231".

This is inconsistent with what the stack trace is showing:

https://github.com/Microsoft/ApplicationInsights-dotnet/issues/973

The recommended workaround is to use 2.7.2 of Application Insights dependency.

For now, the options are:

1. use the same version of AppInsihgts that Functions use (or lower)
2. Filter out internal SDK messages. You can do this by creating and configuring telemetry processor. You can have a filter that checks if telemetry is TraceTelemetry and traceTelemetry.Context.Operation.SyntheticSource is SDKTelemetry

One of the issues I can see here is that internal logger of AI is reporting unexpected character. I see that one of the possible issues is that there is some problem in the sanitization logic and that prevents the item to be sent to end point and hence you are not able to see the data on the portal. Also there are some known logback issues which are already mentioned on the github: https://github.com/Microsoft/ApplicationInsights-Java/issues/453 This should answer your question. Feel free to create another issue on Github if you wish to do so. Hopefully next public release should fix this.