Diagnostics Container

Diagnostics Container performs diagnostics of basic functionality to work with ioFog.

Use diagnostic container if something goes wrong on your machine with ioFog agent, e.g. Comsats are not available, a container cannot connect to ioFog host, ioFog client is not created, RestBlue or Log Container are not available and so on. With a detailed report you can be aware of these issues that may arise.

Diagnostics Container performs the following checks:

Examples of configuration JSONs:

Complete config for Diagnostics container should look the following way:

{ "report_url": { "ip": "", "host" : "localhost", "port" : 6666, "url" : "/report", "secure" : false }, "comsat_list" : [ "", "", "" ], "ping_rb": true, "ping_logger": true, "interval" : 60}

If "report_url" is not provided or is not available then the whole output will be logged to console. Following example is valid and can be used if you don't want to send logs outside:

{"comsat_list" : [ "", "", "" ], "ping_rb": true, "ping_logger": true, "interval" : 60}

Config explanation:

"comsat_list" : list of Comsats that should be pinged
"ping_rb" : connect to RestBlue System Container if true is set
"ping_logger" : connect to Log System Container if true is set
"interval" : perform checks after the specified interval; every 30 sec if not specified
"report_url": config specifying where to send logs (not required parameter)
"ip": ip of machine for log reporting (used when host is unreachable)
"host" : host of machine for log reporting
"port" : port of listening server that is ready for log receiving (if not specified assumed to be 80)
"url" : relative url where to send config
"secure" : set this parameter to true if you want to use https protocol (if not specified assumed to be false using http)

Launching the Container

The element you need can be found in the catalog on the Build page (named "Diagnostics")

You can drag and drop the element (either x86 or ARM one) to the main area of Build page, provide Name, ioFog to run this element, as well as Configuration JSON (examples are provided above).

Diagnostics output is the detailed logs about system functionality.

1. Go to Terminal.

2. Get the list of containers with the following command: sudo docker ps in order to use container name for obtaining logs

3. See detailed logs about system functionality with the following command: sudo docker logs CONTAINER_NAME (the last value is Container name taken from the output of sudo docker ps).