Help Docs

Threshold and Availability for OpenTelemetry monitors

After adding an application monitor to your Site24x7 OpenTelemetry, you can create a Threshold and Availability Profile for the alarms engine to send alerts when the resource is critical, down, or in trouble. The alert occurs on any breach of predefined conditions that you can set. 

Add Threshold and Availability

Follow the steps below to add Threshold and Availability to the OpenTelemetry monitor:

  1. Log in to the Site24x7 web client.
  2. Click Admin > Configuration Profiles > Threshold and Availability.
  3. Click Add Threshold Profile on the top right corner in the Threshold and Availability screen to launch the Add Threshold Profile screen.
  4. Choose OpenTelemetric Service as the Monitor Type.
  5. Provide a Display Name for the identification purpose.
Note

Threshold profiles can also be added by following the below steps.

  1. Navigate to APM > OpenTelemetry > your application.
  2. Click the hamburger (Hamburger icon) icon near the Services drop-down menu and choose Edit.
  3. Click the add symbol in the Threshold and Availability field to launch the Add Threshold Profile screen.

Please keep in mind that the Monitor type will be OpenTelemetric Service by default.

Threshold Configuration

You can select the required parameters from the Set Threshold Values drop-down menu.

  • Apdex Threshold:
    Apdex score values range from zero to one, with one indicating maximum user satisfaction and zero indicating frustrated satisfaction levels. You can set up trouble or critical alerts for Apdex score values that fall below the configured threshold.

  • Average Response Time Threshold:
    When the Average Response Time breaches the configured threshold value, you will be notified with Trouble or Critical status. The average response time is set to 2,000 ms by default. Select any condition from the Condition drop-down menu, such as >, >=, =, and =, and then enter a value in the Threshold box.

  • Error Count Threshold:
    When the error count breaches the configured threshold value, you will be notified with Trouble or Critical status.
    For example, you can configure your application to receive alerts when your error count exceeds 50, or whatever value you deem appropriate for your application.

  • Error Rate Threshold:
    When your error rate breaches the specified threshold value, you will be notified with the status Trouble or Critical.
    For example, you can configure to get alerted if 10% of your total transactions are errors.

  • Throughput Threshold:
    When the Throughput breaches the configured threshold value, you will be notified with the status Trouble or Critical.
    Select any condition from the Condition drop-down menu, such as >, >=, =, and =, and then enter a value in the Threshold box.

  • Exception Count Threshold:
    When the exception count exceeds the configured threshold value, you will be notified with the status Trouble or Critical.

Validating threshold breach

Poll count serves as the default strategy to validate the threshold breach. You can validate a threshold breach by applying multiple conditions (>, <, =, >=, <=) on the Condition drop-down.

Poll Strategy

You can choose any strategy from the Poll Strategy drop-down, such as Poll count, Poll average, Time duration, and Average time.

When the condition applied to any of the below threshold strategies holds true, the particular monitor's status changes to Trouble or Critical.

  • Poll count:
    When the condition applied to the threshold value is continuously breached for the number of times specified in the Poll count, the status of the monitor changes to Trouble or Critical.

  • Poll average:
    When the average value of the breached values (for the number of specified polls) satisfies the condition applied to the threshold value, the status of the monitor changes to Trouble or Critical.

  • Average time:
    When the average value of the captured values (for the configured time in the time duration) satisfies the condition applied to the threshold value, the status of the monitor changes to Trouble or Critical.

  • Time duration:
    When the condition applied to the threshold value is continuously breached for the time duration specified in the time duration, the status of the monitor changes to Trouble or Critical.
Note

Click on Add Critical Threshold option to add new record for the Critical status.

Edit Threshold and Availability

  1. Go to Admin > Configuration Profiles > Threshold and Availability.
  2. Click the profile to launch the Edit Threshold Profile screen.
  3. Change the parameters you want.
  4. Click Save.
Note

You can also edit a particular application's threshold profile by following the steps below.

  1. Navigate to APM > OpenTelemetry > your application.
  2. Click the hamburger (Hamburger icon) icon near the Services drop-down menu and choose Edit.
  3. Click the edit symbol in the Threshold and Availability field to change the parameters you want.

Please keep in mind that the Monitor type will be OpenTelemetric Service by default.

Delete Threshold and Availability

  1. Go to Admin > Configuration Profiles > Threshold and Availability.
  2. Click the hamburger (Hamburger icon) icon of the profile which you want to delete.
  3. Click Delete.

Was this document helpful?

Would you like to help us improve our documents? Tell us what you think we could do better.


We're sorry to hear that you're not satisfied with the document. We'd love to learn what we could do to improve the experience.


Thanks for taking the time to share your feedback. We'll use your feedback to improve our online help resources.

Shortlink has been copied!