Add log monitoring guidance and examples to "About subscription licenses" #91
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
✅ Deploy Preview will be available once build job completes!
|
y82
reviewed
Jan 23, 2025
aHigs
reviewed
Jan 23, 2025
ADubhlaoich
approved these changes
Jan 23, 2025
travisamartin
force-pushed
the
doc-1533-usage-reporting-and-jwt-logs
branch
from
0626dae to
39e2c39
Compare
mjang
approved these changes
Jan 23, 2025
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.
Summary
This PR updates the "About subscription licenses" documentation to include guidance on monitoring logs for subscription-related issues. It specifies the log location and provides examples of relevant log entries for common issues, such as failed usage reports and license expiration.
Changes
/var/log/nginx/error.logas the log location for subscription-related events.Purpose
These updates address customer needs by providing clear guidance on identifying and troubleshooting subscription-related issues through log monitoring.