Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Andrea Richiardi

My feedback

  1. 11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Azure Functions » Portal  ·  Flag idea as inappropriate…  ·  Admin →
    Andrea Richiardi supported this idea  · 
    An error occurred while saving the comment
    Andrea Richiardi commented  · 

    Dear Colby, this is really really unfortunately and I hope you will eventually decide to .

    The fact that an app should not be concerned with logging is a very important thing to have. It is so important that it shows up in The 12-Factor App Logs section: https://12factor.net/logs.

    As you can read there:

    > [...] each process’ stream will be captured by the execution environment, collated together with all other streams from the app, and routed to one or more final destinations for viewing and long-term archival. These archival destinations are not visible to or configurable by the app, and instead are completely managed by the execution environment.

    In summary, the app should not be concerned about "how" the runtime treats its output.

    This is especially true for functions, which are generally more lightweight and should not really carry the burden that fully-fledged applications have. Logging is done to stdout, aggregation is out of band and the function is leaner.

    I think probably you are aware of all this, I apologize if that is the case, and I hope you reconsider the decision.

Feedback and Knowledge Base