Monitoring a Connection Server
In the Monitoring mashup for the Connection Server, you can see the configured metrics. Monitoring is enabled by default. Performance metrics can be collected from the Connection Server in real time. It uses a reporting standard that is supported by several useful reporting technologies. The Connection Server collects timer and counter information so that it can be displayed in graphical format.
 |
A Connection Server binds to the ThingWorx Platform as an ephemeral Thing, which means that it binds without your having to create a Thing for it first. The Connection Server passes in the gateway information and name of the name of the Thing Template in the bind request. If the Connection Server does not show up in the Monitoring mashup, ensure that the Thing Template in question implements the Gateway Thing Shape and extends the ConnectionServer Base Template.
|
You can troubleshoot problems that may arise by checking the metrics and by viewing the log files for the connection server.
|
|
When troubleshooting, stop the server, set the log level to TRACE, and re-create the scenario that caused the issue. The log messages at the TRACE level can help you track down where and when the issue occurred.
|