Hello! This is a post-report from the mitap Backend United, our series of themed meetings for backend developers. This time we talked a lot about working with incidents, discussed how to build our own system to improve the incident response and became convinced of the value of technical debt.

Go under the cut if you are interested in these topics. Inside you will find meeting materials: video recordings of reports, presentations of speakers, feedback from meetup guests and links to a photo report.

Reports

Simple Tools to Improve Incident Response: The Tutu Experience. Andrey Borzov (Tutu.ru)

Andrey told how Tutu made life easier for themselves during incidents with the help of simple technical solutions. They got a customizable system for teams that makes important diagnostics closer to them, alerts from different systems are more useful, and their routing is easier.

→ Presentation

Listener reviews

• "It is interesting to hear about the application of similar technologies used in our company."
• “The team is great. But now sawing their bikes is not very productive for a company that does not have this bike as a business product. Because of this, I do not consider this solution as a model for implementation, but many of the problems that were voiced were taken into account. Thank you. Healthy".

Working with Production explosions: detection, loss assessment, incident management. Dmitry Khimion (Avito)

Dmitry spoke about how the practice of incident management is organized in Avito, and what kind of research and automation we use in our work.

→ Presentation

Listener reviews

• "I've outlined a lot, class."
• "Interesting and structured."

AutoLSR - Automated collection of information for significant incidents. Vladimir Kolobaev (Avito)

We have collected all the secret knowledge, failure scenarios of various systems and services and transferred it all to the code for the purpose of automated detection and primary analysis of significant incidents. This is Vladimir's report.

→ Presentation

Listener reviews

• "Interesting and useful report."
• "A light and interesting report."

We broke it now, but we'll fix it later. Technical debt and its value. Boris Kaiser (Ozon)

Boris told what he and his team are doing to control everything that breaks down and is quickly repaired, how they help the development not to forget about the promises made, and also how they provide the business with complete and understandable information about what happened, how they fixed it and what will be done so that the situation does not repeat itself.

→ Presentation

Listener reviews

• “Opsjini 🙂 I love learning about new technologies.”
• “In my opinion, the best report. Smart, interesting and practical. Took a lot for myself."

A few pictures

Click to see pictures

We have posted all the photos in Facebook и VC. See how it was and tag yourself and friends if you were at the meeting.

references

A playlist with all the videos from the meetup can be found on our YouTube channel.

We publish all new events for developers, first of all, on our website. Timepad. Subscribe so you don't miss out.

Until next time!

Source: habr.com