If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Viewable log parser logs

RESOLVED WONTFIX

Status

Tree Management
Treeherder: Data Ingestion
P4
normal
RESOLVED WONTFIX
3 years ago
5 months ago

People

(Reporter: lightsofapollo, Unassigned)

Tracking

Details

(Reporter)

Description

3 years ago
In the case of using non-bb tooling the log parser is pretty opaque process. When it fails there is very little indication why and in the case of success (but incomplete parsing) there is no indication what is missing... Ideally we could have a "log parser log" that is an artifact (stored on s3 or somewhere with a short expiration) that would log the parsing state and dump useful information particularly in the case of an error.

Updated

3 years ago
Blocks: 1072676

Comment 1

3 years ago
Does the access to newrelic now solve this use case?

If not, would bug 1087999 solve this?
Or do we need additional logging in the log parser as well?
OS: Mac OS X → All
Priority: -- → P3
Hardware: x86 → All

Updated

3 years ago
Flags: needinfo?(jlal)
(Reporter)

Comment 2

3 years ago
It really helps me personally but I think we should have some kind of artifact ("parser error logs") if/when the parser fails. This is mostly useful for people who are submitting data via the API. This goes with the team of (self-service API) if you cannot see the error its almost impossible to debug without access to all the right tooling.
Flags: needinfo?(jlal)

Updated

3 years ago
No longer blocks: 1072676
Component: Treeherder → Treeherder: Data Ingestion

Updated

3 years ago
Priority: P3 → P4

Updated

3 years ago
Blocks: 1152742

Updated

5 months ago
Status: NEW → RESOLVED
Last Resolved: 5 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.