Configuring Metrics and Audit Storage

This document describes Metrics and Audit Log storage configuration details for your Apcera deployment.

Metrics Manager storage

The Metrics Manager handles statsd traffic and tracks and reports the utilization of cluster resources (disk, CPU, RAM, network) over time using Graphite, a real-time graphing system. It can have heavy I/O requirements, depending on the number of metrics being sent to the Graphite server, which is affected by the number of running jobs and the number of IMs.

If the load increases beyond what the disk can handle it can lead to high IO wait times, missing metrics, and possible stability issues on the server. For this reason, you should choose a high-performance storage interface for the Metric Manager, such as NVMe/SSD or SAN.

Audit log DB (HA)

To store the audit logs, Apcera requires an auditlog-database machine configured in HA mode.

If the auditlog-database is configured and deployed on the cluster, the Audit log tab appears on the web console and its access is governed by poliyc. If the auditlog-database is not configured, the Audit log tab is not be available on the web console.

The following example cluster.conf snippet shows how to configure the auditlog-database:

machines: {
  audit: {
    hosts: [ "10.224.214.48","10.224.214.49"]
    suitable_tags: [ "auditlog-database" ]
  }
}

components: {
  # auditlog databases
   auditlog-database: 2
}

External auditlog-database

You can specify an external PostgreSQL DB instance as the auditlog-database. If the auditlog_database_external_address is set in cluster.conf, the auditlog settings are configured to connect to it. The auditlog_database_external_address setting takes precedence over the search for the auditlog-database-master.

chef: {
  "continuum": {
    "auditlog_database_name": "auditlog333",
    "auditlog_database_password": "apassword",
    "auditlog_database_user": "audituser333",
    "auditlog_database_external_address": "a.remote.postgres.server.example.com",
  }
}