All TKB Articles in Learn Splunk

Learn Splunk

All TKB Articles in Learn Splunk

WATCH THIS PAGE FOR UPDATES — Click the caret menu above right, then Subscribe... Want notification of new monthly Product Update editions? Click this link, then click Subscribe on the message bar ... See more...
WATCH THIS PAGE FOR UPDATES — Click the caret menu above right, then Subscribe... Want notification of new monthly Product Update editions? Click this link, then click Subscribe on the message bar In September, releases included the 22.9 versions of AppDynamics SaaS Controller, AppDynamics Cloud, and the Account Management Portal. In this article…  What release highlights should I know about? Heads Up - What else should I know about? Resolved and known issues Essentials What’s new in this month’s feature enhancements? What’s new? The following release highlights include the newest features and capabilities this month. Check out the table below to see who in your organization may be most interested in or impacted by each highlighted enhancement. PRODUCTS / ENHANCEMENT HIGHLIGHTS USER & PERFORMANCE ANALYST  ADMIN & IMPLEMENTER  DEV OPS  AppDynamics Cloud Anomaly detection test mode  ✓ ✓    Azure Disk and Azure LB support    ✓   K8s custom event for OOM-killed pods    ✓   Pre-defined health rules for K8s entities       UI for filtering is enhanced ✓ ✓ ✓ Agents Cluster Agent   ✓   Java Agent   ✓ ✓ Machine Agent   ✓   Private Synthetic Agent   ✓   SaaS Controller Dash Studio: Nested variables for tiers ✓ ✓   Synthetic API: GUI configuration ✓     Root cause analysis includes service instances   ✓    NOTE | Product enhancements are described in detail, and on an ongoing basis, on the respective documentation portals • AppDynamics (CSaaS) Release Notes  • AppDynamics Cloud Release Notes AppDynamics Cloud Highlights NOTE | See the complete AppDynamics Cloud Release Notes in our documentation portal. Anomaly detection configuration With the newly-released test mode in the Anomaly Detection API, you will be able to confirm that anomaly detection is working as expected before running it on services in production. In addition to enabling and disabling test mode, you will be able to use the API to observe test mode alerts. Anomaly Detection in AppDynamics Cloud (GA 22.9, Released September 23, 2022) Azure Disk and Azure LBs are now supported Azure services are now expanded to include both Azure Disk and Azure Load Balancers. NOTE | For your existing Azure Cloud Connections, you will need to edit the connection to enable Disk and/or Load Balancers. See Azure Disk Storage. (GA 22.9, Released September 23, 2022) K8s custom event for OOM-killed pods This Kubernetes custom event is generated on the pod entity, so you can more easily correlate which pods were killed due to being out of memory—for an improved troubleshooting experience. (GA 22.9, Released September 23, 2022) Pre-defined health rules for K8s entities More new predefined health rules for Kubernetes entities reduce your time to value and improve MTTI. Detect and prevent issues by proactively monitoring resource usage, whether enough pods are running, and error count. (GA 22.9, Released September 23, 2022) Root Cause Analysis now includes service instances Root cause analysis (RCA) has been extended to include service instances, guiding you to the right data and therefore reducing troubleshooting time and MTTI. (GA 22.9, Released September 23, 2022) UI for filtering is enhanced Small changes to the filtering bar on both service and service instances pages contribute to greater ease of use when working with our query language. They are: Syntax highlighting Queries are now directly displayed in the drop-down view  Health status is now shown as an alias, rather than as a numerical value (GA 22.9, Released September 23, 2022) Agent Update Highlights NOTE | See the full 22.9 Release Notes for a complete, ongoing, sortable, and filterable list of Agent enhancements  Cluster Agent For AppDynamics Operator and Cluster Agent: Images have been upgraded to Go language version 1.19.  The Alpine docker image has been updated to 3.16.2 (GA v22.8 Released September 27, 2022) Java Agent Java Agent v.22.9 includes two new node properties:  Allows agent module export. See appagent-export-pagackes Disables dynamic services during the agent startup. See disable-dynamic-services In addition, dynamic services JAR signing is now enabled by default. See Dynamic Services JAR signing (GA v22.9 Released September 27, 2022) Machine Agent New option allows you to specify a custom JRE location for Machine Agent on Windows. Find out how to enable this feature here. Timestamps are now automatically added to the Machine Agent’s log4j configuration. See the Release Notes for a short listing of upgraded libraries. (GA v22.9 Released September 27, 2022) Private Synthetic Agent By eliminating the need for an external database (Postgres), Private Synthetic Agent v22.9 has a reduced infrastructure requirement. See Install the Private Synthetic Agent (Web and API Monitoring). (GA v22.9, Released September 3, 2022) SaaS Enhancement Highlights Dash Studio: nested variables for tiers Customers with a large number of applications have already been able to utilize application variables for re-use from one application to another. This update allows you to create tier variables so users only see those designated tiers in an application (rather than all the tiers). (GA v22.9 Released September 27, 2022) Synthetic API: GUI configuration Now, you can create a Synthetic API monitoring job through a simple, user-friendly UI. No development skills are needed. Debugging and fixing are also much easier.  (GA v22.9 Released September 12, 2022 To Table of Contents  |  To Resource List What else should you know? New self-paced Premium University courses are available In September, the AppDynamics University team released new self-paced courses for Premium University subscribers. Read the details here, Updates to the University Group here in Community Introducing AppDynamics University’s own blog, University Updates, located in the AppDynamics University Group. There, you’ll find announcements about new learning products from teacher-led to self-paced courses—as well as accreditation and learning plans. The Instructor edition of the Community Member Spotlight series has moved here too.   The University Group area has a new landing page banner you can use to find your way around the site faster. It includes links to the new University Updates blog, as well as the Ask a Question and Articles & FAQs areas.  TIP | As always with any Community content, you can subscribe to receive notifications by area, topic, or individual post. To Table of Contents  |  To Resource List Resolved issues Now, you can sort the complete Release Notes in AppDynamics documentation by any heading, including product, severity, version information, and release date. They are updated on an ongoing basis. The following key issue was resolved this month.  ANALYTICS 14514 - Make Funnel Watch Visibility version-dependent. LIC 3050 - Licensing producing negative maxDailyDocuments for Event Service. To Table of Contents  |  To Resource List Essentials PLEASE NOTE | Customers are advised to check backward compatibility in the Agent and Controller Compatibility documentation.  Download Essential Components (Agents, Enterprise Console, Controller (on-prem), Events Service, EUM Components) Download Additional Components (SDKs, Plugins, etc.) How do I get started upgrading my AppDynamics components for any release? Product Announcements, Alerts, and Hot Fixes Open Source Extensions License Entitlements and Restrictions Can’t find what you’re looking for? Need assistance? Reach out in the Community Forums! To Table of Contents
Back to TOC | To Essentials What else should you know? Back to TOC | To Essentials   Essentials ADVISORY | Customers are advised to check backward compatibility in the Agent and Control... See more...
Back to TOC | To Essentials What else should you know? Back to TOC | To Essentials   Essentials ADVISORY | Customers are advised to check backward compatibility in the Agent and Controller Compatibility documentation. Download Essential Components (Agents, Enterprise Console, Controller (on-prem), Events Service, EUM Components) Download Additional Components (SDKs, Plugins, etc.) How do I get started upgrading my AppDynamics components for any release? Product Announcements, Alerts, and Hot Fixes Open Source Extensions License Entitlements and Restrictions  
WATCH THIS PAGE FOR UPDATES — Click the caret menu above right, then Subscribe... Want notification of new monthly Product Update editions? Click this link, then click Subscribe on the message bar ... See more...
WATCH THIS PAGE FOR UPDATES — Click the caret menu above right, then Subscribe... Want notification of new monthly Product Update editions? Click this link, then click Subscribe on the message bar Revised 8/24/22 In July, AppDynamics Cloud v22.7.0 was released with key enhancements to a number of agents, Dash Studio, and Account Administration. In this article…  What’s new? This month’s feature enhancements Heads Up - What else should I know about? Resolved and known issues Get started… What’s new? This month’s feature enhancements These release highlights include the newest features and capabilities this month, at a glance. In the grid below, we’ve flagged who within your organization may be most interested or impacted for each enhancement.  PRODUCTS / ENHANCEMENTS USER & PERFORMANCE ANALYST  ADMIN & IMPLEMENTER  DEV OPS  AppDynamics Cloud Anomaly detection  ✓  ✓   Kubernetes event details page  ✓  ✓   Restrict data ingestion by tags  ✓  ✓   Tag filtering and grouping ✓ ✓   Agents Analytics Agent   ✓   C/C++ SDK Agent   ✓   Java Agent  ✓ ✓   Machine Agent   ✓   Node.js Agent   ✓   Python Agent   ✓   SaaS Controller Dash Studio ✓ ✓   Account Administration Create multiple users at a time   ✓   NOTE | Ongoing product enhancements are described in detail in the Release Notes on the documentation portal. You can sort and filter information by release date, version, product, or component right on the Release Notes page.   AppDynamics Cloud Highlights Revised 8/24/22 Anomaly detection Now also available within service instances, the anomaly detection algorithm has been updated to calculate baselines, which helps to reduce false alerts, and improved issue detection. View detected anomaly details to understand and assess health. (GA v22.7 Released July, 2022) Kubernetes event details page You can now drill down from the Events Summary to an Event Details page including timestamp, event messages, and affected entities. Apply filters to view a specific set of events, like severity, cluster, or time range. (GA v22.7 Released July, 2022) Restrict  data ingestion from cloud services Define granular restrictions on what data is ingested in AppDynamics Cloud with tag-based controls. Get only the data you want, with better utilization of AppDynamics licenses and fewer API calls to your cloud provider. (GA v22.7 Released July, 2022) Tag filtering and grouping Easily discover and organize data by grouping and filtering with tags. This feature improves troubleshooting efficiency by enabling you to filter group entities and their corresponding MELT data, as well as limiting health rule evaluation scope. (GA v22.7 Released July 28, 2022) For an overview of what's included in this feature, and how to use it, see Getting started with tags in AppDynamics Cloud. NOTE | See the complete AppDynamics Cloud Release Notes.  Agent Update Highlights NOTE | See the full 22.7 Release Notes for a complete, ongoing, sortable, and filterable list of Agent enhancements  Analytics Agent Updates to various transitive dependency libraries: Apache Groovy, Netty, Apache Fluent, Glassfish  (GA v22.7 Released July 26, 2022) C/C++ SDK Agent Users can mark business transactions started with this agent as a background task using the new appd_bt_begin_bg() function. (GA v22.7 Released July 6, 2022) Database Agent Support for installing the Database Agent on JDK versions 1.18-15.  (GA v22.7 Released July 28, 2022) Java Agent Support for JDK18, MongoDB Reactive Streams Driver 4.2 and 4.3, and Akka HTTP framework support for OpenTelemetry New option to configure the URL segment that the Agent sends to Analytics (GA v22.7 Released July 29, 2022) Machine Agent Tested and confirmed support on Windows 2022. See Release Notes for Supported Environments. Jetty-client and jetty-proxy libraries have been upgraded. (GA v22.7 Released July 26, 2022) Node.js Agent Support for Cisco Secure Application Vulnerability Reporting, as well as connection retries. See additional details on the Release Notes. LibAgent upgraded to version 22/7/0-2120 Support for container.id to resource metadata (GA v22.6 Released July 26, 2022) Python Agent Updated the Jackson Databind library to version 2.13.3 in order to prevent a StackOverflow exception and denial of service from occurring. (GA v22.7 Released July 19, 2022) SaaS Controller Enhancement Highlights Dash Studio Support was added for a browser application variable. (GA v22.7.0 Released July 25, 2022) Account Administration Highlights Company and License Administrators are now able to create multiple users at one time  (GA v22.7 Released July 10, 2022) NOTE | To view all technical documentation associated with this month’s releases, please visit Product Announcements, Alerts, and Hot Fixes in our documentation portal.  To Table of Contents  |  To Resource List What else should you know? Company Admins now have a simpler workflow when assigning University Subscription vouchers to pending users  This month, the AppDynamics University team has released a new enhancement to self-service voucher management tools in the Account Management Portal. Company Admins can now assign a University Subscription voucher to users who have not yet activated their AppDynamics account, and are still in a “Pending” status in the Portal. Read the details here. Updated Privacy Data Sheets for AppDynamics Cloud Our new Privacy Data Sheet for the AppDynamics Cloud product, is available on the Cisco Trust Portal. Customers can use it to help understand Personal Data usage of Personal Data in association with AppDynamics Cloud. TIP | Subscribe to the recent post in News & Announcements to receive notification of any updates and revisions To Table of Contents  |  To Resource List Resolved and known issues You can see a complete listing of this month’s Agent and Controller Resolved Issues, as well as additional detail around known issues in the Release Notes.  To Table of Contents  |  To Resource List Get Started PLEASE NOTE | Customers are advised to check backward compatibility in the Agent and Controller Compatibility documentation.  Download Essential Components (Agents, Enterprise Console, Controller (on-prem), Events Service, EUM Components) Download Additional Components (SDKs, Plugins, etc.) How do I get started upgrading my AppDynamics components for any release? Product Announcements, Alerts, and Hot Fixes Open Source Extensions License Entitlements and Restrictions Can’t find what you’re looking for? Need assistance? Connect in the Community Discussions forums! To Table of Contents
WATCH THIS PAGE FOR UPDATES — Click the caret menu above right, then Subscribe Want a notification of new monthly Product Update editions? Click this link, then Subscribe on the message bar In Jun... See more...
WATCH THIS PAGE FOR UPDATES — Click the caret menu above right, then Subscribe Want a notification of new monthly Product Update editions? Click this link, then Subscribe on the message bar In June, the AppDynamics SaaS Controller v22.6.0 was released with key product enhancements, as well as a number of agent enhancements. AppDynamics Cloud, our new purpose-built, cloud-native monitoring product was released on June 28, 2022. The AppDynamics Accounts portal now includes the ability to use single sign-on access for all account management activities without the need to re-enter passwords. In this article... Feature Enhancements Heads Up - What Else You Should Know Resolved and Known Issues Get Started What release highlights should I know about? These release highlights include the newest features and capabilities this month, at a glance. In the grid below, we’ve flagged who within your organization may be most interested or impacted for each enhancement.  CATEGORY ENHANCEMENT USER and PERFORMANCE ANALYST ADMIN and IMPLEMENTER  DEVELOPER FULL-STACK OBSERVABILITY AppDynamics Cloud ✓  ✓   AGENT UPDATES Cluster Agent   ✓   Database Agent ✓     Flutter Agent    ✓   Java Agent   ✓ ✓ Javascript Agent ✓ ✓   Machine Agent   ✓   .NET Agent ✓ ✓   Private Synthetic Agent   ✓   SAAS CONTROLLER Experience Journey Map ✓     Account Management ✓ ✓   Full-Stack Observability AppDynamics Cloud AppDynamics Cloud is our brand new, purpose-built, cloud-native monitoring product. It provides full-stack observability for large, managed Kubernetes deployments on public clouds, with support for account and user onboarding, cloud onboarding, infrastructure onboarding, and installation of OpenTelemetry-compatible agents to instrument your microservices.  Providing observability across all of your domains without requiring you to switch from tab to tab, ApDynamics Cloud delivers a cohesive at-a-glance health analysis across your entire cloud native stack. See the release notes describing enhancements and new features for this release of AppDynamics Cloud, and the AppDynamics Cloud launches at Cisco Live announcement for an overview of its impact to the technology community. (GA v22.6 Released June 28, 2022) Agent Updates Cluster Agent You can now deploy more than 100 pods during instrumentation using the instrumentationMaxPollingAttempts argument. Please refer to the Configure the Cluster Agent documentation for more details.  Additionally, the Cluster Agent and Operator images have been upgraded to version 1.17.11. (GA v22.6 Released June 21, 2022) Database Agent CPU core counts in the RDS instances are now supported when hardware monitoring is enabled, which applies to MySQL and Postgres databases. Please see Configure the Database Agent to Monitor Server Hardware. (v22.6.0 Released June 13, 2022)   Flutter Agent This release includes a bug fix regarding running the plugin on iOS 12.4 simulators. (v22.6.0 Released June 7, 2022) Java Agent JavaAgent v22.6 includes support for AWS SQS SDK for JAVA 2.x. See Amazon Simple Queue Service Backends.  It also includes the option to configure the transaction stall threshold. See the min-transaction-stall-threshold-in-seconds node property. (v22.6.0 Released June 28, 2022) JavaScript Agent There have been updates in the way Visually Complete Time (VCT) and Page Complete Time (PCT) metrics are calculated through SVGUseElement. Additionally, there is a new API function call for creating custom names for pre-existing SPA2 virtual pages. See Set Custom Virtual Page Names for more details on that. (v22.6.0 Released June 15, 2022)   Machine Agent In release 22.6.0: Machine Agent 22.6.0 is tested and confirmed to be supported on Red Hat Enterprise Linux (RHEL) 9 and Windows 2012. See Tested Platforms. The dropwizard-jetty library has been upgraded to 2.0.22 2.0.29 PLEASE NOTE | AppDynamics recommends using Machine Agent 22.2.0 for AIX OS As of this release, the Machine Agent installation link was removed from the Getting Started Wizard. To download the Machine Agent, visit https://accounts.appdynamics.com/downloads  and see Install the Machine Agent.   .NET Agent This .NET Agent release includes integration of the OpenTelemetry SDK: See Enable OpenTelemetry in the .NET Agent, enabling the enable_tls12 configuration for the .NET Machine Agent, and other fixes and adjustments. See the Release Notes for details. (v22.6.0 Released June 30, 2022)   Private Synthetic Agent This release includes new proxy server configurations for the Agent and Heimdall. See Configure Web Monitoring PSA and API Monitoring PSA. (v22.6.0 Released June 28, 2022)   SaaS Controller Experience Journey Map The 22.6 Controller release includes new custom labels being available which can be used to rename end-user events in user journeys. Additionally, Mobile Sessions are no longer created from connection transitions or network request end-user events. (v22.6.0 Released June 23, 2022) Account Management The Accounts Management portal now allows users to use single sign-on for all activities, enabling all AppDynamics IdP-managed users to access all authorized AppDynamics products and services from any entry point and navigate to any other service or Controller Tenant without entering their password again. This enhancement includes a slight change to the sign-in screen For more information please see Configure Single Sign-on through SAML. (v22.6.0 Released June 1, 2022) NOTE | To view all technical documentation associated with this month’s releases, please visit Product Announcements, Alerts, and Hot Fixes in our documentation portal.  To Table of Contents  |  To Resource List What else you should know  Did you notice the new Community look? Your Community Team is thrilled to unveil the site redesign we’ve been working on. We hope you find the modernized new style more usable. And this is just the beginning, with substantive additional enhancements planned, ongoing.  How is it working for you? What else would you like to see? Please let us know what you think! The current changes include new announcement tiles that link to current topics on the Community’s homepage. There are also updates to the Discussion Forums, as well as reorganized settings (Community Profile, Notifications, and Private Messages). You can find details in this short post: What do you think of our new AppDynamics Community look? AppDynamics University streamlined Learning Plans Throughout the month, University has been streamlining some learning plans included in the Learning Recognition Program, so customers will have a more straightforward path to gain recognition for their learning.  See the full details of what has changed in the Changes to our Learning Plans post here in Community. Also see all the most recent University posts in News and Announcements. Enhancements to University subscription voucher self-service tools The University team has been diligently building additional self-service tools for customers to manage your University subscriptions. Learn about the latest enhancements and what’s to come in our Community post. To Table of Contents  |  To Resource List Resolved and known issues The following key issues were resolved this month. You can see a complete listing of this month’s Agent and Controller Resolved Issues, as well as additional detail around known issues in the Release Notes.  Database Monitoring | In the Databases, Events view doesn't show expected results (DBMON-8621) To Table of Contents  |  To Resource List Get Started PLEASE NOTE | customers are advised to check backward compatibility in the Agent and Controller Compatibility documentation.  Download Essential Components (Agents, Enterprise Console, Controller (on-prem), Events Service, EUM Components) Download Additional Components (SDKs, Plugins, etc.) How do I get started upgrading my AppDynamics components for any release? Product Announcements, Alerts, and Hot Fixes Open Source Extensions License Entitlements and Restrictions Can’t find what you’re looking for? Need assistance? Connect in the Community Discussions forums! To Table of Contents
AppDynamics Identity Provider users get a seamless SSO experience across AppDynamics products and services Beginning with v22.6.0, users authenticated by the global AppDynamics Identity Provider ... See more...
AppDynamics Identity Provider users get a seamless SSO experience across AppDynamics products and services Beginning with v22.6.0, users authenticated by the global AppDynamics Identity Provider (AppD IDP) will only need to sign in to an authorized AppDynamics product or service once. Now, these users will only need to sign in to AppDynamics once. As they navigate from one to another of their authorized AppDynamics products and services, they will not be asked for their password again. NOTE | This change does not affect current Controller local, SAML, and LDAP users, who can continue to sign in as they always have, without disrupting their access. On the horizon… Though this feature is currently only available for users added since v21.11, the ability to convert an existing (pre-v21.11) user account to the new SSO-enabled AppDynamics managed user identity is planned for later in 2022. Be on the lookout for an announcement describing this conversion in the future. In this article…   Frequently asked questions   Getting started with AppDynamics SSO How do I sign in so I can see and navigate to my AppDynamics products and services? Where is the password field in the sign-in screen? Why do I have to enter my username twice? Can I change my local Controller account if I am not currently a global AppDID User? What if an AppD IDP account is used for a service account API authentication on a Controller?   How do I know… What is the AppD IDP and how do I know whether I’m using it? How can I tell whether or not I’m an AppDynamics Identity Provider user?   Questions from Admins As an admin, can I set these users to be authenticated my IDP in the Account Management Portal? As an admin, how do I give users access to a Controller tenant?   Additional resources Frequently asked questions Getting started with AppDynamics SSO How do I sign in so I can see and navigate to my AppDynamics products and services? AppDynamics IDP users can use the following steps to view and navigate to their AppDynamics products and services: Navigate to https://accounts.appdynamics.com/personal-profile  Sign in as usual from any AppDynamics product or service: Starting from your Controller account Enter your account name Enter your username (which is your email address) Click Next The system will recognize you as an AppD IDP user and redirect you to the AppD IDP for authentication.  Enter your username again and click Next. Enter your password and click Sign in. You will land in the Controller signed in. Starting from any accounts service (like University or Community) Click Sign in Enter your username (which is your email address) Click Next Enter your password and click Sign in. Once signed in, you will see your target experience.  From the mini-profile (look for your username in the top of the screen), choose “Manage my Profile” or access this link. From here you can see any AppDynamics Controllers to which your profile is associated, as well as all related services (i.e., AppD University, Community, Documentation, Support) Each time you click a Controller or service from your personal profile, it will open in an active (already authenticated) new tab. Where is the password field in the sign-in screen? The password field appears once you enter the username and click next. It may either appear on the same screen, or once you are redirected to your “global” sign-in page. Why do I have to enter my username twice? You need to enter your username twice when first signing in due to our use of a global identity provider. TIPS | Use the “Remember me” functions to further streamline all your future logins.  Alternatively, sign in to your personal profile page first. It will show you everything you have access to and provide direct access links. Can I change my local Controller account if I am not currently a global AppDID User? We are working on a migration to AppD IDP user capability that will upgrade your existing Controller account to AppD IDP. It is on the roadmap for later this year. What if an AppD IDP account is used for a service account API authentication on a Controller? You can expect successful authentications when an AppD IDP account is used for a service account AppD IDP authentication on a Controller. The service account can be authenticated without the SSO flow. That said, we recommend that customers move to our OAUTH-based API clients for this process , wherever possible, to improve security. See the documentation for this feature here. Back to TOC How do I know… What is the AppD IDP and how do I know whether I’m using it? AppD IDP stands for “AppDynamics Identity Provider”. Until now, each Controller has served as its own identity provider. From this point forward, we are moving that function to the AppD IDP, a global AppDynamics Identity Provider.   If you have chosen SAML or LDAP as your authentication provider in the Controller tenant authentication provider settings tab, then you are not using the new AppD IDP for user identity management, but instead are using your own provider. If your Controller tenant has “AppDynamics” selected in the Controller tenant authentication provider tab, then users created since v21.11  are using the AppD IDP for user identity management.  How can I tell whether or not I’m an AppDynamics Identity Provider user? If your account was created between now and v21.11, and your email address is your username, then you are an AppDynamics Identity Provider user.   You can confirm this by logging into your personal profile at https://accounts.appdynamics.com/personal-profile. If the Assigned Controller Tenants sections lists the Controllers you use, you are an AppDynamics Identity Provider user. Legacy local AppDynamics user accounts are those created before v.21.11 that do not use email as their username. NOTE | As with Controller based SAML and LDAP users, current pre-v21.11 legacy local users can continue to sign in as they always have, without a disruption to their access. Back to TOC Questions from Admins As an admin, can I set these users to be authenticated my IDP in the Account Management Portal? Yes! This is like any other AppDIDP-managed user except that when they sign in, they will be redirected to the customer IDP. Just add the user using their email address to the Controller account.  As an admin, how do I give users access to a Controller tenant? The user must be added from the Controller users page, using their email address. If a user’s email exists in the AppD IDP, that account will be used for SSO features. NOTE | Users cannot be given access to a Controller tenant from the Accounts Management Portal at this time. Back to TOC   Additional Resources You may find the following AppDynamics Documentation resources useful: Create AppD IDP User API OpenAuthorization Mechanisms  SAML Federation AppDynamics API Clients Also related to this topic are the following Knowledge Base articles: Access to AppDynamics University is easier than ever Changes to user creation and password policy  AppDynamics Global Identity Migration Experience FAQ
Use this technical support tool to collect information for troubleshooting Support Report is a technical support tool AppDynamics customers and Support Engineers can use to collect and archive the ... See more...
Use this technical support tool to collect information for troubleshooting Support Report is a technical support tool AppDynamics customers and Support Engineers can use to collect and archive the information needed to correctly identify technical issues.  This article explains the tool, and its configuration and use. In this article... What is Support Report? How do I configure and run Support Report? What happens once a report is generated? Additional Resources What is Support Report? Support Report is a technical support tool that facilitates the process of collecting and archiving data, for AppDynamics customers and Support Engineers alike. It gathers general operating system information vital for correctly identifying issues—including hardware-specific information, logs, and configuration—both from the AppDynamics On-prem components (such as Controller, Enterprise Console, EUM, Events Service) and from across the operating system.  Prerequisites Support Report works on most Linux flavors. It needs only Bash Unix shell, which is available on every Linux. It is designed to not crash even when a fundamental tool is unavailable. Though the script can be run by either the regular user or by root, the tool will only be able to collect all information and logs when it is running by root. That said, it will not crash or give up when running as a regular user. All of the above make dependencies and requirements very low, allowing it to work accurately on any machine.  How it works The tool is made from a Bash script and tries to gather information about the system from generally available places and basic system tools. If a particular tool is not present in the customer's environment, this script will keep working, simply informing that the tool is not there. The script is meant to detect Linux flavor, adjusting all needed paths and behaviors accordingly. If, as strongly recommended, the customer provides a password to the MySQL database, the tool will connect to it and gather information from the database as well. The tool does not collect any customer metrics or other sensitive information from the database.  Since AppDynamics applications can be installed freely in any directory on a server, and support_report is not an official part of the AppD package, the tool needs to correctly detect where actually files of interest are located. It is quite easy to tell when the Controller process is running. But this tool troubleshoots based on the more difficult scenario of no running AppD processes. It looks for the correct path by "brute force", by finding specific files on the server. How do I run the Support Report? The Support Report tool can be attached to the Zendesk support ticket by an AppDynamics Engineer, or it can be downloaded from this article (see below). After it is uploaded (by SCP, or in any other way convenient for the customer) to a server where troubleshooting needs to be performed, the tool can be run from any directory. Use the controls to pick the specific information you’d like to collect—and to disable the information you DON’T want to share. Below is a sample run with ‘-help’ option , where all available parameters are described. $ ./support-report.sh -help Usage: support-report.sh [ -CEUScpHlazeoxv ] [ -d days of logs ] [ -o dir ] -C Collect information about Controller -E Collect information about Enterprise Console -U Collect information about EUM server -S Collect information about Events Service -c Disable generating system configuration -p Enable measuring system load/performance. It will be 720 of 5s samples. 1h in total. -H Disable generating hardware report -l Disable gathering system logs -a Disable gathering AppD logs -d Number of days back of logs to retrieve (default is 3 days) -z Do not zip report and leave it in /tmp -e Encrypt output report archive with password -o Set the support-report output path -x Keep the support-report logs in /tmp for debugging -v Version What happens once a report is generated? Once a report is generated, the entire report archive is stored in a location related to AppDynamics component, on the customer’s server. The customer can easily review the report’s information before sending it to technical support. Example output from  the tool: root@appd-ha1:~# ./support-report.sh Determining system environment and configuration... Provide controller MySQL root user password: Provide Controller root user password (hit enter to skip): Generating report... Building system configuration Building package list Checking hypervisor Getting EC2 instance info Copying hardware profile Memory information Storage information Copying system logs..Done! Getting systemd info Networking information Init info Checking time config Checking AppD environment Numa stats Fetching install user environment Get processes. Done! Collecting TOP output Creating Appdynamics files list Getting selinux config Controller logs Collecting rotating logs from 3 days Mysql Controller logs Controller configs Controller Keystore content Collecting Controller SQL queries Controller related information Controller report HA and DB replication status Creating report archive... Done The support-report has been saved to: /appdynamics/platform/product/controller/logs/support-report/support-report_controller_appd-ha1.conserit.pl_2022-05-20_00-15-22.tar.gz You will be directed where to submit this report by your technical support contact. The tool's report output can be attached to a Zendesk support ticket proactively by the customer. It will greatly speed up the troubleshooting process, as very likely all the needed information to help - will already be present in the initial Zendesk message! Additional Resources How do I submit a Support ticket? An FAQ A guide to AppDynamics Help resources
Watch this page for updates — click the caret menu above right, then Subscribe Want to receive all monthly Product Updates? Click this link, then the Subscribe link on the message bar In May, the ... See more...
Watch this page for updates — click the caret menu above right, then Subscribe Want to receive all monthly Product Updates? Click this link, then the Subscribe link on the message bar In May, the AppDynamics SaaS Controller v22.5.0 was released with key product enhancements. There have also been a number of agent enhancements.  Additionally, the latest AppDynamics for SAP release, 22.5.0, is available on the download site. In this article... Feature Enhancements Heads Up - What Else You Should Know Resolved and Known Issues Get Started Ask a Question What release highlights should I know about? These release highlights include the newest features and capabilities this month, at a glance. In the grid below, we’ve flagged who within your organization may be most interested or impacted for each enhancement.  CATEGORY ENHANCEMENT USER and PERFORMANCE ANALYST ADMIN and IMPLEMENTER  DEVELOPER AGENT UPDATES Agent Installer (ZFI)   ✓   Java Agent   ✓   Machine Agent ✓ ✓   .NET Agent   ✓   Node.js Agent   ✓   Python Agent   ✓   Private Synthetic Agent   ✓   React Native Agent   ✓   SAP ABAP Agent ✓ ✓   SAAS CONTROLLER Mobile Real User Monitoring ✓ ✓   Synthetic Monitoring ✓ ✓ ✓ Database Monitoring ✓     Agent Updates Agent Installer A new custom tier naming rule in the Agent Installer provides the capability to create tier names based on rules using server types, environments, variables, or conditions. Highlights include:  Built-in and simplified Rego capabilities  Exporting and importing of existing sets of rules  Setting rule priorities and precedence  Rule definition preview and troubleshooting For more information, see the Manage Tier Naming Rules documentation.  Java Agent The latest Java Agent now includes a number of new node properties. Please see the Agent Node Property References documentation for details. The new node properties are: (v22.5.0 Released May 26, 2022) custom-activity-correlation custom-interceptor-rules sensitive-data-filter sensitive-message-filter sensitive-url-filter Machine Agent The Machine Agent has some minor bug fixes and several upgrades to various operating systems’ JRE libraries. In addition, the Oshi library, a 3rd party library, has been updated to 6.1.6. (v22.5.0 Released May 26, 2022) .NET Agent There are various updates to the latest .NET Agent, and in addition, ends support for .NET Frameworks 4.5.2, 4.6, 4.6.1, and .NET 5. See .NET Supported Environments. Implements the agent side of supported controller features for .NET.  Adds support for grammar in agent configuration. See Use Grammars to Configure the .NET Agent. Adds support for MS SQL Client instrumentation from the nuget package Microsoft.Data.SqlClient.  Improves the reflection for HTTP response types, assembly metadata validation for loaded types, type equality operations, and usage of lock objects.  (v22.5.0 Released May 25, 2022) Node.js Agent The Node.js Agent includes updates for common environment variables to configure the Node.js Agent. (v22.5.0 Released May 11, 2022) Private Synthetic Agent The Private Synthetic Agent now supports proxy configurations using environmental variables. (v22.5.0 Released May 5, 2022) Python Agent The latest Python Agent contains a bug fix (v22.5.0 Released May 26, 2022) React Native Agent The React Native Agent includes minor fixes and optimizations. (v22.5.0 Released May 17, 2022) SAP ABAP Agent The SAP 22.5.0 release is SAP Certified having also passed internal security compliance checks and includes: Support for Expert Settings UI giving deeper customization to the ABAP Agent Exit calls can be switched to Limited mode Per server event service connection check New collector for SAP table lock monitoring (SM12), and more.  Please also note that Datavard Insights will soon be renamed to SNP CrystalBridge Monitoring. (v22.5.0 Released May 30, 2022) NOTE | To view all technical documentation associated with this month’s releases, please visit Product Announcements, Alerts, and Hot Fixes in our documentation portal.  To Table of Contents  |  To Resource List Heads up - What else you should know  Webinar | Cut the chaos with AppDynamics full-stack observability Enter the world of full-stack observability, through a live demonstration, and gain insight on how to understand the connection between your app's health, your user satisfaction and business results. Join Paul Wright to deep dive into how AppDynamics can help you further your digital transformation.  Register to view it here Support Advisories You should be aware of two support advisory notifications that have come out in May. Support Advisory: .NET Agent End of Support for .NET 5 - The .NET Agent no longer supports .NET 5 due to Microsoft having ending support.  Support Advisory: End of Support for the PDX/Oregon SaaS EUM Collector Static IP Range The latest Java Agent has removed support for the End of Life JDK 6 and JDK 7. See Java Supported Environments documentation. New AppDynamics University courses Check out the latest installment of our instructor interview series. Also, see the most recent education product updates or access these new instructor-led and short-form courses directly on AppDynamics University. Or read about them in recent News and Announcements posts. To Table of Contents  |  To Resource List Resolved and known issues The following key issues were resolved this month. You can see a complete listing of this month’s Agent and Controller Resolved Issues, as well as additional detail around known issues in the Release Notes.  Controller | Cut down the size of packet from Controller response to the agent by decreasing the frequency of sending EUM configuration. EUMPLAT-2932 Services | PDX EUM data drop due to the ELB outage. EUMPLAT-3211 UI Controller | License Summary drill down page is not sending a dateFrom and dateTo query params in usage request. LIC-2431 You can see a complete listing of this month’s Agent and Controller Resolved Issues, as well as additional detail around known issues in the Release Notes.  To Table of Contents  |  To Resource List Get Started PLEASE NOTE: customers are advised to check backward compatibility in the Agent and Controller Compatibility documentation.  Download Essential Components (Agents, Enterprise Console, Controller (on-prem), Events Service, EUM Components) Download Additional Components (SDKs, Plugins, etc.) How do I get started upgrading my AppDynamics components for any release? Product Announcements, Alerts, and Hot Fixes Open Source Extensions License Entitlements and Restrictions Can’t find what you’re looking for? Need more assistance? Connect in the Community Feedbsck forum To Table of Contents
Synthetic monitoring APIs introduced in v22.5, their prerequisites, and use cases to make the most of them   As of May 2022, AppDynamics Synthetic monitoring features can now be accessed using RE... See more...
Synthetic monitoring APIs introduced in v22.5, their prerequisites, and use cases to make the most of them   As of May 2022, AppDynamics Synthetic monitoring features can now be accessed using REST APIs. This article lists these new APIs, as well as a selection of use cases. In this article... New Synthetic monitoring APIs Overview: Use cases with the new Synthetic monitoring APIs Integrate Synthetic jobs with code repositories  Integrate a synthetic script from a code repository  Use Synthetic monitoring APIs to manage code centrally  Implement use cases  Integrate synthetic jobs with CI/CD pipeline  Implement use case  Additional Resources New Synthetic monitoring APIs WEB MONITORING Create Synthetic Web Monitoring Job Create Multiple Synthetic Web Monitoring Jobs Update Synthetic Web Monitoring Job Get Synthetic Web Monitoring Job Configuration Data Get All Synthetic Web Monitoring Jobs Get Synthetic Web Monitoring Job Execution Status API MONITORING Create Synthetic API Monitoring Job Create Multiple Synthetic API Monitoring Jobs Update Synthetic API Monitoring Job Get Synthetic API Monitoring Job Configuration Data Get All Synthetic API Monitoring Jobs Get Synthetic API Monitoring Job Execution Status Use cases with the new Synthetic monitoring APIs Using these REST APIs, customers can implement new use cases and scenarios that are not otherwise supported within the AppDynamics Controller UI. Following are a few of the new use cases that can be implemented using the Synthetic monitoring APIs Integrate Synthetic jobs with code repositories Integrate Synthetic jobs with CI/CD pipeline Execute Synthetic jobs in multiple environments - Test, Pre-prod, Production Apart from these use cases, Synthetic monitoring APIs can be used to implement these features: Manage the Synthetic jobs from code repositories/central location Manage the Synthetic jobs using APIs without logging into AppDynamics Controller Bulk creation and management of Synthetic jobs Schedule maintenance window Analyze license consumption by job/app/collection Let's explore in detail how these new use cases can be implemented. Back to Top Integrate Synthetic jobs with code repositories Scenario 1 | Integrate a synthetic script from a code repository Synthetic web monitoring scripts are created using any 3rd-party script recorder, or by writing Python-based selenium scripts. After creating the scripts, they are stored in code repositories. From there, the scripts are copied and pasted into AppDynamics job editor for creating Synthetic monitoring jobs.  When these synthetic web monitoring scripts need updating, modification, or debugging, they are copied from AppDynamics jobs editor and pasted into a Python IDE for updating or debugging scripts. It is hard to maintain the same code base in both the code repository and the AppDynamics jobs editor because of this repeated copy/pasting. With Synthetic monitoring APIs, the scripts in the code repositories can be integrated with the Synthetic monitoring jobs in AppDynamics, thereby avoiding multiple copies and versions of each script. Any changes required in a script can be updated in the code repository, and then updated in the AppDynamics jobs using the Synthetic monitoring APIs. Scenario 2 | Use synthetic monitoring APIs to manage code centrally A Synthetic monitoring application can have multiple jobs. Job configurations (such as browsers, locations, execution schedule, execution frequency, etc.) are configured for each job during job creation.  Making configuration changes to these job configurations across all the jobs in an application is not possible from the AppDynamics Controller. There, since the configurations can only be changed for a single job at time, it is difficult to manage the (jobs) configuration when the application has several jobs. Instead of managing job configurations at the job level in AppDynamics Controller UI, the configuration can be stored and managed centrally from a code repository using Synthetic monitoring APIs. Back to Top   How can I implement either use case? Let's explore in detail how these scenarios can be implemented: Prerequisites, Create a job Prerequisites to integrating Synthetic jobs with code repositories Synthetic monitoring jobs scripts are stored in code repository Job configurations are stored in a JSON file in the code repository Job configuration is the list of all the parameters required for creating a job. The script used in the job could be part of the jobs configuration, or it could be stored in a separate file and referenced in the job configuration. Each job should have the job configuration data. Job configuration of each job could be stored in separate files, or  The job configurations of all the jobs in the application could be stored in a single JSON file. Create a job using the following execution steps This job must be triggered whenever there is a commit in the code repository where the jobs scripts and jobs configurations are stored. Check whether any job needs to be created Get the job configurations data from the code repository Check whether each job configuration has a job ID NOTE | All jobs created in AppDynamics will have a job ID Create job  If any job configuration in code repository does not have a job ID: Create a new job in AppDynamics using Create Synthetic job API or create multiple jobs APIs Update the job id received in the response from create API in the jobs  configuration in code repository Check whether any jobs need to be updated If job ID exists for any job, check to see if it needs to be updated: Use the Get Synthetic job configuration data API to fetch the the jobs configuration from AppDynamics  Compare all parameters of the job configuration in Appdynamics with the corresponding parameters in the job configuration in code repository Update job If the job configuration of a job in the code repository does not match the same job's job configuration  in AppDynamics, update the Synthetic job in AppDynamics using update Synthetic job API. Back to Top   Integrate Synthetic jobs with CI/CD pipeline Whenever a new code is deployed in the production, DevOps Engineers want to ensure that the application is available and performant. If the newly deployed code has any availability or performance issues, DevOps might want to roll back or pause the deployment. Using Synthetic monitoring APIs, DevOps Engineers can monitor the availability and performance of the application or microservices as part of the deployment pipeline. Based on the Synthetic monitoring availability and performance data gathered as part of the deployment pipeline, a DevOps Engineer can automate deployment decisions such as continuing, pausing, or rolling back the deployment, etc.  How can I implement this use case? Let's explore how this use case can be implemented. Prerequisites for integrating Synthetic jobs with CI/CD pipeline Synthetic monitoring jobs are available for the application or microservices. CI/CD pipelines are available for the deployment of the application or the microservice. Create a job with the following execution steps The job must be triggered after the successful deployment of the application or microservice. Start the Synthetic monitoring jobs using the Update Synthetic monitoring jobs API. To start the Synthetic monitoring job, set the value of "userEnabled" parameter in the job configuration “true”. Monitor the availability and performance of the jobs using Get job status API. Get the job status every minute or based on the frequency of the job execution. Deployment decision/action based on Synthetic monitoring jobs status. Availability issue and  job status Deployment actions Availability issue with job status Failed Roll back the deployment Create alerts, PD or Zendesk ticket  Availability issue with job status Warning Pause further deployment Create alerts, PD or Zendesk ticket Application available with job status OK for a specific duration Continue the deployment or complete the deployment process/steps.   After completing the deployment, stop the Synthetic monitoring using Update Synthetic monitoring jobs API. Set the value of the "userEnabled" parameter in the job configuration to “false” to stop the Synthetic monitoring job. Back to Top Additional Resources In the Documentation Portal Synthetic Monitoring API  In the Knowledge Base Synthetic API Monitoring APIs  Changes to Synthetic monitoring browsers
Watch this page for updates — click the Subscribe button, above right Want to receive all monthly Product Updates? Click to subscribe to the series   In April, the AppDynamics SaaS Controller v... See more...
Watch this page for updates — click the Subscribe button, above right Want to receive all monthly Product Updates? Click to subscribe to the series   In April, the AppDynamics SaaS Controller version 22.4.0 was released with key product enhancements. There have also been a number of agent enhancements. Finally, There are a number of new bug fixes and/or optimizations with SaaS Controller version 22.3.1 and Enterprise Console (on-prem) version 21.4.14. In this article... Feature Enhancements Heads Up - What Else You Should Know Resolved and Known Issues Get Started Ask a Question What release highlights should I know about? These release highlights include the newest features and capabilities this month, at a glance. In the grid below, we’ve flagged who within your organization may be most interested or impacted for each enhancement. CATEGORY ENHANCEMENT USER and PERFORMANCE ANALYST ADMIN and IMPLEMENTER  DEVELOPER AGENT UPDATES Analytics Agent   ✓     Cluster Agent   ✓   Database Agent   ✓   Java Agent  ✓     Javascript Agent  ✓ ✓   .NET ✓  ✓   Python Agent   ✓   Xamarin Agent ✓ ✓   SAAS CONTROLLER   Agent Installer   ✓   Dash Studio ✓     Agent Updates Analytics Agent The Analytics Agent includes updates to the Azul JRE and SLF4J builds. (v22.4.0 Released April 28, 2022)   Cluster Agent There have been some minor bug fixes. (v22.4.0 Released April 29, 2022)   Database Agent There have been some minor bug fixes and enhancements. (v22.4.0 Released April 25, 2022) Java Agent Supports the Z Garbage Collector and reports the metrics as a minor collection. (v22.4.0 Released April 22, 2022) JavaScript Agent Beacons are now sent to the HTTP endpoint if available. Otherwise, HTTP endpoints will be used. (v22.4.0 Released April 15, 2022) Machine Agent There were several enhancements: The flag -Dappdynamics.machine.agent.extensions.calcVolumeFreeAndUsedWithDfCommand is set to "true" to reserve 5% of disk space on Linux systems. The solaris_sparcv9 Java version was upgraded to JRE11. There are also a number of upgrades to third party libraries.  (v22.4.0 Released April 27, 2022) .NET Agent There were several enhancements: Signs AppDynamics.Agent.netstandard.dl in Agent NuGet packages.  Improves dynamic reflection with runtime type re-binding capability. Extracts the process identity on Linux to make it in parity with Windows. Uses stdout instead of temp-file communication for processing.  (v22.4.0 Released April 5, 2022) Python Agent Python version 3.10 is now supported. (v22.4.0 Released April 27, 2022) Xamarin Agent You can now attach a custom user data property to a specific network request by adding it to HttpRequestTracker. (v22.4.0 Released April 18, 2022)   NOTE | To view all technical documentation associated with this month’s releases, please visit Product Announcements, Alerts, and Hot Fixes in our documentation portal.  To Table of Contents  |  To Resource List Heads up - What else you should know  New Webinar | Embracing AppDynamics for OpenTelemetry  View our webinar to learn how you can embrace the OpenTelemetry™ open-source standard for any data source, and leverage AppDynamics agents and industry-leading AI and ML capabilities for advanced, business impacting insights. Register to view it here OpenTelemetryTM is a trademark of The Linux Foundation®. New AppDynamics University courses AppDynamics University has seen a wealth of new courses and certification recognition features. Check out the most recent education product updates as well as the introduction of our instructor interview series. Access these new instructor-led and short-form courses directly on AppDynamics University. Or read about them in recent News & Announcements posts.  To Table of Contents  |  To Resource List Resolved and Known Issues The following AppDynamics Controller versions have either known or resolved issues.  SaaS Controller version 22.2.4 does not contain any resolved issues, however, there are some 22.3.1 SaaS controller resolved issues. Enterprise Console version 21.4.14 was released April 14 and provides a bug fix for the Database Monitoring Agent (DBMON-8554) The Cluster Agent for RedHat is currently unavailable due to a change in the RedHat release process. The Database Agent 22.4.0 has a known issue - The Database Agent does not run on JDK versions 16 and 17, therefore please use JDK 15 or lower.  You can see a complete listing of this month’s Agent and Controller Resolved Issues, as well as additional detail around known issues in the Release Notes.  To Table of Contents  |  To Resource List Get Started PLEASE NOTE: customers are advised to check backward compatibility in the Agent and Controller Compatibility documentation.  Download Essential Components (Agents, Enterprise Console, Controller (on-prem), Events Service, EUM Components) Download Additional Components (SDKs, Plugins, etc.) How do I get started upgrading my AppDynamics components for any release? Product Announcements, Alerts, and Hot Fixes Open Source Extensions License Entitlements and Restrictions Can’t find what you’re looking for? Need more assistance? Ask a question in the Latest Release forum. To Table of Contents
The AppDynamics iOS Agent now supports M1 Simlator and XCFrameworks for DEM MRUM As of the March 22.3 iOS Agent release, DEM MRUM iOS supports use of M1 Simulator and XCFrameworks builds through XC... See more...
The AppDynamics iOS Agent now supports M1 Simlator and XCFrameworks for DEM MRUM As of the March 22.3 iOS Agent release, DEM MRUM iOS supports use of M1 Simulator and XCFrameworks builds through XCode 13. You can download the new Agent and integrate it into your pipeline. In this article… Where do I find information to build my application to use iOS Agent features? Where do I download AppDynamics iOS Agent 22.3?  Additional Resources Where do I find instructions for building my application to use the latest iOS Agent features? For detailed instructions on how to build your application, see the instructions in the AppDynamics Documentation portal: Mobile Real User Monitoring: Install the iOS SDK Or in Apple’s Developer Documentation Running Your App in the Simulator or on a Device | Apple Developer Documentation   Where do I download iOS Agent 22.3? You can download the latest version of iOS Agent from the following locations: AppDynamics Downloads page: https://accounts.appdynamics.com/downloads You can download the latest version of AppDynamics iOS Agent from the Downloads page in the Accounts portal CocoaPods Repo: https://cocoapods.org/pods/AppDynamicsAgent You can download AppDynamics iOS Agent from its Cocoapods page Additional Resources Blog: What is Digital Experience Monitoring?
What do I need to know about OTel and using it with AppDynamics? Get up to speed on OpenTelemetry and how AppDynamics will support it, expanding telemetry data sources for our advanced analytics, A... See more...
What do I need to know about OTel and using it with AppDynamics? Get up to speed on OpenTelemetry and how AppDynamics will support it, expanding telemetry data sources for our advanced analytics, AI/ML, and troubleshooting capabilities. In this article… About the technology What is OpenTelemetry (OTel)? I understand what OTel is, but what is it not? How is AppDynamics supporting OTel? How do I access OTel capabilities? I thought AppDynamics could already collect metrics, events, logs and traces/BTs? What’s changing, and why? How much OTel data can I get? Additional Resources ABOUT THE TECHNOLOGY What is OpenTelemetry (OTel)? Owned by the Linux Foundation, OpenTelemetry is a vendor-neutral standard for collecting telemetry data for applications, their supporting infrastructures and services. Read the details in the What is OpenTelemetry (OT) and why should you care? post on the AppDynamics Blog. TIP | See additional resources below. And don’t forget to subscribe if you want notifications of updates to this FAQ (click the 3-dot menu, then “Subscribe”) I understand what OTel is—but what is it not? While OpenTelemetry provides a solution similar to AppDynamics Agents, there are some differences and common misconceptions: It is not only APM OpenTelemetry started as a standard for cloud native application monitoring, but the scope quickly expanded. With special interest groups looking into “Client Side Telemetry” and eBPF, OTel is turning into a cross-cutting standard for telemetry spanning from Digital End-User Monitoring (DEM), over APM, DB and Infrastructure Observability. It is OTel OpenTelemetry is the successor to OpenTracing (OT) and OpenCensus, so to avoid confusion, the community uses OTel as an abbreviation. “Agent” can mean different things In the context of OpenTelemetry, you will find the term ‘Agent’ being used for two different things: A collector running on the same host as the app (sidecar) An auto-instrumentation agent which is equivalent to AppDynamics agents Agents are not the only way to collect telemetry It is not mandatory to use an agent for auto-instrumentation OpenTelemetry. An application can support OTel natively via an SDK, and there is no need to inject an agent. Actually, one of the goals is to make every library and application observable out-of-the box by having them call the APIs directly. Back to TOC APPDYNAMICS AND OPENTELEMETRY What is AppDynamics doing to support OTel? Once ingested, OpenTelemetry data will be a first-class citizen, treated as any data coming from our own agents, on which you can have health rules, flowmaps, and more. Starting in Spring 2022, we will cover IT Ops use cases for health assessment and alerting. Expect additional use cases in due course, too. How do I access AppDynamics OTel capabilities? Depending on your region, you’ll see a new OTel tab in the menu bar once you upgrade to AppDynamics version 22.3. NOTE | Please check the current list of AppDynamics for OpenTelemetry-supported regions. To use AppDynamics OTel, you will need to: Configure your OTel collectors Use the generated API key with the Endpoint to connect to the AppDynamics Controller If you are considering ingesting OpenTelemetry data with the AppDynamics Java and Node.js Agents, they should be updated to the latest version. NOTE: Some language-specific SDKs can export the OTel traces directly (without the need for the separate OTel collector in-between) to the telemetry backend, given the required OTel resource attributes are supported by those exporters (see this document). The AppD-specific telemetry backend, as part of the "AppDynamics for OpenTelemetry" feature, has the support for the following OTLP-specific implementations. If you would like to report the OTel traces directly from the particular OTel Language-specific SDK, it's possible to specify the required resource attributes and achieve that. If you need further guidance on this particular use case, please contact AppD Support and mention this particular use case. I thought AppDynamics could already collect metrics, events, logs and traces/BTs? So, what's changing and why? With the OTel standard, you can now leverage from more telemetry data sources to enrich AppDynamics' advanced analytics, AI/ML, and troubleshooting capabilities. How much OTel data can I get? Please read this AppDynamics Documentation for more info:  Licenses and Entitlements. Back to TOC Additional Resources Documentation: AppDynamics for OpenTelemetry AppDynamics for OpenTelemetry Supported Regions AppDynamics Blog posts: What is OpenTelemetry and why should you care? OpenTelemetry: How Cisco and AppDynamics are contributing to the future of observability AppDynamics for OpenTelemetry: Accelerating innovation across software development ecosystems What’s on our radar: OpenTelemetry™ expert shares A-list OTel content Demonstration Video and product information: AppDynamics for OpenTelemetry video Live Webinar: Embracing AppDynamics for OpenTelemetry (April 27, 2022)
Watch this page for updates — click the Subscribe button, above right Want to receive all monthly Product Updates? Click to subscribe to the series Revised March 25, 2022 In March, we released C... See more...
Watch this page for updates — click the Subscribe button, above right Want to receive all monthly Product Updates? Click to subscribe to the series Revised March 25, 2022 In March, we released Controller version 22.3 which contains key product enhancements and agent updates, along with SaaS Controller fixes. In this article... Feature Enhancements Heads Up - What Else You Should Know Resolved Issues Get Started Ask a Question What release highlights should I know about? These release highlights include the newest features and capabilities this month, at a glance. In the grid below, we’ve flagged who within your organization may be most interested or impacted for each enhancement. CATEGORY ENHANCEMENT USER and PERFORMANCE ANALYST ADMIN and IMPLEMENTER  DEVELOPER FULL-STACK OBSERVABILITY ThousandEyes and Dash Studio ✓ ✓ ✓ AGENT UPDATES C/C++ SDK ✓ ✓ ✓ Database Agent ✓ ✓   Flutter Agent for MRUM ✓ ✓ ✓ IBM Integration Bus Agent   ✓   iOS Agent   ✓   .NET ✓ ✓ ✓ PHP Agent ✓ ✓   Xamarin Agent ✓  ✓   SAAS CONTROLLER Mobile RUM  ✓ ✓   Full-stack Observability Enhancements ThousandEyes and DashStudio Thousand Eyes and Dash Studio now support a new Gauge widget so we can set thresholds to indicate color status. The previous Thousand Eyes test limit has been removed. Agent Updates C/C++ SDK Agent The C/C++ SDK Agent now supports the Alpine Linux distribution and can match limits set by the Analytics Agent. (v22.3.0, Released March 15, 2022) Database Agent There is a new SSL environment setting for the CASSANDRA_SSL-CONTEXT_PROTOCOL system. See Configure Cassandra Collectors documentation for more information.  Additionally, there is now an option to delete servers manually from the database topology window. And state servers are now automatically deleted from the database server table. (v22.3.0, Released March 24, 2022) Flutter Agent for mobile RUM AppDynamics’ new Flutter Agent allows you to monitor your mobile Flutter applications. See Instrument Flutter Agent and Customize the Flutter Instrumentation. (v22.3.0, Released March 8, 2022) IBM Integration Bus Agent You can now reuse historical VM node names for new VMs and in addition. It prevents the rapid increase of differently named nodes, especially when the nodes are identical processes that run over different times, helping you monitor environments with short-life VMs. Please see the Enable the Node Name Reuse documentation for more details. Additionally, IBM App Connect Enterprise version 11 running on Kubernetes is now supported. (v22.3.0, Release March 3, 2022) iOS Agent AppDynamics iOS Agent now supports Xcode 12.5 and later. (v22.3.0, Released March 22, 2022)   PHP Agent This release includes support to report analytics data after a specific number of data events/transactions or after a specific time interval. See Configure Transaction Analytics for Node.js, PHP, and Python Applications. (v22.3.0, Released March 3, 2022) SaaS Controller Enhancements SaaS Controller version 22.2.4 In March, SaaS Controller version 22.2.4 was released which supports a number of Mobile RUM enhancements such as asynchronously correlating business transactions for mobile sessions, including fetching and loading endpoints for Mobile Session Details.  NOTE | To view all technical documentation associated with this month’s releases, please visit Product Announcements, Alerts, and Hot Fixes in our documentation portal.  To Table of Contents  |  To Resource List Heads up - What else you should know  New ‘Synthetic API Monitoring’ demo Learn how the new AppDynamics API Monitoring solution helps you proactively identify and resolve API performance and availability issues to minimize impact on your users’ experience and business outcomes. Watch the video for a first-hand experience.  Full-Stack Observability webinars AppDynamics Full-Stack Observability Webinar Series  Want to learn how to transform your business faster? Join us as our experts walk you through the benefits of full-stack observability and the impact it can have on your customer experience, profitability, and optimization of your IT team’s time. Walk away with valuable knowledge. View or Register Today New AppDynamics University Systems Engineering Masters accreditation February marked the first recipients of AppDynamics’ Qualified Systems Engineering Masters accreditation. To qualify, these candidates met their AppDynamics Partner Program Stage 1 and 2 learning map obligations via the Cisco Black Belt Academy, and then successfully combined it with an AppDynamics Certification. See the February 2022 cohort here. More from AppDynamics University AppDynamics University has seen a wealth of new courses and certification recognition features. Access these new instructor-led and short-form courses directly on AppDynamics University. Or read about them in recent News & Announcements posts. To Table of Contents  |  To Resource List Resolved Issues The following AppDynamics Controller versions have enhancements and/or resolved issues.  SaaS Controller versions 22.2.2, 22.2.3 and 22.2.4 were released with Controller Resolved Issues Enterprise Console version 21.4.13-24717 was released with Controller (SaaS/On-Premises) Resolved Issue The following key Agent issue was resolved in the 22.3 release. Agent Scope fails added in cases where there are a large number of Analytics Agents (ANALYTICS-13883) You can see a complete listing of this month's Agent Resolved Issues, as well as Controller Resolved Issues, in AppDynamics documentation. To Table of Contents  |  To Resource List Get Started PLEASE NOTE: customers are advised to check backward compatibility in the Agent and Controller Compatibility documentation.  Download Essential Components (Agents, Enterprise Console, Controller (on-prem), Events Service, EUM Components) Download Additional Components(SDKs, Plugins, etc.) How do I get started upgrading my AppDynamics components for any release? Product Announcements, Alerts, and Hot Fixes Open Source Extensions License Entitlements and Restrictions   Can’t find what you’re looking for? Need more assistance? Ask a question in the Latest Release forum. To Table of Contents
What do I need to know about API Monitoring? With Synthetic API monitoring, you can monitor the availability and performance of HTTP(s) based APIs. These APIs can be internal, external, or third-pa... See more...
What do I need to know about API Monitoring? With Synthetic API monitoring, you can monitor the availability and performance of HTTP(s) based APIs. These APIs can be internal, external, or third-party APIs.  In this article…  What Synthetic API Monitoring offers Monitoring APIs from different locations Managing API password security Licensing for Synthetic API Monitoring  Moving from Service Availability Monitoring (SAM) to Synthetic API monitoring of service endpoints   Getting started with Synthetic API Monitoring  Additional Resources What does Synthetic API Monitoring offer? Which API metrics will I have insights into? API Monitoring can be use to monitor the availability and performance trends of APIs, API jobs and API collections:   Metrics API collection Availability % Average response time API job Availability trend Performance trends Average response size trends API Status code trends Response time trends Response size trends Time-related trends, e.g., wait time, TLS time, TCP time, DNS time, etc… How does Synthetic API Monitoring compare to AppDynamics Synthetic Web Monitoring? Synthetic API monitoring Synthetic web monitoring  Designed to gather granular API level information, such as:  wait time DNS time TCP time request time download time, and more… Also designed to monitor API monitoring trends, such as:  status code trends response size trends API trends granular API data for debugging Designed to gather page-level information, such as:  page screenshot page resources domains requested waterfall view of the page load events compute visually complete, and more… Can I monitor a sequence of API requests as a workflow? Yes. Synthetic API Monitoring can be configured to monitor a single API or a sequence of multiple API endpoints. You can find sample scripts for multiple API requests, in this document. How often can API tests be configured to run? Synthetic API Monitoring can be configured to run with a minimum frequency of 1 minute. Back to Top | To End   What do I need to know about monitoring APIs from different locations? How many locations can API tests be run from? You can monitor APIs from 17 hosted locations distributed worldwide.  You can also use private synthetic agents to monitor APIs in your intranet, VPC, or in any other locations. Find the steps for setting up private synthetic agents on the Install the Private Synthetic Agent (Web and API Monitoring) page in AppDynamics Documentation. Is it possible to add custom locations from which to test private APIs? Yes, AppDynamics customers can set up private synthetic agents in any location they require to test private APIs. Back to Top | To End   How can I manage API password security? Do you have an encrypted store for passwords? Yes, customers can use the Synthetic Credentials Vault to store their passwords securely and use it in the API Monitoring jobs. For more information, refer to AppDynamics Documentation. Back to Top | To End   What licensing do I need for Synthetic API Monitoring? Can I use my existing AppDynamics Synthetic Monitoring license for API Monitoring? Yes, The Synthetic Monitoring license can be used for both Web and API Monitoring.   Web Monitoring API Monitoring Hosted agent Metered in 5-second time blocks Metered in seconds Private agent Minimum supported frequency of 5 minutes Minimum supported frequency of 1 minute   Can I use or transfer my Service Availability Monitoring (SAM) license for use of Synthetic API Monitoring?  You need an active Synthetic Monitoring license to use Synthetic API Monitoring.  While there is no mechanism to convert the SAM license to a Synthetic monitoring license, customers can continue to use their active SAM license with the SAM product   Back to Top | To End   I currently monitor my service endpoints using Service Availability Monitoring (SAM). How can I move to Synthetic API monitoring? Depending on whether you use Service Availability Monitoring with SaaS Controller or on-premises Controller, you can use either Synthetic API or Synthetic Web monitoring products to monitor your service endpoints.     Synthetic API Monitoring method to monitor service endpoints SaaS Controller Method: Install private synthetic agents Instructions Set up the Private Synthetic Agent (PSA) for API Monitoring Reach out to our support team to move your jobs from SAM to Synthetic API Monitoring On-premises Controller Method: Move to a SaaS controller Instructions Set up the Private Synthetic Agent (PSA) for API Monitoring Reach out to our support team to move your jobs from SAM to Synthetic API Monitoring Method: Install web monitoring private synthetic agents Instructions Set up the Private Synthetic Agent (PSA) for Web Monitoring Follow the configuration instructions in the Documentation portal to create a Synthetic job for monitoring your service endpoints How can I move my service endpoints from SAM to Synthetic API Monitoring? Our team can help you to move the service endpoints monitored in SAM to Synthetic API Monitoring. Please reach out to your regular AppDynamics contact person or raise a support ticket. Back to Top | To End   How do I get started with Synthetic API Monitoring? You can refer to AppDynamics Documentation to learn how to get started with Synthetic API monitoring. Does Synthetic API Monitoring support OAuth? Yes, you can use JavaScript to implement OAuth authentication for your API Monitoring jobs. To implement OAuth, you can refer to these sample code snippets. Which API standards does API Monitoring support? API Monitoring supports the HTTP and HTTPS protocols. Additional protocols will be supported based on customer requests. Are there sample API monitoring scripts I can refer to? Yes, sample JavaScripts based scripts for API monitoring are available here. Back to Top | To End     Additional Resources AppDynamics Micro Demo: Synthetic API Monitoring AppDynamics Documentation: Synthetic API Monitoring AppDynamics Support
Watch this page for updates — click the 3-dot menu upper right, then subscribe Want to receive all monthly Product Updates? Click to subscribe to the series In February, we released Controller v... See more...
Watch this page for updates — click the 3-dot menu upper right, then subscribe Want to receive all monthly Product Updates? Click to subscribe to the series In February, we released Controller version 22.2 which contains key product enhancements and agent updates, along with SaaS Controller fixes. Revised March 1, 2022 In this article... Feature Enhancements Heads Up - What Else You Should Know Resolved Issues Get Started Ask a Question What release highlights should I know about? These release highlights include the newest features and capabilities this month, at a glance. In the grid below, we’ve flagged who within your organization may be most interested or impacted for each enhancement. CATEGORY ENHANCEMENT USER and PERFORMANCE ANALYST ADMIN and IMPLEMENTER  DEVELOPER FULL-STACK OBSERVABILITY Synthetic API Monitoring ✓ ✓ ✓ AGENT UPDATES Apache Web Server Agent   ✓   Automatic Network Request Instrumentation   ✓   Database Agent   ✓   Machine Agent   ✓   .NET Agent   ✓   JavaScript Agent    ✓   SAAS CONTROLLER   License availability and usage display  ✓ ✓   Full-stack Observability Synthetic API Monitoring Synthetic API Monitoring delivers proactive monitoring and advanced troubleshooting of API performance and availability issues, enabling you to reduce MTTI/MTTR and minimize the impact of issues on user experience and business outcomes. To learn more read our documentation. (v21.11.0, Released January 31, 2022) Agent Updates JRE upgraded to v11.0.13 The Java Runtime Environment (JRE) has been upgraded to version 11.0.13. (v22.2.0, Released February 18, 2022) Xamarin Agent now supports Automatic Network Request Instrumentation This release of AppDynamics Xamarin Agent includes support for Automatic Network Request Instrumentation, made available as a separate beta NuGet package. See Instrument Xamarin Applications for details. (v22.2.0, Released February 14, 2022) Database Agent can now be installed as a container image This release adds support for installing the Database Agent as a container image. See Install the Database Agent. (v22.2.0, Released February 23, 2022) New Machine Agent adds platform architectures and addresses vulnerabilities This release adds the ARM64 and AARCH64 platforms on Linux, and has upgraded Square’s meticulous HTTP client libraries to 4.9.3 to account for known vulnerabilities. (v22.2.0, Released February 28, 2022) .NET Agent now uses FULL_AGENT variable by default Now, you don’t need to use the FULL_AGENT variable with containers. As of this release, .NET Agent uses it by default (v22.2.0, Released February 17, 2022) JavaScript Agent includes error handling support JavaScript Agent v22.2 includes error handling support for  UnhandledRejection events. (v22.2.0, Released February 18, 2022) SaaS Controller License availability and usage display This Controller release includes a UI enhancement that displays license availability and usage for applications that can enable Application Analytics. These representations of license availability include: Healthy availability Availability warning None available.  See Collect Transaction Analytics Data for more information. NOTE | To view all technical documentation associated with this month’s releases, please visit Product Announcements, Alerts, and Hot Fixes in our documentation portal.  To Table of Contents  |  To Resource List Heads up - What else you should know  New ‘Synthetic API Monitoring’ demo Learn how the new AppDynamics API Monitoring solution helps you proactively identify and resolve API performance and availability issues to minimize impact on your users’ experience and business outcomes. Watch the video for a first-hand experience.  Full-Stack Observability webinars AppDynamics Full-Stack Observability Webinar Series  Want to learn how to transform your business faster? Join us as our experts walk you through the benefits of full-stack observability and the impact it can have on your customer experience, profitability, and optimization of your IT team’s time. Walk away with valuable knowledge and gain eligibility to receive a $50 prize! View or Register Today AppDynamics Full-Stack Observability for Government & Education Join AppDynamics and experts from IDC on March 15 at 2 p.m. ET to learn how government and educational organizations are overcoming barriers to accelerate digital transformation and taking steps to ensure security and performance of new digital services in a time of constant change.   Register Today New AppDynamics University courses AppDynamics University now offers single-topic Short Focused Topics (SFTs), as well as  SAP instructor-led Education. To learn more about these offerings, as well as the AppDynamics Learning Recognition Badge program, go to AppDynamics University and search for the course code (listed below). NOTE | SFT courses are available to users with a Premium University Subscription. Get up to speed with Short Focused Topics SFT courses are 60-90 minutes long and include demos and labs. Delivered with the same high-caliber instruction as longer format AppD University courses, each is geared to get you working in the product topic area quickly and proficiently.  COURSE CODE COURSE DESCRIPTION DEV310 Developers: AppDynamics for release comparison and validation PRO520 Pro Series: Building effective dashboards with AppDynamic SAP210 AppDynamics essentials for SAP   New 2-day SAP Essentials for SAP Check out AppDynamics Essentials for SAP—a new two-day, instructor-led course designed for customers who want to use AppDynamics to proactively monitor their SAP system.  This course is available to users with a Premium University Subscription. COURSE CODE COURSE DESCRIPTION SAP210 AppDynamics essentials for SAP AppDynamics Community Read up on the small adjustments that make a big difference in our Share a tip space. Another spot where AppD Community members can exchange peer-to-peer advice, be sure to add your own insights there too. To Table of Contents  |  To Resource List Resolved Issues To see a complete listing of this month's resolved issues, see Resolved Issues by Month. For information about the log4j Apache vulnerability, see the Agent Updates section, above To Table of Contents  |  To Resource List Get Started PLEASE NOTE: customers are advised to check backward compatibility in the Agent and Controller Compatibility documentation.  Download Essential Components (Agents, Enterprise Console, Controller (on-prem), Events Service, EUM Components) Download Additional Components (SDKs, Plugins, etc.) How do I get started upgrading my AppDynamics components for any release? Product Announcements, Alerts, and Hot Fixes Open Source Extensions License Entitlements and Restrictions Can’t find what you’re looking for? Need more assistance? Ask a question in the Latest Release forum. To Table of Contents
How can I run a simulator on my M1-based Mac using Rosetta to provide the needed ARM64 support?  To run a simulator on an M1-based Mac, your linked frameworks need to support an ARM64 for M1 slice.... See more...
How can I run a simulator on my M1-based Mac using Rosetta to provide the needed ARM64 support?  To run a simulator on an M1-based Mac, your linked frameworks need to support an ARM64 for M1 slice. This is accomplished by application vendors shipping a new product packaged as an XCFramework rather than the traditional Framework. This new product version can include an M1 Simulator slice for testing. AppDynamics is working on releasing our iOS Agent XCFramework version in the near term In the meantime, if you want to test your product that includes our current iOS Agent Framework version, you will need to employ a work-around using Rosetta to run the simulator.  NOTE | An Apple-supplied tool that emulates an Intel Mac running on an M1 Mac, Rosetta is available on any M1 Mac. In this article… How do I implement the Rosetta work-around? When will an XCF Framework version of the iOS Agent be available?  Want to be notified of updates about either this work-around or an XCFramework version of iOS Agent? Click the 3-dot icon on the upper right, then select Subscribe from the drop-down list.   How do I implement the Rosetta work-around? There are a couple of simple steps for this workaround. 1. Set your project build settings’ Build Active Architecture only to ‘Yes’ In your project Build Settings, set the ‘Build Active Architecture Only’ to Yes for Debug mode. This will cause Xcode to only build a version of your app required to run on the currently chosen simulator. For most developers, this is the default setting. This does not affect the release version of your app. 2. Make certain your simulator can run under Rosetta Make sure your Simulator will run under Rosetta. This will force the Simulator to run an Intel version of the code, avoiding an M1 support error message. There are two ways to make this happen: NOTE | In both cases be sure to Clean Build Folder, and then rebuild and test your app. Select a simulator that runs iOS 13.7 or older These simulators were made by Apple only in Intel-based versions. Simulators newer than 13.7 have both Intel and M1 support. Using an older simulator will force Rosetta to run and allow you to debug your app. You will notice that this simulator will run slower than normal due to the Rosetta emulation. Force Xcode to run under Rosetta If you need to run a newer simulator than 13.7, you can force Xcode itself to run under Rosetta. This will cause all of Xcode to run slower due to the emulation but it will work with any version of the simulator. To force Xcode to run in Rosetta:  Quit Xcode if it is running. Use Finder to locate Xcode.app in the Applications folder of your Mac. Right click Xcode.app and select ‘Get Info’ Click the ‘Open using Rosetta’ check box. Restart Xcode. It will now be running in emulation and will be slower than usual. When will an XCF Framework version of the iOS Agent be available? We are working towards delivering an XCFramework version of our agent in the near term. We will notify the customer community here, as well as in the usual AppDynamics product announcement publications. To receive a message alerting you to any updates to this workaround article, including news of an XCFramework iOS Agent, click the 3-dot icon on the upper right, and select Subscribe from the drop-down list.
What naming conventions are recommended when defining configuration objects for AppDynamics Database Visibility? We highly recommend the following standard naming conventions for different configu... See more...
What naming conventions are recommended when defining configuration objects for AppDynamics Database Visibility? We highly recommend the following standard naming conventions for different configuration items used in AppDynamics because sound naming standards are an important practice for: Efficient identification of objects Understanding data context Navigation Searching Housekeeping Decommissioning efforts plus more...! NOTE | In this article, we are specifying standards for setting configuration items' values, rather than methods. See more below. These recommendations are based on standard configurations and are not intended to be a universal solution, and therefore may not work with custom-configured instances. In this article... Naming conventions for Database Visibility Overarching principles for naming conventions Additional Resources Naming conventions for Database Agent Successful naming is based on emphasizing the use of common standards. So, where available, use nomenclature that already exists, whether public or company-based. The following table contains naming best practices for AppDynamics Database Collectors. Database Agent naming conventions Database Collectors    {Country}-{DB name}-{Environment} {DB name} should be the CMDB name of the Database, unless the CMDB name does not adhere to the overarching principle, in which case it should be decided by the application teams with assistance from AppDynamics-knowledgeable resources. Database collector names and APM database back-end names for the same database should match (or be very similar) whenever possible. Back to Contents Overarching principles for naming conventions Some configuration items do not specify a strict pattern or convention. Instead, we leave it up to you to decide. In such cases the following principle should always apply:   Names chosen for any configuration item should be a sensible, non-technical description. DO THIS NOT THIS Use plain language Avoid too-formal, distancing language Be descriptive, but concise Don’t be verbose—or curt Use business terminology where possible Don’t use technical terms Make it meaningful to all intended users Avoid jargon that won’t be familiar to all of the intended users. When in doubt, leave it out. PLEASE NOTE: In this article, we are not specifying the method of setting values for configuration items, only standards for the values themselves. In the case of agent configuration properties, use one of the following methods to set the values: Configuration files System Properties Environment Variables Let us know in the comments below if you have further questions on methods.   Additional Resources For APM, what naming conventions are recommended? For Analytics metrics, what naming conventions are recommended?  For Dashboards, what naming conventions are recommended? For EUM, what naming conventions are recommended?  For Health Rules, what naming conventions are recommended? For AppDynamics Machine Agent, what naming conventions are recommended?
What naming conventions are recommended when defining configuration objects for AppDynamics server visibility? We highly recommend the following standard naming conventions for different configura... See more...
What naming conventions are recommended when defining configuration objects for AppDynamics server visibility? We highly recommend the following standard naming conventions for different configuration items used in AppDynamics because sound naming standards are an important practice for: Efficient identification of objects Understanding data context Navigation Searching Housekeeping Decommissioning efforts plus more...! NOTE | In this article, we are specifying standards for setting configuration items value, rather than methods. See more below. These recommendations are based on standard configurations and are not intended to be a universal solution, and therefore may not work with custom-configured instances In this article... Naming conventions for Machine Agent Overarching principles for naming conventions Additional Resources Naming conventions for Machine Agent Successful naming is based on emphasizing the use of common standards. So, where available, use nomenclature that already exists, whether public or company-based. The following table contains naming best practices for server visibility Machine Agent. Server visibility Machine Agent naming conventions Server Visibility/  Machine Agent    {hostname} The machine name should be defined using the property’s  Uniquehostid {application_name} - {data_centre} The machine hierarchy should be defined using the machine hierarchy property Standalone Machine Agents alongside APM Agents  Application, tier and node names should be left blank.  Uniquehostid should be used to match the machine agent to the correct application and tier and node from an APM agent. Independent Standalone Machine Agents  If the server should be attached to a node in a business application then follow the same naming standards as for APM application, tier and node. If the server is not required to report metrics into an APM business application (i.e., only visible under Server’s view then application), tier and node names should be left blank. Back to Contents Overarching principles for naming conventions Some configuration items do not specify a strict pattern or convention. Instead, we leave it up to you to decide. In such cases the following principle should always apply:   Names chosen for any configuration item should be a sensible, non-technical description. DO THIS NOT THIS Use plain language Avoid too-formal, distancing language Be descriptive, but concise Don’t be verbose—or curt Use business terminology where possible Don’t use technical terms Make it meaningful to all intended users Avoid jargon that won’t be familiar to all of the intended users. When in doubt, leave it out. PLEASE NOTE: In this article, we are not specifying the method of setting values for configuration items, only standards for the values themselves. In the case of agent configuration properties, use one of the following methods to set the values: Configuration files System Properties Environment Variables Let us know in the comments below if you have further questions on methods.   Additional Resources For APM, what naming conventions are recommended? For Analytics metrics, what naming conventions are recommended?  For Dashboards, what naming conventions are recommended? For AppDynamics Database Visibility, what naming conventions are recommended?  For EUM, what naming conventions are recommended?  For Health Rules, what naming conventions are recommended?   Need to go deeper? Reach out to Call a Consultant
What naming conventions are recommended when defining configuration objects in AppDynamics Dashboards? We highly recommend the following standard naming conventions for different configuration ite... See more...
What naming conventions are recommended when defining configuration objects in AppDynamics Dashboards? We highly recommend the following standard naming conventions for different configuration items used in AppDynamics because sound naming standards are an important practice for: Efficient identification of objects Understanding data context Navigation Searching Housekeeping Decommissioning efforts plus more...! NOTE | In this article, we are specifying standards for setting configuration items' values, rather than methods. See more below. These recommendations are based on standard configurations and are not intended to be a universal solution, and therefore may not work with custom-configured instances.  In this article... Naming conventions for AppDynamics Dashboards Overarching principles for naming conventions Additional Resources Naming conventions for AppDynamics Dashboards Successful naming is based on emphasizing the use of common standards. So, where available, use nomenclature that already exists, whether public or company-based. The following table contains naming best practices for AppDynamics Dashboards. Dashboard naming conventions {Team who owns the Dashboard}_{Full Business Application Name or Service}_{Dashboard Purpose} Example: CoE_MCA_ExecutiveSummary Since Dashboards do not have any hierarchy, the dashboard name must be used to segregate the dashboards into logical groups. Back to Contents Overarching principles for naming conventions Some configuration items do not specify a strict pattern or convention. Instead, we leave it up to you to decide. In such cases the following principle should always apply:   Names chosen for any configuration item should be a sensible, non-technical description. DO THIS NOT THIS Use plain language Avoid too-formal, distancing language Be descriptive, but concise Don’t be verbose—or curt Use business terminology where possible Don’t use technical terms Make it meaningful to all intended users Avoid jargon that won’t be familiar to all of the intended users. When in doubt, leave it out. PLEASE NOTE: In this article, we are not specifying the method of setting values for configuration items, only standards for the values themselves. In the case of agent configuration properties, use one of the following methods to set the values: Configuration files System Properties Environment Variables Let us know in the comments below if you have further questions on methods. Back to Contents   Additional Resources For APM, what naming conventions are recommended? For Analytics metrics, what naming conventions are recommended?  For AppDynamics Database Visibility, what naming conventions are recommended?  For EUM, what naming conventions are recommended?  For Health Rules, what naming conventions are recommended? For AppDynamics Machine Agent, what naming conventions are recommended?   Need to go deeper? Reach out to Call a Consultant
What naming conventions are recommended when defining configuration objects for Health Rules? We highly recommend the following standard naming conventions for different configuration items used i... See more...
What naming conventions are recommended when defining configuration objects for Health Rules? We highly recommend the following standard naming conventions for different configuration items used in AppDynamics because sound naming standards are an important practice for: Efficient identification of objects Understanding data context Navigation Searching Housekeeping Decommissioning efforts plus more...! NOTE | In this article, we are specifying standards for setting configuration items' values, rather than methods. See more below. These recommendations are based on standard configurations and are not intended to be a universal solution, and therefore may not work with custom-configured instances. In this article... Naming conventions for defining configuration objects in AppDynamics Health Rules Overarching principles for naming conventions Additional Resources Naming conventions for defining configuration objects in AppDynamics Health Rules Successful naming is based on emphasizing the use of common standards. So, where available, use nomenclature that already exists, whether public or company-based. The following tables contain naming best practices for Health Rules, actions and policies, as well as RBAC. Back to Contents Naming conventions for Health Rules Health Rules {Full Business Application Name}_{Description of alert} Example: UK Digital_CPU is High Since Dashboards do not have a hierarchy, the Dashboard name must be used to segregate the dashboards into logical groups: Actions and Policies {A sensible, non-technical description of what the action does} Example: Send Alert to Production Incident Management RBAC {Description of Role or Group} Apply the overarching naming principle to descriptions Back to Contents Overarching principles for naming conventions Some configuration items do not specify a strict pattern or convention. Instead, we leave it up to you to decide. In such cases the following principle should always apply:   Names chosen for any configuration item should be a sensible, non-technical description. DO THIS NOT THIS Use plain language Avoid too-formal, distancing language Be descriptive, but concise Don’t be verbose Use business terminology where possible Don’t use technical terms Make it meaningful to all intended users Avoid jargon that won’t be familiar to all of the intended users. When in doubt, leave it out. PLEASE NOTE: In this article, we are not specifying the method of setting values for configuration items, only standards for the values themselves. In the case of agent configuration properties, use one of the following methods to set the values: Configuration files System Properties Environment Variables Let us know in the comments below if you have further questions on methods.   Additional Resources For APM, what naming conventions are recommended? For Analytics metrics, what naming conventions are recommended? For Dashboards, what naming conventions are recommended? For AppDynamics Database Visibility, what naming conventions are recommended? For EUM, what naming conventions are recommended? For AppDynamics Machine Agent, what naming conventions are recommended?   Need to go deeper? Reach out to Call a Consultant
What naming conventions are recommended when defining configuration objects for server visibility Machine Agent? We highly recommend the following standard naming conventions for different configu... See more...
What naming conventions are recommended when defining configuration objects for server visibility Machine Agent? We highly recommend the following standard naming conventions for different configuration items used in AppDynamics because sound naming standards are an important practice for: Efficient identification of objects Understanding data context Navigation Searching Housekeeping Decommissioning efforts plus more...! NOTE | In this article, we are specifying standards for setting configuration items' values, rather than methods. See more below. These recommendations are based on standard configurations and are not intended to be a universal solution, and therefore may not work with custom-configured instances. In this article... Naming conventions for EUM Overarching principles for naming conventions Additional Resources Naming conventions for EUM Successful naming is based on emphasizing the use of common standards. So, where available, use nomenclature that already exists, whether public or company-based. The following tables contain naming best practices for End User Monitoring (EUM), including EUM applications, RUM, and Synthetic job names. Back to Contents Naming conventions for EUM EUM applications {Full Business Application Name} - {EUM Type} {EUM Type} must be one of the following: BRUM for Browser Real User monitoring iOS for iOS mobile application monitoring Android for Android mobile application monitoring RUM PAGES, AJAX CALLS, and NETWORK REQUESTS {To be decided by the application teams, with assistance from AppDynamics knowledgeable resources} As required to conform to the Overarching Principle, use manual renaming or custom match rules. Whenever possible, BRUM Page names or Ajax calls should match (or be very similar to) the APM BT’s that performs the corresponding back-end processing. Synthetic job names {Description of journey and steps involved} Application teams to define a naming standard, with assistance from AppDynamics-knowledgeable resources. The naming standard should conform to the overarching naming principles: names chosen for any configuration item should be a sensible, non-technical description Back to Contents Overarching principles for naming conventions Some configuration items do not specify a strict pattern or convention. Instead, we leave it up to you to decide. In such cases the following principle should always apply:   Names chosen for any configuration item should be a sensible, non-technical description. DO THIS NOT THIS Use plain language Avoid too-formal, distancing language Be descriptive, but concise Don’t be verbose Use business terminology where possible Don’t use technical terms Make it meaningful to all intended users Avoid jargon that won’t be familiar to all of the intended users. When in doubt, leave it out. PLEASE NOTE: In this article, we are not specifying the method of setting values for configuration items, only standards for the values themselves. In the case of agent configuration properties, use one of the following methods to set the values: Configuration files System Properties Environment Variables Let us know in the comments below if you have further questions on methods.   Additional Resources For APM, what naming conventions are recommended? For Analytics metrics, what naming conventions are recommended?  For Dashboards, what naming conventions are recommended? For AppDynamics Database Visibility, what naming conventions are recommended?  For Health Rules, what naming conventions are recommended? For AppDynamics Machine Agent, what naming conventions are recommended?   Need to go deeper? Reach out to Call a Consultant