Accenture MDR Quick Start Guide for HA Proxy
This quick start guide will help Accenture MDR customers configure HA Proxy to send logs to the Log Collection Platform (LCP).Â
The document includes the following topics:
Supported Versions
A list of supported versions is available in the Accenture MDR Supported Products List document (Accenture_MSS_Supported_Products_List.xlsx) which can be found in Accenture MDR Portal.
Port Requirements
Table 1-1: Port requirements for LCP communication.
Source | Destination | Port | Description |
HA Proxy | LCP | 601 (TCP) | Default port |
Configuring HA Proxy
To configure the HA Proxy to send the syslog events to the LCP, follow the below steps.
Supported Platforms - |
---|
CentOS/RHEL 7 |
Debian release 10 (buster/sid)Â |
SSH to the Server CLI on which haproxy get deployed.
Configuration of rsyslog server to enable syslog reception over UDP.
Note: This is optional step and it does not get required if local syslog server has already been configured for log reception over UDP.
To configure the rsyslog server to enable local syslog reception over UDP
Stop rsyslog service and edit /etc/rsyslog.conf (default path for rsyslog configuration file) file to enable local syslog server reception over UDP using the below commands.
# sudo systemctl stop rsyslog.service
# sudo vi /etc/rsyslog.conf
Add the below lines in this configuration file. If you find them commented then uncomment them from the file. Save the file.Â
$ModLoad imudp
$UDPServerRun 514
Now start rsyslog service.
# sudo systemctl start rsyslog.service
 3. Steps to configure haprpxy with custom log-format and local syslog redirection.
By default, haproxy configuration file- haproxy.cfg can be found at /etc/haproxy/ location if installed through standard installation. If you are using Docker, then this file is mounted as a volume into the container at the path /usr/local/etc/haproxy/haproxy.cfg.
Edit the haproxy.cfg file to configure it with recommended Custom Log Format and redirect logs to local rsyslog server.
Execute the following commands.
Under global config block section, append the following line.
Under defaults section, append the following config lines.
Note: Reference Screenshot added below.
Note that the above configuration should be appended under the defaults section only to declare it as default logging configuration for all servers served by haproxy. Any other log configurations appended to the other sections such as frontend or listen may rule out the default logging configuration which we have followed here.Â
Although this configuration can also be appended to the other sections such as frontend or listen to get logs from that sections only.
Under frontend block, append the following configuration lines.
Reference Screenshot added below.
Now start the haproxy service. This will forward haproxy access logs to the local rsyslog server.
4. Redirect haproxy logs to LCP.
Create a new configuration file under /etc/rsyslog.d/. Ensure that it should start with prefix as 99.
For an example, create a new file named 99-lcp.conf under /etc/rsyslog.d path. Â Execute the below Commands.
Paste the following lines and save the newly created file. This configuration will forward logs to LCP over TCP Protocol.
Start rsyslog service.
LCP Configuration Parameters
Table 1-2: The HA Proxy event collector (Syslog -3961) properties to be configured by MDR are shown in the table.
Property | Default Value | Description |
Protocol | TCP | The default protocol for syslog. Device only support logs to be shared over TCP. |
IP Address | HA Proxy IP Address | Logging device IP address mentioned in the Pre-Installation Questionnaire (PIQ). Note: If the device sends logs using multiple interfaces, contact the Accenture MDR onboarding team. |
Signatures | haproxy[,haproxy_accesslogs | MDR recommended signatures processed by the HA Proxy event collector. |
Port Number | 601 | The default port number for syslog. Note: The LCP can be configured to listen on a non-standard port, please advise the Accenture MDR onboarding team if this is a requirement. |
Â
Legal Notice
Copyright © 2021 Accenture. All rights reserved.
Accenture, the Accenture Logo, and DeepSight Intelligence are trademarks or registered trademarks of Accenture in the U.S. and other countries. Other names may be trademarks of their respective owners.
The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Accenture and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. ACCENTURE SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq. "Commercial Computer Software and Commercial Computer Software Documentation," as applicable, and any successor regulations, whether delivered by Accenture as on premises or hosted services. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.