|Oracle® Real User Experience Insight User's Guide
Release 6.5.1 for Linux x86-64
Part Number E18053-01
This glossary provides an explanation of the terms used in RUEI.
Assigned users responsible for maintaining the RUEI installation. This includes monitoring the system's health status, performing configuration backups, and defining the scope of network operations that will be monitored. They are also responsible for maintaining users and permissions.
Automatically generated notifications issued when KPIs move outside their defined target ranges. When configuring alerts, you need to specify the duration a KPI must be up (or down) before an alert is issued, the severity of the incident, and whether additional notification should be created when the KPI has returned to its set target range.
Defines the users who will be notified (and how they will be notified) if business or technical KPIs have been down (or up) for the specified duration required to generate alerts. Depending on how the KPIs has been defined, users will also receive an up notification when the KPIs return to within their set target range.
Two types of alert schedule are available: Business and Technical. If your organization uses alerts to notify staff members about incidents that impact service levels, these schedules specify who should be notified and when.
Page identification mechanism. An application is a collection of Web pages. This is because pages on a Web site are typically bound to a particular application. Each application has a page naming scheme defined for it, which specifies its scope. This can be specified in terms of a domain name or a URL structure, or a partial match of both of these.
Users who are concerned with evaluating visitor behavior according to business goals. As such, they use the business intelligence that RUEI offers them to monitor a wide variety of issues, such as identifying the most popular paths taken to your Web site, or how engaged visitors are on particular pages or sections. See also IT users.
Specifies the interval over which KPIs will be monitored in order to determine their value. Note that the selected value does not affect the level of monitoring. However, selecting a longer period of time (such as 15 minutes) is useful for Web sites with low traffic levels, and where a sample time of 5 minutes would mean that often nothing was measured.
Reports or information within the Data Browser provides information about a particular date or period. The From and To sections within the Calendar provide a mechanism to specify the required period. This can be specified in terms of days, weeks, or months.
A means of grouping KPIs, reports, and user flows. Typically, each category contains items relevant to a particular aspect of an organization's operations. For example, performance, page availability, visitor traffic, and so on.
Small files that are stored on the user's computer while browsing a Web site. They are used to track visitors. RUEI needs to know and understand the cookie technology you Web site is using. This will either be a standard technology (such as ASP or ColdFusion), or a custom implementation.
A visual display of the most important information required to achieve one or more objectives, consolidated, and arranged on a single screen so the information can be monitored at a glance. You are free to configure your dashboards to reflect your organization's specific requirements, with each dashboard containing relevant performance indicators. For example, you could have separate dashboards for such things as availability issues, performance, and visitor traffic.
The information captured during monitoring is stored as a multidimensional data structure. The Data Browser allows you to explore Web data by simply clicking down through increasing levels of detail, and view by different dimensions (such as period, referrer, visitor type, and so on). You can use it to understand the context of the data shown in reports.
Provides a powerful means for Application Managers and IT technical staff to perform root-cause analysis of operational problems. Diagnostics information is available from within the All sessions group, the Service test group, the Failed URLs, pages, and functions groups, as well as the accelerator-specific groups.
Areas of the Internet specified by a URL address. The top-level domain is at the end after the dot and the second-level domain comes before it, and shows where in the top-level domain the address can be found. For example in www.webtrends.com, ".com" is the top-level domain, and "webtrends" is the second level domain.
RUEI maintains an event log that contains a record of all system events. Normally, it should be empty. If any error is reported in the file, you should contact Customer Support.
Specifies that only data items that do not match the data value in the filter should be shown. See also inclusive filters.
You can export the data currently shown in the Data Browser to a wide variety of applications, such as spreadsheets. In addition, you can customize how the data should be exported. You can modify the order of data columns, specify additional columns that will appear in a Microsoft Excel export, and specify the format in which the data will be exported.
Facility that helps you to quickly locate the reports you work with most often by creating shortcuts to them.
User-defined strings that are reported when they appear on a requested page view. For example, "Your credit card has expired". Contrast with page content checks.
KPIs and dashboards can be defined as generic or bound to a specific application, suite, or service. Access to the information within an item is automatically managed through each user's assigned permissions.
Each Data Browser group is either Business or IT-related (or both). Examples of such groups include the All sessions group, and the All and Failed pages groups.
Contains general information about the reports you are viewing. This includes the report's title, an indication of the reported metrics, and the date or period to which the report refers.
Specify that only data items that match the data value in the filter should be shown. See also exclusive filters.
Each report contains an information screen providing a glossary of the terms used in the report. This is useful when you (or other report users) need an explanation of the metrics used in a report.
When reports are opened, they are shown in inline mode. This offers a high-level overview of the report's contents, and provides ready access to more detailed information available through the report. See also print layout mode.
Users who are concerned with supporting the IT information that RUEI needs to monitor the Web environment, such as configuring the cookies used to identify users. Typically, they are responsible for deeper analysis of failed SLAs or KPIs. For example, they might identify that failed user visits are only occurring for users from a particular network domain.
Monitored Web pages that receive special attention. Typically, these are pages in which you have particular interest. For example, your organization's home page, or a series of pages within a user flow (such as placing an order). For these pages, additional information is recorded. This includes client information (such as ISP, the country of origin, and so on), and the visitor browser information (such as operating system, browser version, and so on).
Key performance Indicators. A means of measuring and benchmarking specific aspects of an organization's performance. These are based upon metricss. KPIs can be set independently of SLAs. What distinguishes SLAs from KPIs is that SLAs must have targets associated with them, while for KPIs targets are optional.
Facility that allows you to compare the behavior of a selected KPI over a given period with other KPIs and performance metrics during the same period. In this way, you can gain insight into performance issues, identify any related symptoms, and their possible causes.
Facility that allows you to review the current status of your authorized KPIs within each category. Access to individual KPIs is available by drilling-down through the displayed information.
Allows you to obtain a ready overview of the reports you receive through automatic e-mails, and the frequency (daily, weekly, or monthly) with which they are sent to you. See also favorites.
The Collector can be configured to omit logging of sensitive information. This is called masking, and it allows you to prevent passwords, credit card details, and other sensitive information from being recorded on disk.
The underlying benchmark for KPIs. It is the parameter or quantitative assessment of the aspect of the monitored Web environment to be measured. It defines what is to be measured. For example, the number of current sessions or page views per minute.
A facility that allows you to enhance the information associated with visitor IP addresses. The additional information is viewable via the Data Browser.
A facility that allows you to assign ranges of IP addresses to a Web server group, and to individual Web servers. For example, a server group could be a department or data center, and the server name refers to specific Web servers within that group. The additional information is viewable via the Data Browser.
You can use network filters to manage the scope of monitored traffic. They allow you to restrict monitoring to specific servers and subnets, and to restrict the level of packet capture. See also scope.
Specifies a text string that should appear on a specific page. For example, your Web application has an Order page, and at the end of a successful sale, the text string "Thank you for shopping with us" should appear. Note that page content checks are specific to a defined page, while functional errors apply to an entire application.
Specifies the user's experience when viewing application pages within a session. This can be satisfactory (that is, the page loads in the user browser within a specified threshold), tolerable (the page takes longer to load than the specified threshold), and frustrating (the page takes more than four times the specified threshold to load).
Every page monitored by RUEI must be identified to it. Information about any pages not defined to the system is discarded. Page identification is based on applications.
These are located in the URL immediately after a question mark and followed by an equal sign and a return value, in the format name=value.
These are described in Table 1-1, "Roles".
This layout can be thought of as the report's template: it defines the report's structure and appearance. This is the mode you will use when modifying reports, or creating new reports. See also inline mode.
Provides you with the insight you need to assess the performance of your network infrastructure. RUEI comes with an extensive library of predefined (standard) reports. Reports are grouped into categories, dedicated to specific aspects of the monitored traffic. Each report is made of headers (report), an information screen, and a number of sections.
Specifies any additional conditions for KPIs. Using this facility, you can build compound KPI conditions.
The request return status specifies whether the transfer was successful and why. See Appendix E, "Explanation of Failure Codes" for more information about the HTTP result codes that can be sent to visitors as replies to requests.
Within RUEI, you control the scope of traffic monitoring by specifying which TCP ports RUEI should monitor. Obviously, no information is available for unmonitored ports.
Typically, reports contain several sections. For example, a daily traffic report could contain two sections: one reporting traffic in terms of page views for the requested period, and the other reporting traffic in terms of bytes.
Assigned user responsible for managing security-related issues. These include defining which sensitive information (such as credit card details) are omitted from logging, and the installation and management of SSL keys to monitor encrypted data. Se also masking and KPIs.
Allows users opening a created report to select the information they view.
For example, if you are viewing client location information (within the all sessions group), you could create a report that allowed its users to select on client location. See also inclusive filters and exclusive filters.
Specifies when the service levels defined for your organization should apply. Typically, an organization has a core time (for example, 9 am - 5 pm, Monday - Friday) when the committed service level should be achieved. However, you may need to define exceptions to this, such as for public holidays and planned maintenance periods.
Specific applications can be monitored for Oracle Enterprise Manager service test traffic and, when detected, reported via the Service tests group.
A period of activity for one visitor to a Web site. A unique user is determined by the cookie IP address. Typically, a user session is terminated when a user is inactive for more than 15 minutes.
Specifies the seriousness to the organization when KPIs move outside their defined boundaries. Possible values are Harmless, Warning, Minor, Critical, or Fatal.
Service Level Agreements. An agreement between a provider and a customer that explains the terms of the provider's responsibility to the customer, and the level of service that the customer can expect. For example, an SLA for a given service might promise that it will be up and running 99.99 percent of the time. Because these are monitored, they must be based on KPIs.
Single sign-on (SSO) is a method of access control that enables a user to log in once and gain access to the resources of multiple software systems without being prompted to log in again. Because different applications and resources support different authentication mechanisms, single sign-on has to internally translate and store different credentials compared to what is used for initial authentication.
A collection of predefined applications. Currently, three suites are delivered: E-Business Suite (EBS), Siebel, and PeopleSoft. They save time in the configuration of applications, and ensure the applications within them are more compatible, and are correctly monitored.
For KPIs with SLAs associated with them, a target must be specified. You can define them in terms of fixed ranges (for example, between 80 and 100), or specify a number of days over which KPIs are sampled for small, medium, or large deviation from their upper or lower limits.
Within RUEI, dashboards are created based on templates. There are three of templates: system, public, and published. System templates are provided with the product installation, and cannot be modified. Public templates are created and maintained by Administrators. Published templates are used to create dashboards that are viewable by external users via a generated link.
Pages that have been identified as belonging to an application through its URL definition, but for which no classified name has been found. By default, these are discarded and not reported.
A sequence of pages that define a logical task. For example, a ferry booking application might have the following pages defined for the user flow booking: route and date details, passengers and vehicle details, payment details, and confirmation.
By default, data in report sections is shown in graphic form. However, you can choose to view the data in a tabular form. You can also specify the number of values that are shown in the displayed table.
A clearly defined business function that operates independently of the state of any other service. It has a well-defined contract with the consumer of the service. Services are made available through service descriptions, which describe how to call the service, and what information is required to request the service and get a response.