iofog/diagnostics-arm repository overview

Use the 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 the detailed report that the Diagnostics Container creates, you can be aware of the issues that may arise.

Diagnostics Container performs the following checks:

Client creation (tries to create ioFog client that checks if all the required parameters are provided);

• Tries to update config (tries to get ioFog config, ping report_url provided from config);
• Sends HEARTBEAT “signal” to report_url (every 30 sec if not specified);
• Tries to connect to Sockets (Control and Message Websockets);
• Checks if Comsats are available (pings list of Comsats’ IPs provided in config);
• Checks if RestBlue is available (connects to RestBlue System Container);
• Checks if Log Container is available (connects to Log System Container).

Config: "report_url": config specifying where to send logs (log to console; 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" and uses http) "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

All the results can be found in container's logs.

Version: latest (0.1)

Code: https://github.com/ioFog/example-microservices/tree/master/diagnostics⁠ Eclipse ioFog: https://github.com/ioFog/ioFog⁠