A good CI system is able to cater for future needs. We use technologies and tools that allow us to redeploy the system as needed and track any change on our software automation as if it was code (Infrastructure as Code). This is applicable to any subsystem of the CI/CD system.
Even though it feels great to work on projects with seemingly unlimited resources, we sometimes need to reduce costs on the infrastructure. We do this by understanding the system. Some parts of it may be unnecessarily oversized compared to the requirements to run specific workloads. We sometimes don't need to run as many tests as we are currently running.
Visualise how your changes perform over time. Identify when regressions occur and in which patches they were introduced. Get notified as soon as there is a significant regression identified by your automation. Using the latest tools, e.g. Grafana, or a charting JS or python library. Let's create beautiful visualisations that make sense for your team.