-
Notifications
You must be signed in to change notification settings - Fork 719
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
Move tracers into config .yaml
file
#443
Comments
it probably would make sense to type them like: |
@CodiePP I was thinking of a dictionary structure per tracer in the yaml file like this:
Or we can add an additional constructor to
or
|
444: CAD-379 Update `nix/cardano-node-service.nix` with tracing arguments r=jbgi a=Jimbo4350 Previously not specifying a tracer did not turn it off, it just changed its severity. Currently if you do not specify a tracer, that tracer is turned off. Therefore this is a temporary fix until #443 is implemented. Co-authored-by: Jordan Millar <[email protected]>
or |
Made the changes you suggested above 👍 I'd like to make verbosity definable per trace unless there is a reason not to. |
could there also be a global default for MinSeverity? so if it is not indicated for a tracer, then the default will be applied. |
Yep we could define that via |
447: Move tracers to `.yaml` files r=disassembler a=Jimbo4350 Specifying the tracers on the command line is cumbersome and the consensus is to move to them to the configuration `.yaml` files. Relevant: #443 Co-authored-by: Jordan Millar <[email protected]>
447: Move tracers to `.yaml` files r=Jimbo4350 a=Jimbo4350 Specifying the tracers on the command line is cumbersome and the consensus is to move to them to the configuration `.yaml` files. Relevant: #443 Co-authored-by: Jordan Millar <[email protected]>
Tracers should be specified from the config
.yaml
file as having them on the command line is cumbersome.The text was updated successfully, but these errors were encountered: