You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
traces
| where message startswith "stdout log" or message startswith "rpc log"
Expected behavior
These are the logs I see on windows consumption:
Actual behavior
These are the logs I see on 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.
The text was updated successfully, but these errors were encountered:
Repro steps
Provide the steps required to reproduce the problem:
Clone this repo: https://github.com/ejizba/func-stdout-file-load
Run
npm install
Deploy to a flex consumption Node.js app
Hit the http trigger
Run the following query in app insights:
Expected behavior
These are the logs I see on windows consumption:
Actual behavior
These are the logs I see on 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.
The text was updated successfully, but these errors were encountered: