<img src="https://certify.alexametrics.com/atrk.gif?account=Zpb+p1uhUo20dG" style="display:none" height="1" width="1" alt="">
Chaos Engineering for DevOps


Think About Your Audience Before Choosing a Webinar Title

Sponsored by Sumo logic partnered with aws    AWS-SumoLogic_Partner-Logo_Right_Color_RGB


On Demand

DevOps is all about safe experimentation, failing fast and continuous feedback loops. Chaos engineering is all about purposefully triggering a software failure in production to build confidence and resilience. How can DevOps teams leverage chaos engineering to deliver better customer experiences?

Join us as we discuss:

  • How chaos engineering can uncover failure before it impacts customers
  • How to get all teams on board and comfortable with chaos
  • Using chaos engineering to train teams and improve individual, team and technology performance
Bryce Lindsey
Principal Site Reliability Engineer, Alaska Airlines
As a member of the SRE team at Alaska Airlines, Bryce ensures that the alaskaair.com site is running smoothly and that any issues are detected and mitigated as quickly as possible. In addition to observability, Bryce champions service level agreements and chaos engineering to help teams own the reliability of their systems.
Brad Johnson
WW DevOps Category Leader, AWS
WW DevOps Category Leader, AWS
WW DevOps Category Leader, AWS
WW DevOps Category Leader, AWS
Emily Brand
Global Ecosystem Leader, Red Hat
Global Ecosystem Leader, Red Hat
Global Ecosystem Leader, Red Hat
Global Ecosystem Leader, Red Hat
Bruno Kurtic
Co-Founder and Head of Strategy - Sumo Logic
Bruno leads strategy and solutions for Sumo Logic, pioneering machine-learning technology to address growing volumes of machine data across enterprise networks. Before Sumo Logic, Bruno held various product and strategy leadership positions at SenSage, Boston Consulting Group (BCG), webMethods, and others. Bruno holds an MBA from Massachusetts Institute of Technology (MIT) and B.A. in Quantitative Methods and Computer Science from University of St. Thomas, St. Paul, MN.
Mitch Ashley
CTO, Techstrong Group & Principal, Techstrong Research
Mitchell Ashley is a renowned strategist and technology executive. Mitchell has led successful IT, SaaS, and cybersecurity transformations. He’s led multiple teams in developing and bringing to market successful online services, cybersecurity, and networking products and services. Mitch serves as Principal of Techstrong Research where he leads a team of preeminent experts in digital transformation, DevOps, cloud-native, and cybersecurity. In this role, Mitch works with companies to align digital transformation and technology strategies to achieve disruptive goals and high impact results. Mitch is in high demand as a speaker at conferences the world over, and his popular DevOps Chats podcast engaging with digital leaders is one of the most widely followed in the field.

Register to Watch Now:

What You’ll Learn in This Webinar

You’ve probably written a hundred abstracts in your day, but have you come up with a template that really seems to resonate? Go back through your past webinar inventory and see what events produced the most registrants. Sure – this will vary by topic but what got their attention initially was the description you wrote.

Paint a mental image of the benefits of attending your webinar. Often times this can be summarized in the title of your event. Your prospects may not even make it to the body of the message, so get your point across immediately.  Capture their attention, pique their interest, and push them towards the desired action (i.e. signing up for your event). You have to make them focus and you have to do it fast. Using an active voice and bullet points is great way to do this.

Always add key takeaways. Something like this....In this session, you’ll learn about:

  • You know you’ve cringed at misspellings and improper grammar before, so don’t get caught making the same mistake.
  • Get a second or even third set of eyes to review your work.
  • It reflects on your professionalism even if it has nothing to do with your event.