The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Feature #914

A logging harness needs to be added to the Indirector

Added by Luke Kanies over 6 years ago. Updated over 3 years ago.

Status:AcceptedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:reports
Target version:-
Affected Puppet version:0.24.4 Branch:
Keywords:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This ticket may be automatically exported to the PUP project on JIRA using the button below:


Description

Some functions that pass through the indirector need to be logged sometimes, but not all the time — for instance, we want to log compile times when compiling a remote configuration, but not a local one.

We need some kind of harness that allows us to declaratively specify how things should log under what circumstances.

History

#1 Updated by Redmine Admin almost 6 years ago

  • Status changed from 1 to Needs Decision

#2 Updated by Luke Kanies over 5 years ago

  • Status changed from Needs Decision to Accepted
  • Affected Puppet version set to 0.24.4

#3 Updated by James Turnbull almost 5 years ago

  • Assignee deleted (Puppet Community)

#4 Updated by Nigel Kersten over 3 years ago

  • Status changed from Accepted to Needs More Information
  • Assignee set to Luke Kanies

Can you expand on whether this is relevant anymore Luke?

#5 Updated by Luke Kanies over 3 years ago

  • Status changed from Needs More Information to Accepted
  • Assignee deleted (Luke Kanies)

I think it is still relevant, but obviously not urgent.

Basically, if you are trying to figure out why you can’t find a given host’s facts, it’s just about impossible. You don’t know which terminus was looked in, nor where it looked (e.g., which directory).

The entire indirector is absent of logging, and tracing is not that useful in many cases.

#6 Updated by Nigel Kersten over 3 years ago

excellent. thanks.

Also available in: Atom PDF