Hi @fe11x , no problem. sorry for the delay.
It depends on your script, assuming that you used Chronograf to generate the TICK script you might have selected the endpoints you want to monitor. That would add a part to your script something like
var whereFilter = lambda: ("endpoint" == 'endpoint1' OR "endpoint" == 'endpoint2')
If you click to edit the tick script, you pick the measurement and you can see the available tags in there. Selecting the values in “endpoint” or “station” tag will add them to that filter above ^^^^, to remove the endpoint you just need to unselect it.
Sorry i don’t have access to any test data at the moment to post a screenshot.
That works ok if you know when an endpoint will come online and you plan to add it. However if you don’t when this will happen it can be tedious to manage and eventually cumbersome if you have endpoints coming on at random intervals.
If you don’t select endpoints, you’ll get a value like this for the whereFilter
var whereFilter = lambda: TRUE
That will make your script process against all endpoints that appear in the measurement. The issue there is that as you’ve seen, once the endpoint goes offline it would keep sending out the alerts. In this case, i’d use the stateChangesOnly() node mentioned in my previous post to stop the alerts.
Then, you would only receive an alert if the endpoint came back online - You would get an OK message, then if the endpoint disappeared again you would get another alert.