Closed Bug 1163758 Opened 10 years ago Closed 10 years ago

Port the OF logparser to AWS

Categories

(Tree Management Graveyard :: OrangeFactor, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jgriffin, Assigned: jgriffin)

References

()

Details

The OF logparser is currently housed in PHX1, but we need to move it out of there. I'm going to port it to AWS.
Seeing as the method of calculating the denominator for the orangefactor is already incorrect - I wonder if we could just use a treeherder API for "number of pushes" and use that for now instead? Or alternatively, make the OF graph just use the absolute number of failures, rather than a rate? It just seems pretty unfortunate to have to re-host the log parser, when we don't actually need the contents of the logs parsed, and will hopefully bin elasticsearch entirely soon.
Is there already an API in Treeherder that could be used for this? Transplanting this to AWS is pretty trivial and doesn't incur long-term costs, so it's a backup strategy in case no one has the time to do the necessary refactoring in OF before we need to be out of PHX1.
Re API, I guess we could just use the the pushlog directly? Though if it's not much hassle then perhaps AWS is the best solution short term..
I tried this out and it was easier than I thought; I'll file a separate bug rather than overloading this one.
We're just removing the dependency on logparsing instead in bug 1164260.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.