Set default log level to Information and add pipeline override #539
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Charles-Gagnon
requested review from
MaddyDev,
chlafreniere and
lucyzhang929
as code owners
lucyzhang929
approved these changes
Nov 29, 2022
PBBlox
pushed a commit
to PBBlox/azure-functions-sql-extension
that referenced
this pull request
Apr 6, 2025
…#539) * Default to warning * Information default * Add update log level script * Update readme
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Having debug enabled was causing major delays when running tests (especially benchmark tests) and so I'm reverting my change to enable debug by default and instead have a setting that can be enabled in the pipeline to add more verbose logging.
This has the downside that if a transient error occurs then it'll be a bit harder to track down as we'll have to rely on it happening again or Information logging being enough - but our runs have generally been stable enough that this should be fine for normal runs (and then debug logging can be enabled for getting additional logs during pipeline runs)
Times before (with debug logging enabled)
Times after (with default Information logging)