Table of Contents
Read Time: 6 mins
The Sonar Status page is used to relay information and provide updates around Sonar's uptime/downtime, system metrics, as well as both ongoing and past incidents. This article will provide details on the information and actions you can access from this status page along with how you can set yourself up to receive automatic updates for incidents.
The Sonar status page is available here: https://status.sonar.software/
Current Status Page
The Current Status page is the first screen you will land on when accessing https://status.sonar.software/. It contains a few different sections which are discussed in more detail below.
Subscribe to Updates
Subscribing to updates is a great way to ensure you are kept in the loop for any outages or interruptions that come up and for corresponding updates as the team works to identify and resolve the root issue. There are several different ways that the updates can be sent out, such as email, text message, Slack, or webhooks - simply click the "Subscribe to Updates" button on the main screen, select the notification method, complete any necessary fields (if applicable), and you're all set!
Each option available will provide details on the events you will be notified of when subscribing.
If there are no ongoing incidents, the current status screen will appear with an "All Systems Operational" message, as can be seen below.
If, however, there is an ongoing incident, details about the incident will be displayed here instead, as can be seen in the image below.
There will be a banner across the top of the incident that provides the incident name (which is "Database error" in the example image above) and a button to "Subscribe" to updates for this specific incident. Although we recommend subscribing to all general updates, you can subscribe to updates for just specific incidents via email and/or text message - simply click "Subscribe", fill out any necessary fields, and you'll receive email notifications when incidents are updated and text message notifications whenever Sonar creates or resolves an incident.
Clicking on the incident name in the banner will also open a new page where you can view all details for that particular incident, including what the incident affects within Sonar.
A little further down on the main status page you will find a record of Sonar's uptime/downtime for the last 90 days. Each vertical bar represents a day in the last 90 days and hovering over each one will provide additional details for that day. Green indicates no downtime, grey means no data exists for that day, and yellow/orange will be used to indicate some sort of event/issue.
By clicking on an individual bar, or by expanding either of the "Exposed Services", "Backend Services", or "Third Party" groups, you will see the uptime/downtime for any child components that make up that group.
Using the image below as an example, the Exposed Services group contains the following child components: Web Application, GraphQL API, and Netflow Processors. Hovering over the "?" icon next to each child component will provide further details on that component.
The uptime for the last 90 days will be displayed within the current status screen, but historical uptime data outside of these 90 days is also available by clicking the "View historical uptime" link at the top of the uptime segment.
By clicking this link, you'll be taken to the Historical Uptime screen where you can further inspect uptime data via a calendar view. The dropdown can be used to filter the uptime data to just specific groups or child components/services, and the date toggle allows you to go further back in time than just the last 90 days. Hovering over the squares within a month will provide additional details for the uptime on that specific day as well. Each day will also appear as a color, similar to the individual bars for the uptime on the current status screen, with green indicating no downtime, grey indicating no data for that day, and yellow/orange indicating some sort of event/issue.
Below the uptime stats on the Current Status screen, you'll find a section dedicated to system metrics that includes data for HTTP response time and GraphQL API response time. By default, it will show the data for the day, but you can toggle the graphs to see past data by using the "Day", "Week", or "Month" options in the top-right corner. Hovering over the "?" icons next to the graph titles will provide details about what this data is referring to.
The last segment, at the bottom of the current status screen, is a section dedicated to past incidents and their details. Each day will have an entry and indicate whether there were no incidents reported, or provide the details for the incident if one occurred.
The incidents displayed in the Past Incidents section will be the most recent, but you can also view historical data for incidents previous to this point in time. At the very bottom of the Past Incidents section, you will see the link to "Incident History" - this will take you to the screen for the historical incident data.
The Incident History screen will provide details for any outages or disruptions that happened in the past, organized by month - this will include any planned or scheduled maintenance as well. The incident history for the last 3 months is displayed by default, but through the date toggle in the top-right, you can change this to view historical incident data for further back in time.
For any incident that appears on the Incident History screen, you can obtain further details for it by simply clicking on the name of the event. This will take you to a new screen where data for just that specific incident can be viewed.
For example, after clicking on the incident name "[Scheduled] Postgres Maintenance" (in the above image), we are taken to a new screen where we can view all of the details for this specific event (pictured below).