-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debugging output not working as expected #80
Comments
Running with Here's a release Zeek build with no special CAF logging configuration:
A standalone Broker debug build (don't think debug matters, just what I happened to build) and again without special CAF logging configuration (looks like it defaults to QUIET logging level):
|
I was also testing current |
The plan is to add the capability to switch on two levels of Broker-side debug output:
Turning that on will work through an environment variable and through config files, and it will work in both release & debug builds. Goal is to get this into Zeek 3.1 still. |
CAF defaults to quiet, but the logger is always available since recent CAF versions.
Broker uses its own set of logging macros. They are independent of whatever So far I did not measure how much overhead these extra branches amount to. Also, there's currently no build option for removing them. Maybe we should run some benchmarks to see whether it's worth it to add a
I'm working on this, but as it turns out: CAF doesn't propagate this properly. CAF only signals
Broker needs to knows which of the three it is, because only in one case we'd try to reconnect.
I'll try to get this fixed on the CAF side with an 0.17.4 bugfix release in time. |
With the patch to CAF (submitted as PR 1023), I now see this output when trying to connect two incompatible Broker versions:
Tested by changing the application ID for one Broker endpoint on the command line. We already log this error in I'll also do a pass over Broker to improve usefulness of INFO and DEBUG logs, but I'd prefer to do that on the "new" code in |
Think we've got everything to call this done now: improved configuration for Broker logs and now using CAF 0.17.4 branch to better report version mismatches. Or re-open / correct me if wrong. |
Not sure if I'm missing something, but I'm not getting the debug output I'd expect.
According to an old commit, we have 3 environment vars:
However, no matter how I set these, I don't get any Broker-level messages, but only
caf.flow DEBUG
level messages. Would be good to review how debug logging is working currently and document how to activate it.Note I noticed this outside of Zeek with the new zeek-agent. That one hardcodes the debug level to -1 currently, which I changed to 2 when trying this. See also zeek/zeek-agent#2
The text was updated successfully, but these errors were encountered: