Sending Hits and Failures to a Webhook Application

To make this configuration, access the product for which you want to
set up monitoring and click on the “New Resource” button. Once you
click, a window will open with various monitoring options. Select:
“Receive and record hits and failures via Webhook.”

Once the configurations open, select the environment, give a name to
the application, and configure the values for “Interval in seconds” and
“Fails to incidents.”

When you finish filling in the fields, click on “Save,” and the
application monitoring page will appear. In the box located in the right
corner, click on the button “Monitoring is inactive” to activate the
monitoring. After that, click on the button “HITS AND FAILURES API” to
configure the hits and failures data transmission to the designated API.

You’ll see a pop-up window  that contain the information to be used
for communication between your environment and the platform. This
communication is crucial for data analysis, development of the
resilience matrix, incident control, and other resources available on
the platform.

Just replace the <token> and follow the instructions of the pop-up windown to finish the configuratino and initiate the monitoring. 

 

Note: Our application has a rate limit of 30 requests per second. This means that each IP can make a maximum of 30 requests to the server in a period of 1 second. If this limit is exceeded, additional requests will be temporarily blocked.

To make this configuration, access the product for which you want to
set up monitoring and click on the “New Resource” button. Once you
click, a window will open with various monitoring options. Select:
“Receive and record hits and failures via Webhook.”

Once the configurations open, select the environment, give a name to
the application, and configure the values for “Interval in seconds” and
“Fails to incidents.”

When you finish filling in the fields, click on “Save,” and the
application monitoring page will appear. In the box located in the right
corner, click on the button “Monitoring is inactive” to activate the
monitoring. After that, click on the button “HITS AND FAILURES API” to
configure the hits and failures data transmission to the designated API.

You’ll see a pop-up window  that contain the information to be used
for communication between your environment and the platform. This
communication is crucial for data analysis, development of the
resilience matrix, incident control, and other resources available on
the platform.

Just replace the <token> and follow the instructions of the pop-up windown to finish the configuratino and initiate the monitoring. 

 

Note: Our application has a rate limit of 30 requests per second. This means that each IP can make a maximum of 30 requests to the server in a period of 1 second. If this limit is exceeded, additional requests will be temporarily blocked.