MTP-1921: Add Azure Application Insights request tracing and logging #587
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.
uWSGI now runs in lazy mode such that each process loads its own complete application rather than forking the master. This now requires the spooler to setup django.
Lazy apps are needed if telemetry is to be sent to Azure Application Insights: the
opencensus
library starts a background thread on launch to transport telemetry to Azure, but if uWSGI loads the application and then forks, this thread is no longer accessible from the new process.In
prod
environment:•
mtp
logs of level INFO and higher• other logs of level WARNING and higher
• 10% of requests traces
…will be sent.
Depends on common#539.