-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[APM] Enable logging_level agent configuration for EDOT Python, PHP and .net
#223947
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
Conversation
|
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
03e10d4 to
1dd6e55
Compare
a98e3a8 to
62cac33
Compare
|
I guess this will need #224160 for a proper 8.19 backport |
logging_level agent configuration for EDOT Pythonlogging_level agent configuration for EDOT Python, PHP and .net
💚 Build Succeeded
Metrics [docs]Async chunks
History
cc @xrmx |
|
@tonyghiani Are you able to take a look at this one sometime? This is the same as the recent #222883 but for a few more of the EDOT SDK languages. We (the Application Agents team) are attempting to get this and a subsequent PR for APM agent Central Config support in by the 9.1 freeze date. |
tonyghiani
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Additions to the agent names LGTM 👌
rmyz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
3 similar comments
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Summary
Enable
logging_levelagent configuration options for EDOT Python (opentelemetry/python/elastic), PHP (opentelemetry/php/elastic) and .net (opentelemetry/dotnet/elastic).Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesIdentify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.