Skip to content
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.

Sign up for GitHub

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

Jump to bottom

The HBAR Limit Service is generating an excessive volume of logs. #3352

Open
quiet-node opened this issue Dec 23, 2024 · 0 comments
Open

The HBAR Limit Service is generating an excessive volume of logs. #3352

quiet-node opened this issue Dec 23, 2024 · 0 comments
Labels
internal For changes that affect the project's internal workings but not its outward-facing functionality.
Milestone
0.64.0

Comments

@quiet-node
Copy link
Member

quiet-node commented Dec 23, 2024 •
edited
Loading

Problem

The HBAR Limit Service is generating an excessive number of repetitive logs, making debugging highly challenging and inefficient.

Solution

Optimize the logging mechanism for the HBAR Limit Service to reduce redundant entries while maintaining sufficient detail for effective debugging.

Alternatives

No response
@quiet-node quiet-node added the enhancement New feature or request label Dec 23, 2024
@quiet-node quiet-node added this to the 0.64.0 milestone Dec 23, 2024
@quiet-node quiet-node changed the title HBAR Limit Service is logging way too many logs The HBAR Limit Service is generating an excessive volume of logs. Dec 23, 2024
@quiet-node quiet-node added internal For changes that affect the project's internal workings but not its outward-facing functionality. and removed enhancement New feature or request labels Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
internal For changes that affect the project's internal workings but not its outward-facing functionality.
Projects
Smart Contract Sprint Board
Status: Backlog
Milestone
0.64.0
Development

No branches or pull requests
1 participant
@quiet-node