Avenue

The Monitor Details page provides you with a comprehensive overview of all the essential information related to your monitors. 

1. This label describes the current state of the monitor, in the example above we see that the monitor is in an Active state, but you may see Failed, Paused, or Verifying. 

1. Indicates which of the four main monitor types this monitor is configured as. Learn about the four monitor types here: <a href="https://docs.useavenue.com/en/articles/8160441-monitor-types">Monitor Types</a>.

1. This label identifies the monitor group this monitor belongs to. See <a href="https://docs.useavenue.com/en/articles/6957797-monitor-groups-bulk-edit">Monitor Groups</a>

1. Here you can remove or add both Dynamic and Static tags to your monitor. These tags will then be associated witch each signal. See <a href="https://docs.useavenue.com/en/articles/7735754-adding-tags-to-signals">Tags</a>.

1. If your monitor is an Event, Report, or Metric type you will see a button to Pause/Start your monitor. If you are using a Webhook/Form type monitor you will see a button to submit a form and create a signal. 

1.  Set the priority level that you want each new signal to be set with.  

1. Monitor State 
 1. This label describes the current state of the monitor, in the example above we see that the monitor is in an Active state, but you may see Failed, Paused, or Verifying. 
2. Monitor Type 
 1. Indicates which of the four main monitor types this monitor is configured as. Learn about the four monitor types here: <a href="https://docs.useavenue.com/en/articles/8160441-monitor-types">Monitor Types</a>.
3. Monitor Group 
 1. This label identifies the monitor group this monitor belongs to. See <a href="https://docs.useavenue.com/en/articles/6957797-monitor-groups-bulk-edit">Monitor Groups</a>
4. Tags
 1. Here you can remove or add both Dynamic and Static tags to your monitor. These tags will then be associated witch each signal. See <a href="https://docs.useavenue.com/en/articles/7735754-adding-tags-to-signals">Tags</a>.
5. Pause Monitor/Submit Form
 1. If your monitor is an Event, Report, or Metric type you will see a button to Pause/Start your monitor. If you are using a Webhook/Form type monitor you will see a button to submit a form and create a signal. 
6. Default Priority
 1. Set the priority level that you want each new signal to be set with.

1. This section shows information related to the setup of your monitors
 1. Created at - Time this monitor was created. 
 2. Last updated at - Time this monitor was last adjusted.
 3. Run cadence - Schedule of monitor runs. 
 4. Recipients - Designation of notifications. 
 5. Escalation Policy - The rules dictating escalations. 
 6. Message - The note sent with the notification.

1. This selection allows you to switch notifications to be either notifications or tickets. Once Create Ticket is selected you will see options on Auto-Resolving tickets and setting an Assignee. 

1. Monitor Configuration Info
 1. This section shows information related to the setup of your monitors
 1. Created at - Time this monitor was created. 
 2. Last updated at - Time this monitor was last adjusted.
 3. Run cadence - Schedule of monitor runs. 
 4. Recipients - Designation of notifications. 
 5. Escalation Policy - The rules dictating escalations. 
 6. Message - The note sent with the notification. 
2. Create Ticket
 1. This selection allows you to switch notifications to be either notifications or tickets. Once Create Ticket is selected you will see options on Auto-Resolving tickets and setting an Assignee.

1. This is a stream of all the signals created by this monitor. Keep in mind you can also view these in the <a href="https://docs.useavenue.com/en/articles/8032534-signals-table">Signals Table</a>.

1. Monitor runs give you a summary of each execution of your monitor. You can see errors if it fails, or check on the number of rows returned 

1. Here you can see all of the changes that have been applied to this monitor and by whom.

1. Monitor Actions allow you to create manually triggered or event triggered workflows after signals are created. For example, you could add a "File Bug" action which if selected creates a ticket in your engineering teams task manager of choice with information populated from the signal. 

1. Signals 
 1. This is a stream of all the signals created by this monitor. Keep in mind you can also view these in the <a href="https://docs.useavenue.com/en/articles/8032534-signals-table">Signals Table</a>. 
2. Monitor Runs 
 1. Monitor runs give you a summary of each execution of your monitor. You can see errors if it fails, or check on the number of rows returned 
3. Audit Logs 
 1. Here you can see all of the changes that have been applied to this monitor and by whom.
4. Actions 
 1. Monitor Actions allow you to create manually triggered or event triggered workflows after signals are created. For example, you could add a "File Bug" action which if selected creates a ticket in your engineering teams task manager of choice with information populated from the signal.

1. Selecting this allows you to add a Playbook to this monitor which subsequently will apply the Playbook to each created signal. 

1. Attach a Playbook 
 1. Selecting this allows you to add a Playbook to this monitor which subsequently will apply the Playbook to each created signal.

Header

Properties

Overview

Playbook