Project

General

Profile

Actions

Feature #17185

open

[adc] add broken node metrics

Added by Ward Vandewege over 3 years ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assigned To:
Category:
Crunch
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
(Total: 0.00 h)
Story points:
-
Release:
Release relationship:
Auto

Description

Add a broken-node metric

(counter) VMs that are determined to be "broken nodes"

Add a label to separate VMs marked as broken before the first container is started on them (likely boot problem) and after (likely container related problem).

Note that we already have a boot outcome metric. Make sure that we increment the broken node counter ("before first container" label) when we have a boot outcome == failed, though not in the timeout case.


Subtasks 1 (1 open0 closed)

Task #17554: ReviewNew

Actions

Related issues

Related to Arvados - Feature #16636: [arvados-dispatch-cloud] Add instance metricsResolvedWard Vandewege08/03/2020

Actions
Related to Arvados - Bug #17186: [dispatch] broken node logs should also be copied to a-d-c logsNew

Actions
Actions #1

Updated by Ward Vandewege over 3 years ago

  • Related to Feature #16636: [arvados-dispatch-cloud] Add instance metrics added
Actions #2

Updated by Ward Vandewege over 3 years ago

  • Description updated (diff)
Actions #3

Updated by Ward Vandewege over 3 years ago

  • Related to Bug #17186: [dispatch] broken node logs should also be copied to a-d-c logs added
Actions #4

Updated by Ward Vandewege over 3 years ago

  • Description updated (diff)
Actions #5

Updated by Tom Clegg about 3 years ago

  • Category set to Crunch
  • Assigned To set to Tom Clegg
  • Target version set to 2021-04-28 bughunt sprint
Actions #6

Updated by Peter Amstutz about 3 years ago

  • Target version deleted (2021-04-28 bughunt sprint)
Actions #7

Updated by Lucas Di Pentima over 1 year ago

  • Release set to 60
Actions

Also available in: Atom PDF