Sabitlenmiş Tweet
Jeli.io
635 posts
Jeli.io
@jeli_io
We've moved! Follow us at @pagerduty. Respond Faster. See Patterns. Learn From Your Incidents. Helping engineering teams at @indeed, @xero, and more.
San Francisco Katılım Mayıs 2020
124 Takip Edilen1.3K Takipçiler
On the twelfth day of Incidentmas my true love gave to me (drumroll please) 🥁🥁🥁🥁🥁🥁🥁🥁🥁🥁🥁🥁 the gift of learning from incidents with Jeli's Incident Analysis 101 e-book!
Available to download for free here: hubs.la/Q02dsd8C0
English
On the eleventh day of Incidentmas my true love gave to me six different ways that can be mixed and matched to create an incident learning pipeline that works for your organization.
Read more on how to share your incident findings: hubs.la/Q02dsbLf0
English
On the tenth day of Incidentmas my true love gave to me insight into approaching action items from a sociotechnical lens instead of just a-leaping to add to the ticket backlog.
Find those insights and more in this Incident Analysis 101 blog: hubs.la/Q02ds9qW0
English
On the ninth day of Incidentmas my true love gave to me advice on how to approach hard topics and avoid spending a learning review dancing around blame. 💃💃💃💃💃💃💃💃💃
hubs.la/Q02dsdrb0
English
On the eighth day of Incidentmas my true love gave to me a primer on how to facilitate a learning review! (in a learning review, just like gift giving, knowing your audience is key, or you’ll end up giving 8 dairy farmers to someone lactose intolerant.)
hubs.la/Q02dsd7n0
English
On the seventh day of Incidentmas my true love gave to me the understanding that a postmortem document is not a solo swan song, but something to iterate on as a team! 🦢🦢🦢🦢🦢🦢🦢
Learn more about your calibration doc here: hubs.la/Q02ds6Nj0
English
On the sixth day of Incidentmas my true love gave to me the skills to tell an incident story. Recounting an incident as a narrative makes it more accessible, and is a much easier task than attempting to collect eggs from six geese. 🪿🪿🪿🪿🪿🪿
hubs.la/Q02dlM8z0
English
On the fifth day of Incidentmas my true love gave to me the knowledge of who to interview as you’re analyzing an incident (in a pear tree). 🍐🎁
Give this Incident 101 blog a read and you'll find the types of folks you want to talk to ring true: hubs.la/Q02dd6cD0
English
On the fourth day of Incidentmas my true love gave to me the four different types of data to consider when approaching an incident to analyze (in a pear tree). 🍐🎁
Learn what incident related data you're looking for in this Incident Analysis 101 blog: hubs.la/Q02dd6-j0
English
On the third day of Incidentmas my true love gave to me three traits of someone who should not investigate an incident (in a pear tree). 🎁🍐
Find out the skills you’ll need and what you’ll learn as an incident analyst in this Incident 101 blog: hubs.la/Q02dd6TV0
English
On the second day of Incidentmas my true love gave to me an incident involving two teams and a good reason to analyze an incident (again, in a pear tree). Read this Incident Analysis 101 blog to find out what makes a good candidate for incident analysis!
hubs.la/Q02d7t540
English
On the first day on Incidentmas my true love gave to me a better understanding of incident analysis and why we should do it! In a pear tree, obviously.
Join us for the 12 Days of Incidentmas and give the gift of learning from incidents to your coworkers! hubs.la/Q02d1g3S0
English
Jeli.io retweetledi
“The SDK for Oso makes it trivial to query and add data. Less code to maintain means we're moving fast on projects when we add or update features.” — Will Gallego, @jeli_io (part of @pagerduty).
Hear from Will on their journey to finding an authz solution!
osohq.com/post/oso-bear-…
English
🚀 We're cooking with gas here at the end of the year! As of today you can create an incident from within the Jeli web app. See more on that here—and subscribe to get updates on all the new things we're shipping! hubs.la/Q02bwYBG0
English
It's already started: holiday deploy freezes in the effort to prevent the introduction of bugs. But do code freezes really prevent incidents?
Check out Jeli's Hot Takes on Code Freezes blog post and tell us what hot takes and tips resonate with your org!
hubs.la/Q029HkPR0
English
ICYMI: We had a great time chatting with @SoftwareHuddle! New podcast with veteran hosts - definitely check them out 💯
Jeli founder @nora_js and @danmccall from @pagerduty sat down with @seanfalconer to talk all things #incidentmanagement! It's been one crazy ride to this point and we're just getting goin' 🚀
Software Huddle@SoftwareHuddle
It's that time again! Join us for an engaging conversation in our latest release. From Code Red to Green: Incident Management with Nora Jones of Jeli and Dan McCall from PagerDuty 🎉 Today's episode is all about Incident Management. We have two amazing guests, Nora Jones, Founder and CEO of @jeli_io, and Dan McCall, the VP and GM of Incident Management at @pagerduty. There's of course a technical aspect to managing incidents that PagerDuty excels at, very well known for, and there's also a human side, like how do you learn from an incident so it doesn't happen again in the future, and this is where Jeli steps in. In the episode, Nora and Dan talk through the evolution of Incident Management, the hard problems in the space, and a future that leverages AI with a human in the loop component to scalably and proactively manage incidents and reduce outages. We also touch on the recent announcement that Jeli was acquired by PagerDuty. Watch on Youtube: youtube.com/watch?v=5prxUD… Timestamps: -- Introduction [01:53] -- Types of Incidents [02:46] -- Handling Incidents [06:09] -- Evolution of Incident Management [09:42] -- Measuring Effectiveness [17:56] -- Hard Problems [22:56] -- Recommendations [27:22] -- Why Become an Entrepreneur [31:35] -- Human Part of Incident Management [36:19] -- Jeli Acquisition [41:32] -- History of AI in Incident Response [45:04] -- Leveraging Generative AI [50:14] @nora_js | @danmccall | @seanfalconer @alexbdebrie
English