Closed Bug 1198284 Opened 9 years ago Closed 9 years ago

Parse taskcluster error and exception messages from task logs that originate from taskcluster components

Categories

(Tree Management :: Treeherder: Data Ingestion, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: garndt, Assigned: garndt)

Details

Attachments

(1 file)

46 bytes, text/x-github-pull-request
emorley
: review+
Details | Review
In bug 1174557 there was a regex introduce to parse error messages in the format "^\[taskcluster\] Error:".  This worked for some things, but limited the messages to be only [taskcluster] where we have components that log as [tc-vcs].  Also, it relies on "Error:" being the start of the error message, which doesn't always happen or if it does makes some information in the error message redudant.

We are switching some of our tooling to log in the format "[component:event] message" such that a taskcluster error could appear as:

[taskcluster:error] Some bad message

Or in the case of one of our tools:
[taskcluster-vcs:error] Bad things happened


This bug is to allow any arbitrary component to put something into the logs with an "error" or "exception" event and TH parse that out.
Attached file Treeherder PR 905
Attachment #8652355 - Flags: review?(emorley)
Comment on attachment 8652355 [details] [review]
Treeherder PR 905

Thank you! :-)
Attachment #8652355 - Flags: review?(emorley) → review+
This is also now deployed :-)
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: