Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GA plan for Microsoft.Azure.Functions.Worker.ApplicationInsights #1263

Closed
3 of 6 tasks
brettsam opened this issue Jan 10, 2023 · 14 comments
Closed
3 of 6 tasks

GA plan for Microsoft.Azure.Functions.Worker.ApplicationInsights #1263

brettsam opened this issue Jan 10, 2023 · 14 comments

Comments

@brettsam
Copy link
Member

brettsam commented Jan 10, 2023

There are several outstanding work items needed before the Microsoft.Azure.Functions.Worker.ApplicationInsights nuget package can be declared generally available (GA).

We'll be resolving any related App Insights issues here and making sure there is a central place to bring up issues that we can add to this list. Once the package is GA, we'll close this and handle new issues as we would any other package.

To fix the issue with App Insights logs missing from Console logging in Core Tools:

OpenTelemetry support (on worker only):

Documentation:

@jacobjmarks
Copy link

jacobjmarks commented Feb 24, 2023

Might I also suggest that the Net7Worker sample be updated to include proper Application Insights configuration when available? I have recently been on the rollercoaster that is AI configuration for .NET 7 Isolated Workers and at this point I'm very much interested in some official documented solutions.

@JayAtSherweb
Copy link

Your documentation seems to outline how to use in an application, but not an isolated function.
Please help.

@fgheysels
Copy link

Is there already any progress or news regarding the General Availability of this package ?
The latest release of this (preview) package is already 5 months old. Is this project still alive ?

@Shumigaj
Copy link

Functions with HttpTrigger don't work with Microsoft.Azure.Functions.Worker 1.8.0 and Microsoft.Azure.Functions.Worker.ApplicationInsights 1.0.0-preview3 packages. The problem is solved by updating Microsoft.Azure.Functions.Worker to 1.10.0 version

@stijnmoreels
Copy link

Functions with HttpTrigger don't work with Microsoft.Azure.Functions.Worker 1.8.0 and Microsoft.Azure.Functions.Worker.ApplicationInsights 1.0.0-preview3 packages. The problem is solved by updating Microsoft.Azure.Functions.Worker to 1.10.0 version

How does custom telemetry then work, as there is no more TelemetryClient registered in the dependency container?

@stijnmoreels
Copy link

@Shumigaj any update on this?

@Shumigaj
Copy link

My functions doesn't work at all with Microsoft.Azure.Functions.Worker 1.8.0 and Microsoft.Azure.Functions.Worker.ApplicationInsights 1.0.0-preview3 packages. I couldn't make any requests to it on my local machine until I just updated Microsoft.Azure.Functions.Worker to 1.10.0 version, after that update everything works as expected. I wanted to mention this side effect with the version because it seems that there is no limitation for the version of the Microsoft.Azure.Functions.Worker package in the Microsoft.Azure.Functions.Worker.ApplicationInsights package.

@stijnmoreels
Copy link

stijnmoreels commented Mar 28, 2023

My functions doesn't work at all with Microsoft.Azure.Functions.Worker 1.8.0 and Microsoft.Azure.Functions.Worker.ApplicationInsights 1.0.0-preview3 packages. I couldn't make any requests to it on my local machine until I just updated Microsoft.Azure.Functions.Worker to 1.10.0 version, after that update everything works as expected. I wanted to mention this side effect with the version because it seems that there is no limitation for the version of the Microsoft.Azure.Functions.Worker package in the Microsoft.Azure.Functions.Worker.ApplicationInsights package.

Yes, ok, but how does custom telemetry work with this? As it is the preview package that registers the TelemetryClient, @Shumigaj ?

@stijnmoreels
Copy link

stijnmoreels commented Apr 27, 2023

Could you please provide some feedback on how to do custom telemetry in isolated Azure Functions, without using the Microsoft.Azure.Functions.Worker.ApplicationInsights package?
As no TelemetryClient or TelemetryConfiguration is registered in the application services when solely using the Microsoft.Azure.Functions.Worker package.

@Shumigaj
FYI @fgheysels @pim-simons

@Shumigaj
Copy link

It is possible, just use Microsoft.ApplicationInsights and Microsoft.ApplicationInsights.WorkerService packages. Dependencies can be registered by AddApplicationInsightsTelemetryWorkerService method. But, there are drawbacks of this approach (e.g. operation id won't be populated)

@ChrisProlls
Copy link

Any news about this ?
Will the previewXX packages prevents us from upgrading our Function to .NET 8 in the future ?

@stijnmoreels
Copy link

But, there are drawbacks of this approach (e.g. operation id won't be populated)

Then it is rather pointless to use this approach when there's no service-to-service/transactional correlation available; feels like an incomplete workaround.

The preview package is still the best solution, here.

@renjums
Copy link

renjums commented Aug 16, 2023

I see the package is available as stable in Nuget. https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.ApplicationInsights/1.0.0

Is this thread still open ?

@mattchenderson
Copy link
Contributor

We wanted to wait for the Azure Update. But yes, now closeable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants