Understanding the System Status

Owned by Simon Watts (Deactivated)
Last updated: Apr 05, 2023 by Ryan Clifton
4 min read

The Welcome page

Once some configuration has taken place, e.g through the wizard, users will get an eye catching status on the welcome screen of how their JEMH Cloud system is currently running. The status block quickly lets the admin know if there is a problem with their JEMH Cloud and enabling a drill down to the detail.

  • Green - everything is okay.

  • Yellow - something needs attention.

  • Red - something is really broken and needs fixing

At the bottom of each block you will see "Details...", clicking this will take you to a new System Status page where we group related features allowing you to visualise various parts as well as the impact each component has on your system (the detail view is shown next).

Accessing the System Status

The System Status page contains a component view of JEMH Cloud and quick access to configuration and underlying problem identification. Each component will provide expandable details as to problems and a link to configuration if available.
 

  1. On your JEMH Cloud system click the licensing tab on the navigation bar.





  2. From the left hand menu click System Status, after a couple of seconds the system status page should be fully loaded.




Below we go into a little more detail regarding each section on the system status page.
 

Red boxes indicate an invalid configuration or an offline component. Yellow boxes indicate some configuration that may be improved to work as desired. Green boxes indicate component is working fine!

Host Section

This section gives the status of your JEMH Cloud system and provides a summary of your plan usage / system notification recipients.

Inbound Messages Section

This section contains information regarding inbound message sources, message handlers and profiles on your JEMH Cloud system:

Profiles

Profiles (see 1 above) define how a message is to be processed, if the profile isn't connected to a message handler it won't be used.

Message Handlers

Message Handlers (see 2 above) associate an inbound Message Source (the email source) with a Profile (how to process the email).

Message Sources

Message Sources (see 3 above) are mechanisms to receive email, if it is offline no email will be processed. If the message source isn't connected to a message handler no mail will be retrieved from the mailbox.

Outbound Messages Section

This section contains information regarding message outbounds, notification mapping and events on your JEMH Cloud system.

Events

Events (see 1 above) shows a summary of the web-hook events that have been received and processed.

Notification Mapping

Notification Mapping (see 2 above) associate a Profile with a Message Outbound (where the mail goes). If the notification mapping doesn't include a given project then events from that project won't drive a notification through this Notification Mapping.  Also Notification Mappings can be temporaily disabled and whilst in this state no notifications will be generated.

Outbound Mail

Message Outbound (see 3 above) are mechanisms to send email, if it is offline no email will be processed. If the Message Outbound isn't connected to a Notification Mapping no email will be passed sent through the mailbox.  A common problem with outbound mail is that the password has expired or the account has been rate limited.

Slack Notifications Section

This section contains information regarding what Slack rooms have been configured to receive notifications.  Typical problems with Slack are tokens expiring after a year and rate limiting.

Storage Section

The storage section shows external storage services that can be used in JIRA projects. At this time this is only available via the view issue screen directly we do plan to enable the usage of these services for email attachment storage in the future.  Typical problems for external storage services are expired tokens and / or rate limiting.