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

No spans from blog trigger in isolated worker (host or worker) #2802

Open
lmolkova opened this issue Oct 23, 2024 · 0 comments
Open

No spans from blog trigger in isolated worker (host or worker) #2802

lmolkova opened this issue Oct 23, 2024 · 0 comments
Labels
area: http Items related to experience improvements for HTTP triggers logging .NET 9

Comments

@lmolkova
Copy link
Member

Here's the repro app: https://github.com/lmolkova/testfuncotel

Environment:

  • A .NET 9 RC 2 SDK
  • Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore at v2.0.0-preview1
  • Microsoft.Azure.Functions.Worker.Sdk at v2.0.0-preview1
  • Azure Functions Core Tools at v4.0.6280

It has:

  • HTTP and blob triggers
  • configures otel to collect incoming and outgoing HTTP and function worker sources
  • it sends some custom spans from function invocations
  • it exports all logs, traces and spans to local aspire dashboard

What I see:

  • HTTP trigger works fine: spans and logs are exported as expected
    Image

  • Blob trigger does not produce any spans from the worker - even custom ones. It produces a bunch spans from the host, but none of them are related to the specific invocation (or not correlated to it)

  • It produces logs, which have trace-id, but there is no corresponding trace
    Image

    Mysteriously, even the custom activity that works perfectly fine in the HTTP trigger becomes null inside blob trigger.

    It also produces a bunch of host-level storage-polling noise, but I don't see any spans describing the triggered function
    Image

Expected:

Blob trigger is reported as a span on the host and custom activity is reported from inside the trigger code.

@liliankasem liliankasem added logging area: http Items related to experience improvements for HTTP triggers .NET 9 and removed Needs: Triage (Functions) labels Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: http Items related to experience improvements for HTTP triggers logging .NET 9
Projects
None yet
Development

No branches or pull requests

2 participants