Entities & Vocabulary
An official record of all server events.
An event is an action or occurrence recognized by the server
LoRaWAN core process
LORIOT Application (Container for devices)
gateway Extended Unique Identifier
device Extended Unique Identifier
application Extended Unique Identifier
Custom Filter Expression
payload in MAIL ERROR event
ask for confirmation or not in a downlink
random number of join request
device sequence number
has Adaptive data rate
has Adaptive data rate Acknowledgement Request
network server instance
is the last LORIOT gateway software version used by the Gateway
message of the event type
message integrity code
path of the error events
request body of the http
received signal strength indicator
message Sequence number
stack of the error event
status code of the http response
error POSTing message
URL (with regards to LORIOT)
URL of the target application server
Your real-time and historical data, the Log Browser allows you to view log data in real time, or look back on previous events, providing the ability to quickly analyze and solve problems.
➜ Log data also provides information for identifying and troubleshooting network problems including configuration and hardware issues.
✔ Capturing server events from a variety of sources and filtering between critical or noncritical events keeps your organization safe, secure, and running smoothly.
The Log browser is a back-end system tool accessible to Server Operators through the admin user interface and provides a comprehensive overview of all events on the Network Server.
➜ Log in with your Server Operator account to the admin interface.
Log Browser Features
Real-time or filter by time and date for historical events/data.
➜ To access data from a specific time and date, select the icons to set the correct parameters. All data from that point will be displayed which can be navigated by selecting different pages at the bottom.
✔ Live Log Browser – select the Live Log Browser toggle icon for the logs to automatically refresh and display the latest data.
Filter server events by severity and required information.
➜ Events can be included or filtered out by selecting the specific icon. All filter icons with a tick are displayed (if that event has previously occurred).
Select the icon to display or hide the different sources of server events.
LoRaWAN Core server events
Select the Column icons to add the relevant additional columns to the event log page below for an easier to read format.
Customer Filter Expression
Custom Filtering enables specific data/events to be displayed based on selected metadata.
The list of available metadata to filter by is dynamically generated
➜ When an event containing a specific type of metadata occurs, it will be available in the drop-down menu.
a) Select the metadata from the drop-down menu
b) Select if the value is :
c) input require data
➜ Alternatively, select the required metadata from the event log by clicking the blue text.
➜ The selected filtering metadata will display in the Custom Filter Expression box.
➜ Multiple metadata filters can be selected at once to narrow down events.
➜ For example, select a specific DevUI value and also filter to display all devices with an RSSI > -100
Extended event information
To view the event data in more detail, select either the expand icon on the left or the extend icon on the right when available for certain events.
➜ This provides further details and a more readable format for the data.
➜ For example:
Log Browser event description
HTTP - Error POSTing device uplink message to WEB API endpoint
DATA_DOWN - Sending downlink down failed Data down cannot be sent to offline gateway
MAIL_ERROR - Cannot read property '_id' of undefined
API_TLS - Invalid app setup output(s):"websocket" "httppush"
GW_SW - Gateway not found
PACKET_FWD - Data from unregistered gateway
AMAZON_IOT - sending device uplink message to Microsoft Amazon IoT Core failed
AZURE_IOT - sending device uplink message to Microsoft Azure IoT Hub failed
MYDEVICES - sending device uplink message to Cayenne MyDevices failed
DEVICE_CREATE - Could not import OTA device
WS_UNAUTH - attempting to open/connect to a WebSocket with an invalid token for instance
INVALID_MIC - Invalid MIC in frame
NONCE_MISMATCH - Received join request with nonce= while already queuing join with nonce=
REPEATED_NONCE - Join request has repeated NONCE
JOIN_NO_APP: No application join server found by JoinEUI
LOST_FRAMES - lost frames for DEV
UNKNOWN_GATEWAY - Unregistered gateway at (IP) attempted to retrieve configuration file
FAST_DATA - Ignoring new sequence number arrival before old could be processed
ALL_THINGS_TALK - Discard not supported message
MAC_ERROR - Could not identify best downlink gateway
JOIN_BAD_MHDR - Join request MHDR is not zero but 1
GATEWAY - WebSocket already connected. Replacing existing connection.
ADR - DR -> DR
DEVICE_UPDATE - Device updated succesfully
HTTP - POSTing message successfully
DATA_UP - Downlink uplink received from device
DATA_DOWN - Downlink data sent to device with confirmation request
DATA_DOWN_CNF - Downlink data sent to device with confirmation request
REPEAT_SEQNO - Received repeated message
UPDATE_GET - No update for version (xxxx)
MQTT - POSTing message successfully
MYDEVICES - POSTing message successfully
JOIN_REQUEST - LoRaWAN Join request sent to DEV
JOIN_ACCEPT - LoRaWAN Join accept sent to DEV
ALL_THINGS_TALK - POSTing message successfully
SEQDN_RESET - device sequence reset successfully
GW_DELETE - gateway removed from the server
Custom Filter Expression examples
With large network deployments, filtering thousands of events to find the right data is key to managing networks at scale.
Important details such as viewing all gateway traffic, debugging any errors and displaying all the data from a specific application, the logs filtering makes it quick and simple.
Log browser filtering is a necessary tool required to find, evaluate and fix any issues so you can seamlessly operate a network.
View all event types associated with a specific device using its DevEUI, a quick method to view data from a single or a multiple number of devices.
a) select Customer Filter Expression = deveui
b) use the symbol = or ~
c) Input the devEUI and click the plus symbol
d) the custom metadata filter will appear in the box
➜ It is possible to filter by more than one value for even more specific data.
DevEUI + RSSI
Display device events with a specific rssi parameter, very useful for checking signal quality and how well your device signal is received.
a) Follow the previous steps for filtering devEUI:
b) Add extra layer of RSSI filtering:
c) All metadata filter will be displayed:
d) the event logs will only display DevEUI data which meets the required extra filtering parameters:
Filter by a specific gateway EUI to display all events and data associated with the gateway:
gwEUI + SF
Filter by the gateway and display any device transmitting on a specific spreading factor, great to view all devices, not on an optimal spreading factor:
Filtering by AppID is the perfect method to see all events associated with a specific application on the server.
➜ To get the correct appID format we must convert the hexadecimal application ID in the user UI to decimal for the log browser filtering.
➜ Input the decimal number to filter by a specific application:
Filtering by message length can help determine what devices are not functioning as expected.
For example, a device in the field sensing correctly has a message length above 50, then filter for all devices below 50 to find which devices are not working as they should be:
These are just a few examples of the Custom Filtering Expressions an operator can use to debug and gain deeper insights to events on the server.
There are many combinations of metadata filtering that ensure you can find and solve any issues.
Severity Filter examples
Severity filtering enables an operator to quickly view certain types of events by removing what's not relevant and take action if required.
Combined with Custom Filter Expressions you can, for example, quickly view all errors for a specific gateway, device or application.
Display all error events on the server by deselecting all non-relevant severity types:
A great method to find all ADR events for a specific device.
a) select Notice severity
b) Custom Filter for a specific devEUI
With the power of the Log Browser, server operators can view server events and data instantly and easily. When operating a network at scale, monitoring, debugging and problem-solving can be a challenge without the right tools.
Using this guide, we hope you have a better understanding of the functionality and usability of the Log Browser to ensure your network runs like clock-work and can scale!