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

Where can I find information on AppDynamics’ integration with VMware Tanzu (formerly PCF)? The AppDynamics integration with VMware Tanzu Application Service (formerly Pivotal Cloud Foundry or PCF) lets you easily deploy AppDynamics-monitored applications on the VMware Tanzu platform, and gather performance and infrastructure metrics. Two distinct tiles are at the center of the AppDynamics integration with VMware Tanzu: Application Monitoring for VMware Tanzu and Platform Monitoring for VMware Tanzu. 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 VMware Tanzu platform and correlate it with business data in real time. Contents Integration tiles AppDynamics Application Monitoring for VMware Tanzu AppDynamics Platform Monitoring for VMware Tanzu Resources Installation and end-to-end workflows Release Notes and FAQs Recommended reading Hands-on training: recorded webinars The integration tiles AppDynamics Application Monitoring for VMware Tanzu For performance monitoring of applications running on Cloud Foundry: APM is provided through AppDynamics support inside the standard Cloud Foundry buildpacks and Service Broker deployed through the tile An Extension Buildpack is provided to help instrument Java and .NET HWC applications For detailed information on the integration and Application Monitoring for VMware Tanzu, visit these resources: AppDynamics Application Performance Monitoring for VMWare Tanzu AppDynamics Service Broker AppDynamics Extension Buildpack How it works To simplify APM setup, this tile delivers a service broker to support an AppDynamics marketplace service. The Controller parameters are configured in the tile and automatically published to the marketplace when the tile is installed. AppDynamics Platform Monitoring for VMware Tanzu Used 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 VMware Tanzu, visit the resources linked below: Download AppDynamics Platform Monitoring for VMware Tanzu AppDynamics Platform Monitoring for VMWare Tanzu NOTE | Prior to v4.5.460, Application and Platform metrics were managed as one tile. Starting with 4.5.460, Platform Metrics are managed by a separate tile. How it works Quick to install with minimal configuration and memory usage, the Platform Monitoring for VMware Tanzu 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. For a deep dive on the monitored performance metrics and instructions on how to use the Dashboard Generator and enable health rules, see AppDynamics KPI Dashboard in the Pivotal documentation. To take advantage of this tile, you’ll need a Go SDK AppDynamics license. Back to Contents Resources Installation and end-to-end workflows VMware Tanzu integration tile Installation and configuration resources Application Monitoring Follow the steps outlined in the resources below to install and configure Application Monitoring (APM): Installing and Configuring AppDynamics Using AppDynamics This page provides more information on end-to-end workflows using sample Java, .NET, Python, and PHP applications, AppDynamics Application Performance Monitoring for VMware Tanzu Workflow Platform Monitoring The pages linked below detail the process for installing and configuring Platform Monitoring for PCF. Installing and Configuring AppDynamics Platform Monitoring Overriding Default Configurations NOTE | 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. Back to Contents Release Notes and FAQs To stay up-to-date on the latest functionality in the AppDynamics/VMware Tanzu integration tiles, see the following Release Notes, as well as FAQs about using AppDynamics with Pivotal VMWare Tanzu in the Pivotal documentation: VMware Tanzu integration tile Release Notes and FAQ resources Application Monitoring Release Notes for AppDynamics Application Performance Monitoring for VMware Tanzu tile See AppDynamics VMware Tanzu Tile FAQs for troubleshooting tips and answers to common questions about the AppDynamics tile, Service Broker and buildpacks, and other topics. Platform Monitoring Release Notes for AppDynamics Platform Monitoring for VMware Tanzu The AppDynamics Platform Metrics for VMware Tanzu FAQs addresses questions about the Platform tile, SSL configuration, Dashboards, and more. Back to Contents Recommended Reading For overviews of VMwareApplication Performance and platform monitoring, examples of how the Buildpack and Service Broker work, an outline of the Extension Buildpack, and a list of 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 Back to Contents Hands-on training: recorded webinars Here on Community, we host the following AppDynamics webinar recordings (original airdates 2018) about using Pivotal integration. Webinar: Technical Session and contents Monitoring Pivotal Cloud Foundry Applications and Infrastructure Learn how to monitor polyglot distributed applications deployed to VMware Tanzu in this hands-on training geared towards operations teams and developers. Guidance through the complete application lifecycle, including: 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 VMware Tanzuand BOSH infrastructure health and availability using the new monitoring integration recently introduced for Pivotal 2.x Included with the recording, read a transcript of the Q&A, and access additional resources. AppD and PCF Updates on .NET Core, Platform Monitoring for Multiple Foundations, Multi-Buildpacks and More This session covers: Our multi-buildpack support, plus a demo of how to deploy and monitor .NET Agent for Linux using the multi-buildpack extension  Show the multi-foundation platform monitoring tools that are part of our loggregator integration  Back to Contents

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:

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_...

AppDynamics integration with VMWare Tanzu: What do...

How do I create Business Transaction Match Rules f...