WSO2 requires an email server with SMTP Auth enabled to send direct email alerts and notifications to other servers. If the customer cannot provide an email server, WSO2 uses Amazon Simple Email Service (SES). We need support from the customer to verify the domain and set up DomainKeys Identified Mail (DKIM), which is an email validation system designed to detect email spoofing. As part of ICinga installation, a local email server is set up. The WSO2 DevOps team configures this server to relay emails to a known email server that resides within or outside the AWS infrastructure.
We maintain application logs using the Logstash, ElasticSearch and Kibana solutions. WSO2 configures a Logstash agent in each host to collect application data and send over to ElasticSearch that is running on the monitoring host in a different subnet in the same VPC. The Kibana dashboard is exposed only to the WSO2 network over HTTP/S.
The monitoring and alerting implementation is depicted in the diagram below:
If the customer wants to synchronize their monitoring with that of WSO2, DevOps teams from both sides need to agree on certain technical requirements such as additional agents that must be installed on hosts, how to expose dashboards to other networks, send alerts to additional email addresses, phones, etc.
Next, go to Handover.