User Tools

Site Tools


monitor:server:specifics

Server Specifics

In this section we are going to explain some details about the information stored in the CouchBase database located at the back end of the monitoring server.

Document types

As mentioned before, the CouchBase server is a database that supports the storage of JSON files. In our case these files will contain the information monitored by the CONFINE monitoring system. Accordingly, we will have four basic types of JSON documents:

  1. Node: This kind of files contain the node-centric data monitored by the client daemons running on the Research Devices.
  2. Synthesized: This kind documents contain data monitored by the server (more specifically, by the collect module).
  3. Traceroute: This type of files contain the information about the network topology collected by a pluggable client daemon running on the Research Devices.
  4. Most recent: these documents contain the most recent data stored in the database. They are copies of the most recent documents. For every one of the three types of documents explained above, the server will generate a copy of the most recent ones. Therefore, if we take into account the “most recent” documents, we will have six different types of documents stored in the database.

Figure 6 shows an example of how the monitoring server generates the “most recent” documents from the “node” documents collected from all the Research Devices. As we can see in the figure, for all the JSON documents of type node generated by an RD, the server creates another document of type “node_recent” containing a copy of the last node document received.

                  Figure 6: Generation of the "most recent" documents by the monitoring server

How documents are stored

As explained in the Monitoring Client section, the RDs monitor node-centric data every 60 seconds. This data is saved in a JSON format, which means that the RDs will generate a JSON document every minute. This information is stored in the database of the server using an unique identifier composed by the IPv6 of the RD node and a timestamp corresponding to the moment when the monitoring server receives the information sent by the RD. Figure 7 depicts an example of a node document generated at time Δ by an RD with IP “IPv6”. This document is received by the server at time Δ' and stored in the database using the document identifier IPv6-Δ'.

                  Figure 7: How documents are stored in the database using a document identifier       

Equally, for any type of JSON document generated by the client or by the server, it will have a document identifier composed by the IPv6 of the node that generated the document and a timestamp corresponding to the moment when the monitoring server receives it.

monitor/server/specifics.txt · Last modified: 2014/07/22 18:43 by esunly