Creating and Managing Monitors

Monitors are tools that you can create that will allow you to be automatically notified in the event that conditions you specify exist. An example of when you might want to use this would be to be notified if your site or page is unreachable, is acting sluggish, or if something on the page is causing the page to load slowly.

Creating a new Monitor

  1. To create a new monitor log in to the Yottaa portal and click the top menu bar entry labeled "Monitors"

  2. On the Monitors page under "Manage your Monitors" if you have created monitors before click the button labeled "NEW"  to bring up your options, otherwise click the green button labeled "Create A Monitor"

Setting Basic Info

This section sets up basic information for the monitor including the name, the page to be monitored, and the venue to be monitored. This is the default page you start on when creating a new monitor.

  1. Set what you will call your your monitor in the text field next to "Monitor Name"
  2. Set what page will be monitored and whether it will be HTTP or HTTPS using the dropdown menu and text field next to unreachable, you do not include http/s in the URL text box, for example http://www.foo.com would just be entered as www.foo.com in the URL text box
  3. Select what you're specifically monitoring using the dropdown menu.

NOTE:

  • HTTP Monitor is for monitoring the back-end or server side features. This is most useful for checking site availability and speed related events
  • Features under the heading "Monitor Webpage with Real Browser" display rendering results as seen by common web browser engines. This is useful for monitoring display results to clients using multiple browsers and verifying certain content is being properly displayed
  • "Monitor Mobile Web Apps" displays results users that connect to your site through common mobile devices

Scheduling Options

This section goes over setting the frequency that the monitor will run, and for how long the monitor will run.

  1. The checkbox next to "Enabled" defines whether this Monitor is set to run. Toggle this on to start enabled and off to start disabled. Once the Monitor is created
  2. Sample frequency is how often the monitor will run.
  3. Run Monitor denotes whether the monitor should run all the time, during a specific set of days a week or at a specific time of day every day.
  4. Start and end monitor are when the monitor should begin and end. Setting the Start Monitor for Now and the End Monitor for Never will run until you disable the monitor.

Location and Connectivity Options

This section sets the specific regions to monitor and the type of network to test against.

  1. Check or uncheck the boxes next to the datacenter locations to test those locations.
  2. The dropdown for "Last Mile Connectivity" allows you to test for specific network conditions or use the Default option to test with settings that will capture conditions for most users.



Setting Issue Definitions

This section defines the specific conditions to monitor for and allows you to define a severity level for the event. By default this section populates all available types of issue definitions, but only enables HTTP response status code when the monitor is first created.

  1. To turn on or off individual Issue Categories click the grey or green eye icon next to the category text
  2. To add a new issue definition mouse over the bottom left of the box  on the button for "Add issue definition" and in the option menu that pops up select the type of issue you'd like to keep track of
  3. Set the options for each issue you would like within the monitor and define a severity for the issue. The severity is important for defining notifications for the monitor

  • HTTP response status code - HTTP responses with status code 400 and above are considered as HTTP response status code issues by default. Typically these status codes mean a significant problem on your site, and therefore it is classified as a Critical Error by default. (You can change this in the issue definitions)
  • Site reachability - Network connectivity issues refer to issues that prevent users from connecting to your site. These issues include DNS problems and TCP/IP problems. This is classified as a Critical Error by default. You can configure it to alert once for the issue in any/all regions, or individually for each region
  • Network performance - Network performance issues occur when a backend timing metric (such as connection time, time to first byte, time to last byte, etc.) exceeds the time limit you've set for it. You can set this up to track the performance of your DNS service or backend server responses
  • HTTP response header - When a user attempts to access a page with a web browser they submit information to the site within the headers. In return your site sends back a header file with information regarding the site. You can use this to make sure your site is sending proper information to end users. This can include instructions not to cache the site, the server that the site is loaded from, and HTTP response status codes. 
  • HTTP response content - Network performance issues occur when a backend timing metric (such as connection time, time to first byte, time to last byte, etc.) exceeds the time limit you've set for it. You can set this up to track the performance of your DNS service or backend server responses.

Advanced Options for Monitors

This section sets advanced options including methods, authentication, and more complex configuration options to test against specific actions.

  1. HTTP Method - Choose the method of HTTP that defines the action of the configurations you make in the options below. The default choice, "GET" is the most common.  Keep this selection if you are using a cookie to monitor performance of a logged in session.  
  2. Authentication - Enter credentials here if the page you'd like to monitor requires a login using HTTP Basic Authentication. (If you're using a cookie to monitor a logged-in session of a SaaS app that has its login screen in the frame of the browser, this step is not necessary)
  3. Custom HTTP Header - Enter a value here to create a custom HTTP header for your monitor. Doing so allows users to simulate certain conditions for website visits made by the monitor. A common use for this feature is to paste a cookie from a logged-in session of a SaaS app in order for the monitor to bypass login credentials and thus monitor the performance of pages within the app.
  4. Custom HTTP Body - Enter a value here to add parameters to the HTTP body for your monitor. Doing so allows users to simulate certain conditions for website visits made by the monitor. Most use cases for this feature involve using the POST method. You could make the monitor send a large amount of data to the server (simulating a file upload or other form of data transfer) 

Save the monitor

You can save your new monitor at any time by clicking the "Save"  button in the top right hand corner of the page. You can cancel your new monitor at any time by clicking the "Cancel" button in the top right hand corner of the page.

Have more questions? Submit a request

Comments

Powered by Zendesk