I read docs but can't find a solution for customizing the auto-generated alert-messages. Can anybody tell me, how this is done?
I ask because of the fact that we need to send some specific auth-string in the subject for forwarding those mails to an SMS-gateway. Another thing we need to do, is cutting the message itself a little bit because of the allowed 160 characters in a SMS.
The current version of HQ does not allow a user or developer to customize the the alert messages. However, in the forthcoming open source release, you will have the option to either customize the source code itself to generate the messages in the format that you need, or create your own email notification action implementation to plug into the alerting subsystem. I can furnish you with more details at that time.
The entire alerting feature will undergo significant enhancements in the future. We already have numerous enhancements planned on our roadmap that definitely include some customization to the notifications.
I think all of us here agree with you about the the alerting subsystem. While we think we already offer some really cool alerting features, we have been talking extensively about where we need to take it to make it truly useful. The list of alerting enhancements, as you can imagine, is quite long. We really want to focus specifically on alerting for the next release. Therefore, we will be working to refine the alerting roadmap promptly after the release of the source code. The roadmap will be published as soon as we have it available and we hope to solicit community feedback on it. So, please look for it in the month of July.
There are no currently no plans to integrate a role manager in the open source version. However, we do have an implementation of group- role-based access control in the enterprise subscription, and the open source HQ does share the same underpinnings that allows for permission checking extensions. We will evaluate whether or not the same model works for open source HQ or another model is better suited for the community. We are definitely hoping for participation on both feature design and implementation for new features.
I hope that answers your questions for now. Thanks for the compliment on HQ!