Child pages
  • See poller nodes from the master

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This features works better with opHA 3.0.4 and opCharts 3.0.6. We still can see the poller nodes when working with previous versions of opHA, but we are not going to be able to access the poller url. 

When opHA 3.0.4 synchronise a peer, is going to place in a new nmisng database collection, the information for that poller. So, NMIS can access all the information needed from the pollers. 

Image Modified

The document looks like this:

{
  "_id":"5d26d988860b5b04db8c4af1",
  "cluster_id":"0d28dcf0-8fe2-49d9-a26f-6ccf3f2875c0",
  "updated":"2019-07-11T06:39:16.000Z",
  "url_base":"http://poller-nine","server_priority":5,
  "nmis_url_base":"nmis9",
  "auth":"U2FsdGVkX19Nn5uXJ6OpyM/...",
  "nmis_cgi_url_base":"cgi-nmis9",
  "server_name":"poller-nine",
  "other_peers":[]
}

The object NMING implements new accessors for this information:

  • remote_collection: Returns the collection
  • get_remote(filter): returns all remotes matching the query created with the filter

When we click on a poller node, NMIS is going to redirect to the poller server:

Image Modified

Image Modified

If we can't see the node url properly, we need to check if the information is correct in opHA. When opHA works with a peer with an old version of opHA, some information is going to be empty. 

Other considerations:

  • Collect is only going to keep collecting local nodes. 
  • We can manage all nodes using node_admin. 

opHA 3.0.4

When pulling an existing peer, the Remote collection in NMIS database is going to be created, if still doesn't exist. 

We can modify this information when we edit a peer (http://server/en/omk/opHA/peers):

Image Modified

opCharts 3.0.6

When running opHA 3.0.4 we will be able to see the nodes url, that it is going to redirect us to the NMIS node URL:

Image Modified