@nazim_m@benoit_chambon I'm thinking of a API integration from Koinju into my own personal lightstep incident response instance to get on-call notifications when BTC is down below 40k level ;)
@milkers Consolidating the monitoring to identify service health, with the incident response workflows to fix things when they break will lead to great efficiencies for teams.
Cool product, congrats on your launch! — Have you taken a look at Rootly.io before? I know a few companies using them to manage incidents right from Slack which is pretty cool. They do a lot of automation like creating incident channels, JIRA tickets, postmortem timeline, paging people via PD, etc.
@maomorales Thanks for the shout! Love seeing new players in this space as managing incidents effectively is a superpower. If anyone wants a demo feel free to reach out https://rootly.io/demo :)
👋 Hey there Hunters!
⏲TL;DR: Reduce downtime with deeper and more actionable insights with Lightstep Incident Response—now available for early access (absolutely free for 6 months).
🚀At Lightstep we've been focused on providing clarity and confidence to the teams that build and operate the software that powers our daily lives. Joining ServiceNow helped us accelerate this vision, and now, we're excited to share more about what we've been working on together — Lightstep Incident Response.
We believe that a seamless integration between observability and incident response tools will drive greater clarity and confidence for SRE and DevOps teams, ultimately making their jobs easier.
So, why are we doing this? Complex tools and app architectures create challenges for teams trying to address downtime; systems can be clunky and often don't play nice with each other.
This makes it difficult to access the information needed to respond quickly.
With Lightstep Incident Response, our aim is to provide teams with the real-time information and context needed to keep systems and services up and running – and the ability to act on it.
Key features to support fast resolution times include:
✅ Accelerate incident resolution and page the right responders with contextual, rules-based alert routing
✅ Minimize downtime and resolve issues quickly with complete service context for the impacted systems
✅ Get systems back online fast by automating key processes
Of course, the product doesn't stop there. We plan to continuously evolve Lightstep Incident Response, and the user feedback we receive during the early access period will be critical to helping us make the product better.
We'd love to hear your thoughts!
👉 Sign up for early access here: https://lightstep.com/incident-r...
I love how easy it is to organize your team schedules and know who's gonna be on call to respond to incidents whenever they happen, and for them to know what to do and have the right context to make quick decisions. Having managed the engineering team at a tech startup, this wasn't something easy to achieve. I wished I had this 2 years ago!
The best part? You & your team can get your hands on a full access 6 month free trial, no credit card required -> https://www.airapp.lightstep.com...! We wanted to ensure to empower Dev/Ops teams to make their own tool stack decisions, and this product is the first step in that direction. I joined this project because I saw firsthand the strain caused by lengthy on-call hours, constantly ringing phones causing alert fatigue, and "P1" issues happening during key life moments (family soccer games, weddings, etc.). Our mission is to help your team move you away from the noise and toil of traditional on-call, towards true service resilience to reduce the amount of alerts, incidents, and degradations in your environment. As a PM on the team, I look forward to your feedback!
Great work. If you're looking for something simple and Slack focused, would recommend checking out Rootly: https://www.producthunt.com/post....
Of course I am a little bias :)
koinju