-
Notifications
You must be signed in to change notification settings - Fork 33
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
For Cloud: include cribl section in configuration output #918
Comments
I added the cribl section to json output, and added unit tests for the same. For confirmation, I ran these commands, which I expected to write the (default) config of
From this, I inspected /tmp/scope.log and saw the cribl output I expected:
By piping the the json portion of this last line through jq, I made it easier to confirm that the cribl node and appropriate sub-nodes are there, with default values:
|
TLDR: I see cribl section in the #966. I have tested the #966 with a following command: Terminal 1
Terminal 2
Besides seeing the cribl section in The start info messageon master branch:
on #966:
The content of
|
For debugging we output the process configuration in our logging output if the logging level is set to do so ("info", I think?). Right now the cribl section is not included in the output which makes it hard to double-check configuration settings when using this cribl mode. Here's what I mean by cribl section (I grabbed this from the input scope.yml file, but we should output the section in json as we do with the rest of our config):
The text was updated successfully, but these errors were encountered: