|Note:||To use this guide, you need to know how to use AlertSite DéjàClick transaction recording tool. If you do not have the DéjàClick toolbar in your Firefox browser, go to the DéjàClick Downloads page to download the DéjàClick add-on and additional modules (TrueScreen and ImageMagick). If you have never used DéjàClick before, please go to the DéjàClick Quick Start Guide. After you have become comfortable with recording DéjàClick transactions, you will be able to move on to this more advanced feature.|
Today's websites have content from a variety of sources, not only from your own company, but 3rd party content as well. DéjàClick™ ContentViews categorizes this content, providing segregated reporting capabilities and the ability to intelligently notify the responsible owner of the content when it is down or in error. This enhances your ability to troubleshoot performance issues within your site without having to deal with poorly performing components from external sources.
ContentViews automatically captures all site content found in your transactions, allowing you to:
Easily monitor the components independent of each other.
Select and prioritize whether or not to receive notifications based on ContentView errors.
Produce ContentViews-specific reports with graphs and charts.
Easy set-up through the DéjàClick Properties Sidebar or the Validation selector on the DéjàClick toolbar.
Visibility in the AlertSite console.
Alert notification control.
Configurable ad-hoc (one-time) reports.
Each feature and procedure is explained in detail below.
Before you get started, you must first decide how you want to partition the content contained in your transaction. For example, you may want to have only URLs with your web site's domain in one ContentView. In another, you might want certain Content Delivery Network (CDN) URLs. The third might contain other 3rd party URLs. It is completely up to you to determine how you want to categorize the content within your transaction.
Once you have decided how to classify your content, you are ready to add and configure different ContentViews.
There are two ways to configure ContentViews:
In Plan-Based accounts, ContentViews can be included as an additional feature for most DéjàClick plans. Once added to an existing plan, ContentViews can be configured as described in this guide. In Usage-Based accounts, ContentViews consume measurement credits at a rate of 1/4 usage credit per action in your AlertSite account. However, if no matching content is reported by the ContentView, no usage credits are charged to your account.
Let's take an example in which we partition one domain into one ContentView, another domain into another ContentView, and create the third ContentView for all pages not contained in either of the other two ContentViews.
If a transaction has ContentViews, the AlertSite Dashboard will display the icon next to the monitor name.
|Note:||If you have configured everything correctly and do not see the icon, make sure the Show ContentViews in device grid: is set to Yes in the monitor Tab Preferences settings.|
The icon is displayed even if ContentViews is disabled on the Manage Transaction screen.
Along with partitioning on URLs, ContentViews, and predefined lists, the Add ContentView dialog has 3 optional attributes you can use in addition to the URLs or Domains to separate URLs by:
Select the Filter on Content Type check box.
In the list, select types that you do not want to include in the ContentView and click .
If you want to a Content type to the list, click , enter a new Content Type, and click OK.
Minimum size – Minimum size of pages in bytes.
Maximum size – Maximum size of pages in bytes.
Click to the left of an action or event to be excluded from the ContentView.
You can also configure the ContentView to continue to the next action or event in case of an error. To do this, select the check box under Replay Options. Enable this option, if the ContentView does not contain the critical path of the transaction.
After you have recorded and verified a transaction and configured ContentViews, upload the script to AlertSite. You will be redirected to the Manage Transaction screen, where you can make more configuration changes, such as monitoring type, timeouts, locations, and so on. You can also configure there Fullpage Options, Capture Options, ContentViews, and Transaction Description.
You can configure ContentViews notifications in the ContentView Settings section of the Manage Transaction screen:
|Note:||The ContentView Settings section will not be displayed if the transaction does not have any ContentViews.|
There are two settings:
By default, some global errors that occur in the transaction may affect individual ContentViews, but they are not passed through to the ContentView, so notifications will be issued for the error in the main transaction but not in the ContentView.
If you want ContentViews to inherit these errors from the main transaction, for example, if a fullpage timeout occurred on one step, you may want pass that error through to the ContentView set up for your domain. In that instance, select the Inherit Global Errors check box for that ContentView.
The following AlertSite Status Codes apply to Inherit Global Errors:
|80||Browser event timeout encountered.|
|81||Maximum transaction time was exceeded.|
|90||Unexpected processing exception occurred.|
|92||Maximum number of skipped events exceeded.|
|93||Missing instruction for dialog prompt.|
|96||Unable to parse transaction XML.|
|97||Target page element was not found.|
To receive notifications for the base transaction, make sure the Notify on Error option of the Device Settings section is set to Yes, because the script may fail while the ContentViews may still be successful.
You can configure recipients for ContentViews. For the most control over notifications, we recommend that you create a recipient group for all ContentViews otherwise all recipients in AlertSite will be alerted on ContentView errors. This takes advantage of the main reasons for utilizing ContentViews. By using Notifier Groups, you select who is to be notified based on content of interest.
To create a recipient group:
From the top menu, select Notifiers > Notifier Groups.
Click Add a New Group at the upper right.
In the Notifier Group Name field, enter a group name. For example, Amazon Only CV Group.
Locate the transaction in the Available Sites list, find the Amazon Only ContentView and click to move it to Included Sites.
Select recipients from the Available Notifiers list and click to move them to Included Notifiers. In our example, we selected Administrator, Operations, and Management.
Click Submit at the upper right to save the changes.
Similarly, add Two more groups:
The Doubleclick Ads Only CV Group group for the Doubleclick Only ContentView. In our example, we assigned Marketing to this recipient group.
The Neither Amazon nor Doubleclick Content Group group for the Neither Amazon nor Doubleclick ContentView. In our example, we assigned Management and Operations to this recipient group.
Now, when the pages with the amazon.com domain produce errors, only the Administrator, Operations, and Management recipients will be notified. If pages with ad.doubleclick.net in the domain name are in error, only the Marketing recipient will be alerted. And when pages with any domains other than amazon.com or ad.doubleclick.net are in error, only Administrator and Operations will receive alerts.
After uploading the transaction to your account, it will take some time for the transaction to propagate out to your selected monitoring locations and begin gathering performance measurements. Allow 10-15 minutes past your monitoring interval before attempting to run a report.
You can produce graphs and charts based on the selected ContentViews.
Performance Graphs (Availability, Response Time, etc.)
Report API for data extraction
When a transaction has been configured with ContentViews, the AlertSitePerformance Reports screen will display the ContentViews below the main transaction in the Site/Device list:
To illustrate the properties of ContentViews-partitioned reports, we have created a couple of reports for the Amazon Only and Doubleclick Only ContentViews.
A line of measurements has been expanded in each one. By expanding the sections and drilling down to the object level, you can see that the list of objects in Amazon Only contains only objects with amazon.com in the URL:
The objects in Doubleclick Only contain only objects with the domain ad.doubleclick.net:
The objects in Neither Amazon nor Doubleclick contain only objects that do not include the domains amazon.com or ad.doubleclick.net:
In this way, reports with relevance for particular groups or individuals can be created and scheduled, then distributed as needed.