Monitoring Pepperdata

Pepperdata processes write detailed operations information to log files. You can view the log files in the same manner as any program’s logged information.

Pepperdata PepAgents provide near real-time monitoring views via Web (HTTP/HTTPS) servlets. By using a Web browser, you can access all the monitoring status.

On This Page

Pepperdata Log Files
Pepperdata Status Views via Web Servlets

Pepperdata Log Files

By default, the PepAgents write metrics data to /var/log/pepperdata/metrics. (You can customize the location by changing the PD_LOG_DIR environment variable; see Configure Pepperdata Logs Retention and Disk Usage.) Because the files in these directories typically grow quite large (up to several GB per week), we recommend that you remove logs that are over a month old.

The files contain Google protobuf contents compressed in bzip2. The file names end with .proto.bz2. One method for viewing the log files’ content is to use the Pepperdata print_proto_metrics_file utility. For example:

/opt/pepperdata/supervisor/print_proto_metrics_file pd_task_metrics.20140227_131948_601-1393535988601-pep08.pepperdata.com.proto.bz2

Pepperdata Status Views via Web Servlets

Pepperdata PepAgents provide near real-time monitoring views via Web (HTTP/HTTPS) servlets. (To enable SSL support, see Configure SSL Near Real-Time Monitoring on Port 50505.)

Note: The URLs for the monitoring views are for the default port setting (port 50505 for the PepAgent). If this port is used by another service, you can reconfigure which port Pepperdata uses by redefining the pepperdata.agent.rpc.server.port property.

If you do not want the Pepperdata Status Views to be available to all your Pepperdata users, you can disable the views; see Disable Pepperdata Status Views.

ResourceManager Views

To monitor an area of interest, use a Web browser to access the associated servlet. In the following URLs, change hostname to the hostname of the ResourceManager, and replace {your-protocol} with http or https as applicable.

Cluster Status—{your-protocol}://hostname:50505/Cluster. Shows basic status of the PepAgent cluster, as viewed by the ResourceManager.
Capacity Optimizer—{your-protocol}://hostname:50505/CapacityOptimizer. Shows Capacity Optimizer status of the cluster
Top RPC—{your-protocol}://hostname:50505/RpcRoot. Describes metrics related to the communication between PepAgents in the cluster.

(In Pepperdata Supervisor v7.1.10 or earlier, PepAgents on the ResourceManager hosts listen on port 50510 for HTTP requests for these web pages. So use port 50510 above instead of port 50505 to access the pages.)

Note: If the port 50510 is used by another service, you can reconfigure which port Pepperdata uses by redefining the pepperdata.supervisor.rpc.server.port property.

NodeManager Views

For the following PepAgent servlet, change hostname to the hostname of any NodeManager that is running a PepAgent. (In most cases, PepAgent runs on all the NodeManagers in a cluster.)

Task Metrics—{your-protocol}://hostname:50505/TaskMetrics. Reports resources used by all running containers on the associated NodeManager host, including memory, CPU, and Hadoop file counters.
RPC—{your-protocol}://hostname:50505/Rpc. Describes metrics related to the communication to the PepAgent on the NodeManager host.