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

Device failure count setting not respected #470

Closed
bmfmancini opened this issue Nov 23, 2020 · 3 comments
Closed

Device failure count setting not respected #470

bmfmancini opened this issue Nov 23, 2020 · 3 comments
Milestone

Comments

@bmfmancini
Copy link
Member

Hello Guys

I just found an issue where when you set a fail count for a specific device that setting is not being respected
the device instead waits for the global fail count to trigger a down event

I have set the device to fail at 1 poll cycle at 1-minute polling
yet the device wait for 10 minutes which is the setting I have in the device defaults

My test best is 1.2.12 but I am seeing the same thing in 1.2.15

@TheWitness
Copy link
Member

That's not the same thing. The fail count is the number of times it's failed since you last reset the counters. So, you are misunderstanding the purpose of that column.

@TheWitness TheWitness transferred this issue from Cacti/cacti Nov 27, 2020
@TheWitness
Copy link
Member

Moving this here as it's a thold setting.

@TheWitness TheWitness reopened this Nov 27, 2020
@TheWitness TheWitness added this to the Thold 3.0 milestone Jul 25, 2023
TheWitness added a commit that referenced this issue Apr 6, 2024
Device failure count setting not respected
TheWitness added a commit that referenced this issue Apr 6, 2024
TheWitness added a commit to Cacti/cacti that referenced this issue Apr 6, 2024
Making Cacti compatible with Cacti/plugin_thold#470
TheWitness added a commit to Cacti/cacti that referenced this issue Apr 6, 2024
Making Cacti compatible with Cacti/plugin_thold#470
@TheWitness
Copy link
Member

Fixed in Cacti now too. Device Console pick.

TheWitness added a commit that referenced this issue Apr 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants