docs: Well Architected Framework content migration #21099
Conversation
boruszak
added
type/docs
…l-monitoring-docs
website/data/docs-nav-data.json
Outdated
| "title": "Monitor service communication", | ||
| "path": "agent/monitor/service" |
There was a problem hiding this comment.
I don't think this is an intuitive place for it if we're centering around jobs to be done, but ok if this is a temp measure
These are usually two different personas:
- Consul operator monitoring Consul itself
- Service operator/developer monitoring the services on Consul
There was a problem hiding this comment.
This is a temp place, with the only req from me is that they all go in the same location (for now anyway).
There was a problem hiding this comment.
The other option is to place it in /connect/observability. It's an easy enough fix before merging...@cjobermaier is it critical that they're all in the same location? Happy to go either way, with the temp location or splitting them into two locations.
There was a problem hiding this comment.
If it's easier to discover, splitting into two locations is probably fine, especially since we will have redirects sending people who bookmarked it during the first publication.
boruszak
deleted the
docs/WAF-212-Content-Migration-Migrate-Consul-monitoring-docs
branch
Description
Migrates content from the Well Architected Framework documentation set to the Consul documentation set.
Links
PR Checklist