Discussion Feed

Updated on 10/2/18   Contents Overview Application Monitoring and KPI Dashboard Transaction Analytics Platform Analytics and KPI Dashboard Implementation and End-to-End Workflows Release Notes and Upgrading FAQs and Troubleshooting Webinar   Overview The AppDynamics integration with Pivotal Cloud Foundry (PCF) lets you easily deploy AppDynamics-monitored applications on the PCF platform and gather performance and infrastructure metrics. At the center of this integration are two distinct tiles:   1. Application Monitoring for PCF : For APM and Transaction Analytics of applications running on the Cloud Foundry. APM is provided through AppDynamics support inside the standard Cloud Foundry buildpacks and Service Broker deployed through the tile. Transactional Analytics for applications are provided via the AppDynamics Analytics Agent, deployed through the tile. Extension Buildpack is provided to help instrument .NET HWC applications.  For detailed information on the integration and Application Monitoring for PCF, visit the resources linked below: AppDynamics for Pivotal Cloud Foundry AppDynamics Service Broker AppDynamics Extension Buildpack   2. Platform Monitoring for PCF : For Cloud Foundry infrastructure monitoring . The tile includes: A Nozzle application written in GoLang to collect the metrics from the Cloud Foundry Loggregator. A Python application that automatically creates and manages health rules and a Dashboard from those collected metrics. For product overview of Platform Monitoring for PCF, visit the resources linked below: AppDynamics Platform Monitoring for PCF AppDynamics Platform Monitoring for Pivotal Cloud Foundry   Note: Prior to v4.5.460, Application and Platform metrics were managed as one tile. Starting with 4.5.460, Platform Metrics are now managed by a separate tile.   With these two tiles, you have access to full performance and infrastructure KPI metrics and out-of-the-box KPI dashboards, health rules, and alerts that enable you to monitor the performance of any PCF platform. For overviews of PCF Application Performance and Platform Monitoring, examples of how the PCF Buildpack and Service Broker work, an outline of the Extension Buildpack, and a list supported environments, check out the blog posts below: The AppD Approach: Pivotal Cloud Foundry Performance Monitoring AppDynamics Enhances Pivotal Cloud Foundry Performance Monitoring with New Infrastructure View AppDynamics Launches Extension BuildPack for Pivotal CloudFoundry Applications Pivotal Cloud Foundry: Two Tiles Are Better Than One Blue-Green Deployment Strategies for PCF Microservices   Application Monitoring and KPI Dashboard The APM KPI Dashboard visualizes the application performance of the PCF platform on which your AppDynamics tile is running in one single view from your AppDynamics Controller UI. For a deep dive on the monitored PCF performance metrics and instructions on how to use the PCF Dashboard Generator and enable health rules, see AppDynamics PCF KPI Dashboard .   Transaction Analytics If you are on version 4.4.337+ and have an Analytics license, you can also view Transaction Analytics in your AppDynamics Controller. For instructions on configuring your tile for analytics, binding applications to the Analytics Agent, configuring your Controller to fetch data from the Events Service and configuring the Analytics Collector on your Controller, visit Configuring Transaction Analytics .   Platform Analytics and KPI Dashboard Quick to install with minimal configuration and memory usage, the Platform Monitoring for PCF tile allows you to configure infrastructure monitoring with KPI Dashboards, health rules, and alerting capabilities . The AppDynamics Firehose Nozzle uses a lightweight Go SDK to collect and report metrics to the Dashboard. Go Language is the official language for Pivotal Cloud Foundry, so this ensures you’re compliant with PCF. To take advantage of this tile, you’ll need a Go SDK AppDynamics license.   Implementation and End-to-End Workflows APM and Transaction Analytics Follow the steps outlined in the resources below to install and configure Application Monitoring (APM) and Transaction Analytics: Installing and Configuring AppDynamics Configuring Transaction Analytics Using AppDynamics These four pages provide examples of end-to-end workflows using sample Java, .NET, Python, and PHP applications: Java Application in PCF – Monitoring Workflow .NET Application in PCF - Monitoring Workflow Python Application in PCF – Monitoring Workflow PHP Application in PCF – Monitoring Workflow   Platform Monitoring The pages linked below details the process for installing and configurating Platform Monitoring for PCF. Installing and Configuring AppDynamics Platform Monitoring Overriding Default Configurations   Release Notes and Upgrading Note: Please note that upgrades from AppDynamics v1.x are not supported. If you previously installed AppDynamics v1.x, uninstall it and install the latest version. This is especially important since the Platform Metrics framework has been rewritten to use the new Firehose Nozzle instead of JMX Bridge.   APM and Transaction Analytics To stay up-to-date on the latest functionality in the AppDynamics/PCF integration for APM and Transaction Analytics, check out the Release Notes regularly.   Platform Monitoring For updates on Platform Monitoring for PCF, also visit the Release Notes .   FAQs and Troubleshooting APM and Transaction Analytics This  FAQ page includes troubleshooting tips and answers to common questions about the AppDynamics tile, Service Broker and buildpacks, Machine agents, PCF Dashboard, and other topics.   Platform Monitoring This FAQ page addresses questions about the Platform tile, SSL configuration, Dashboards, and more.   Webinar For more hands-on training geared towards operations teams and developers, you can watch our recorded webinar on how to monitor polygot distributed applications deployed to PCF. @mark.prichard ,  @Pavan Krishna.Nimmagadda , and  @Jeffrey.Holmes guide you through the complete application lifecycle, showing you: How to deploy and configure APM solutions using Cloud Foundry buildpacks for Java, .NET, node.js, Python, and other languages. How to install and configure the AppDynamics Service Broker tile. How to monitor PCF and BOSH infrastructure health and availability using the new monitoring integration recently introduced for Pivotal 2.x.   To view the recording, read a transcript of the Q&A portion, and access additional resources, visit [Technical Session] Monitoring Pivotal Cloud Foundry Applications and Infrastructure . ... View more

