We are thrilled to announce 📢 Kosli is now SOC 2 Type 2 compliant - Read more
New Feature: Kosli Trails is liveCreate comprehensive audit trails for any DevOps activity - Read more

How SolarWinds Continuously Monitors Change Across Large Distributed Architectures

published March 26, 2024
  • IT
  • Enterprise
  • Monitoring
SolarWinds is a leading provider of simple, powerful, secure observability and IT management software. Their globally distributed engineering teams work across complex systems and architectures, using various tools. Staying on top of this complexity is challenging for incident response, observability, and just knowing what’s changing daily. With Kosli, they can track changes in real time and provide shared context for everyone on the engineering team.
  • Challenges

    • How to build a single source of truth for distributed teams in different time zones
    • How to quickly pinpoint the changes responsible for incidents and outages
    • How to know exactly what’s been shipped to production
  • Solutions

    • • A shared view of changes to environments and pipelines available in real time
    • • The ability to log and diff environment changes for faster mean time to resolution
    • • Developer observability over what was deployed and how it was qualified

SolarWinds

Location
Austin, TX
Industry
IT
Profile
FTE 2100, Founded 1999
Website
solarwinds.com

Kosli doesn’t just help us to respond to incidents, it helps us to reduce their frequency.

Mark Martin, Sr. Director Platform Engineering @SolarWinds

Mark Martin, Sr. Director Platform Engineering @SolarWinds

One of the significant challenges for us is collaborating on a shared set of facts. We have dynamic systems and architecture that changes constantly, and the teams working on them are spread across the US, Europe, and Asia. That makes it hard for everyone to understand how environments are changing.

The important thing to know about Kosli is that it records exactly what’s been deployed - and where, when, and how it was deployed. That means an engineer in the United States has all the context required to understand what changed earlier in the day, long after colleagues in Europe and Asia have logged off.

Incident response illustrates exactly why this is useful. If a team in one part of the world is responding to an outage because of a bad change deployed in another region, they can use Kosli to quickly understand how and when that change happened. There’s no guesswork or calling people in the middle of the night to figure out which change caused the issue. We can get to the change we need quickly.

Kosli doesn’t just help us to respond to incidents, it helps us to reduce their frequency. Because we can use Kosli to track the history of a deployment, it’s easy for us to gate release candidates that haven’t been through the test environment. So, nothing goes to production without going through testing, making outages much less likely.

Kosli also gives us the insights we need to deliver more value to our customers. Our developers have observability over what has been deployed to production, so they can be sure that the features they spent time on have been shipped.

Because the history of deployments is recorded in Kosli, the manual work required for compliance and audit is greatly reduced. The evidence for a secure chain of custody is readily available from the app.

Overall, Kosli simplifies our software delivery process, and it frees up time for us to work on the things that really add value.

Ready to ship with more confidence?

Get security and compliance you can trust without slowing down or changing your tools.
Request a demo Start for free
Auditor and Kosli user

Got a question about Kosli?

We’re here to help, our customers range from larges fintechs, medtechs and regulated business all looking to streamline their DevOps audit trails

Contact us