Matriz diamante de Porter

Management, and Administration options.

NOTE

VantageView only supports Internet Explorer.

After it is enabled, VantageView is available from the main menu. For more information see the VantageView Online Help.

Glossary

application

An application is a universal container that can accommodate transactions. Each application can contain one or more transactions and those transactions can originate form different sources. Applications organize the data that travels through your network into logical units or logical categorizations of tasks that are performed over the network.

Application Health Status dashboard

Dashboard that enables you to analyze the health of an application via fault domain isolation and root cause analysis.

browser time zone

The server and browser may reside in different time zones. The Portal displays the time of the browser location.

component

In the Service Model, a logical service's components (Components service property) are the child services that are essential to the function of the logical service. A simple example of a component relationship is a logical service representing a database with component physical services representing resources and functions that the database cannot operate without, such as file space availability and database query response.

connection

A connection is the definition of a specific usage of an adaptor. Each connection consists of a set of adaptor configuration settings and a connection ID.

control panel

Administrators typically use the Control Panel to access the portal administration tools and modify various settings. These tools are organized into categories and accessible through a link on the Control Panel. To access the Control Panel, click Administration ➤ Control Panel.

dashboard

A user interface which organizes and presents performance information from multiple

applications into a unified readable and interactive display. Each dashboard contains pages and portlets to display application performance, availability, usage and infrastructure health.

data center analysis

Page that facilitates a targeted application performance and transactional analysis to find out what tiers are underperforming and what is contributing to this.

Data Mining Interface (DMI)

Data Mining Interface (DMI) is a Web-based, interactive, dynamic report-building module. DMI reports have immediate access to currently available data and can refresh automatically when new data becomes available.

Trending and baseline data is also available for customized reports. Trending data is transparently used when needed, while baseline data can be mixed with current data on the same screen. DMI reports have variable time-range settings, variable resolution settings, and dynamic sorting and filtering mechanisms. Tabular reports and extensive chart generation capabilities are also available, with the ability to mix multiple report sections on the same page. Custom-built reports can have a hierarchical structure, with contextual drilldown, sibling, and parent reports.

data view

Sets of dimensions and metrics related to specific issues or topics. This data can be presented in tables, charts, and gauges.

data view group

That entity housing the data views for which data is collected.

dynagrid layout

Layout that lets you edit add lines and merge cells in a simplified layout editor dialog until the desired effect is achieved.

event

Any occurrence in a system, database, or server.

Executive dashboard

Provides a view of problems in the organization, their impact, and the trends and current statuses for a service or group of services. The Executive dashboard contains Summary, Improve and Scoreboard pages.

Fault Domain Analysis (FDA) Portlet

Portlet which supports the Applications dashboards allowing for deeper, more detailed fault analysis targeting users, applications, software modules, locations, and operations.

LAR file

LAR (Liferay Archive) files are zipped files used in the Liferay framework. Dynatrace Enterprise Portal is built on the Liferay enterprise web platform.

look and feel

Exposes the themes for pages and reports, which can transform the entire look of a portal.

metric

A measurement taken for a particular entity at a particular time or for a particular period. Each metric has a unique name. For example, the total count of bytes transferred by specific clients during a given length of time is referred to as Client bytes. Note that there are different metrics for different data views.

notification

A message sent from the Service Model via email, paging, or SMS.

Operations dashboard

Designed for use by operations staff and provides a detailed view of the status of services within an organization. The Operations dashboard contains Summary, Details, Transactions Summary and Events pages.

page

A subsection of a dashboard which contains portlets. Pages are used to organize the dashboard into distinct sections depending on the information being displayed by the portlets and the intended purpose and audience.

portal admin

Section of the Control Panel used to configure and control users, dashboards, user groups, roles, settings and monitoring.

portlet

A predefined unit of data which may include graphs, geographic views, other visual elements, or tabular data for services mapped from the Service Model.

portlet type

Organizational categorization for BSM default portlets dependant on their purpose, intent, and display information. Types include:

• Availability: Availability portlets display the "up" or "down" status of a service over time. • Downtime: Downtime portlets display how long a service is down or how many users are

affected.

• Events: Events portlets include alerts, status changes, and notifications pertinent to the services.

• Integration: Integration portlets bring data from a non-Gomez product or service. • Performance: Performance portlets display the quality of one or more services.

• Reconciliation: Reconciliation portlets include information and utilities used to track outages. • Service Model: The Service Model portlets display configuration elements (as opposed to

data) of the Service Model, such as tools or schedules.

• Utilities: Utilities portlets add functionality such as navigation, labels, or controls.

service

A service is the most basic object in the Service Model. Each service in the model calculates and maintains current status properties (for example, service quality, availability, performance

metrics, user impact or affected user counts), as well as historical status information based on these properties; all of which are analyzed by the Service Model statistics engine. Services fall into two categories:

• Physical Services representing physical objects that are necessary for the business to

function. Simple examples would be disk drive space or a connection device. In the Service Model, a physical service receives events and data directly from the Service Model system's data adaptors (that is, events and messages from your business enterprise).

• Logical Services representing business functions. An example would be a complete billing

