Skip to content

Add "tracing" to Project navigation menu, nested under "monitor"

Proposal

Observability team is building Tracing, Metrics and Logs and intends to release all 3 to GA status within the next 9 months. This request is for adding the following 3 sub-navigation items, nested under "Monitor" in the Project navigation for the current navigation information architecture:

  • Tracing
  • Metrics
  • Logs

Screenshot_2023-06-29_at_9.20.59_AM

Figma: https://www.figma.com/file/aRqRA4Fn20kOxpbmp6gX93/Combine-metrics%2C-logs-and-tracing-nav-items-gitlab-com%26329135?type=design&node-id=362-0&mode=design&t=AE4D1sJ1GX1gCimu-0

Other locations that were considered

This location has already been suggested as the best location by UX and Design. @jmandell, @kbychu, @wleidheiser have more context that they might be able to provide if necessary.

Update

Prior to 15.0 GitLab already had two tabs as proposed in this proposal for 'tracing' and 'metrics'. Those tabs were deprecated as part of deprecating the old features they referenced. #416655 (comment 1465659634)

Checklist

  • Review the handbook page for navigation changes
  • Add relevant information to the issue description detailing your proposal, including usage and business drivers.
  • List at least two other places you considered to introduce your feature
  • Add relevant designs to the Design Management area of the issue
  • Ensure your UI suggestion align with the Documentation Style Guide
  • Engage Technical Writing. They can help craft a term that best describes the feature(s) you’re proposing.
  • Follow the product development workflow validation process to ensure you are solving a well understood problem and that the proposed change is understandable and non-disruptive to users. Navigation-specific research is mandatory for additions or when restructuring.
  • Engage the Foundations Product Manager for approval. The Foundations DRI (@cdybenko) will work with UX partners in product design, research, and technical writing, as applicable.
  • Consider whether you need to communicate the change somehow, or if you will have an interim period in the UI where your item will live in more than one place.
  • Ensure engineers are familiar with the implementation steps for navigation.
Edited by Mat Appelman