Closed Bug 1561338 Opened 5 years ago Closed 5 years ago

[logging] Ensure that message handlers and oneShot tasks are logging something

Categories

(Taskcluster :: Services, task)

Product:
Taskcluster
Component:
Services
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: dustin, Assigned: dustin)

References

Details

We'll want to see that these processes are running reliably by looking for some kind of logging message from them. Services using tc-lib-iterate already log.

Summary: Ensure that message handlers and oneShot tasks are logging something → [logging] Ensure that message handlers and oneShot tasks are logging something
Blocks: 1565939

Confirmed for oneShot: every oneShot invocation is timed, so there is some logging output.

Looks like tc-github's handlers should use monitor.timedHandler. Index already does, as does notify. Hooks' listeners already do lots of logging.

I don't know what I was talking about. tc-github uses timedHandler.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Blocks: 1572775
You need to log in before you can comment on or make changes to this bug.