step monitoring (event_mon) on swarming |
|||||||||||
Issue descriptionBuildbot sends events for each step, e.g. duration, results, etc. Swarmbucket does not have that. We should probably do it with logdog: a separate service is listening to logdog's public pubsub topic, loads logs, parses them as milo protos and sends events to event_mon
,
Aug 3 2016
,
Sep 1 2016
,
Oct 4 2016
,
Oct 21 2016
,
Oct 22 2016
We can translate the steps in the annotation proto at the end of a build from within kitchen into eventmon events. https://chromium.googlesource.com/external/github.com/luci/luci-go/+/master/common/proto/milo/annotations.proto
,
Oct 23 2016
,
Nov 2 2016
,
Jan 17 2017
Assigning to Pawel since he did the implementation in December. Can we mark it as Fixed?
,
Feb 22 2017
(bulk edit) setting P2 because this bug has luci label and not _required_ for the current milestone
,
Feb 22 2017
,
Dec 1 2017
Removing myself from bugs because of team transfer, back to re-triage. See https://goto.google.com/phajdan-goodbye-chrome (Google-internal) and issue 783662 . In case of any questions, feel free to ask - use phajdan@google.com for a faster response.
,
Dec 1 2017
That's technically fixed. Issue 765435 is about BQ. |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by sheriffbot@chromium.org
, Jul 5 2016