+1
On Thu, May 9, 2019 at 3:23 PM Leif Hedstrom <zw...@apache.org> wrote: > > Hi all, > > I’d like to propose that we eliminate the “email” feature out of Alarms. I > think this is misguided, and in reality, could be wrapped into a script if > someone really, really wanted to send emails. We would remove > proxy.config.alarm_email, but keep the other alarm configurations. > > In addition, I’ll cleanup the alarms, there’s a number of the existing alarms > that are no longer relevant or supported. Such as, all the alarms around > cache clustering. Possibly we should add more, it’s a potentially useful > feature to have a mechanism for ATS to signal / alert on internal issues > outside of just logging. I think … > > Thanks, > > — leif > > P.s > In case you didn’t know (and this is not awesomely documented), the following > alarms can trigger: > > #define REC_SIGNAL_MACHINE_UP 1 > #define REC_SIGNAL_MACHINE_DOWN 2 > #define REC_SIGNAL_CONFIG_ERROR 3 > #define REC_SIGNAL_SYSTEM_ERROR 4 > #define REC_SIGNAL_LOG_SPACE_CRISIS 5 > #define REC_SIGNAL_CONFIG_FILE_READ 6 > #define REC_SIGNAL_CACHE_ERROR 7 > #define REC_SIGNAL_CACHE_WARNING 8 > #define REC_SIGNAL_LOGGING_ERROR 9 > #define REC_SIGNAL_LOGGING_WARNING 10 > // Currently unused: 11 > #define REC_SIGNAL_PLUGIN_CONFIG_REG 12 > #define REC_SIGNAL_PLUGIN_ADD_REC 13 > #define REC_SIGNAL_PLUGIN_SET_CONFIG 14 > #define REC_SIGNAL_LOG_FILES_ROLLED 15 > #define REC_SIGNAL_LIBRECORDS 16 > > > Many of them can never trigger.
