From users-return-7725-archive-asf-public=cust-asf.ponee.io@trafficserver.apache.org Thu May 9 22:23:58 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 8ECD4180649 for ; Fri, 10 May 2019 00:23:58 +0200 (CEST) Received: (qmail 18268 invoked by uid 500); 9 May 2019 22:23:56 -0000 Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@trafficserver.apache.org Delivered-To: mailing list users@trafficserver.apache.org Received: (qmail 18251 invoked by uid 99); 9 May 2019 22:23:56 -0000 Received: from Unknown (HELO mailrelay2-lw-us.apache.org) (10.10.3.159) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 May 2019 22:23:56 +0000 Received: from [192.168.201.21] (c-73-217-8-61.hsd1.co.comcast.net [73.217.8.61]) by mailrelay2-lw-us.apache.org (ASF Mail Server at mailrelay2-lw-us.apache.org) with ESMTPSA id D906B403F; Thu, 9 May 2019 22:23:55 +0000 (UTC) From: Leif Hedstrom Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\)) Subject: [PROPOSAL] Remove the email feature from Alarms (proxy.config.alarm_email) and cleanup Message-Id: Date: Thu, 9 May 2019 16:23:54 -0600 To: dev , Mailing-List trafficserver X-Mailer: Apple Mail (2.3445.104.8) Hi all, I=E2=80=99d like to propose that we eliminate the =E2=80=9Cemail=E2=80=9D = 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=E2=80=99ll cleanup the alarms, there=E2=80=99s 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=E2=80=99s a potentially useful feature to have a mechanism for ATS to = signal / alert on internal issues outside of just logging. I think =E2=80=A6= Thanks, =E2=80=94 leif P.s In case you didn=E2=80=99t 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.=