Log forwarder destination port keeps reverting back to TCP 514 once the changes are saved.
search cancel

Log forwarder destination port keeps reverting back to TCP 514 once the changes are saved.

book

Article ID: 423642

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

After configuring Log Forwarding with the RAW format on a custom port (e.g., 1517) and saving the settings, the port value automatically reverts to the default port (e.g., 514) upon reopening the configuration.

Although the logs are successfully being sent to the intended custom port (1517), the configuration screen consistently displays the incorrect default port (514)

Environment

Aria Operations for Logs 9.0.x

Cause

This was identified to a UI bug

Resolution

Engineering team is aware of the issue and this will be fixed in the upcoming release.