AMC does not send email alerts until logged in to console

The Aerospike Knowledge Base has moved to https://support.aerospike.com. Content on https://discuss.aerospike.com is being migrated to either https://support.aerospike.com or https://docs.aerospike.com. Maintenance on articles stored in this repository ceased on December 31st 2022 and this article may be stale. If you have any questions, please do not hesitate to raise a case via https://support.aerospike.com.

AMC Is Now Community Supported!

Aerospike no longer supports the AMC, which has been replaced by the Aerospike Monitoring Stack. The AMC has been turned over to the community, with code hosted at aerospike-community/amc and documentation on the repo Wiki.

AMC does not send email alerts until logged in to console

Problem Description

When AMC is being used to monitor an Aerospike cluster there is a facility to configure email alerts by editing the mailer stanza of /etc/amc/amc.conf. When this has been done and AMC has been started there are no email alerts sent, regardless of cluster state, until the AMC console has been accessed via web browser.

Explanation

This issue will manifest when there has been no cluster configured for monitoring in /etc/amc/amc.conf. Until this is done, AMC is not aware of any clusters to be monitored. Logging in to AMC via the web browser requires a cluster to be selected for monitoring. At this point AMC has something to monitor and so will send alert emails as appropriate. This is expected behaviour.

Solution

To ensure that email alerts are sent all the time an entry should be made in /etc/amc/amc.conf in the amc.clusters stanza. This means that as soon as AMC starts it will monitor the chosen cluster and send email alerts. An example is shown below:

[amc.clusters.db1]
host = "172.17.0.3"
port = 3000
show_in_ui = true

Keywords

AMC EMAIL ALERT NOT SENT

Timestamp

27 June 2019