Thoughts on configuring action-based timer reporting

[Tom Zeller]

> we could drive this pretty effectively with a child context

Makes sense. That's the paradigm we've been following, it seems.

> That way the overhead for the "off" case is just a check for an absent child context, and otherwise it would know to check to see if it should start or stop a timer based on the identity of the profile action class.

Just a comment wondering if there should be an activation condition
for the "off" case, maybe per metric or action ? dunno