Monitoring Routers | Cluster Administration

Overview
Viewing Statistics
Disabling Statistics View
Viewing Logs
Viewing the Router Internals

Overview

Depending on the underlying implementation, you can monitor a running router in multiple ways. This topic discusses the haproxy template router and the components to check to ensure its health.

Viewing Statistics

The haproxy router exposes a web listener for the haproxy statistics. Enter the router’s public IP address and the correctly configured port (1936 by default) to view the statistics page, and enter the administrator password when prompted. This password and port are configured during the router installation, but they can be found by viewing the haproxy.config file on the container.

Disabling Statistics View

By default the haproxy statistics are exposed on port 1936 (with a password protected account). To disable exposing the haproxy statistics, specify 0 as the stats port number.

$ oadm router hap --service-account=router --stats-port=0

Note: haproxy will still collect and store statistics, it would just not expose them via a web listener. You can still get access to the statistics by sending a request to the haproxy AF_UNIX socket inside the haproxy Router container.

$ cmd="echo 'show stat' | socat - UNIX-CONNECT:/var/lib/haproxy/run/haproxy.sock"
$ routerPod=$(oc get pods --selector="router=router"  \
    --template="{{with index .items 0}}{{.metadata.name}}{{end}}")
$ oc exec $routerPod -- bash -c "$cmd"

For security purposes, the oc exec command does not work when accessing privileged containers. Instead, you can SSH into a node host, then use the docker exec command on the desired container.

Viewing Logs

To view a router log, run the oc logs command on the pod. Since the router is running as a plug-in process that manages the underlying implementation, the log is for the plug-in, not the actual haproxy log.

To view the logs generated by haproxy, start a syslog server and pass the location to a router pod using the following environment variables.

Table 1. Router Syslog Variables
Environment Variable	Description
`ROUTER_SYSLOG_ADDRESS`	The IP address of the syslog server. Port 514 is the default if no port is specified.
`ROUTER_LOG_LEVEL`	Optional. Set to change the haproxy log level. If not set, the default log level is warning. This can be changed to any log level that haproxy supports.

To set a running router pod to send messages to a syslog server:

$ oc set env dc/router ROUTER_SYSLOG_ADDRESS=<dest_ip:dest_port>  ROUTER_LOG_LEVEL=<level>

For example, the following sets haproxy to send logs to 127.0.0.1 with the default port 514 and changes the log level to debug.

$ oc set env dc/router ROUTER_SYSLOG_ADDRESS=127.0.0.1 ROUTER_LOG_LEVEL=debug

Viewing the Router Internals

routes.json

Routes are processed by the haproxy router, and are stored both in memory, on disk, and in the haproxy configuration file. The internal route representation, which is passed to the template to generate the haproxy configuration file, is found in the /var/lib/containers/router/routes.json file. When troubleshooting a routing issue, view this file to see the data being used to drive configuration.

haproxy configuration

You can find the haproxy configuration and the backends that have been created for specific routes in the /var/lib/haproxy/conf/haproxy.config file. The mapping files are found in the same directory. The helper frontend and backends use mapping files when mapping incoming requests to a backend.

Certificates

Certificates are stored in two places:

Certificates for edge terminated and re-encrypt terminated routes are stored in the /var/lib/containers/router/certs directory.
Certificates that are used for connecting to backends for re-encrypt terminated routes are stored in the /var/lib/containers/router/cacerts directory.

The files are keyed by the namespace and name of the route. The key, certificate, and CA certificate are concatenated into a single file. You can use OpenSSL to view the contents of these files.