Link Search Menu Expand Document

Remote Log Receivers

Support > Technical Assistance > Remote Log Receiver

This table lists all configured remote log receivers that are sent and managed by Orchestrator. You can choose between sending your data between the following different types of receivers: HTTP, HTTPS, KAFKA, SYSLOG, and WEBSOCKET. Each receiver employs a different mechanism for supporting asynchronous notifications. After you determine which remote receiver you want to use to send your data, you can configure specific settings for that receiver.

Complete the following instructions to add a receiver.

  1. Click Add Receiver.

  2. Select the type of receiver you want to use from the list.

  3. Depending on which receiver you choose, a settings pop-up will appear. Enter the appropriate information for each receiver. See the following tables below for each receiver’s settings.

  4. Click Save.

HTTP Receiver Settings

FieldDescription
Enable ReceiverClick this slider to toggle between enabled and disabled state.
NameName of the receiver the logs are going to.
Log TypeSelect the type of log from the list you want to apply.
URLURL served by HTTP/HTTPS log server that Orchestrator will send log data with POST REST calls.
User NameUser name used in Basic Authentication when making REST calls (Optional).
PasswordPassword used in Basic Authentication when making REST calls. (Optional).
Repeat PasswordYour password repeated.

HTTPS Receiver Settings

FieldDescription
Enable ReceiverClick this slider to toggle between enabled and disabled state.
NameName of the receiver the logs are going to.
Log TypeSelect the type of log from the list you want to apply.
URLURL of the HTTPS Receiver.
User NameUser name used in Basic Authentication when making REST calls (Optional).
PasswordPassword used in Basic Authentication when making REST calls (Optional).
Repeat PasswordYour password repeated.

KAFKA Receiver Settings

FieldDescription
Enable ReceiverClick this slider to toggle between enabled and disabled state.
NameName of the receiver the logs are going to.
Log TypeSelect the type of log from the list you want to apply.
TopicTopic name on KAFKA Receiver.
Bootstrap ServersDomain name served by KAFKA Receiver. For example, “xxx.com:9092”, “1.1.1.1:9092”.
AcksDefines the amount of KAFKA servers that acknowledge a message before considering the message delivered.
  • acks=0: Expect no acknowledge.
  • acks=1: Only leader server must acknowledge.
  • ack=all: All servers must acknowledge.
RetriesAmount of times KAFKA will try before returning an error.
Batch SizeMultiple messages KAFKA will produce until the batch size is exceeded.
Buffer SizeMaximum memory size that can be used for buffering messages. When buffer size is exceeded, a message will be blocked.
Linger TimeAmount of time that KAFKA will wait before sending next message batch.

SYSLOG Receiver Settings

FieldDescription
Enable ReceiverClick this slider to toggle between enabled and disabled state.

General Settings

FieldDescription
Log TypeType of log being sent to the SYSLOG receiver.
ProtocolProtocol being used between devices.
HostnameHostname of the SYSLOG receiver to identity the device.
PortPort number of the SYSLOG receiver that accepts incoming events.
Custom DataCustom data embedded inside the SYSLOG message.

Facility Settings

FieldDescription
Audit LogType of audit log.

Audit Log Severity Settings

FieldDescription
ErrorSeverity level of the error; select from the drop-down menu.
InfoSeverity level of the information; select from the drop-down menu.
DebugSeverity level of the debug; select from the drop-down menu.

WEBSOCKET Receiver Settings

Provides a reliable streaming mechanism for alarms and Orchestrator audit logs across all appliances. It is initiated from the client side and sent to Orchestrator for authentication. When authenticated by Orchestrator, asynchronous notifications are sent in JSON objects.

FieldDescription
EnableClick this slider to toggle between enabled and disabled state.
NameName of the WebSocket receiver.
Log TypeType of log being sent to the WebSocket receiver.
IP Allow ListList of source IP addresses that are allowed WebSocket access to Orchestrator.

WebSocket Receiver Configuration

You need the following items to establish connectivity from Orchestrator to the WebSocket receiver:

  • Key generated by Orchestrator after the above configuration is completed

  • ID created by Orchestrator when it is configuring the WebSocket server


Back to top

© Copyright 2022 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Aruba Networks and the Aruba logo are registered trademarks of Aruba Networks, Inc. Third-party trademarks mentioned are the property of their respective owners. To view the end-user software agreement, go to Aruba EULA.