Empty tracer config header sent if no config selected

[chetanmeh]

There is a panel to select/enable ad hoc loggers. If none of the logger is selected then an empty tracer config header is sent which causes request to fail on server side. This has been handled better with SLING-6118 however it would be good that plugin does not send any header if no logger is selected

[davidjgonzalez]

@chetanmeh I changed it to send Sling-Tracer-Config:sling-tracer-configs-not-set;caller=true if no tracer sets are specified. I did this so we can still send ;caller=true which is now helpful (with the new LoggerNames panel) to pick a tracerSet to tracer on; else its a chicken-and-the-egg situation.

This seems to work fine unless there is a better syntax?

[chetanmeh]

Note that the logger names are collected by default and does not depend on passing caller param. That param is only required if you are interested in caller stacks

[davidjgonzalez]

Ah; I thought it odd since the caller is attached to each tracer set.

Let me check again - I had the issue where loggernames were empty when my sling-tracer-config header was not present, thus the dummy value.