Foglight.NET How to install and troubleshoot

Transcription

1 Foglight.NET How to install and troubleshoot

2 Slide Index Learning Objectives- Slide #3 Product Overview- Slides#4,5 Installation tips Slides #11-14 Known Issues Slide #24 Troubleshooting Checklist-Slides # Relevant Documentation Slide #36 Prerequisites for Contacting Support-Slide #38 2

3 Learning Objectives How To Install & Troubleshoot Upon completion of this lesson, the student should have an understanding of the product use case, the product components, and be able to troubleshoot issues. The student should also be able to collect all the necessary information that support would require to diagnose an issue in the event a service request needs to be raised. 3

4 Product Overview Architecture Foglight for Microsoft.NET gives you the tools you need to monitor the availability and perfomance of your Microsoft.NET applications. The product components that allow for such functionality include: FMS Foglight Agent Manager Instrumented Agent Nexus 4

5 Product Overview Architecture FGLAM MONITORED HOST A1 A2 FMS HOST NEXUS AGENT Installs transactions msi Installs counters msi Collects perf metrics Performasure agents Collects request metrics FGLAM A1 A2 Counters Agent 8080 Cdt config FMS Agent adapter DOT NET CARTRIDGE Data Processing FMS DB IIS Agent 1 IIS Agent 2 Generic Agent 1 Foglight Agent Host ( windows service) Rules Dashboard Generic Agent 2 5

6 Management Server Foglight provides 24x7 monitoring to help you detect and resolve performance issues in your application server infrastructure and in the applications running in that infrastructure. Foglight includes a set of standard dashboards, as well as a number of rules that notify application and system administrators about performance problems. These dashboards display data stored on the Management Server. You can create agents to monitor servers after you install the cartridge file on the Management Server. 6

7 Foglight Agent Manager The Agent Manager is a client that manages agents installed on particular hosts. It provides a centralized communications link between the Management Server and the agents. The Agent Manager also provides a number of support services such as installation, upgrade, and the ability to configure agents. An instance of the Foglight Agent Manager is automatically installed with new installations of the Foglight Management Server. This embedded Agent Manager instance runs on the Management Server machine. 7

8 Nexus Foglight creates a default Nexus as part of the installation process. The Nexus behaves as an agent: you can activate and deactivate it, start and stop its data collection, view its properties, assign a profile that contains recording settings to it, or delete it. The default Nexus controls all agent data correlation and submision unless you create and assign another Nexus It receives data collected from the agents, then combines and converts agent-based event information into a cohesive information set that can be queried and presented graphically by Foglight. 8

9 .NET Agents An instrumented agent collects performance information from.net domains and passes this data to the Foglight Management Server through the Nexus and the Agent Manager. At the application level, service request agents use bytecode instrumentation to measure method-level performance information. At the server level, agents monitor the application server metrics through vendor-provided interfaces. At the.net run-time level, agents monitor various metrics; at the operating system level, they monitor platform-level metrics 9

10 .NET Agents There are two types of.net Agents Transactions Agent Collects request information via instrumentation, sends data through the Nexus. Counters Agent Collects metrics via WMI, sends data through FglAM. Remote: Really only recommended for POCs without Application Operations where the monitored host cannot be touched. Locally: Runs on the monitored host, along with the transaction agent. Needed for Application Operations. 10

11 Installation Tips - Agents For installation, please review the following video solution and installation guide Create the Counters agent which takes responsibility for installation and integration of the Transactions agent with IIS. Counteragent will install two msi's. - Counters msi is to collect perf metrics. Counter agent sends data straight to FMS through Transaction msi is the performasure agent. Transactions agent also installs a new service called foglight agent host. Agent host sends data to nexus to send request data through

12 Installation Tips- Agents First agent starting with DotNET is the counters agent you created. The second agent, named after host and application pool name was automatically created when the application pool was started. 12

13 Installation Tips - Agents All IIS Servers will need to be restarted to complete integration. Use iisreset to restart and pick up new environment variables. Always use Application Servers Administartion dashboard for installation/upgrades. Never use the Agent Status dashboard 13

14 Installation Tips -Nexus One-to-one relationship with FgLAMs (i.e. one Nexus per FglAM) Use Nexus on separate system if you are looking for maximum FMS scalability (i.e. offload processing off of FMS) Use multiple Nexus's if you want different Nexus settings for different environments. 14

15 .NET Administration Select to setup and manage.net agent configurations and installations. 15

16 .NET Administration Transaction Configuration Used to tune what is actually instrumented..net instrumentation settings currently still in text. Application pool restart required for new transaction configuration settings. If application pools are set to recycle, settings will be picked up next interval. If not, restart IIS. 16

17 .NET Administration Integration Configuration To include/exclude IIS and Included Web Application-By default, the IIS performance counters and application availability metrics are monitored when you create a performance counters agent.if you want to monitor specific web applications, you can include or exclude them by name. Standalone and Windows Services - Integrating with a Windows Service provides availability and transaction metrics, as well as performance counters Editing.NET Thread Metrics Integration Configurations- Specify whether to enable or disable collection of thread metrics from integrated IIS, Windows Services, and standalone applications. By default, thread metrics are not collected. Switch Nexus Connection 17

18 .NET Administration Manage Collection Schedules Adjust the collection schedule of different categories of WMI metrics. New schedules can be created and assigned to individual agents. 18

