I don't think we want to have a dependency on JobsModel here. It would be good if the logparser can function standalone without treeherder dependencies. Instead of passing in a job_id, pass in the url to the log. You could add a JobsModel method that retrieves the urls and calls the logparser, this will allow the logparser to be used by non-treeherder clients. A good example of this type of use case would be a web service method that takes a log url and returns structured json data, there won't be an associated job_id.