Re: [cacti-user] data query re-index method

[Ceylan, H. <Has...@do...>]

I see this problem with data queries, specially on windows servers:

On windows servers, there is a process list that cpu, foot print can be tracked using informant oids. The process is index based where depending on the location of the index, a process can be tracked. However, the caveat is that on windows servers process comes and goes away all the time thus index location changes. How does cacti tackle this problem?

I see that there are 4 data-query re-index methods, none, uptime goes backwards, index count changed, and verify all fields. Assuming that index will change, which re-index method would be more applicaple? Regardles of the situation, what would be the best re-index method?