system that consists of a combination of various system components. A logical service receives and acts upon data from other services.

The Service Model works with services by:

• Specifying, for each physical service, rules or tests that are used to assess relevant incoming data.

• Setting status properties of the service concerned on the basis of the results of those tests. • Deriving the status settings for higher-level, logical services from their child physical

services using rules or methods set for the logical service. Here, methods used for setting status properties range from simple functions such as determining best, worst or average of child services, to more complex expression-based logic.

service group

In the Service Model, a service group (Service Groups Service Model property) is a definition of user-defined search criteria that are applied to the Service Model to determine the services that are included in the group. Several default service groups are provided with the Service Model. A usage example is to apply, in a single action, attributes (for example, a statistics profile) to all services in a group. Another example is to apply a service group to focus the Service Model display on services that match group's search criteria.

service quality

In the Service Model, service quality indicates a service's current condition, based on criteria such as evaluator results, availability status, or the condition of another service. Service quality status is assigned from a user-customizable defined set of quality rankings; for example Excellent, Good, Normal, Bad, and Critical. Assignment of service quality status from a range of rankings, and basing the assignment on evaluation criteria is a key concept in modeling a business enterprise. You are able to define the different levels of quality that can be represented in the Service Model, ranging from IT event type severities to levels that highlight potential business impacts. You can then set different thresholds to determine what service quality rankings indicate that a service is acceptable, unavailable, or in failure.

statistics

In the Service Model, statistical analysis can be enabled and configured to convert the Service Model's response to incoming messages into data patterns that show how business services are performing over time.

The Service Model processes these main types of performance data for its current set of services:

• Data that is based solely on the results of the application of service evaluators (logic and ranking data) and generally represents multi-state information (service quality and availability).

• Metric data derived from connection event value properties, some of which may have been processed by expressions configured in the Metrics property of the involved service. When processed, both types of data are tagged with details of whether they fall within various service time tables, peak times, etc. The tagged data can be fed into the Service Model's statistics engine for detailed analysis and assessment of performance compliance. They can also be supplemented by reference to various types of user count data derived from service availability patterns.

The Service Model is provided with a pre-defined set of statistics type definitions that identify reporting periods: StatisticsHourly, StatisticsDaily, StatisticsWeekly, StatisticsMonthly, and StatisticsYearly. Statistics types that can be selected individually or in combination.

For each statistics type, there is a pre-defined set of statistics calculation types, each of which outputs a set group of statistics: Availability, Metrics, Six Sigma, Service Quality, and User Impact. Statistics calculation types also can be selected individually or in combination. The Statistics Service Model property enables selection of statistical reporting periods, schedules for data polling and statistics calculation, which statistic to calculate, the services from which to collect the supporting data, and publishing (output destination) options.

themes

Deployable plugins which can transform the look and feel of the portal. You can create a theme plugin which can then be installed, allowing for a new look and feel.

tier

Logical application layer, a representation of a fragment of your monitored environment. The front-end tier in a user-defined configuration is the layer that is closest to the end user. Each application is defined as a set of transactions and can be divided into logical layers (tiers), such as Web servers, middleware, or a database. Each transaction can be a collection of data gathered across various tiers.

transaction

A transaction is defined as a unit of interaction between the server and the client, such as a user requesting a URL. A transaction is one of the following:

• A simple transaction consisting of a single operation such as a Web page load. • A more complex transaction consisting of sequences of operations.

• A collection of non-sequenced operations.

user

In the Central Security Server users are added either locally or via LDAP by a system

administrator so they can access Business Service Management, the Dynatrace Enterprise Portal and Data Center Real User Monitoring.

user role

In the Central Security Server, five default roles are provided to define product access to users. For example, a user with a system administrator role would have complete access to all product functionality, while a user with a guest role would only have view-access to some default dashboards and other components.

user group

In the Central Security Server, a user group can be created by a system administrator so similar groupings of people can be assigned access roles, domains or dashboards in the Dynatrace Enterprise Portal.

Index

A

access page without logging in 22 access the Portal 10

add 28 user groups 28 add roles 30 add user 26 Adding user groups

25

in the Dynatrace Enterprise Portal 25 adding users 25

Adding users 25

in the Dynatrace Enterprise Portal 25 administration overview 9

Alerting 25

assign page rights 15 assign user roles 30 Assigning roles

25

in the Dynatrace Enterprise Portal 25

B

banner 23

C

configure VantageView 37 Console User 29 role 29 contact information 6 Control Panel 19–24 adding dashboards 19 adding pages 19 creating a page 22 customized page 22

Control Panel (continued) exporting 24 importing 23 Look and Feel 21 page distribution 21 page settings 22 page type 20 Portal administration 19 Customer Support 6 information to provide 6

D

database settings 25 define permissions 30

Dynatrace Enterprise Portal interface 11

E

enabling VantageView from the portal 37 Enterprise Synthetic

25, 33, 35–36 Agent Health portlet 33 configuring connection 35 edit Agent Health portlet 35

edit Agent Health Transaction Health portlet 36 Transaction Health portlet 33

G

In document Plan estratégico de mejora continua para la empresa de servicios fumilimpieza de la ciudad de Loja (página 111-119)