It’s common sense. When a logstorm hits, you don’t want to be left scrambling to find the one engineer from each team in your organization that actually understands the logging system – then spending even more time mapping the logging format of each team with the formats of every other team, all before you can begin to respond to the incident at hand. It’s a model that simply won’t scale.
As the GitOps paradigm continues to evolve, different interpretations and implementations will continue to appear. SUSE Rancher Fleet is a project creating a powerful, lightweight, and scalable GitOps engine. Recently, we showed the art of the possible between Shipa and SUSE Rancher Fleet. Make sure to check out our joint solution brief where the intersection of the SUSE Rancher and Shipa stacks come together.
Click below to read other articles from our CLI intro series: At the beginning of this series, we looked at the benefits of using the CLI shell on your machine. One of those benefits is the wide range of developer tools available that only have a CLI. In this part of the CLI intro series, we’re going to focus on.
With our April update, we ship some great improvements for Signl categories, category-based alerting and duty scheduling. All details are available in this blog article.