-
Notifications
You must be signed in to change notification settings - Fork 721
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
CAD-379 Update nix/cardano-node-service.nix
with tracing arguments
#444
Conversation
60b7e23
to
5058945
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how can this be tested?
5058945
to
91780d0
Compare
I'm not sure, running the output of
The output script on my branch does look correct however. The scripts successfully passing in hydra should confirm that I didn't break anything but I'll need somebody from devops to confirm the logging output is what they want. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These shouldn't be here. They should be argument in cmd of mkScript instead.
You can test with curl localhost:12798/metrics|grep cardano. If you see the metrics, it works.
91780d0
to
cb00aa9
Compare
nix/cardano-node-service.nix
with tracing argumentsnix/cardano-node-service.nix
with tracing arguments
nix/cardano-node-service.nix
with tracing argumentsnix/cardano-node-service.nix
with tracing arguments
cb00aa9
to
95d9fb2
Compare
bors r+ |
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]>
Build succeeded |
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.