/usr/share/indeni-services/config/livenx.env. When the LiveNX
integration is deleted, this file will also be deleted.Prerequisites
-
Before you configure the integration, ensure that you've set a token for LiveAction Receiver in the Network Configuration page of the LiveNX UI.
-
Note:
Starting in v25.3.0, LiveAssurance uses
gRPCas the transport protocol for the openTelemetry exporter instead ofHTTPto forward alerts to LiveNX.- Due to this change, LiveAssurance v25.3.0 must be integrated with only LiveNX v25.3.0 (or greater). Integrating LiveAssurance v25.3.0 with a LiveNX version earlier than 25.3.0, and vice versa, will fail.
- You must ensure that LiveAssurance can reach LiveNX via port 4317 (that is, the port used for gRPC).
-
Log in to the LiveNX web interface.
-
Select the gear icon available in the Navigation bar.
-
Select in the sidebar.
-
In the Network Configuration page that is displayed, configure the following parameters:
- LiveNX REST API Token—You can obtain this token from the LiveNX Swagger page (<LiveNX-URL>:8093/v1/docs).
- LiveAction Receiver Configuration—Enable this option.
- Token—If not present already, create a token for the
LiveAction Receiver Configuration. You can enter any value
manually. Alternatively, you can automatically generate a UUID
by re-saving the configuration. (TIP: Temporarily modify
a field and select Save.)Note: Greenfield deployments will always have a UUID pre-populated.
-
Make a note of this token as you will use it when configuring the LiveNX integration in the LiveAssurance UI.
-
Select Save.
Procedure to send LiveAssurance alerts to LiveNX
-
Open
<LiveNX-URL>:5443in a browser (bothhttpandhttpsare supported). -
Select Settings in the sidebar, then select Integrations.
-
From the Add New Integration drop-down list, select LiveNX.
-
Configure the following parameters:
- Integration Name—enter a name for the LiveNX integration.
- IP—enter the IP address of the LiveNX server.
- Token—enter the LiveAction Receiver token that grants authorized access to send alerts to LiveNX. This is the same token that is configured in the Network Configuration page of the LiveNX UI.
-
Select Save.
-
For the integration to start, you must restart the
authserverby using the following command:cd /data/bcia && docker compose restart authserver
After successful integration, the LiveAssurance alerts are displayed in your LiveAssurance Events dashboard within LiveNX. Clicking an alert will take you to the Issues tab in the LiveAssurance UI, which displays a detailed view of the alert.