If you are managing a team of developers using Kubernetes, no doubt you are running into some scaling issues - not around supporting end-users, but around easily being able to find, triage and fix problems. On top of that, you have existing tools in place to help with ticketing or your CI/CD pipeline tooling that the development team already uses (and hopefully loves) so you don’t want to interrupt any workflows.
But you do need to ensure Kubernetes is secure and cost effective. This is where Fairwinds Insights helps. It provides you with a centralized view of Kubernetes clusters, helping you to identify security, performance, and cost misconfigurations in your applications. It does all this while enabling Kubernetes service ownership, the ability for development teams to take responsibility for the products and services they deliver through each step of the development life cycle.
When developing your Kubernetes platform, you’ve selected a lot of tooling so you may be wondering why you’d want to put another platform in the development team’s way. You do not need to worry about that!
Fairwinds Insights integrates with some of the most widespread tooling available to the Kubernetes community including Jira, Slack, PagerDuty and more. That integration means that when Insights identifies an issue, a ticket or notification is pushed from Insights to the tools that your developers already love.
Triggering workflows from within Insights streamlines the process of assigning ownership to the appropriate teams, saving time and visits to multiple UIs.
Two recent releases introduce new ways to interact with third party providers from the Insights platform.
Azure DevOps joins Jira and GitHub as the latest third party ticketing integration in Insights. Users can now manually create Azure DevOps Work Items from Insights Action Items, as well as automatically through Automation Rules. Installation is a breeze, and is triggered from the Integrations tab of the Settings page. View the documentation.
While Insights has many existing integrations, there may be a tool you already use and want to extend its functionality to. To do that, Insights uses Automation Rules. This feature enables you to customize workflows for handling new findings from Fairwinds Insights. For example, you may create a new issue in a ticketing system, or fire a Slack alert. It helps ensure that Insights adds efficiency to your development life cycle vs. getting in its way.
An important part of Automation Rules is the ability to secure access to wherever you are sending Insights data. That’s why now you can add and store encrypted secrets expands existing Automation Rule capabilities to address new use cases. Secrets can be uploaded and encrypted to make secure webhook calls to third party services - such as ticketing providers - using the ‘sendHTTPRequest’ function.
With Fairwinds Insights, you get the benefits of a:
Centralized view into clusters and Infrastructure-as-Code scanning
Consistency across dev, sec and ops
Prioritized list of what matters most and how to fix it
With Insights and its interactions, you’ll empower dev teams to own security, performance and cost configurations in their applications.