cerc-io/go-ethereum
18
0
Fork 0
Code Issues 9 Pull Requests Packages Projects Releases 66 Wiki Activity

Make logging level configurable during runtime #302

New Issue
Open
opened 2023-01-11 20:37:30 +00:00 by i-norden · 1 comment
i-norden commented 2023-01-11 20:37:30 +00:00
Member
Copy Link

From talking with @srwadleigh

This would help with debugging issues which pop up during operation without requiring us to bring down the node and bring it up with a different log level. Even more valuable in situations where an issue only occurs under mainnet/production conditions after some accumulation of time/events, as in this case when we cycle the node to investigate the issue the issue may have dissolved during the process of cycling the node.

From talking with @srwadleigh This would help with debugging issues which pop up during operation without requiring us to bring down the node and bring it up with a different log level. Even more valuable in situations where an issue only occurs under mainnet/production conditions after some accumulation of time/events, as in this case when we cycle the node to investigate the issue the issue may have dissolved during the process of cycling the node.
telackey commented 2023-01-13 22:26:40 +00:00
Member
Copy Link

I think you can use the debug API to do this, specifically the debug_verbosity and debug_vmodule methods:

https://geth.ethereum.org/docs/interacting-with-geth/rpc/ns-debug#debugverbosity
https://geth.ethereum.org/docs/interacting-with-geth/rpc/ns-debug#debugvmodule

I think you can use the `debug` API to do this, specifically the `debug_verbosity` and `debug_vmodule` methods: https://geth.ethereum.org/docs/interacting-with-geth/rpc/ns-debug#debugverbosity https://geth.ethereum.org/docs/interacting-with-geth/rpc/ns-debug#debugvmodule
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
bug

   
critical

   
duplicate

   
enhancement

   
epic

   
help wanted

   
in progress

   
invalid

   
low priority

   
question

   
rebase

   
v1

   
v5

   
wontfix
  
Copied from Github

An issue or PR manually copied from GitHub.

  
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No Label
bug
critical
duplicate
enhancement
epic
help wanted
in progress
invalid
low priority
question
rebase
v1
v5
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/go-ethereum#302
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?