-
Notifications
You must be signed in to change notification settings - Fork 15
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
Scrape action should not be performed during startup when scan interval set to 0 #359
Comments
What should the value of the sensors be on startup in this case? |
To be honest : don't care, because I don't need nor use them at that moment - that's why their scan interval is set to 0 in the first place. |
Would also like this. I use the IMO keep the default behavior as-is but introduce a new optional boolean like |
Glad somebody agrees with my point.
|
I agree with @Paul-Vdp and I will work on implementing this. It's not a small feature request though, so it will take some time. |
Much obliged @danieldotnl |
Title says it all.
My scrape sensor relies on 'params' for some parts of the resource. Because these params have not (yet) been initialized on startup, the (unwanted and unneeded !) scrape results in errors.
The text was updated successfully, but these errors were encountered: