Change monitoring->observability - #1927
Draft
puneetsarna wants to merge 1 commit into
Draft
puneetsarna wants to merge 1 commit into
puneetsarna wants to merge 1 commit into
Conversation
github-actions
Bot
added
the
documentation
puneetsarna
force-pushed
the
ps-dev-imp-obser
branch
2 times, most recently
from
May 6, 2026 01:28
cbe4649 to
bd1931c
Compare
✅ Deploy Preview will be available once build job completes!
|
A lot of our metrics-related docs are labeled as "monitoring" which is a bit misleading even though that's what Google calls it. IMHO "observability" is a good overall name to indicate how a user can observe their deployment generally, and we can have specific sections around enabling logs, metrics, (or WAF logs in the future).
puneetsarna
force-pushed
the
ps-dev-imp-obser
branch
from
May 6, 2026 01:31
bd1931c to
ca3b4fa
Compare
|
This PR is stale because it has been open 90 days with no activity. Remove the stale label or add a comment to keep it open. If you do not take action, this will be closed in 10 days. |
valyria257
reviewed
Sep 11, 2026
| ### Service Frontend | ||
|
|
||
| The service frontend of an NGINXaaS deployment controls how client ingress traffic reaches your deployment. There are two frontend types: managed public endpoint and private endpoint. | ||
| The service frontend of an NGINXaaS deployment controls how client ingress traffic reaches your deployment. There are two frontend types: **Managed Public Endpoint** and **Private Endpoint**. |
Contributor
There was a problem hiding this comment.
There was a discussion in slack and we decided that managed public endpoint and private endpoint shouldn't be capitalized (I'll send you the link)
Contributor
|
Is there somewhere we need add redirects so existing URLs aren't broken? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
A lot of our metrics-related docs are labeled as
"monitoring" which is a bit misleading even though that's what Google calls it.
IMHO "observability" is a good overall name to
indicate how a user can observe their deployment
generally, and we can specific sections around
enabling logs, metrics, (or WAF logs in the
future).
Proposed changes
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