On the Home page, click Analytics Servers > Edit.
In Log level, select the required log level from the list.
|
Log level |
Description |
|---|---|
|
Info |
Sends informational messages such as requests sent to web servers and the results of authentication requests. |
|
Error |
Sends warning messages. |
|
Debug |
Sends debug messages |
(Optional) In Dashboard Public IP/DNS, specify the <DNS/IP>:port for launching the dashboard. This is the IP/DNS of the load balancer. It can also be the IP address of the individual dashboard server. Port number is optional.
NOTE:If you have configured Analytics Server behind Access Gateway, you can configure the published DNS name in this field.
(Optional) In Audit Event Listener IP/DNS, specify the load balancer or Logstash server IP address to which the audit events must be sent.
NOTE:Failover in the high availability configuration is directed to any active standby nodes. If all the standby nodes are inactive, then the failover is directed back to the primary node.
Click OK.
In a cluster setup, ensure that the following ports are open for Analytics Server cluster communication:
8445
22
IP tables can be used to restrict cluster communication. The following is a sample configuration of IP tables:
Iptables -P INPUT DROP ## By default drop all iptables -A INPUT -s 164.99.184.0/23 -j ACCEPT ## You can allow traffic only between Analytics Dashboard cluster nodes and Access Manager devices instead of the entire network. iptables -A INPUT -i lo -j ACCEPT ## Enable Loop back communication iptables -A INPUT -p tcp --dport 8445 -j ACCEPT ## Enable 8445 for public access iptables-save