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

Azure Function output trace level log in log stream with information level in host.json #8719

Closed
RetYn opened this issue Sep 8, 2022 · 1 comment

Comments

@RetYn
Copy link

RetYn commented Sep 8, 2022

Check for a solution in the Azure portal

For issues in production, please check for a solution to common issues in the Azure portal before opening a bug. In the Azure portal, navigate to your function app, select Diagnose and solve problems from the left, and view relevant dashboards before opening your issue.

Investigative information

log level in host.json is
{
"version": "2.0",
"logging": {
"applicationInsights": {
"samplingSettings": {
"isEnabled": true,
"excludedTypes": "Request"
}
}
}
}
When I run azure function locally, the console window does not output any [verbose] level log
But when I deployed to azure, and I can [verbose] debug level log in log stream
image
Httpclient debug level log will also print httpheader for each request.
That will leak our authorization within HTTP request header.
Function version is v4.

Repro steps

Provide the steps required to reproduce the problem:

Expected behavior

The function should not output any [verbose] level log

Actual behavior

The function output any [verbose] level log
image

Known workarounds

Provide a description of any known workarounds.

Related information

-->
@ghost ghost assigned kashimiz Sep 8, 2022
@RetYn RetYn changed the title Azure Function output verbose level log in log stream Azure Function output trace level log in log stream Sep 9, 2022
@RetYn RetYn changed the title Azure Function output trace level log in log stream Azure Function output trace level log in log stream with information level in host.json Sep 9, 2022
@RohitRanjanMS
Copy link
Member

This is addressed through this PR .

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

No branches or pull requests

3 participants