-
Notifications
You must be signed in to change notification settings - Fork 447
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
How to turn off "Executing | Executed | Trigger details" traces #10308
Comments
Thanks for reporting please refer this doc ::https://learn.microsoft.com/en-us/azure/azure-functions/functions-monitoring#disable-built-in-logging |
I've already seen that documentation, however, it doesn't answer the question. |
@vany0114 it is not possible to configure these specific logs beyond the log-level filters you mentioned. However, we are making investments in moving to open telemetry, which will improve this area in the future. /cc: @RohitRanjanMS |
@vany0114, we recently launched OpenTelemetry support in Azure Functions, as detailed here. One of our goals was to reduce telemetry, and as a result, we no longer generate "Executing..." and "Executed..." logs. Instead, we only provide a request telemetry that contains all the necessary information. Currently, this feature is available for the Flex consumption plan, but we plan to extend it to all SKUs in the future. |
Is your question related to a specific version? If so, please specify:
"@azure/functions": "^3.5.1"
What language does your question apply to? (e.g. C#, JavaScript, Java, All)
Javascript - NodeJS
Question
Is there a way to configure the log level to avoid ingesting these runtime traces?
I noticed that using the Application Insights SDK there's no way we can sample those, they never land in the telemetry processor, I guess it's because they are runtime traces.
I know we can configure the log level per function, like:
However, that's not ideal or maintainable and if I do this:
Then I lose all the logs.
We need to do so because they swamped our telemetry data, they are not useful for us and we're being charged for that which is super expensive.
Related issue: microsoft/ApplicationInsights-node.js#1359 (comment)
The text was updated successfully, but these errors were encountered: