ACT now: Aggregate Comparison of Traces for Incident Localization
Incidents in production systems are common and downtime is expensive. Applying an appropriate mitigating action quickly, such as changing a specific firewall rule, reverting a change, or diverting traffic to a different availability zone, saves money. Incident localization is time-consuming since a...
Gespeichert in:
Hauptverfasser: | , , , |
---|---|
Format: | Artikel |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext bestellen |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
container_end_page | |
---|---|
container_issue | |
container_start_page | |
container_title | |
container_volume | |
creator | Ramasubramanian, Kamala Raina, Ashutosh Mace, Jonathan Alvaro, Peter |
description | Incidents in production systems are common and downtime is expensive.
Applying an appropriate mitigating action quickly, such as changing a specific
firewall rule, reverting a change, or diverting traffic to a different
availability zone, saves money. Incident localization is time-consuming since a
single failure can have many effects, extending far from the site of failure.
Knowing how different system events relate to each other is necessary to
quickly identify \emph{where} to mitigate. Our approach, Aggregate Comparison
of Traces (ACT), localizes incidents by comparing sets of traces (which capture
events and their relationships for individual requests) sampled from the most
recent steady-state operation and during an incident. In our quantitative
experiments, we show that ACT is able to effectively localize more than 99% of
incidents. |
doi_str_mv | 10.48550/arxiv.2205.06933 |
format | Article |
fullrecord | <record><control><sourceid>arxiv_GOX</sourceid><recordid>TN_cdi_arxiv_primary_2205_06933</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>2205_06933</sourcerecordid><originalsourceid>FETCH-LOGICAL-a673-d4547ca8761fc6a4055067e4ae22b08d72f923c884387dc96bdaa1a771d0a5453</originalsourceid><addsrcrecordid>eNotz7tqwzAYhmEtGUrSC-hU3YBdWWd3M6ZJA4Ys3s0fHYzAloJsesjVN007fdvL9yD0VJGSayHIC-Sv8FFSSkRJZM3YA2qatscxfb7iZhyzG2F1uE3zBXJYUsTJ4z6DcQv2KeNjNMG6uOIuGZjCFdaQ4g5tPEyLe_zfLer3b337XnSnw7FtugKkYoXlgisDWsnKGwmc3O5I5Tg4Ss9EW0V9TZnRmjOtrKnl2QJUoFRlCQgu2BY9_2XvhuGSwwz5e_i1DHcL-wG0G0ME</addsrcrecordid><sourcetype>Open Access Repository</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype></control><display><type>article</type><title>ACT now: Aggregate Comparison of Traces for Incident Localization</title><source>arXiv.org</source><creator>Ramasubramanian, Kamala ; Raina, Ashutosh ; Mace, Jonathan ; Alvaro, Peter</creator><creatorcontrib>Ramasubramanian, Kamala ; Raina, Ashutosh ; Mace, Jonathan ; Alvaro, Peter</creatorcontrib><description>Incidents in production systems are common and downtime is expensive.
Applying an appropriate mitigating action quickly, such as changing a specific
firewall rule, reverting a change, or diverting traffic to a different
availability zone, saves money. Incident localization is time-consuming since a
single failure can have many effects, extending far from the site of failure.
Knowing how different system events relate to each other is necessary to
quickly identify \emph{where} to mitigate. Our approach, Aggregate Comparison
of Traces (ACT), localizes incidents by comparing sets of traces (which capture
events and their relationships for individual requests) sampled from the most
recent steady-state operation and during an incident. In our quantitative
experiments, we show that ACT is able to effectively localize more than 99% of
incidents.</description><identifier>DOI: 10.48550/arxiv.2205.06933</identifier><language>eng</language><subject>Computer Science - Distributed, Parallel, and Cluster Computing</subject><creationdate>2022-05</creationdate><rights>http://creativecommons.org/licenses/by-nc-sa/4.0</rights><oa>free_for_read</oa><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><link.rule.ids>228,230,780,885</link.rule.ids><linktorsrc>$$Uhttps://arxiv.org/abs/2205.06933$$EView_record_in_Cornell_University$$FView_record_in_$$GCornell_University$$Hfree_for_read</linktorsrc><backlink>$$Uhttps://doi.org/10.48550/arXiv.2205.06933$$DView paper in arXiv$$Hfree_for_read</backlink></links><search><creatorcontrib>Ramasubramanian, Kamala</creatorcontrib><creatorcontrib>Raina, Ashutosh</creatorcontrib><creatorcontrib>Mace, Jonathan</creatorcontrib><creatorcontrib>Alvaro, Peter</creatorcontrib><title>ACT now: Aggregate Comparison of Traces for Incident Localization</title><description>Incidents in production systems are common and downtime is expensive.
Applying an appropriate mitigating action quickly, such as changing a specific
firewall rule, reverting a change, or diverting traffic to a different
availability zone, saves money. Incident localization is time-consuming since a
single failure can have many effects, extending far from the site of failure.
Knowing how different system events relate to each other is necessary to
quickly identify \emph{where} to mitigate. Our approach, Aggregate Comparison
of Traces (ACT), localizes incidents by comparing sets of traces (which capture
events and their relationships for individual requests) sampled from the most
recent steady-state operation and during an incident. In our quantitative
experiments, we show that ACT is able to effectively localize more than 99% of
incidents.</description><subject>Computer Science - Distributed, Parallel, and Cluster Computing</subject><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2022</creationdate><recordtype>article</recordtype><sourceid>GOX</sourceid><recordid>eNotz7tqwzAYhmEtGUrSC-hU3YBdWWd3M6ZJA4Ys3s0fHYzAloJsesjVN007fdvL9yD0VJGSayHIC-Sv8FFSSkRJZM3YA2qatscxfb7iZhyzG2F1uE3zBXJYUsTJ4z6DcQv2KeNjNMG6uOIuGZjCFdaQ4g5tPEyLe_zfLer3b337XnSnw7FtugKkYoXlgisDWsnKGwmc3O5I5Tg4Ss9EW0V9TZnRmjOtrKnl2QJUoFRlCQgu2BY9_2XvhuGSwwz5e_i1DHcL-wG0G0ME</recordid><startdate>20220513</startdate><enddate>20220513</enddate><creator>Ramasubramanian, Kamala</creator><creator>Raina, Ashutosh</creator><creator>Mace, Jonathan</creator><creator>Alvaro, Peter</creator><scope>AKY</scope><scope>GOX</scope></search><sort><creationdate>20220513</creationdate><title>ACT now: Aggregate Comparison of Traces for Incident Localization</title><author>Ramasubramanian, Kamala ; Raina, Ashutosh ; Mace, Jonathan ; Alvaro, Peter</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-a673-d4547ca8761fc6a4055067e4ae22b08d72f923c884387dc96bdaa1a771d0a5453</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2022</creationdate><topic>Computer Science - Distributed, Parallel, and Cluster Computing</topic><toplevel>online_resources</toplevel><creatorcontrib>Ramasubramanian, Kamala</creatorcontrib><creatorcontrib>Raina, Ashutosh</creatorcontrib><creatorcontrib>Mace, Jonathan</creatorcontrib><creatorcontrib>Alvaro, Peter</creatorcontrib><collection>arXiv Computer Science</collection><collection>arXiv.org</collection></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>Ramasubramanian, Kamala</au><au>Raina, Ashutosh</au><au>Mace, Jonathan</au><au>Alvaro, Peter</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>ACT now: Aggregate Comparison of Traces for Incident Localization</atitle><date>2022-05-13</date><risdate>2022</risdate><abstract>Incidents in production systems are common and downtime is expensive.
Applying an appropriate mitigating action quickly, such as changing a specific
firewall rule, reverting a change, or diverting traffic to a different
availability zone, saves money. Incident localization is time-consuming since a
single failure can have many effects, extending far from the site of failure.
Knowing how different system events relate to each other is necessary to
quickly identify \emph{where} to mitigate. Our approach, Aggregate Comparison
of Traces (ACT), localizes incidents by comparing sets of traces (which capture
events and their relationships for individual requests) sampled from the most
recent steady-state operation and during an incident. In our quantitative
experiments, we show that ACT is able to effectively localize more than 99% of
incidents.</abstract><doi>10.48550/arxiv.2205.06933</doi><oa>free_for_read</oa></addata></record> |
fulltext | fulltext_linktorsrc |
identifier | DOI: 10.48550/arxiv.2205.06933 |
ispartof | |
issn | |
language | eng |
recordid | cdi_arxiv_primary_2205_06933 |
source | arXiv.org |
subjects | Computer Science - Distributed, Parallel, and Cluster Computing |
title | ACT now: Aggregate Comparison of Traces for Incident Localization |
url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-03T19%3A18%3A43IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-arxiv_GOX&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=ACT%20now:%20Aggregate%20Comparison%20of%20Traces%20for%20Incident%20Localization&rft.au=Ramasubramanian,%20Kamala&rft.date=2022-05-13&rft_id=info:doi/10.48550/arxiv.2205.06933&rft_dat=%3Carxiv_GOX%3E2205_06933%3C/arxiv_GOX%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_id=info:pmid/&rfr_iscdi=true |