Conversation
This comment has been minimized.
This comment has been minimized.
✅ Docs preview readyThe preview is ready to be viewed. View the preview File Changes 0 new, 1 changed, 32 removedBuild ID: 7fcb4694f68e273df1551517 URL: https://www.apollographql.com/docs/deploy-preview/7fcb4694f68e273df1551517 |
b92962e to
8ca54ac
Compare
|
Question: Since we are reorganizing a lot of information do we need to worry about customers who have any current pages bookmarked in this section and would now experience 404s. Have we considered adding redirects? |
@DMallare, great question! everything has redirects from their old url. no bookmarks will be broken. check out the top of the *.mdx files for a section like the one below to see how I've configured the redirects. |
tninesling
left a comment
There was a problem hiding this comment.
Love the idea to improve the organization here! Left a few suggestions to think about
docs/source/_sidebar.yaml
Outdated
There was a problem hiding this comment.
I think Instruments, Events, Spans, Attributes, Conditions, and Selectors should stay as peers in this structure. Selectors are used with Attributes, Conditions, Spans, Events, and Instruments. Conditions can be applied to the first three. Since these are somewhat intertwined, I think the previous structure made more sense.
I agree that folks probably want to know the standard instruments first to get started up, so we can keep Instruments as the first page. Maybe it's worth merging Instruments with Standard Instruments?
There was a problem hiding this comment.
Maybe it's worth merging Instruments with Standard Instruments?
I looked into this and it would result in a very long page unfortunately.
docs/source/_sidebar.yaml
Outdated
There was a problem hiding this comment.
I like this change to group the different APM docs together! Some of these pages seem fairly short, so it might make things easier for everyone if we just merge the sub-pages together (ie. have a single page for each APM that covers metrics, traces, etc).
There was a problem hiding this comment.
i agree, but I won't be able to get the old bookmarks to navigate to the correct subsection.
Redirect limitations
Redirects don't currently support redirecting to or from anchors.
There was a problem hiding this comment.
I could combine New Relic and Dynatrace but that's about it.
Datadog would be too long. I could do it by splitting off the old Datadog native configuration into its own page, but that would break old links to it.
Prometheus isn’t all that long, but I believe its two pages, metrics and trace metrics, are better off being separate since they don’t have the same concept of using the same exporter like the others do where you use the otlp exporter for both metrics and traces.
Zipkin and Jaeger only have one page already.
23a6e41 to
6410784
Compare
alyssahursh
left a comment
There was a problem hiding this comment.
This looks great, Robert! Thanks for putting so much thought and care into this, and for organizing the work so clearly that it's easy to review.
mabuyo
left a comment
There was a problem hiding this comment.
++ to Alyssa's comment! I really appreciate the cleanliness of organizing this work. Besides the minor comment, two things:
-
cc @BlenderDude's, I see
redirectFroms set up which is great, is there anything else we can do or have done in the past to catch any broken links with a restructure like this? -
This is a part of the docs I don't visit very often and a topic I don't know much about. I see some teammates already gave their reviews, which is great. I would recommend also pulling in other folks who use this part of the docs more (maybe someone from Solutions?).
Giving my approval because these are non-blocking comments!
|
Looks like some file conflicts popped up! After fixing those, LGTM to hit merge (tho my previous PR review comment still applies!). |
8f18a06 to
2ab4574
Compare
devfreddy-apollo
left a comment
There was a problem hiding this comment.
I love it. Very logical split between GraphOS data and Router Telemetry. There's a place for guides / longer form content now. Really liking the more natural fit of Instruments/standard instruments under a Metrics section.
|
LGTM |

Summary
This Pull Request re-organizes and enhances the documentation structure for observability, telemetry, and performance monitoring in the Apollo GraphOS Router. It primarily focuses on restructuring content, modifying links, integrating redirects for legacy paths, and ensuring consistency across documentation. JIra RR-305
This branch has a sister branch in docs-rewrite. In order to preview the PR you will need to pull both branches down and run locally. The librarian preview in the comments below does not work because there are related changes in the https://github.com/apollographql/docs-rewrite/pull/758 PR that needs to be merged at the same time as this PR.
Main Changes:
Outcome
These changes focus on improving user experience and ensuring that observability-related documentation is easier to navigate and utilize. GraphOs insights documentation and router otel telemetry documentation are now in separate sections. Users will be able to find all of the apm specific documentation in a dedicated folder for their apm of choice. This allows room for future PRs that will add documentation for apm specific dashboards and monitoring recommendations.
The Plan
Excalidraw

Checklist
Complete the checklist (and note appropriate exceptions) before the PR is marked ready-for-review.
Exceptions
This is a docs only PR. Checklist items around Unit testing and router compatibility need not appy.