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

Stdout/stderr logs during worker init not sent to app insights #10222

Closed
ejizba opened this issue Jun 11, 2024 · 0 comments · Fixed by #10345
Closed

Stdout/stderr logs during worker init not sent to app insights #10222

ejizba opened this issue Jun 11, 2024 · 0 comments · Fixed by #10345

Comments

@ejizba
Copy link
Contributor

ejizba commented Jun 11, 2024

Repro steps

Provide the steps required to reproduce the problem:

  1. Clone this repo: https://github.com/ejizba/func-stdout-file-load

  2. Run npm install

  3. Deploy to a flex consumption Node.js app

  4. Hit the http trigger

  5. Run the following query in app insights:

    traces
    | where message startswith "stdout log" or message startswith "rpc log"

Expected behavior

These are the logs I see on windows consumption:

windows consumption

Actual behavior

These are the logs I see on flex:

flex

Related information

This is a big deal because the workers send app startup errors over stdout/stderr (the suggested workaround for #9360) and app startup errors are quite common/frustrating with the new programming models. I suspect this issue might be related to the host split work, so I feel it's important we figure this out before moving the host split to non-flex skus.

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

Successfully merging a pull request may close this issue.

3 participants