ICEfaces  is an  open source   Software development kit  that extends  JavaServer Faces  (JSF) by employing  Ajax .   It is used to construct  rich Internet applications  (RIA) using the  Java  programming language. With ICEfaces, the coding for interaction and Ajax on the client side is programmed in Java, rather than in JavaScript , or with  plug-ins .   To create a Business Transaction match rule in AppDynamics that effectively matches ICEfaces entry points, follow these steps:   In the Transaction Detection UI tab in the Controller UI (Configuration > Instrumentation > Transaction Detection), create a new custom match rule. Choose Servlet as the entry point type for the rule. For the Transaction Match Criteria, match by URI containing the word faces . In the Split Trasactions Using Payload tab, split by POJO Method Call. Split based on the second parameter  (at index=1) of the  com.sun.faces.application.ViewHandlerImpl.renderView() method, getViewId(). For example: ... View more

In some instances, you may need to perform additional configuration to properly instrument Microsoft SharePoint sites with the AppDynamics .NET Agent.   New in 4.1.3 ,  if you are running Microsoft SharePoint with .NET Framework 4.5.2 or 4.6 and later, the .NET Agent automatically instruments SharePoint without configuration changes to SharePoint.   Symptom If you suspect you are having issues instrumenting SharePoint sites with the .NET Agent, check the agent log (AgentLog.txt) for entries as follows:   2015-05-13 17:38:18.9799 13436 w3wp 2 26 Error ConfigurationChannel Exception: Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401)Exception: System.IO.FileLoadException: Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401) at System.Net.HttpWebRequest.GetRequestStream() at AppDynamics.Shared.Communication.qe.ju(Byte[] , String ) at com.appdynamics.ee.rest.controller.request.av.kkw() See "Log Files" on .NET Agent Directory Structure.   Solutions Choose the solution below that best fits your environment.   Modify the SharePoint application web.config   Check the value of the legacyCasModel attribute of the trust element in the SharePoint web.config: <trust level="Full" originUrl="" legacyCasModel="true" /> If legacyCasModel  is set to "true," then change it to "false". Save the web.config file Restart IIS. Confirm your application continues to work normally. If, for any reason, setting legacyCasModel to "false" is not possible, use the option below to modify the registry.   Modify the Global Registry Microsoft has provided the following workaround for this issue.   Back up the .NET agent Logs directory (for example, %ProgramData%\AppDynamics\ DotNetAgent\Logs) and remove its contents, but be sure to retain the Logs directory itself.  Configure the following registry settings: Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework Create new DWORD "LoaderOptimization" with value 1 Under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\ Create new DWORD "LoaderOptimization" with value 1 This configuration disables loader optimization assemblies that cause this issue. Restart the Appdynamics.Agent.Coordinator service. Restart IIS.     ... View more