-
Notifications
You must be signed in to change notification settings - Fork 153
Clarify export behavior of diagnostic settings #196
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
base: main
Are you sure you want to change the base?
Conversation
This behavior makes sense but one of my customers was confused about it. Noticed we do not have a current statement on our docs for this.
@didiergbenou-ms : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Learn Build status updates of commit 76ad271: ✅ Validation status: passed
For more details, please refer to the build report. |
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
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.
Pull Request Overview
This PR adds clarification about the export behavior of diagnostic settings in Azure Monitor documentation. The purpose is to address customer confusion by explicitly documenting that diagnostic settings only export data generated after they are enabled.
- Added a note section explaining that diagnostic settings only export data created after enablement
- Clarified that historical data before configuration is not exported
- Included guidance to enable settings early to capture necessary logs
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Can you review this old PR and determine whether it needs to be closed or merged? @MicrosoftDocs/public-repo-pr-review-team |
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
This behavior makes sense but one of my customers was confused about it. Noticed we do not have a current statement on our docs for this.