Skip to content

Cookie preferences

We use cookies for our own analytics, to see how our campaigns perform and, if you allow it, to load content from other services such as the Google site search. We never sell your data. Necessary cookies keep the site working and cannot be switched off. See our Cookie Policy for details and our Privacy Policy for how we handle personal data.

Security, load balancing and remembering your cookie choice.

Show us which pages people read, how they find the site and where they get stuck, so we can improve it (Google Analytics, Microsoft Clarity).

Show us which of our ad campaigns bring visitors to the site and remember the campaign or partner link you arrived from (Google Ads, LinkedIn, Meta, partner program). We do not use these cookies to build advertising profiles.

Load the site search from Google when you use it. Google sets its own cookies and shows ads in the search results.

© 2026 The ThingsBoard Authors
180 Try for free

ThingsBoard Cloud

Choose your data region

Your data stays in the region you choose, for residency and compliance. No credit card required.

Rather run it yourself? Install on your own servers

Monitor message statistics

The message statistics dashboard lets you monitor the state of uplink (Edge → server) and downlink (server → Edge) message flows in real time. Use it to identify message backlogs, delivery failures, and queue lag before they affect data visibility on the server.

  1. Download the preconfigured dashboard file: uplink_downlink_edge_stats.json

  2. Log in to your ThingsBoard server and go to Dashboards.

  3. Click Add (+) and select Import dashboard. Browse for the downloaded .json file and click Import.

ThingsBoard Edge exposes the following telemetry keys on the Edge entity. These keys power the dashboard widgets and can also be queried directly or used in rule chains.

Key Description
uplinkMsgsAdded Messages added to the uplink queue
uplinkMsgsPushed Messages successfully delivered to the server
uplinkMsgsPermanentlyFailed Messages that failed and will not be retried
uplinkMsgsTmpFailed Messages that failed temporarily (e.g., network issue) and will be retried
uplinkMsgsLag Messages remaining in the queue — a sustained non-zero value indicates a backlog
Key Description
downlinkMsgsAdded Messages added to the downlink queue
downlinkMsgsPushed Messages successfully delivered to Edge
downlinkMsgsPermanentlyFailed Messages that failed and will not be retried
downlinkMsgsTmpFailed Messages that failed temporarily and will be retried
downlinkMsgsLag Messages remaining in the queue — a sustained non-zero value indicates a backlog

A rising *MsgsLag value means messages are accumulating faster than they are delivered. Check network connectivity and Edge resource usage if this occurs.