19 .NET Administration Installations Manage installations Upgrade an installation Delete an installation 19

20 Nexus Administration Select to create, configure, and control Nexus agents, including Recording settings. Recording settings are shared by all agents connected to a single Nexus. 20

21 Nexus Administration Recording Settings (Request Sampling) Update Filtering Rules. Separation Rules and URL Transformation Rules will currently be ignored by the.net Agent. Settings will take effect immediately for all agents connected to a Nexus using these recording settings. 21

22 Nexus Administration Additional Nexuses Multiple Nexuses can be created. Agents that will participate in a single request should be connected to the same Nexus. Recording settings can be changed on a per- Nexus basis. Allows for different recording settings for different groups of agents. 22

23 Nexus Administration Recording Settings (Collection Details) Use to set collection details for individual request types or for all request types. Enable Individual Requests for Application Operations functionality. Settings will take effect immediately for all agents connected to a Nexus using these recording settings. The Advanced tab can generally be ignored. Have a look if you re interested. 23

24 .NET agent Known Issues Solution SOL SOL SOL Description WMI configured with insufficient internal resources Counter collector not getting samples after initial category read fails. No more threads can be created in the system" error message when collecting counter metrics SOL The.NET agent process shows signs of memory leaks on Windows 7 and Windows 2008 R2 24

25 Install Locations On Monitored Host Transactions Agent - C:\Quest_Software\Foglight.NETAgent\transactions Counters Agent -C:\Quest_Software\Foglight.NET Agent\counters Msi location -C:\Quest_Software\Foglight _Agent_Manager\agents\DotNet\<5.9.1_build>\Installers On Nexus Host Nexus agent - C:\Quest_Software\Foglight _Agent_Manager\agents\ApplicationServer-Nexus 25

26 Troubleshooting- Transactions Agent Examine log file on disk - C:\Quest_Software\Foglight.NET Agent\transactions\5.9.1\dist\logs - Find and read FATAL,ERROR,WARN log messages for clues Use the Event Viewer to examine Windows Application logs Download fglam support bundle 26

27 Troubleshooting- Transactions Agent Make sure the worker process is instrumented. This can be verified by using Process Explorer tool COR_ENABLE_PROFILING should be set. - Open process explorer, navigate to the w3wp.exe process. - Right click on Properties and navigate to Environment tab. Make sure COR_ENABLE_PROFILING=1 27

28 Troubleshooting- Transactions Agent A few performasure dlls should be loaded as well. - Open process explorer, navigate to the w3wp.exe process. It should have entries for Performasure_.dll if application pool is successfully instrumented 28

29 Troubleshooting Counters Agent Examine log file on disk - C:\Quest_Software\Foglight_agent_manager\state\default\process\DotNET\logs 29

30 Troubleshooting Counters Agent -2 Examine log file on disk C:\Quest_Software\Foglight_agent_manager\state\default\process\DotNET\l ogs\dotnet\5.9.2\dotnet 30

31 Troubleshooting- Agent Installation For installation issues-examine msi log located below 31

32 Troubleshooting Creating Agents In the Task History section, click Success/Failure 32

33 Troubleshooting Creating Agents If the agent was created but unable to start collections, then use Get log 33

34 Troubleshooting Nexus Examine the Nexus log file located here - <FGLAM_HOME>\state\default\logs\ApplicationServers-Nexus\5.9.1\Nexus\ - <FGLAM_HOME>\state\default\agents\ApplicationServers-Nexus\5.9.1\logs\ Can be downloaded and viewed in Foglight 34

35 Troubleshooting Checklists The Quest Support Portal provides several valuable knowledgebase articles to address common product issues: SOL How to enable debug for the.net Agent? SOL DotNet Monitoring is not working SOL How to set debug on Nexus 5.9.x SOL41911 How to set debug mode for FGLAM 35

36 Relevant Documentation Release Notes 592_ReleaseNotes.html Installation covered in installation guides html/frameset.htm?href=cartridge-apm/dotnetcartridgeinstall/index.php 36

37 Prerequisites for Contacting Support 37

38 When opening a service request submit the following: Problem Description, Issue severity and business impact, timeframes, etc. FMS Support bundle, Fglam support bundle, screenshots Environmental details (OS versions, FMS version,.net Agent version,.net framework version, IIS version etc.) Unexpected behaviour may require DEBUG or DEBUG2 agent Logs. If there is a problem with instrumentation, a restart of the application pool may be required to capture instrumentation time log messages. 38

39 DELL CONFIDENTIAL AND PROPRIETARY This document Foglight for.net Support Training contains confidential information of Dell and embodies trade secret and proprietary intellectual property of Dell. It is legally protected and shall not be copied, modified, reverse engineered, published, disclosed, disseminated outside of Dell or otherwise used, in whole or in part, without Dell s written consent, provided, however, that you have the right to use the Document solely for your internal use and solely as necessary for you to enjoy the benefit of Services under the applicable SOW (or other agreement) you have entered into with Dell. Copyright 2012 by Dell Inc. The copyright notice does not imply publication of this document or its contents. DELL, the E (Stylized in a sphere) logo, Dell Compellent, OpenManage, EqualLogic, PowerEdge, PowerVault and other Dell trademarks are the trademarks or registered trademarks of Dell Inc. in the U.S. and certain other countries. 39