GitLab helps you get faster from idea to production, but things don't stop once they're in production. The original I2P vision included Monitoring, which is a part of Ops, but it's become clear that we can really go further and deliver a full offering around Operators and Operations.
We have a growing list of features that help you monitor and manage changes in production, and we're quickly expanding to offer more ops-level features.
- Monitoring Dashboard: gitlab-ce#26905 (closed)
- Monitoring alert on merge request: gitlab-ce#26944 (closed)
- Deploy Boards: #1589 (closed)
- Dependency security/update checking: #3710
- SLO / Automatic revert: #1661
- Show current status of pods in deploy board: #2413
- Ops view of monitoring and deploy board: #1788
- Pipeline view of environments: gitlab-ce#28698
- Dashboard of all environments in a group: #3713
- Error tracking: #5459 (closed)
Currently all these features are under the Pipelines tab, but is that the best place for them? Many of these are tagged as
deploy items, but as we look at things through the lens of an operator, the connection with CI/CD pipelines is less apparent. Production systems can go down for a lot of reasons unrelated to code changes: network outages, system limits, etc. Do we need a new top-level category for operations? Originally, the Pipelines/Environments sub-tab only showed the last CI/CD deployment status and history for environments. But now it includes deploy boards showing more detailed information about rollouts. Eventually it will show current status of pods, and maybe system logs. Should Pipelines/Environments be moved into this new category?
What's the word for things beyond CI/CD? I'm tempted to use DevOps, but that's a really broad term that includes VCS itself. Ops may be the best word.
Is there a word that covers CI/CD + Ops? If so, then we could rename the top-level Pipelines tab to whatever that word is.