In One Platform it is possible to generate a status page about your applications and dependencies registered in your digital product.

This page is modular and customizable according to your needs or your customer. It can be configured which applications and dependencies you want to monitor in a macro way (only the status of the application in the total set) or if you prefer to present the status of each individual component.

You can register as many status pages as you want, with different components for a given team, customer or objective.

On the status page, it is possible to follow the current status of the application or dependency, informing if it is Operational, Partially Operational or Non-Operational along with the average response time of the respective component. Helping to understand if, in addition to being operating normally, the time that the component is taking to answer the end user.

You can also track, in the last 7 days, whether there have been incidents on a given day and their current status, making it public if the incident has already been resolved or if the status remains. Only application incidents and dependencies that are configured to be displayed are shown.

Internal metrics or sensitive operating information are not presented for the engineering and product team, and may only be monitored in the Resilience Matrix.

The status page feature is available for use according to your 1P plan. If it is not released, talk to our customer service in the chat.

To create a status page, go to the left sidebar and click on Status Page.

On the next screen, there will be a listing of all status pages already configured (if any).

To create a new public status page, click on NEW, the green button in the upper right corner.

A new page configuration screen will open. In this step, you customize name, url and the components that will be displayed in this particular status page.

First enter a name that will be displayed on your Status Page. Below are comparative images of configuration and presentation.

By default, we use the same name as the page to create the URL slug, but it can be customized as you wish. It is not mandatory to have the same name and slug.

( 1P configuration)

(displayed on the public status page)

Below the name and slug, the status page components are displayed.

The components are divided and configured by groups, and in these groups are shown the applications and dependencies desired for each separation.

In this step, we have two blocks: My Resources x What will be shown in your Status Page.

My Resources field presents your products registered in 1P, with the names pre-configured on the application pages.

What will be shown in your Status Page, well, is what will definitely be presented and made public.

Click on ADD Group and a component icon will be placed in the block on the right. Name the group in the available field, and drag an application or dependency under the created name.

This configuration works as a drag-and-drop, that is, just select, drag the components from one block to another and drop.

After configuring as desired, click on Save at the bottom of the page.

Automatic saving is not done.

The public status page URL created will be generated after performing the steps described above and the name and slug will be available right below.

See below a model of how it was configured in 1P and how it looks:

(configuration made in 1P)

(components shown on the status page)

Did this answer your question?