Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Monitoring dashboards: WSO2 hosts monitoring services monitoring services and collects statistics  about resource utilization (i.e., disk, CPU, memory, and JVM heap usage) and application health . All statistics  collected are presented using  dashboards. WSO2 requires direct access to all monitoring  dashboards, and will grant read-only access to the customer upon the customer's request.
  • Monitoring the logs: WSO2  monitors logs using ElasticSearch Logstash and  Kibana (ELK)   solutions. A Logstash agent collects application data and sends over to ElasticSearch that is running on the monitoring host. The Kibana dashboard displays the analyzed data in a graphical UI.
  • System monitoringAll systems statistics  are presented using  ICinga , the monitoring and dashboard tool and Cacti, the network g raphing solution. 
  • Application monitoring WSO2 product runtimes are monitored by the WSO2 Operations team. WSO2 is not responsible for monitoring the  services deployed on top of the WSO2 product runtimes. They must be managed by the customer.WSO2 requires an email server with SMTP Authentication 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 i s an email validation system designed to detect email spoofing. 
  • Alerts and notifications WSO2 requires an email server with SMTP Authentication 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. 

    The monitoring and alerting implementation is depicted in the diagram below:
         
    Diagram : Monitoring and alerting implementation

    If the customer's environment that is managed by WSO2 cannot be reached through the Internet, the customer must facilitate an HTTP proxy server for WSO2 to receive alerts. The diagram below depicts this scenario:
     
    Diagram:  Monitoring and alerting implementation when the customer's environment cannot be reached through the Internet

...