From a5b89681e6566206c205cc37469a267b4dccb313 Mon Sep 17 00:00:00 2001 From: Ken Sedgwick Date: Thu, 25 Apr 2024 14:35:57 -0700 Subject: [PATCH] demote two specific noisy plugin_hook logging entries to trace These are too prolific at the debug level: DEBUG lightningd: Calling rpc_command hook of plugin clboss DEBUG lightningd: Plugin clboss returned from rpc_command hook call As seen in https://github.com/ZmnSCPxj/clboss/issues/194 --- lightningd/plugin_hook.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lightningd/plugin_hook.c b/lightningd/plugin_hook.c index 62dc9d438ec4..e32986779b07 100644 --- a/lightningd/plugin_hook.c +++ b/lightningd/plugin_hook.c @@ -146,7 +146,7 @@ static void plugin_hook_callback(const char *buffer, const jsmntok_t *toks, /* We really only handle plugins dying: other errors are fatal. */ if (h) { - log_debug(ph_req->ld->log, + log_trace(ph_req->ld->log, "Plugin %s returned from %s hook call", h->plugin->shortname, ph_req->hook->name); resulttok = json_get_member(buffer, toks, "result"); @@ -197,7 +197,7 @@ static void plugin_hook_call_next(struct plugin_hook_request *ph_req) } while (ph_req->hooks[ph_req->hook_index] == NULL); plugin = ph_req->hooks[ph_req->hook_index]->plugin; - log_debug(ph_req->ld->log, "Calling %s hook of plugin %s", + log_trace(ph_req->ld->log, "Calling %s hook of plugin %s", ph_req->hook->name, plugin->shortname); req = jsonrpc_request_start(NULL, hook->name, ph_req->cmd_id, plugin->non_numeric_ids,