...
The first time the script runs, it is going to request all the data for each configured poller. Next time, it is going to request only the modified data since the last synchronisation.
3.0.
...
5
| Status | ||||
|---|---|---|---|---|
|
Released August 22, 2019
opCharts 3.0.5 requires NMIS 9.0.6
- Support for centralised configuration from the master with support for OMK and NMIS files.
3.0.
...
4
| Status | ||||
|---|---|---|---|---|
|
- Support for NMIS 9 to show poller nodes from the master.
- A new button is added on the peers screen to edit manually the poller's url.
3.0.
...
3
| Status | ||||
|---|---|---|---|---|
|
- Support for node deletion on the pollers. When a node was deleted on the poller, all this data wasn’t remove on the master. Now the pull process is going to remove nodes and associated data that was removed on the poller.
- Retry policy on pull failures: If there was a failure during the poller update, the pull finished. Now it is possible to specify a retry policy:
- retry number: How many times retry a request before finish the process unsuccessfully. 3 is the default value.
- delay: How many seconds is going to wait between retries (5 seconds by default).
- It is possible to modify this params in opCommon.nmis:
...
- Show the registry synchronised data on the GUI.
- Small improvements on the GUI.
3.0.2-
...
1
| Status | ||||
|---|---|---|---|---|
|
Hot fix to solve the problem of visualise the nodes graphics of the poller from the master.
3.0.
...
2
| Status | ||||
|---|---|---|---|---|
|
On this version, the master is going to request the information by chunks. The number of calls is based on the chunk size and the number of results. The chunk size can be modified on conf/opCommon.nmis on the poller, with the next parameter (Note that a service restart is needed to use the new parameters):
...