立即与支持人员聊天
与支持团队交流

Foglight for Application Operations 5.9.8.5 - User Guide

Introducing Foglight APM Monitoring Transactions Examining Response Times Examining Error Breakdowns Viewing Real User Activity from a Geographical Perspective Using the SOC Transactions Tab Using the SOC for APM triage Creating Custom Drag-and-Drop Dashboards APM Tile and View Reference Appendix: Enabling End User Transactions from FxM and FxV

Introducing Foglight APM

This User and Reference Guide provides an overview of Application Performance Monitoring (APM) with Foglight for Application Operations and Foglight APM for Real User Experience (hereafter called Foglight APM). It includes conceptual information to help you envision an APM installation with Foglight and overviews of the Service Operations Console (SOC) and other applicable dashboards that help you manage your unified APM installation.

This guide is intended for Application Performance Managers or Administrators who administer the overall design, implementation, and execution of the application performance monitoring strategy.

Application Performance Monitoring (APM) refers to a set of capabilities or technologies that IT staff use to support the incident and problem management processes on multi-tier applications. A comprehensive APM implementation generally includes technology that provides the following capabilities:

Foglight APM supports all of these capabilities, and provides information to the right users at the right time through a set of role-oriented operational dashboards.

Although there is no single organizational alignment or uniformly agreed upon set of titles for the actual practitioners of APM, the following role descriptions indicate the types of functions that typically interact with a Foglight APM installation:

Foglight Administrator — responsible for configuring and managing Foglight, and for performing administrative tasks.
Application Performance Manager — responsible for the design, implementation, and execution of the APM strategy.
Application Support — responsible for ensuring that application services are performing as expected. Identifies and triages service degradations or outages.
Platform Specialist or Administrator — responsible for the operation of an individual application component (for example, a database, a host, an application server, or a web server). Receives and responds to Foglight alarms on their platform or domain.
Application Architect — a senior escalation resource who is typically engaged by Application Support for assistance in locating the source of an application issue.
Application Developer — responsible for the application code. Uses the Foglight transactional performance dashboards to gain understanding of the operational execution and performance of their code.

For more information, see the following topics:

Understanding the Foglight APM implementation

Foglight supports a modular approach to APM that allows customers to implement as many or as few pieces of the APM solution as required. This guide is intended as a comprehensive overview of an end-to-end APM installation strategy, and therefore includes cross-domain views.

Before you implement an APM strategy, it is important to perform proper requirement gathering, environment sizing, project planning, and scoping, just as you would with any other application. Our Professional Services team has developed a comprehensive strategy for APM implementation. You can review our process online at:
http://support.software.com/professional-services-product-select/.

Foglight requirements for APM workflows

In order to make the best use of this document, ensure that your Foglight installation meets the following requirements before starting the workflows:

 

Monitoring Transactions

A transaction occurs when a user or synthetic robot makes a request to a monitored application. Depending on the components in your installation, Foglight can capture and correlate transactional activity at multiple layers including:

With the Transactions dashboard, you can examine transactional data in the following ways:

The tiles on the Transactions dashboard represent different transactional views. Use the table below to quickly determine the type of transaction, then review Investigating real user APM transactions or Investigating application server transactions for an overview of how to drill down for more information.

Foglight APM for Real User Experience transaction.

For more information, see Real User (APM) Performance detail view.

Foglight Experience Monitor/Viewer End User transaction.

For more information, see Real User (FxM) Performance detail view.

Foglight for Java EE Technologies or Foglight for Microsoft .NET transaction.

For more information, see Application Server detail view.

Foglight Transaction Recorder Synthetic User transaction.

For more information, see Synthetic Result detail view.

Sequence.

For more information, see Sequence tile.

Pivot - Browsers.

For more information, see Pivot tiles.

Pivot - Content Types.

For more information, see Pivot tiles.

Pivot - Endpoints.

For more information, see Pivot tiles.

Pivot - Locations.

For more information, see Pivot tiles.

Pivot - OSes.

For more information, see Pivot tiles.

For example, in the following image, the Physician group of tiles represents a real user perspective with pivot data. The performance summary on each tile includes an alarm state overview and other key metrics. For a full description of the metrics displayed on each type of tile, see APM Tile and View Reference.

For more information, see the following topics:

自助服务工具
知识库
通知和警报
产品支持
下载软件
技术说明文件
用户论坛
视频教程
RSS订阅源
联系我们
获得许可 帮助
技术支持
查看全部
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级