The New age of Self Integration Management

It All Starts with Why

The foundation of any observability platform is data. The more data the platform collects, and the better it can correlate data points to tell a story, the more successful its customers will be.

Following the apartment moving analogy, consider the difference between:

1. The old way -  Googling the need, reading about it to understand which type of service provider is needed, Googling again to find the relevant service provider and then checking the same area once in a while for maintenance purposes. Sounds tedious, right? 
2. The modern way - Go into a single platform, see in one place all the gaps you have and the relevant service providers to work with, invite them in a click of a button and have an automated monitor set up for you so you wouldn’t need to check it again.

Similarly, when we thought about simplifying the integrations’ setup, we decided to take a step back and focus on empowering our customers to manage their ecosystem. Consider the following examples:

1. Scraping intervals are too frequent, resulting in high cloud costs.
2. A critical metric isn’t monitored.
3. An additional region is added, either for redundancy or to support an additional region.
   

Just like any production issue, a lifecycle is formed for handling production incidents: Detect the issue → Triage the root cause → Issue a fix → Monitor that the fix is in place.

In case of issues related to logs, traces and metrics, groundcover users already have a vast set of tools for triaging and monitoring.

With data sources, they didn’t until now. 

Meet the new standard for integration management

If you add a new cluster, you want full visibility into its performance and the ability to set up monitors accordingly.

We built the new integration flow to support exactly that:

1. Add new configurations directly from the SaaS interface and easily view existing ones.
2. Duplicate configurations across regions or environments to streamline setup.
3. Manage Infrastructure-as-Code (IaC) through Terraform. Check our documentation here.
4. Pause and resume integrations based on your needs. For instance, if you set up a temporary testing environment, you can monitor it closely during specific releases, then pause it until needed again.

And coming soon - monitor the performance of your integration and set up monitors and dashboards to track them, just like with any other infrastructure component.

We believe in empowering teams to control their environment and dynamically change it according to ongoing needs. This is just the first release out of a longer journey for reshaping how integrations should be managed.