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.

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

When parsing the logs, caching would help speed up processing #4851

Closed
TheWitness opened this issue Jun 30, 2022 · 1 comment
Closed

When parsing the logs, caching would help speed up processing #4851

TheWitness opened this issue Jun 30, 2022 · 1 comment
Labels
bug Undesired behaviour confirmed Bug is confirm by dev team logging Logging issue resolved A fixed issue
Milestone

Comments

@TheWitness
Copy link
Member

Describe the bug

When parsing the Cacti.log file, if you have several thousand log's from say spine at -V 3 or -V 5, the number of database turns required to display the log is excessive. Local Caching is required.

Expected behavior

More responsive UI.

@TheWitness TheWitness added bug Undesired behaviour logging Logging issue confirmed Bug is confirm by dev team labels Jun 30, 2022
@TheWitness TheWitness added this to the v1.2.22 milestone Jun 30, 2022
TheWitness added a commit that referenced this issue Jun 30, 2022
Processing the regex rules performs too many database turns to display the log when there are thousands of log entries in debug mode.
@TheWitness TheWitness added the resolved A fixed issue label Jun 30, 2022
TheWitness added a commit that referenced this issue Jun 30, 2022
This device is not reachable via a URL.  Handle it differently.
@netniV
Copy link
Member

netniV commented Jul 1, 2022

looks good to me.

@netniV netniV closed this as completed Jul 1, 2022
@netniV netniV changed the title Too Many Turns on Log Parsing When parsing the logs, caching would help speed up processing Aug 14, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Nov 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Undesired behaviour confirmed Bug is confirm by dev team logging Logging issue resolved A fixed issue
Projects
None yet
Development

No branches or pull requests

2 participants