On Aug 23, 2013, at 8:22 AM, Leif Hedstrom <zw...@apache.org> wrote: > On Aug 22, 2013, at 6:42 PM, Yongming Zhao <ming....@gmail.com> wrote: > >> the result of the change will be: >> 1, the email alarm may able to build, but we removed the origin >> records.config >> 2, the custom alarm script still need your own work >> 3, documents still lack, and more documents to be add on the change > > I'm reverting the commit for master and 4.0.x branch.
Blech. This can be fixed in a compatible way and I'll aim to do it for 4.1. That said, I don't think that we are living in a golden age of Traffic Server alarms. No-one who is running distribution versions of ATS is using alarms because the documentation and installed files are not sufficient to do so. The only people using this are advanced users who have the ability to easily adapt to this change. For 4.10, I will implement my previous proposal, and I will automatically convert legacy configurations to the new configuration (or leave the legacy junk in place). I would like alarms to be useful to the masses (ie. me); I would like to receive an alarm with a stack trace when AT crashes. J
