--- title: "Application Outputs" canonical: "https://docs.loriot.io/space/NMS/6033171/Application%20Outputs" format: markdown --- > ℹ️ The Application Outputs feature allows you to integrate your own Application Server/IoT Platform with the LORIOT Network Management System (NMS). > ℹ️ > ℹ️ The data from the devices/end-points is pushed in real-time to the defined interface or platform. > ℹ️ > ℹ️ An Application has various methods to output data from devices/end-points; this includes HTTP/REST, WebSocket, MQTT, TLS Socket, plus third-party platforms such as Azure IoT, Amazon AWS IoT, Cumulocity, etc. > ℹ️ > ℹ️ More details and guides on the specific integrated Output options are available below. ### Add a new Output --- > Macro (rw-ui-tabs-macro) > > > Macro (rw-tab) > > 1. To configure a new Output, select **Output **from the sidebar menu or select **Manage outputs** in the Application Details page. > > ![image-20251119-074047.png](media://bd8f86c6-acf7-4a94-b383-a77065180ab3) > > 2. Select the **Add new output** button and select the desired [output option](https://docs.loriot.io/space/NMS/6033171/Application+Outputs#Application-Outputs) from the list and configure it accordingly. > > ![image-20251119-074312.png](media://81fe183e-fa11-48df-b616-a8f582b60e60) > > > Macro (rw-tab) > > 1. To configure a new Output, select **Output **from the sidebar menu or select **Manage outputs** in the Application Details page. > > ![image-20240322-072957.png](media://9020b327-eb04-4a5c-b988-05955236bf84) > > 2. Select the **Add new output** button and select the desired [output option](https://docs.loriot.io/space/NMS/6033171/Application+Outputs#Application-Outputs) from the list and configure it accordingly. > > ![image-20240322-073016.png](media://6467ba7f-f57b-411f-b862-a5c74b6a06a3) > > > Macro (rw-tab) > > 1. To configure a new Output, select **Output** from the sidebar menu in the Application Details page. > > ![image-20240322-073044.png](media://7aa18ae5-2278-4aad-8b64-563c072b9c6d) > > 2. Select the **Add new output** button and select the desired [output option](https://docs.loriot.io/space/NMS/6033171/Application+Outputs#Application-Outputs) from the list and configure it accordingly. > > ![image-20240322-073106.png](media://7915e661-50f8-47a8-964e-953ca49239be) ### Application Outputs page --- The following sections provide details about the options and features available in the Application Outputs page. > ℹ️ The details described below address the Application Outputs page layout available for NMS versions **v8.9.0 and later**. #### Output Customization Options These options allow users to customize the messages and information pushed to their configured Outputs. ![image-20251210-161324.png](media://3275a618-28f9-417d-9392-29c694c492de) **Rx Messages** This option allows to configure the sending and verbosity of the uplink data message (`cmd: rx`). By default, this option is set to *Extended Verbosity*. Visit [this article](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6032848) for more details about this type of output message. **Gateway Messages** This option allows to configure the sending and verbosity of the gateway message (`cmd: gw`). By default, this option is set to *Location Data*. Visit [this article](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6032911) for more details about this type of output message. **Other Customization Options** - **Enable downlink enqueue acknowledgement** and **Enable downlink confirmation event **options allow to toggle the sending of `cmd: tx` and `cmd: txd` messages to the Output, respectively. By default, both options are enabled. Visit [this article](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6031866) for more details about both Output messages. - **Enable join events** option allows to toggle the sending of join request (`cmd: jr`) and join accept (`cmd: ja`) messages to the Output. By default, this option is disabled. Visit this article for more details about Join Procedure Output messages. - **Send device name** option allows to toggle the addition of end-devices' `name` in a new field to both uplink data and gateway messages (`cmd: rx` and `cmd: gw`, respectively). #### Enable/Disable Configured Outputs You can **enable or disable already configured Application Outputs** directly from the Outputs section. This is useful when you need to temporarily stop forwarding data to a specific platform or output without deleting the configuration. To use this feature: 1. Locate the output you want to disable or enable. 2. Use the toggle switch next to the output entry to activate or deactivate it. ![image-20251119-081906.png](media://b04f197c-91d5-40ab-8d58-9061fca2a742) > ℹ️ Disabling an output will prevent data from being forwarded to that destination, but the configuration will remain saved for future use. ### Blocked Application Outputs --- The following **HTTP-based Application Outputs** may be **blocked** under certain circumstances: - HTTP Push - AllThingsTalk - Azure IoT Central - Azure Iot Hub - Cumulocity - Datacake - InfluxDBv1 - Iron.io IronMQ v1 - Iron.io IronMQ v3 - Kerlink WMC HTTP Generally, these Outputs** **will be blocked if no response is received from the target Application Server within a determined time frame. This can happen if a request fails due to a network error, timeout or connection refusal. As a consequence of the Application Output being blocked, the data transmission to that Output is suspended. Additionally, [Application logs](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/397443073) referring to failed message delivery attempts to the blocked Output are only visible when Log Verbosity is set to DEBUG on the NMS server (Log Verbosity is set to INFO for [Free Community Servers](https://www.loriot.io/community-server.html) and [Professional Public Servers](https://www.loriot.io/professional-public-server.html), meaning that DEBUG-level logs cannot be seen). When an Application Output results blocked, an ERROR event is logged in the NMS, and a warning banner is presented across the following pages of the User UI while the Output remains blocked: > Macro (rw-ui-expands-macro) > > > Macro (rw-expand) > > ![image-20260702-163310.png](media://9ce1c7cb-acb4-4229-aa00-bde514fe22e5) > Macro (rw-ui-expands-macro) > > > Macro (rw-expand) > > ![image-20260702-163237.png](media://35e7f813-83db-48c9-bff4-506ed4aac1de) > Macro (rw-ui-expands-macro) > > > Macro (rw-expand) > > ![image-20260702-163208.png](media://841ef602-00d7-422d-864a-0fa314cfa648) By default, a blocked Application Output will be automatically unblocked after 60 seconds. However, the Application Output can as well be unblocked manually by toggling its status to “Enabled”: ![image-20260701-114142.png](media://1188f811-d497-4723-bd19-97b0b8bea9f9) ### Description and step-by-step guides of the integrated Outputs --- > ℹ️ Keep in mind that having both [Uplink Messages](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6032848) and [Gateway Messages](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6032911) enabled to be sent to the configured Application Outputs could potentially cause data duplication, especially if sending decoded data using the LORIOT [Payload Codec](https://docs-loriot.atlassian.net/wiki/spaces/NMS/pages/6032014) feature. #### Application Outputs > Macro (ui-children)