Improve the Prometheus configuration form

Problem to solve

Our current Prometheus configuration section could be greatly improved by:

• Using a different layout to progressively disclose the options to the user to make the process less overwhelming
• Using a different layout and behavior for buttons to follow Pajamas guidelines
• Providing more useful help and placeholder text to the user to guide them in the configuration process

Current experience

Intended users

• Delaney (Development Team Lead)
• Sasha (Software Developer)
• Devon (DevOps Engineer)
• Sidney (Systems Administrator)

Further details

WIP Proposal

❗ This proposal needs to be updated to include the new features like managing multiple Prometheus configurations. For more issues around Prometheus configurations check out this epic.

Proposed experience

• Change layout to a tab layout
• Change buttons positioning
• Include good help and placeholder text, link to docs for additional information
• Use an icon + color to indicate the active configuration. We shouldn't rely on color alone to indicate a status for accessibility reasons.

➡ View the WIP full prototype here.

Open questions

• Define help and placeholder text for inputs.

Permissions and Security

Documentation

Availability & Testing

GitLab team members can use https://prometheus-dogfood.ops.gitlab.net/ OAuth'd URL for testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

Programmatic authentication using service account | IAP Docs