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

Dapr log level not respected #1351

Open
1 of 3 tasks
robbss opened this issue Nov 26, 2024 · 0 comments
Open
1 of 3 tasks

Dapr log level not respected #1351

robbss opened this issue Nov 26, 2024 · 0 comments
Labels
Dapr Related to Dapr in ACA

Comments

@robbss
Copy link

robbss commented Nov 26, 2024

This issue is a:

  • bug report -> please search issues before submitting
  • documentation issue or request
  • regression (a behavior that used to work and stopped in a new release)

Issue description

When configuring the Dapr log level on a container, the chosen log level is not respected, such that info logs are always logged even when log level is at warn / error.

Steps to reproduce

  1. Configure Dapr log level to anything other than info
  2. View logs produced by Dapr sidecars

Expected behavior [What you expected to happen.]
Info logs should not be produced when log level is set to warn / error.

Actual behavior [What actually happened.]
Info logs are produced on all log levels.

Screenshots
Image
Image

Additional context

Change has been made through the portal, have not attempted any other methods of changing it.

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: triage 🔍 Pending a first pass to read, tag, and assign label Nov 26, 2024
@v-vish v-vish added Dapr Related to Dapr in ACA and removed Needs: triage 🔍 Pending a first pass to read, tag, and assign labels Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dapr Related to Dapr in ACA
Projects
None yet
Development

No branches or pull requests

2 participants