Trust and observability from commit to production
You don’t have to dig through logs and dashboards during outages, security breaches, or audits. Kosli tracks every change to your environments and connects them to events in your code pipelines to give you a searchable record when you need it.
Developers
Where are my commits?
Follow your commits through the CI pipeline to staging, deployment and beyond. Are your changes built and deployed? Find out with Kosli CLI
SREs and Platform Engineers
What just changed in my environment?
Can't find the source of an incident? Too many changes to track? Diff environments as easily as git commits and see how they’ve really changed
CTOs
Is my software in compliance?
Know exactly what’s running and how it got there. Generate audits instantly by exporting artifacts and accompanying evidence to CSV
Supports any CI / runtime
and more...
Forgotten, Siloed, Hidden
Searching everywhere
vs
Recorded, Connected, Searchable
Instant observability
Forgotten, Siloed, Hidden
Searching everywhere
vs
Recorded, Connected, Searchable
Instant observability
Pinpoint any change from commit through to runtime
My environments are constantly changing. What’s going on?
Tired of trying to figure out what’s happening in your systems? Had enough of piecing things together with repos and glue scripts? Kosli takes a snapshot of your runtimes whenever a change is made, giving you a provable record of how your environments are really changing.
View live example
$ kosli env get beta#43
COMMIT ARTIFACT PIPELINE RUNNING_SINCE REPLICAS
7e2c8b4 Name: cyberdojo/nginx:7e2c8b4 N/A 7 months ago 1
Fingerprint: ddb54f0c8b8c69143d617cc559c231e7389f1d7d8d875a5909aa3303e0397a3b
c4c0333 Name: cyberdojo/languages-start-points:c4c0333 N/A 7 months ago 1
Fingerprint: ed1fee8041e8aee86447ba52ba0155880906f327006afda5021a3dcc1943d3c2
bbf94ef Name: cyberdojo/web:bbf94ef N/A 8 months ago 3
Fingerprint: 95f3d36bd1849b9caf4d014641bfe817384d8990477430e4287c92edb3a68762
f05a57c Name: cyberdojo/differ:f05a57c N/A 8 months ago 1
Fingerprint: 83c8b5b2a65b7381a87eb43a92acddd2a1960bd8bc6164d0c38a5714d4675b7f
916b024 Name: cyberdojo/shas:916b024 N/A one year ago 1
Fingerprint: aadbfc30734b75369002c69e6232a47f45e202f19280747028b5d337a05645e5
c6d6a35 Name: cyberdojo/exercises-start-points:c6d6a35 N/A one year ago 1
Fingerprint: 76e4fef7e98a2248ac2705fee422d8e2e3ce1edb9109e8c0e2f7cb52c28c20c3
a71729f Name: cyberdojo/repler:a71729f N/A one year ago 1
Fingerprint: f740fb1897b22780583cc49c0b8460d4f6a4e56d603cbcc65f10a6132c2ff65a
0aed98e Name: cyberdojo/dashboard:0aed98e N/A one year ago 1
Fingerprint: a3b2190b68c7c2702b2358477629617a12c820fe02e3da32c516b824b9029497
7a05eb4 Name: cyberdojo/creator:7a05eb4 N/A one year ago 1
Fingerprint: 12bfc09116a85d9fd427ff4542932880f1bac088a85b5ebb88cd74175c767807
f1c426f Name: cyberdojo/runner:f1c426f N/A one year ago 3
Fingerprint: 9e490165d5e8f8a8260a7be37595328c3e3ff74252c1ca312ae64f3ebfad1636
68c5eb7 Name: cyberdojo/saver:68c5eb7 N/A one year ago 1
Fingerprint: 8ba413cc804ecac73779925f0d97a021e7c13a0cbd8dd24eaaf27e833c3619e2
ef2352f Name: cyberdojo/custom-start-points:ef2352f N/A one year ago 1 Fingerprint: 1ea9ac6b3ad0e98b6b030e34cd30e330d09e0c9cc7eee7623ba06795364fd91e
I don’t know where my commits are. Is my feature running?
Are your changes live? Maybe they’re still in staging? With Kosli you can follow your code from commit to production and know when your feature is running. Get a real time status of your changes and be able to fix them fast if something goes wrong.
View live example
$ kosli artifact get differ@83c8b5b
Name: cyberdojo/differ:f05a57c
Pipeline: differ
Fingerprint: 83c8b5b2a65b7381a87eb43a92acddd2a1960bd8bc6164d0c38a5714d4675b7f
Created on: Mon, 21 Feb 2022 16:19:42 CET • 8 months ago
Git commit: f05a57c7233bb87b04eab03e016fe902070a5029
Commit URL: https://github.com/cyber-dojo/differ/commit/f05a57c7233bb87b04eab03e016fe902070a5029
Build URL: https://circleci.com/gh/cyber-dojo/differ/61089
State: COMPLIANT
Running in environments: beta#52, prod#51
History:
Artifact created Mon, 21 Feb 2022 16:19:42 CET
branch-coverage evidence received Mon, 21 Feb 2022 16:20:07 CET
Deployment #77 to beta environment Mon, 21 Feb 2022 16:20:57 CET
Started running in beta#30 environment Mon, 21 Feb 2022 16:21:58 CET
Deployment #78 to prod environment Mon, 21 Feb 2022 16:30:10 CET
Started running in prod#32 environment Mon, 21 Feb 2022 16:31:12 CET
No longer running in prod#42 environment Thu, 26 May 2022 20:07:05 CEST
Started running in prod#43 environment Thu, 26 May 2022 20:10:03 CEST
I need to know when a commit started running. Can I go back in time?
Yes, even when things have changed. Get quick explanations for black swan type events. Easily navigate a bird’s eye view of *every* change to your repos, pipelines and environments. Quickly identify changes that cause unusual incidents.
View live example
$ kosli env log prod "~3..NOW" --long
SNAPSHOT EVENT PIPELINE DEPLOYMENTS
#53 Artifact: cyberdojo/runner:f1c426f runner #13
Fingerprint: 9e490165d5e8f8a8260a7be37595328c3e3ff74252c1ca312ae64f3ebfad1636
Description: 1 instance stopped running (scaled down from 4 to 3)
Reported at: Fri, 03 Jun 2022 23:07:00 CEST
#53 Artifact: cyberdojo/web:bbf94ef web #12
Fingerprint: 95f3d36bd1849b9caf4d014641bfe817384d8990477430e4287c92edb3a68762
Description: 1 instance stopped running (scaled down from 4 to 3)
Reported at: Fri, 03 Jun 2022 23:07:00 CEST
#52 Artifact: cyberdojo/languages-start-points:f0eeae4 languages-start-points #32
Fingerprint: a65c49270f831b89660603dee6d20b58a9b50febb72f90c3bbd08a18fa74ce69
Description: 1 instance changed
Reported at: Fri, 03 Jun 2022 23:04:02 CEST
#52 Artifact: cyberdojo/nginx:7e2c8b4 nginx #16
Fingerprint: ddb54f0c8b8c69143d617cc559c231e7389f1d7d8d875a5909aa3303e0397a3b
Description: 1 instance changed
Reported at: Fri, 03 Jun 2022 23:04:02 CEST
Connect the dots between dev and ops
-
Rich support for your runtime environments
Kubernetes cluster, Amazon ECS, Amazon S3, Amazon Lambda, Physical/Virtual server -
Easy to implement in your CI/CD toolstack
No need to change your existing CI structure. To use Kosli you just need to run commands in your pipelines and runtime environments. -
Familiar CLI commands
Log, diff, ls, assert - Kosli uses easy and intuitive commands that let you explore your pipelines and runtime environments.
-
Rich support for your runtime environments
Kubernetes cluster, Amazon ECS, Amazon S3, Amazon Lambda, Physical/Virtual server -
Easy to implement in your CI/CD toolstack
No need to change your existing CI structure. To use Kosli you just need to run commands in your pipelines and runtime environments. -
Familiar CLI commands
Log, diff, ls, assert - Kosli uses easy and intuitive commands that let you explore your pipelines and runtime environments.
How it works
- Record
- Connect
- Search
Start reporting your environments and pipelines. Get started with one line of code in your runtime.
Record your environments
Know *exactly* what’s running in your environments. With one line of code Kosli fingerprints the running components in your environment and makes new commits in the database whenever a change is detected. Replace your config repos and glue scripts without enforcing a deployment approach
Connect your pipelines
Now you know what’s running in ops, connect it to your pipeline events. Get a live map of builds, tests, approvals, and deployments and see how it matches up with what’s actually running in your environments. Follow commits all the way to production and trace deployments back to the commit.
Search your DevOps history
With dev and ops aligned you can take time-consuming guesswork and frustration out of incident response, security, and even evidence gathering for audit. Use Kosli’s powerful search tools to log, diff and browse every change from commit to prod. Get what you need from the browser, API, or command line.
We have GitOps. Why do we need Kosli?
GitOps is great for storing static definitions of how you make your software, but it doesn’t capture the dynamic execution of those definitions and the impact on your environments. Kosli is different because it tells you how your systems are really changing by recording events. GitOps tells you what’s declared. Kosli tells you what’s actually happened.
Discover more about Kosli and GitOps
