Discussion Feed

steve.hetland · ‎02-16-2018

Hello, from your log, it looks like your account name and key are missing from your controller-info.xml configuration. This page explains how to get the values to use: https://docs.appdynamics.com/display/PRO44/Agent-to-Controller+Connections#Agent-to-ControllerConnections-FindingYourAccountNameandAccessKey But what I recommend is getting the agent from the Java Getting Started Wizard in the UI. That way, you'll get the settings you need for your instance preconfigured in the config file.

steve.hetland · ‎12-20-2017

Hi Nisha, Renaming your node in the UI should work fine until the next time the agent/monitored app restarts. At that point, the node will pick up whatever name has been specified in the agent configuration, which would be the old name unless you have made the config change mentioned in the doc. The way you change the name in the configuration depends on the agent type. For Java Agents, it would commonly be set in the controller-info.xml file. See https://docs.appdynamics.com/display/PRO44/Install+the+Java+Agent#InstalltheJavaAgent-ConfiguretheJavaAgent for details. If renaming is not working in the UI at all, make sure you are logged in with a user who has sufficient permissions. If you are not, you would get an error when attempt to save the Node Properties with the new name (although I see that the error may not be entirely clear).

steve.hetland · ‎10-19-2017

Hi Wahyu, You should install the Universal Agent on the Application Server machine, that is, on all machines that run an application to be monitored. The controller-book.json rulebook will reside on those machines. The part of the UA system that resides in the Controller home directory will be the agent repository. That's the location from which Universal Agents retrieve the monitoring agents, Java Agent, Machine Agent, etc. Be sure to browse around the rest of the doc, everything under https://docs.appdynamics.com/display/PRO43/AppDynamics+Universal+Agent For installing agents, for instance, check here: https://docs.appdynamics.com/display/PRO43/Install+the+Universal+Agent And for setting up the Controller repository, here: https://docs.appdynamics.com/display/PRO43/Runtime+Agent+Repository Hope this helps.

steve.hetland · ‎03-13-2017

Hi Sundar, I'm still working on getting an example for you, but in the meanwhile, you may find it helpful to review sample script that processes an event. See https://github.com/bnagallo/ExportParams-AppD The way that the doc puts it, "where "x" is the position of the condition", isn't quite clear.... As I read https://github.com/bnagallo/ExportParams-AppD/blob/master/appd_alert.sh, those values (i.e., $CONDITION_NAME_x, etc) are accessed by parameter position in the list of parameters passed by the Controller when calling the scipt. The sample script checks the number of triggered conditions, and cycles through the parameters by incrementing position reference (CURP). So with two conditions, the first THRESHOLD_VALUE_x would be accessed at parameter position 28, roughly and the next one at around 40 or so. As I say, I'll try and get confirmation on this for you, along with a sample.

steve.hetland · ‎01-06-2016

Updated on 8/1/18 Contents Overview Implementation and End-to-End Workflows PCF KPI Dashboard Transaction Analytics Release Notes FAQs and Troubleshooting Webinar Overview The AppDynamics integration with Pivotal Cloud Foundry (PCF) lets you easily deploy AppDynamics-monitored applications on the PCF platform. The PCF Service Broker tile, installed using the BOSH deployment on your local PCF installation, provides a tight integration between AppDynamics and PCF. You’ll have access to full infrastructure KPI metrics and an out-of-the-box KPI dashboard that enables you to monitor the performance of any PCF platform on which your AppDynamics tile is running. You can also deploy an Analytics Agent to view transaction analytics on your Controller. For a brief overview of Pivotal Cloud Foundry Performance Monitoring, examples of how the PCF Buildpack and Service Broker Tile work, and highlights of our recent PCF enhancements, review the two blog posts below: The AppD Approach: Pivotal Cloud Foundry Performance Monitoring AppDynamics Enhances Pivotal Cloud Foundry Performance Monitoring with New Infrastructure View Implementation and End-to-End Workflows The following 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 For additional information, follow the steps outlined in these two resources: Installing and Configuring AppDynamics Using AppDynamics PCF KPI Dashboard The PCF KPI Dashboard visualizes the performance of the PCF platform on which your AppDynamics tile is running in one single view . For a deep dive on all of the dashboard’s monitored PCF performance metrics, see AppDynamics PCF KPI Dashboard . Transaction Analytics If you are on version 4.4.337+ and have an Analytics license, you can view transaction analytics in your AppDynamics Controller. Instructions on configuring tiles for analytics, binding applications to the Analytics Agent, configuring your Controller to fetch data from the Events Service and configuring the Analytics Controller on your Controller, visit Configuring Transaction Analytics . Release Notes To stay up-to-date on the latest functionality in the AppDynamics/PCF integration, check out the Release Notes regularly. 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. FAQs and Troubleshooting The FAQs page includes troubleshooting tips and answers to common questions about the AppDynamics tile, Service Broker and Buildpacks, Machine agents, PCF Dashboard, and other topics. 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 [Webinar] Monitoring Pivotal Cloud Foundry Applications and Infrastructure .

steve.hetland · ‎10-02-2015

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:

steve.hetland · ‎06-25-2015

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.

Date Registered	‎11-05-2013 05:48 PM
Date Last Visited	‎07-10-2018 05:47 PM
Total Messages Posted	18
Total Kudos Received	3

Discussion Feed

Re: No Load Detected for the Java Agent

Re: Renaming Nodes

Re: Universal agent Controller rulebook

Re: NUMBER_OF_TRIGGERED_CONDITIONS_PER_EVALUATION_...

Where can I find information on the AppDynamics in...

Business Transaction Match Rules for ICEfaces JSF

SharePoint Instrumentation ConfigurationChannel Ex...