Monitor

Ownership of the incident resolution on Jahia Cloud

Jahia is committed to ensuring a 100% availability and snappy response time for all of the platforms hosted on Jahia Cloud. Many measures are deployed to reach that goal:

• Multi datacenter with redundancy for all Production environments 
• Built-in 24/7/365 support
• Support by specialized Jahia/jCustomer Support engineers and dedicated infrastructure Operations teams

While almost all monitoring alerts will be handled by Jahia directly, some alerts can only be solved by Jahia Cloud customers. These alerts are automatically escalated to the customers and are listed below.

Real-life scenario example (Note: This configuration serves as an example and should be adjusted based on your specific context).

My production environment isn't directly accessible to visitors because they must pass through a CDN and/or a WAF. However, it's crucial to ensure that /ping.jsp is always accessible directly. This allows synthetic checks to be performed, thereby maintaining our SLA.

## ALL WAF
acl service_waf req.hdr_ip(x-forwarded-for,-1) -m ip  1.3.4.5/19 
## JAHIA VPN IPs
acl service_jahia_vpn req.hdr_ip(x-forwarded-for,1) -m ip 188.165.59.149 91.134.164.155 51.161.118.223
## DATADOG CHECKS
acl datadog_ping path /ping.jsp
## APPLY RULES TO REQUESTS
http-request deny if !service_waf !service_jahia_vpn !datadog_ping

List of monitoring alerts sent to Jahia Cloud customers

Note that Jahia team will also receive the alerts above. The Jahia team will take action to resolve the alert and coordinate with you if necessary. 

[Synthetics] Check env-name environment

This monitor triggers an alert when the HTTP (initiated by Datadogà requests fails for 2 consecutive minutes at a single location, a notification is sent. And Jahia Support is notified (24/7). An HTTP request is run every minute.

This means that the monitoring system allows for a single failure before triggering an alert. If the test passes on the first minute but fails on the second minute at the same location, a notification is sent, and the alert status is changed to "alert". 

In summary, the monitoring system sends a notification and sets the alert status to "alert" when a test fails for 2 consecutive minutes at the same location, allowing for a single failure before escalating the issue.

HAProxy considers a node to be down if it is unreachable, or if the health check fails (because of time-out, invalid response or RED status). When all nodes are considered down, all requests will fail with a 502 error until at least one node is back up.[Jahia] Sporadic errors on Synthetic tests

[Jahia] Sporadic errors on Synthetic tests

This monitor triggers an alert when multiple queries from the Datadog's Synthetic tests are in error in a short amount of time. (See definition above). This monitor will check for failed synthetic checks and trigger an alert if there are more than 3 fails within a half-hour.

Global logs generation

This monitor checks the global amount of log lines generated over 1 day, all environments/logfiles included. If logs exceed 10M in a day the monitor is triggered. 

Others monitoring alerts available (Customers will not be notified) 

The Jahia team is responsible for monitoring 71 internal infrastructure and application monitors. Not all of these may require your attention, so you will not receive notifications. To view the complete list of Jahia's monitored systems, navigate to the 'Monitors' section on the left side menu in Datadog. If one of these monitors triggers an alert, we will investigate and contact you via Jira support if necessary.