Cirrus Link Website
Contact Us (Sales/Support)
Forum
Cirrus Link Modules Docs for Ignition 8.3.x
Cirrus Link Modules Docs for Ignition 7.9.x
Ignition User Manual
Knowledge Base Articles
Inductive University
Forum
The Cirrus Link modules support logging in the Ignition Gateway logs. Often when you are working with Cirrus Link support you will be asked to turn up a particular logger level to DEBUG or TRACE to assist in trouble shooting the issue.
Here we will document some of the common loggers and the extended information available in DEBUG and/or TRACE level.
Logger: com.cirruslink.mqttengine.gateway.sparkplug.sparkplugBPayloadHandler
Level: TRACE
Description: This will log the incoming messages in the SparkplugB namespace including topic and payload.
Logger: com.cirruslink.mqttengine.gateway.json.JsonPayloadHandler
Level: TRACE
Description: This will log the incoming messages in a custom namespace when parsing the string payload as JSON including topic and payload.
Logger: com.cirruslink.mqttengine.gateway.string.StringPayloadHandler
Level: TRACE
Description: This will log the incoming messages in a custom namespace when not parsing the string payload as JSON including topic and payload.
Logger: io.moquette.spi.impl.ProtocolProcessor (pre v4.0.14)
Level: DEBUG
Description: This will log the connect requests for MQTT Clients. This allows us to see if multiple clients with the same Client ID are trying to connect to the broker which causes Colliding Client IDs.
Logger: com.cirruslink.cahriot.server.core.PacletHandler (4.0.14 and newer)
Level: DEBUG
Description: This will log the connect requests for MQTT clients. This allows us to see if multiple clients with the same ClientID are trying to connect to the broker which cause Colliding Clients IDs.