How to handle frequent presence of undiscovered items?
I have been setting up a backup monitoring template in zabbix, I have an API request that returns a json containing jobs info.
Thing is, I can only search for the jobs within a set timeframe, be it one week, two weeks, month or even a year. I have currently decided on one week.
The template will create job items, job application prototypes, containing the name, percentage of completion, time started, time elapsed etc. etc. I also want to set up some triggers (if a job fails for example).
So the main issue is that after one week, some jobs (probably already complete) will not be discovered anymore cause the API doesnt't include them anymore in the json response.
Now I am wondering, there are a couple ways to handle this:
1. Set an huuuuge time frame (40 years for example) - probably the worst idea, there will be thousands of irrelevent job items, not to mention it will be really slow after a while
2. Hope that zabbix will just replace the item and the item app prototype with the new ones without any fuss - pretty unlikely from what I know about how zabbix works, but correct me if I am wrong
3. Set a really short "Keep lost resources" period for the template, so the no longer discovered jobs will not clutter the server.
At the moment, I am leaning towards the third option - it makes the most sense to me. But I wanted to ask your opinion on this issue, maybe you know some other ways to handle this? Thank you!
Thing is, I can only search for the jobs within a set timeframe, be it one week, two weeks, month or even a year. I have currently decided on one week.
The template will create job items, job application prototypes, containing the name, percentage of completion, time started, time elapsed etc. etc. I also want to set up some triggers (if a job fails for example).
So the main issue is that after one week, some jobs (probably already complete) will not be discovered anymore cause the API doesnt't include them anymore in the json response.
Now I am wondering, there are a couple ways to handle this:
1. Set an huuuuge time frame (40 years for example) - probably the worst idea, there will be thousands of irrelevent job items, not to mention it will be really slow after a while
2. Hope that zabbix will just replace the item and the item app prototype with the new ones without any fuss - pretty unlikely from what I know about how zabbix works, but correct me if I am wrong
3. Set a really short "Keep lost resources" period for the template, so the no longer discovered jobs will not clutter the server.
At the moment, I am leaning towards the third option - it makes the most sense to me. But I wanted to ask your opinion on this issue, maybe you know some other ways to handle this? Thank you!