[{"data":1,"prerenderedAt":778},["ShallowReactive",2],{"content:\u002F11-observability\u002Fresources":3},{"title":4,"description":5,"path":6,"body":7},"Дополнительные материалы: observability","Подборка по logs, metrics, tracing, alerting, profiling и incident response для Go\u002Fbackend-разработчика.","\u002F11-observability\u002Fresources",{"type":8,"value":9,"toc":762},"minimark",[10,15,18,23,53,57,112,116,169,173,281,285,368,372,462,466,516,520,586,590,624,628,662,666,724,728],[11,12,14],"h1",{"id":13},"дополнительные-материалы","Дополнительные материалы",[16,17,5],"p",{},[19,20,22],"h2",{"id":21},"observability-fundamentals","Observability fundamentals",[24,25,26,37,45],"ul",{},[27,28,29,36],"li",{},[30,31,35],"a",{"href":32,"rel":33},"https:\u002F\u002Fwww.oreilly.com\u002Flibrary\u002Fview\u002Fdistributed-systems-observability\u002F9781492033431\u002F",[34],"nofollow","The Three Pillars of Observability"," — хорошая отправная точка про logs, metrics и traces.",[27,38,39,44],{},[30,40,43],{"href":41,"rel":42},"https:\u002F\u002Fsre.google\u002Fsre-book\u002Fmonitoring-distributed-systems\u002F",[34],"Google SRE Book: Monitoring Distributed Systems"," — фундамент про monitoring, alerting и user impact.",[27,46,47,52],{},[30,48,51],{"href":49,"rel":50},"https:\u002F\u002Fsre.google\u002Fworkbook\u002Falerting-on-slos\u002F",[34],"Google SRE Workbook: Alerting on SLOs"," — практичный подход к алертам через SLO\u002Ferror budget.",[19,54,56],{"id":55},"go-logs-и-profiling","Go logs и profiling",[24,58,59,67,80,88,96,104],{},[27,60,61,66],{},[30,62,65],{"href":63,"rel":64},"https:\u002F\u002Fpkg.go.dev\u002Flog\u002Fslog",[34],"log\u002Fslog package"," — стандартный structured logging в Go.",[27,68,69,74,75,79],{},[30,70,73],{"href":71,"rel":72},"https:\u002F\u002Fgo.dev\u002Fblog\u002Fslog",[34],"Go blog: Structured Logging with slog"," — мотивация и модель ",[76,77,78],"code",{},"slog",".",[27,81,82,87],{},[30,83,86],{"href":84,"rel":85},"https:\u002F\u002Fpkg.go.dev\u002Fnet\u002Fhttp\u002Fpprof",[34],"net\u002Fhttp\u002Fpprof"," — стандартные pprof handlers.",[27,89,90,95],{},[30,91,94],{"href":92,"rel":93},"https:\u002F\u002Fgo.dev\u002Fblog\u002Fpprof",[34],"Profiling Go Programs"," — официальный вход в CPU\u002Fheap profiling.",[27,97,98,103],{},[30,99,102],{"href":100,"rel":101},"https:\u002F\u002Fgo.dev\u002Fdoc\u002Fdiagnostics",[34],"Diagnostics in Go"," — runtime diagnostics, tracing, profiling и debugging.",[27,105,106,111],{},[30,107,110],{"href":108,"rel":109},"https:\u002F\u002Fgo.dev\u002Fcmd\u002Ftrace\u002F",[34],"Go tool trace"," — анализ runtime trace.",[19,113,115],{"id":114},"русскоязычные-материалы-по-go-logsprofiling","Русскоязычные материалы по Go logs\u002Fprofiling",[24,117,118,129,137,145,153,161],{},[27,119,120,125,126,128],{},[30,121,124],{"href":122,"rel":123},"https:\u002F\u002Fpcnews.ru\u002Fblogs\u002F%5Bperevod%5D_strukturirovannoe_logirovanie_v_go_s_pomosu_slog-1404145.html",[34],"Перевод: структурированное логирование в Go с помощью Slog"," — вводный материал по ",[76,127,78],{},", handler'ам и уровням.",[27,130,131,136],{},[30,132,135],{"href":133,"rel":134},"https:\u002F\u002Fhabr.com\u002Fru\u002Farticles\u002F470443\u002F",[34],"Непрерывное профилирование в Go \u002F Хабр"," — pprof в бою и подводные камни.",[27,138,139,144],{},[30,140,143],{"href":141,"rel":142},"https:\u002F\u002Fhabr.com\u002Fru\u002Farticles\u002F968660\u002F",[34],"Go profiling lifecycle: от разработки до прода \u002F Хабр"," — heap, goroutines, runtime trace и методика поиска утечек.",[27,146,147,152],{},[30,148,151],{"href":149,"rel":150},"https:\u002F\u002Fhabr.com\u002Fru\u002Farticles\u002F874506\u002F",[34],"Go: тонкости профилирования CPU \u002F Хабр"," — почему CPU profile может быть пустым и как его читать.",[27,154,155,160],{},[30,156,159],{"href":157,"rel":158},"https:\u002F\u002Fhabr.com\u002Fru\u002Farticles\u002F535614\u002F",[34],"pprof в golang: исправляем утечку памяти \u002F Хабр"," — практический пример memory leak.",[27,162,163,168],{},[30,164,167],{"href":165,"rel":166},"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=c4bldaCjYRY",[34],"Видео: Профилирование Go приложений"," — русскоязычный разбор инструментов профилирования.",[19,170,172],{"id":171},"metrics-и-prometheus","Metrics и Prometheus",[24,174,175,183,191,199,207,215,223,231,249,257,265,273],{},[27,176,177,182],{},[30,178,181],{"href":179,"rel":180},"https:\u002F\u002Fprometheus.io\u002Fdocs\u002Fintroduction\u002Foverview\u002F",[34],"Prometheus Documentation"," — базовая модель scrape, metrics и PromQL.",[27,184,185,190],{},[30,186,189],{"href":187,"rel":188},"https:\u002F\u002Fprometheus.io\u002Fdocs\u002Fconcepts\u002Fdata_model\u002F",[34],"Prometheus Data Model"," — модель time series и labels.",[27,192,193,198],{},[30,194,197],{"href":195,"rel":196},"https:\u002F\u002Fprometheus.io\u002Fdocs\u002Fconcepts\u002Fmetric_types\u002F",[34],"Prometheus Metric Types"," — Counter, Gauge, Histogram, Summary.",[27,200,201,206],{},[30,202,205],{"href":203,"rel":204},"https:\u002F\u002Fprometheus.io\u002Fdocs\u002Fpractices\u002Fhistograms\u002F",[34],"Prometheus Histograms and Summaries"," — buckets, quantiles и агрегация.",[27,208,209,214],{},[30,210,213],{"href":211,"rel":212},"https:\u002F\u002Fprometheus.io\u002Fdocs\u002Fguides\u002Fgo-application\u002F",[34],"Prometheus: Instrumenting Go applications"," — практический старт для Go.",[27,216,217,222],{},[30,218,221],{"href":219,"rel":220},"https:\u002F\u002Fpkg.go.dev\u002Fgithub.com\u002Fprometheus\u002Fclient_golang\u002Fprometheus",[34],"client_golang"," — Go client library для Prometheus.",[27,224,225,230],{},[30,226,229],{"href":227,"rel":228},"https:\u002F\u002Fprometheus.io\u002Fdocs\u002Fprometheus\u002Flatest\u002Fquerying\u002Fbasics\u002F",[34],"PromQL Basics"," — instant\u002Frange vectors и query model.",[27,232,233,238,239,242,243,242,246,79],{},[30,234,237],{"href":235,"rel":236},"https:\u002F\u002Fprometheus.io\u002Fdocs\u002Fprometheus\u002Flatest\u002Fquerying\u002Ffunctions\u002F",[34],"Prometheus Functions"," — ",[76,240,241],{},"rate",", ",[76,244,245],{},"increase",[76,247,248],{},"histogram_quantile",[27,250,251,256],{},[30,252,255],{"href":253,"rel":254},"https:\u002F\u002Fprometheus.io\u002Fdocs\u002Fprometheus\u002Flatest\u002Fconfiguration\u002Frecording_rules\u002F",[34],"Prometheus Recording Rules"," — предварительный расчет частых запросов.",[27,258,259,264],{},[30,260,263],{"href":261,"rel":262},"https:\u002F\u002Fprometheus.io\u002Fdocs\u002Fprometheus\u002Flatest\u002Fconfiguration\u002Falerting_rules\u002F",[34],"Prometheus: Alerting rules"," — правила алертов.",[27,266,267,272],{},[30,268,271],{"href":269,"rel":270},"https:\u002F\u002Fprometheus.io\u002Fdocs\u002Fpractices\u002Fpushing\u002F",[34],"Prometheus: When to use Pushgateway"," — когда push уместен, а когда вреден.",[27,274,275,280],{},[30,276,279],{"href":277,"rel":278},"https:\u002F\u002Fprometheus.io\u002Fdocs\u002Foperating\u002Fsecurity\u002F",[34],"Prometheus Security Model"," — безопасность Prometheus endpoint'ов.",[19,282,284],{"id":283},"русскоязычные-материалы-по-prometheus-slo-и-grafana","Русскоязычные материалы по Prometheus, SLO и Grafana",[24,286,287,295,305,322,330,344,352,360],{},[27,288,289,294],{},[30,290,293],{"href":291,"rel":292},"https:\u002F\u002Fhabr.com\u002Fru\u002Fcompanies\u002Fslurm\u002Farticles\u002F728414\u002F",[34],"Prometheus + Grafana: 4 golden signals и другие подходы \u002F Хабр"," — Golden Signals, RED и USE.",[27,296,297,302,303,79],{},[30,298,301],{"href":299,"rel":300},"https:\u002F\u002Fhabr.com\u002Fru\u002Farticles\u002F747350\u002F",[34],"Как из метрик Prometheus построить график Latency \u002F Хабр"," — latency histogram и ",[76,304,248],{},[27,306,307,312,313,242,316,242,319,79],{},[30,308,311],{"href":309,"rel":310},"https:\u002F\u002Fhabr.com\u002Fru\u002Fcompanies\u002Fotus\u002Farticles\u002F501978\u002F",[34],"Как работает гистограмма Prometheus? \u002F Хабр"," — buckets, ",[76,314,315],{},"le",[76,317,318],{},"_count",[76,320,321],{},"_sum",[27,323,324,329],{},[30,325,328],{"href":326,"rel":327},"https:\u002F\u002Fhabr.com\u002Fru\u002Fpost\u002F693834\u002F",[34],"Человеческим языком про метрики 4: PromQL \u002F Хабр"," — базовый PromQL.",[27,331,332,238,337,340,341,79],{},[30,333,336],{"href":334,"rel":335},"https:\u002F\u002Fhabr.com\u002Fru\u002Farticles\u002F905124\u002F",[34],"Как правильно использовать rate() в Grafana \u002F Хабр",[76,338,339],{},"rate()"," и ",[76,342,343],{},"$__rate_interval",[27,345,346,351],{},[30,347,350],{"href":348,"rel":349},"https:\u002F\u002Fhabr.com\u002Fru\u002Farticles\u002F1028008\u002F",[34],"SLI\u002FSLO. Что такое Error Budget Burn Rate на самом деле \u002F Хабр"," — свежий разбор burn rate.",[27,353,354,359],{},[30,355,358],{"href":356,"rel":357},"https:\u002F\u002Fhabr.com\u002Fru\u002Farticles\u002F709204\u002F",[34],"Основы мониторинга: Prometheus и Grafana \u002F Хабр"," — вводный обзор стека.",[27,361,362,367],{},[30,363,366],{"href":364,"rel":365},"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=2JIyHNskK-c",[34],"Видео: Мониторинг и Логи PROD уровня"," — практический стек Grafana + Prometheus + Loki; часть про Promtail воспринимать как legacy.",[19,369,371],{"id":370},"opentelemetry-и-tracing","OpenTelemetry и tracing",[24,373,374,382,390,398,406,422,430,438,446,454],{},[27,375,376,381],{},[30,377,380],{"href":378,"rel":379},"https:\u002F\u002Fopentelemetry.io\u002Fdocs\u002Flanguages\u002Fgo\u002F",[34],"OpenTelemetry Go"," — официальный Go SDK.",[27,383,384,389],{},[30,385,388],{"href":386,"rel":387},"https:\u002F\u002Fopentelemetry.io\u002Fdocs\u002Flanguages\u002Fgo\u002Finstrumentation\u002F",[34],"OpenTelemetry Go instrumentation"," — manual instrumentation, HTTP, logs bridge.",[27,391,392,397],{},[30,393,396],{"href":394,"rel":395},"https:\u002F\u002Fopentelemetry.io\u002Fdocs\u002Flanguages\u002Fgo\u002Fexporters\u002F",[34],"OpenTelemetry Go exporters"," — OTLP exporters.",[27,399,400,405],{},[30,401,404],{"href":402,"rel":403},"https:\u002F\u002Fopentelemetry.io\u002Fdocs\u002Fspecs\u002Fsemconv\u002F",[34],"OpenTelemetry Semantic Conventions"," — стандартные атрибуты.",[27,407,408,238,413,242,416,242,419,79],{},[30,409,412],{"href":410,"rel":411},"https:\u002F\u002Fopentelemetry.io\u002Fdocs\u002Fspecs\u002Fsemconv\u002Fresource\u002F",[34],"OpenTelemetry Resource Semantic Conventions",[76,414,415],{},"service.name",[76,417,418],{},"service.version",[76,420,421],{},"deployment.environment.name",[27,423,424,429],{},[30,425,428],{"href":426,"rel":427},"https:\u002F\u002Fopentelemetry.io\u002Fdocs\u002Fconcepts\u002Fcontext-propagation\u002F",[34],"OpenTelemetry Context Propagation"," — propagation через процессы и сервисы.",[27,431,432,437],{},[30,433,436],{"href":434,"rel":435},"https:\u002F\u002Fopentelemetry.io\u002Fdocs\u002Fconcepts\u002Fsignals\u002Fbaggage\u002F",[34],"OpenTelemetry Baggage"," — baggage и ограничения.",[27,439,440,445],{},[30,441,444],{"href":442,"rel":443},"https:\u002F\u002Fopentelemetry.io\u002Fdocs\u002Fcollector\u002F",[34],"OpenTelemetry Collector"," — collector, pipelines, exporters.",[27,447,448,453],{},[30,449,452],{"href":450,"rel":451},"https:\u002F\u002Fopentelemetry.io\u002Fdocs\u002Fcollector\u002Fconfiguration\u002F",[34],"OpenTelemetry Collector Configuration"," — receivers, processors, exporters и pipelines.",[27,455,456,461],{},[30,457,460],{"href":458,"rel":459},"https:\u002F\u002Fwww.w3.org\u002FTR\u002Ftrace-context\u002F",[34],"W3C Trace Context"," — стандарт передачи trace context между сервисами.",[19,463,465],{"id":464},"русскоязычные-материалы-по-opentelemetry","Русскоязычные материалы по OpenTelemetry",[24,467,468,476,484,492,500,508],{},[27,469,470,475],{},[30,471,474],{"href":472,"rel":473},"https:\u002F\u002Fhabr.com\u002Fru\u002Farticles\u002F994626\u002F",[34],"OpenTelemetry стек в Go: Metrics, Tracing, Logs \u002F Хабр"," — практический Go + Collector + Prometheus + Tempo + Loki.",[27,477,478,483],{},[30,479,482],{"href":480,"rel":481},"https:\u002F\u002Fhabr.com\u002Fru\u002Farticles\u002F710644\u002F",[34],"Трейсинг в Go — это просто \u002F Хабр"," — вводная по tracing в Go.",[27,485,486,491],{},[30,487,490],{"href":488,"rel":489},"https:\u002F\u002Fhabr.com\u002Fru\u002Farticles\u002F919214\u002F",[34],"Наблюдаемость \"по-взрослому\": опыт внедрения OpenTelemetry \u002F Хабр"," — production-разговор про OTel.",[27,493,494,499],{},[30,495,498],{"href":496,"rel":497},"https:\u002F\u002Fhabr.com\u002Fru\u002Farticles\u002F947724\u002F",[34],"Кастомный процессор для OpenTelemetry Collector \u002F Хабр"," — расширяемость Collector.",[27,501,502,507],{},[30,503,506],{"href":504,"rel":505},"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=bGEM2Y48CuQ",[34],"OpenTelemetry на практике \u002F Илья Казначеев, Golang Channel"," — русскоязычный доклад.",[27,509,510,515],{},[30,511,514],{"href":512,"rel":513},"https:\u002F\u002F300.ya.ru\u002Fv_5rryTBPv?nr=1",[34],"OpenTelemetry для самых маленьких \u002F Александр Гольдебаев"," — краткое русскоязычное резюме видео.",[19,517,519],{"id":518},"grafana-stack","Grafana stack",[24,521,522,530,538,546,554,562,570,578],{},[27,523,524,529],{},[30,525,528],{"href":526,"rel":527},"https:\u002F\u002Fgrafana.com\u002Fdocs\u002Fgrafana\u002Flatest\u002F",[34],"Grafana documentation"," — dashboards, datasources, alerting.",[27,531,532,537],{},[30,533,536],{"href":534,"rel":535},"https:\u002F\u002Fgrafana.com\u002Fdocs\u002Floki\u002Flatest\u002F",[34],"Grafana Loki"," — logs aggregation.",[27,539,540,545],{},[30,541,544],{"href":542,"rel":543},"https:\u002F\u002Fgrafana.com\u002Fdocs\u002Floki\u002Flatest\u002Fget-started\u002Flabels\u002Fcardinality\u002F",[34],"Grafana Loki labels and cardinality"," — почему нельзя делать labels из ids.",[27,547,548,553],{},[30,549,552],{"href":550,"rel":551},"https:\u002F\u002Fgrafana.com\u002Fdocs\u002Floki\u002Flatest\u002Fsend-data\u002Fpromtail\u002F",[34],"Promtail EOL notice"," — Promtail EOL с 2 марта 2026, migration path в Alloy.",[27,555,556,561],{},[30,557,560],{"href":558,"rel":559},"https:\u002F\u002Fgrafana.com\u002Fdocs\u002Floki\u002Flatest\u002Fsend-data\u002Fotel\u002F",[34],"Grafana Loki OTLP"," — native OTLP logs в Loki.",[27,563,564,569],{},[30,565,568],{"href":566,"rel":567},"https:\u002F\u002Fgrafana.com\u002Fdocs\u002Ftempo\u002Flatest\u002F",[34],"Grafana Tempo"," — distributed tracing backend.",[27,571,572,577],{},[30,573,576],{"href":574,"rel":575},"https:\u002F\u002Fgrafana.com\u002Fdocs\u002Ftempo\u002Flatest\u002Fset-up-for-tracing\u002Finstrument-send\u002Fset-up-collector\u002F",[34],"Tempo: set up Collector"," — отправка traces через Collector.",[27,579,580,585],{},[30,581,584],{"href":582,"rel":583},"https:\u002F\u002Fgrafana.com\u002Fdocs\u002Falloy\u002Flatest\u002F",[34],"Grafana Alloy"," — collector\u002Fagent для logs, metrics, traces в Grafana stack.",[19,587,589],{"id":588},"elkefk-и-logs-pipeline","ELK\u002FEFK и logs pipeline",[24,591,592,600,608,616],{},[27,593,594,599],{},[30,595,598],{"href":596,"rel":597},"https:\u002F\u002Fwww.elastic.co\u002Fdocs",[34],"Elastic Stack documentation"," — Elasticsearch, Kibana, Beats и ingest pipeline.",[27,601,602,607],{},[30,603,606],{"href":604,"rel":605},"https:\u002F\u002Fwww.elastic.co\u002Fguide\u002Fen\u002Fobservability\u002Fcurrent\u002Fapm-api-otlp.html",[34],"Elastic OpenTelemetry intake API"," — OTLP traces\u002Fmetrics\u002Flogs в Elastic.",[27,609,610,615],{},[30,611,614],{"href":612,"rel":613},"https:\u002F\u002Fdocs.fluentbit.io\u002Fmanual",[34],"Fluent Bit Documentation"," — легкий log processor\u002Fforwarder для EFK-подхода.",[27,617,618,623],{},[30,619,622],{"href":620,"rel":621},"https:\u002F\u002Fopensearch.org\u002Fdocs\u002Flatest\u002F",[34],"OpenSearch Documentation"," — open-source альтернатива Elasticsearch\u002FKibana stack.",[19,625,627],{"id":626},"русскоязычные-материалы-по-logs-stack","Русскоязычные материалы по logs stack",[24,629,630,638,646,654],{},[27,631,632,637],{},[30,633,636],{"href":634,"rel":635},"https:\u002F\u002Fhabr.com\u002Fru\u002Fcompanies\u002Fotus\u002Farticles\u002F721004\u002F",[34],"Kubernetes Observability: логгинг с EFK \u002F Хабр"," — EFK в Kubernetes.",[27,639,640,645],{},[30,641,644],{"href":642,"rel":643},"https:\u002F\u002Fhabr.com\u002Fru\u002Fcompanies\u002Fslurm\u002Farticles\u002F517636\u002F",[34],"Логирование в Kubernetes: как собирать, хранить, парсить и обрабатывать логи \u002F Хабр"," — Docker\u002FKubernetes logging и Fluent Bit.",[27,647,648,653],{},[30,649,652],{"href":650,"rel":651},"https:\u002F\u002Fdockerhosting.ru\u002Fblog\u002Fczentralizovannoe-logirovanie-docker-kontejnerov-s-loki-polnoe-rukovodstvo\u002F",[34],"Централизованное логирование Docker контейнеров с Loki"," — практический compose-пример; Promtail-часть считать legacy.",[27,655,656,661],{},[30,657,660],{"href":658,"rel":659},"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=UpJlfDOlrTw",[34],"Видео: Как логи превращаются в метрики: Fluent Bit в деле"," — collectors, parsing и filters.",[19,663,665],{"id":664},"incident-response","Incident response",[24,667,668,676,684,692,700,708,716],{},[27,669,670,675],{},[30,671,674],{"href":672,"rel":673},"https:\u002F\u002Fsre.google\u002Fsre-book\u002Fpostmortem-culture\u002F",[34],"Google SRE Book: Postmortem Culture"," — как разбирать инциденты без поиска виноватых.",[27,677,678,683],{},[30,679,682],{"href":680,"rel":681},"https:\u002F\u002Fsre.google\u002Fworkbook\u002Fincident-response\u002F",[34],"Google SRE Workbook: Incident Response"," — роли и процесс реакции.",[27,685,686,691],{},[30,687,690],{"href":688,"rel":689},"https:\u002F\u002Fsre.google\u002Fworkbook\u002Fon-call\u002F",[34],"Google SRE Workbook: On-Call"," — on-call практики.",[27,693,694,699],{},[30,695,698],{"href":696,"rel":697},"https:\u002F\u002Fwww.atlassian.com\u002Fincident-management",[34],"Incident Management at Atlassian"," — простой практический фрейм для incident process.",[27,701,702,707],{},[30,703,706],{"href":704,"rel":705},"https:\u002F\u002Fresponse.pagerduty.com\u002F",[34],"PagerDuty Incident Response Docs"," — практики incident command.",[27,709,710,715],{},[30,711,714],{"href":712,"rel":713},"https:\u002F\u002Fprometheus.io\u002Fdocs\u002Fpractices\u002Falerting\u002F",[34],"Prometheus alerting practices"," — правила хороших алертов.",[27,717,718,723],{},[30,719,722],{"href":720,"rel":721},"https:\u002F\u002Fprometheus.io\u002Fdocs\u002Falerting\u002Flatest\u002Falertmanager\u002F",[34],"Alertmanager documentation"," — grouping, inhibition, routing.",[19,725,727],{"id":726},"русскоязычные-материалы-по-incident-response","Русскоязычные материалы по incident response",[24,729,730,738,746,754],{},[27,731,732,737],{},[30,733,736],{"href":734,"rel":735},"https:\u002F\u002Fhabr.com\u002Fru\u002Fcompanies\u002Fslurm\u002Farticles\u002F562758\u002F",[34],"Постмортем инцидентов для начинающих \u002F Хабр"," — культура и шаблон postmortem.",[27,739,740,745],{},[30,741,744],{"href":742,"rel":743},"https:\u002F\u002Fhabr.com\u002Fru\u002Fcompanies\u002Fotus\u002Farticles\u002F722892\u002F",[34],"SRE: управление инцидентами \u002F Хабр"," — роли и процесс.",[27,747,748,753],{},[30,749,752],{"href":750,"rel":751},"https:\u002F\u002Fhabr.com\u002Fru\u002Farticles\u002F982172\u002F",[34],"Инцидент-менеджмент с нуля \u002F Хабр"," — организация процесса.",[27,755,756,761],{},[30,757,760],{"href":758,"rel":759},"https:\u002F\u002Fhabr.com\u002Fru\u002Farticles\u002F878366\u002F",[34],"Руководство по проведению постмортемов \u002F Хабр"," — структура разбора.",{"title":763,"searchDepth":764,"depth":764,"links":765},"",2,[766,767,768,769,770,771,772,773,774,775,776,777],{"id":21,"depth":764,"text":22},{"id":55,"depth":764,"text":56},{"id":114,"depth":764,"text":115},{"id":171,"depth":764,"text":172},{"id":283,"depth":764,"text":284},{"id":370,"depth":764,"text":371},{"id":464,"depth":764,"text":465},{"id":518,"depth":764,"text":519},{"id":588,"depth":764,"text":589},{"id":626,"depth":764,"text":627},{"id":664,"depth":764,"text":665},{"id":726,"depth":764,"text":727},1781022063192]