From 7dfea510d5b54fee7ad1059ff10ce4b158f33ef6 Mon Sep 17 00:00:00 2001 From: Henry de Valence Date: Fri, 20 Nov 2020 15:12:30 -0800 Subject: [PATCH] state: remove state_trace span This turns out not to give much additional information when stacked with child spans. --- zebra-state/src/service.rs | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/zebra-state/src/service.rs b/zebra-state/src/service.rs index c6934eb47..5593cec27 100644 --- a/zebra-state/src/service.rs +++ b/zebra-state/src/service.rs @@ -383,13 +383,7 @@ impl Service for StateService { Poll::Ready(Ok(())) } - // Because the request might have a verbose debug output (e.g., - // an entire block), include it only in a second trace-level span. - // For some reason putting them in this order causes the info-level - // span to be entered first. - #[allow(unused_braces)] // fixes a spurious warning from the proc macro - #[instrument(name = "state_trace", level = "trace", skip(self))] - #[instrument(name = "state", level = "info", skip(self, req))] + #[instrument(name = "state", skip(self, req))] fn call(&mut self, req: Request) -> Self::Future { match req { Request::CommitBlock { block } => {