All TKB Articles in Learn Splunk

Learn Splunk

All TKB Articles in Learn Splunk

Enhance full-stack observability by correlating Mobile Real User Monitoring (Mobile RUM) with network intelligence  In this article... What is Customer Digital Experience Monitoring (CDEM)?  ... See more...
Enhance full-stack observability by correlating Mobile Real User Monitoring (Mobile RUM) with network intelligence  In this article... What is Customer Digital Experience Monitoring (CDEM)?  CDEM offers two-way data flow and analysis across stacks in real time  How do I correlate data across APM, RUM, and NPM domains? Latest CDEM updates extended 2-way information sharing, now including MRUM  Additional resources    What is Customer Digital Experience Monitoring (CDEM)?  In June 2023, Cisco released Customer Digital Experience Monitoring (CDEM) – a bi-directional integration between AppDynamics™ and ThousandEyes™- which extended Cisco’s Full Stack Observability by combining application, network and user experience monitoring to provide powerful customer digital experience monitoring. It helps our customers to:  Proactively identify gaps in monitoring and deliver optimal digital experiences to their users  Correlate inferior user experiences over customer applications attributed due to network issues  Reduce MTTR and prioritize network remediation based on the business impact due to user experience issues  This integration offers a powerful correlation between network insights and customer’s application experience their users face, over their respective web browsers.   CDEM offers two-way data flow and analysis across stacks in real time There is a real-time flow of data across APM, RUM and NPM stacks which is further correlated in near-real time and then analyzed and presented over insightful visualization.  AppDynamics APM Application Performance Management  Helps in monitoring and managing the performance of applications by providing real-time insights into the performance of the application itself, including metrics related to response times, errors, and resource utilization.    AppDynamics RUM   Real User Monitoring  Involves tracking and monitoring the experience of real users interacting with an application. It provides insights into how users are experiencing the application, including details about page load times, user interactions, and more.    ThousandEyes NPM Network Performance Management Helps in monitoring the performance of internet infrastructure — including factors like network latency, packet loss, and bandwidth utilization.    By correlating network insights for similar network domains between NPM, APM, and RUM stacks, we provide our customers with full-stack observability across these stacks, packaged as the CDEM offering. Adding to our current correlation between network performance and user experience over web browsers, this release includes mobile applications as well.   How do I correlate data across APM, RUM and NPM domains?  In AppDynamics, applications are the entities that contain application performance insights and associated user experience data to provide business observability. These applications contain network domains against which ThousandEyes network tests can be configured for getting regular network insights.  Data from common entities across domains including metrics related to application performance, user experience, and network performance is collected.  The collected data is correlated to identify patterns or relationships. This involves associating network performance issues with user experience metrics and eventually with application performance metrics.  Once the data is correlated, it is analyzed to gain insights. This analysis can help identify the root causes of performance issues and can be used to optimize the application and network.  The insights are presented through visualization tools. These tools might create dashboards, charts, and reports to make the information more accessible and actionable for users.  Latest CDEM updates extended 2-way information sharing to now include Mobile RUM (MRUM) RUM is further categorized into Browser RUM (BRUM) and Mobile RUM (MRUM). Early this year, we launched CDEM to integrate ThousandEyes network insights with Browser RUM. In the current release, we have extended it to include Mobile RUM as well.   With bi-directional information sharing between MRUM, APM and NPM, this solution eliminates silos and provides end-to-end visibility to every team, all from within Cisco AppDynamics. It helps isolate issues like slow mobile application responsiveness due to network issues by visualizing aggregated mobile application user experience metrics along with network metrics across the same timelines.    Additional resources  AppDynamics SaaS documentation: End User Monitoring  In the Blog: Mobile Real User Monitoring and Cisco ThousandEyes Integration 
Analyze Transaction Scores to understand the impact of increased user activity   Video Length: 2 min 43 seconds    CONTENTS | Introduction | Video |Resources | About the presenter   An in... See more...
Analyze Transaction Scores to understand the impact of increased user activity   Video Length: 2 min 43 seconds    CONTENTS | Introduction | Video |Resources | About the presenter   An increase in user activity can create a larger impact of degraded performance, should the systems not be fully tuned properly. A small problem could easily lead to an exponential one if not addressed quickly.   The AppDynamics Transaction Scorecard helps you focus on any issue that grows as user access grows by providing a simple yet effective indication of how transactions perform according to one of five categories: normal, slow, very slow, stalled, or those that have errors.   The scorecard directs you to the snapshots that provide the details necessary to understand where the largest surface area issue is, which helps fix things quickly.   Additional Resources  Learn more about trace analysis in the documentation.   Monitor the performance of business transactions  Troubleshoot business transactions performance with transaction snapshots  About presenter Douglas Lindee Douglas Lindee joined Cisco AppDynamics as a Field Architect in late 2021, having a 20+ year career behind him in systems, application, and network monitoring, event management, reporting, and automation — most previously on an extended engagement focusing on AppDynamics. With this broad view of monitoring solutions and technology, he serves as a point of technical escalation, assisting sales teams to overcome technical challenges during the sales process.
What user permissions must be granted when installing Java Agent binaries? While installing Java Agents, it is mandatory for the user running JVM to have certain access permissions for agent binari... See more...
What user permissions must be granted when installing Java Agent binaries? While installing Java Agents, it is mandatory for the user running JVM to have certain access permissions for agent binaries. In this article, find an approach for assigning these permissions, which can be validated in the best order for the environment in which Agents are being installed.  In this article...  How do I assign mandatory permissions for agent binaries? Examples  Additional resources  How do I grant required user permissions when installing agent binaries?  While installing Java agents, it is mandatory for the user running JVM to have certain access permissions to agent binaries.   The following approach can be validated for use in the best order for the environment in which Agents are being installed. For example, you can make slight adjustments based on the OS version, type, and allowed security privileges at the environmental level.  The user must have write privileges to the  conf  and  logs  directories in the Java Agent home. One way to achieve this is to install the agent as the same user that owns the JVM. Provide admin or 777 to agent binaries recursively. Writable permissions to conf/logs and read permissions for all files recursively. Executable permissions to the javaagent.jar file being referenced in the installation. For example: For RHEL9 with SE Linux turned ON Executable permissions to javaagent.jar will be needed for all users. ( chmod a+rx <path>/javaagent.jar ) For IBM WAS running on AIX/UNIX/Linux Try set agent binaries user as JVM/WAS running user to avoid user permissions conflicts.   Additional resources See Install the Java Agent in the documentation 
Use automation capabilities to determine whether purchase abandonment occurs more with specific users, devices, or geographies  Video Length: 2 min 18 seconds  CONTENTS | Introduction | Video... See more...
Use automation capabilities to determine whether purchase abandonment occurs more with specific users, devices, or geographies  Video Length: 2 min 18 seconds  CONTENTS | Introduction | Video | Transcript | Resources | About the presenter  When it comes to e-commerce cart abandonment, it's important to be able to quickly find patterns in whether those abandoning share common characteristics—such as device type or geography—that could inform us of technical issues affecting the digital experience of a subset of customers.   Cisco AppDynamics Experience Journey Map makes this task easy with a Sankey visualization diagram showing at-a-glance which site journeys have the most traffic.       Video Transcript Spoiler (Highlight to read) 00:00:00 - 00:00:38  When it comes to e-commerce cart abandonment, it's important to be able to quickly find patterns in whether those abandoning share any common characteristics—such as device type or geography—that could inform us whether there are technical issues affecting the digital experience for a subset of customers. The Experienced Journey Map in AppDynamics makes this task easy.   The Experience Journey Map uses a Sankey diagram to visually indicate at-a-glance which journeys through the site have the most traffic.  00:00:39 – 00:01:01  Each step in a journey denotes the drop-off rate at that step, so we can understand immediately where most abandonment is occurring in each journey. Having identified that most abandonment is occurring during the checkout step, we click through the drop off rate and are automatically shown additional context to help easily and quickly determine if abandonment is disproportionately occurring for any specific set of users, device types, geographies and so on.     00:01:01 - 00:01:22  The session data for abandoning users is automatically aggregated and sorted in descending order, readily surfacing any patterns. We can easily see that users with iPhone 12 devices abandoned nearly twice as often compared to users visiting with any other device model. Further, we can also see that a higher proportion of customers in the U.S. are abandoning compared to other geographies.     00:01:23 - 00:01:49  We can review more detailed per customer insights by selecting the corresponding radio buttons to define the specific set of users we are most interested in and clicking analyze: AppDynamics loads of full session data that was captured for iPhone 12 users located in the U.S. We can use AppDynamics advanced analytics capabilities to further refine the set of abandoning customers, for instance by selecting a specific region within the U.S. to deeply understand how the customers of interest were interacting with the mobile app at each step in their journey.     00:01:50 – 00:02:18  This user experience data can also be correlated with the backend performance data for an end-to-end view of the user experience, from browser or mobile device through the network and into the backend services responsible for fulfilling the request. This allows ITPs to quickly rule out performance issues as being a factor in abandonment.  00:00:00 - 00:00:38  When it comes to e-commerce cart abandonment, it's important to be able to quickly find patterns in whether those abandoning share any common characteristics—such as device type or geography—that could inform us whether there are technical issues affecting the digital experience for a subset of customers. The Experienced Journey Map in AppDynamics makes this task easy.   The Experience Journey Map uses a Sankey diagram to visually indicate at-a-glance which journeys through the site have the most traffic.    00:00:39 – 00:01:01  Each step in a journey denotes the drop-off rate at that step, so we can understand immediately where most abandonment is occurring in each journey. Having identified that most abandonment is occurring during the checkout step, we click through the drop off rate and are automatically shown additional context to help easily and quickly determine if abandonment is disproportionately occurring for any specific set of users, device types, geographies and so on.     00:01:01 - 00:01:22  The session data for abandoning users is automatically aggregated and sorted in descending order, readily surfacing any patterns. We can easily see that users with iPhone 12 devices abandoned nearly twice as often compared to users visiting with any other device model. Further, we can also see that a higher proportion of customers in the U.S. are abandoning compared to other geographies.     00:01:23 - 00:01:49  We can review more detailed per customer insights by selecting the corresponding radio buttons to define the specific set of users we are most interested in and clicking analyze: AppDynamics loads of full session data that was captured for iPhone 12 users located in the U.S. We can use AppDynamics advanced analytics capabilities to further refine the set of abandoning customers, for instance by selecting a specific region within the U.S. to deeply understand how the customers of interest were interacting with the mobile app at each step in their journey.     00:01:50 – 00:02:18  This user experience data can also be correlated with the backend performance data for an end-to-end view of the user experience, from browser or mobile device through the network and into the backend services responsible for fulfilling the request. This allows ITPs to quickly rule out performance issues as being a factor in abandonment.  Additional Resources  Learn more about the Experience Journey Map in the documentation:  Experience Journey Map Overview  Analyze Traffic Segments  About presenter Adam Smye-Rumsby Adam Smye-Rumsby, Cisco AppDynamics Senior Sales Engineer Adam J. Smye-Rumsby joined AppDynamics as a Senior Sales Engineer in 2018, after nearly 16 years with IBM across a variety of roles — including 5+ years as a Senior Sales Engineer in the Digital Experience and Collaboration business unit. Since then, he has helped dozens of enterprise and commercial customers improve the maturity of their application monitoring practices.    More recently, Adam has taken on the challenge of developing subject-matter expertise in the application security market.  He has contributed to two published books on the use of Java technology, and holds patents in AI/ML, Collab, VR and other technology areas. Reach out to Adam to learn more about how AppDynamics is helping Cisco customers secure their applications in an ever-changing threat landscape. 
When should I opt to use Business Metrics and how do I configure them?  Organizations commonly track KPIs like Total Revenue, Order Count, etc. to monitor the health of their business. These KPIs ... See more...
When should I opt to use Business Metrics and how do I configure them?  Organizations commonly track KPIs like Total Revenue, Order Count, etc. to monitor the health of their business. These KPIs influence the organization's spending decisions and allow the analysis of the impact of their spending. It is also desirable to track these KPIs in near real-time rather than waiting for periodic reports. Recently, Cisco AppDynamics released support for Business Metrics as part of the Cisco Cloud Observability Platform. This brings about a powerful capability for business owners to monitor application performance. It also enables users to slice business metric data into segments and set up health rules. In this article… Why Business Metrics? How do Business Metrics work? Business Metrics best practices Additional resources Why Business Metrics? The obvious question that arises is: what is the need for the feature and why can’t Custom Metrics or Span Metrics do the job? Custom Metrics are emitted from the application and are usually aggregated in a time series for presentation. The measurements are usually generated in the application with the help of an OpenTelemetry Metrics SDK and usually have dimensions attached. The measurements are aggregated in a time series fashion within an observability solution. Span Metrics are emitted by a custom, which can be used to scrape span attributes to generate metric measurements with the required dimensions. This approach also allows you to emit metric measurements with the desired dimensions. It can potentially be used to build a custom collector that emits the measurements by processing the entire trace. However, it may require code changes and multiple iterations to get the desired functionality in place. Custom Metrics or Span Metrics may serve your purpose very well if the metric of interest and the associated dimensions originate from a single span and you know which span to find it in. However, in modern distributed architectures in the cloud, an application consists of multiple microservices. A single business transaction can have spans across 10s or 100s of microservices. In such deployments, it is not easy to correlate different dimensions for the same metric across spans. Business Metrics in Cisco Cloud Observability solves this problem by traversing business transaction spans and collecting the metric and all its dimensions as part of a single measurement. This can be extremely useful as users can now slice and dice metric data based on the dimensions to gain deep insights into the performance of their business. Business Metrics also has an easy configuration experience with prescriptive templates for business owners to easily configure the metrics for their use cases. Another advantage of this approach is that the user also gets a visual data preview during the configuration, allowing them to select the attribute for generating measurements as well as the dimensions to segment the data. Back to TOC How do Business Metrics work? Let us walk through a use case based on the sample OpenTelemetry demo application. You can follow this by getting access to AppDynamics Cloud Observability integration. Business Use case: Track the Total Revenue for this e-commerce application and then further analyze the data based on shipping zip code. 1. Instrumentation | 2. Configuration | 3. Analysis of metric data | 4. Health rule setup | 5. Health alert analysis Step 1: Instrumentation The business owner collaborates with developers to instrument the checkout and shipping service. This involves instrumenting order amount and zip code information to be sent as part of the Open Telemetry span attributes as follows: Figure 1 Instrumentation of checkout service with app.order.amount attribute on line 276 Figure 2 Instrumentation of shipping service with app.shipping.zip_code attribute on line 77 The above changes result in the app.order.amount and app.shipping.zip_code being added as span attributes for the respective spans for checkout and shipping services. You can visualize the position of those attributes below: Figure 3 Service map for opentelemetry-demo app. Attributes of interest annotated in red. Figure 4 Trace view of checkout business transaction. Attributes of interest annotated in red. While processing the trace in the cloud, the attributes are scraped and presented for configuration. Step 2: Configuration The DevOps owner goes to the checkout business transaction page, navigates to the business metric section, and begins configuration. The “Sum” template is selected for the use case and the metric attribute is selected. The list of metric attributes and data type is generated using the attributes scraped from the trace. NOTE | The attributes with only summable data type are displayed in the list. The attribute for the zip code is a string and not listed here. Figure 5 Metric attribute list presented to the user for configuration. After selecting the desired title for the metric template, the segmentation attributes are selected. In this case, the attribute of interest is zip code, so that is selected. This completes the configuration for the selected use case. Figure 6 Select option for segmentation of metric data. Step 3: Analysis of metric data The business owner can now use the configured metric for business analysis. The metric appears on the business transaction page in the Business Metrics section. The business owner can examine the metric data on a timeline as per the global time selector. There are options to show a 15-day, 30-day, or 90-day baseline. For analysis based on segments, the user clicks “Show Segments” to analyze revenue based on zip codes. The individual values can be analyzed by selecting them on the x-axis. Figure 7 Animation showing business metric analysis. Step 4: Health rule setup Users can set up health rules to ensure the metric is in the expected range. They should follow the same health rule setup flow as for any other business transaction metric. Figure 8 Health rule configuration based on BT entity and associated business metric. Figure 9 Setting up evaluation condition based on deviation from baseline. Step 5: Analysis of health alerts Based on the health rules set up above, the user gets notified of any health rule violation. The user can go to the business transaction page and click on the health rule violation widget that displays the violating metric. Figure 10 On clicking the health violation timeline, the violating metric Total Revenue is displayed. The user can further scroll down to find the cause for the drop by investigating the performance data. This single pane of glass that correlates business metrics with performance data allows the user to find business-affecting performance issues and prioritize them. In this example, the increase in Average Response Time is correlated with the drop in Total Revenue. Figure 11 Note that the revenue is trending lower as the average response time increased. Back to TOC Best practices During the instrumentation of attributes on spans, we recommend adding a prefix to business attribute names that are distinct from those found in the OTel semantic convention. This will help you to find business attributes during configuration. For example: In the OTel demo, the app.* prefix helps in finding the business attributes. We recommend assigning unique attribute names on each span. While gathering attributes from spans of a trace, if a duplicate attribute name is seen, then the latest value is reported. Figure 12 Attributes with app.* prefix are business attributes and http.* prefix are auto-instrumented attributes. While choosing the attributes as dimensions for segmentation, we recommend selecting attributes that don’t have an exceedingly high cardinality. This makes it easier to analyze the data in a segmented view. Additional resources See Configure Business Metrics, under Application Performance Management, Business Transactions in the documentation
How can you leverage a monitoring-as-code mechanism to initiate new workload monitoring, or to create new visualizations?       CONTENTS | Introduction | Video |Resources | About the presente... See more...
How can you leverage a monitoring-as-code mechanism to initiate new workload monitoring, or to create new visualizations?       CONTENTS | Introduction | Video |Resources | About the presenter  Video Length: 3 min 33 seconds  In this demo, see how Cisco AppDynamics can integrate with Flux CD (Continuous Delivery)—a GitOps Kubernetes operator tool that offers a simple and efficient interface to synchronize manifests within CD workflows from GitHub repositories.    See how easy it is to upgrade existing software with just a few lines of code such as when instrumenting new workloads with the OpenTelemetry Agent or customizing a Grafana dashboard.  Additional Resources  Learn more about OpenTelemetry auto-instrumentation in the documentation.  About presenter Charles Lin Charles Lin, Cisco AppDynamics Field Domain Architect Charles is a Field Domain Architect at Cisco AppDynamics. He joined Cisco as a Senior Sales Engineer in 2019. Since then, he has helped large enterprises and financial sector customers improve their monitoring practices. As a Field Domain Architect, he focuses on Cloud Native and Open Telemetry best practices and helping fellow team members overcome technical challenges. He holds multiple patents in the area of IT Monitoring and Operations and is a certified Cisco DevNet Associate.
In September, v23.9 included enhancements to FSO Platform Developer Support, Cloud Native Application Observability,  SaaS Controller and Agent, and On-premises Platform. WATCH THIS PAGE FOR UPDA... See more...
In September, v23.9 included enhancements to FSO Platform Developer Support, Cloud Native Application Observability,  SaaS Controller and Agent, and On-premises Platform. WATCH THIS PAGE FOR UPDATES — Click the Options menu above right, then Subscribe Want to receive all monthly Product Updates? Click here, then subscribe to the series In this article…  What new product enhancements are there this month? FSO | Cloud Native Application Observability | Agents | SAP | SaaS Controller | On-premises Controller |  Where can I find additional information about product enhancements?  Advisories and Notices Resolved and known issues Essentials What new product enhancements are there this month? This month, there were enhancements to  FSO Platform Developer Support, Cloud Native Application Observability,  SaaS Controller and Agent, and On-premises Platform. Find the highlights under each heading below. TIP | Each product category below includes a link to the product's complete Release Notes, where you can find more detail for each enhancement.  Full-Stack Observability (FSO), Developer Support NOTE | There is no FSO Platform release for August 2023. For Developer Support enhancements, see the 23.9 FSO Platform Developer Support Release Notes. Accounts sign-in process The sign-in process for Cloud Native Application Observability customers has been updated. New customers will sign in through a new URL, while existing customers will continue using the existing URL. No action is required from users, who will be automatically directed to their correct login page.    Anomaly Detection Anomaly Detection enabled for Kubernetes entities Anomaly Detection is now enabled for various Kubernetes entity types. This feature allows automatic detection of anomalies and provides options for customization such as linking HTTP request actions, tuning sensitivity levels, and testing anomaly detection in different environments.  App Root Cause Analysis using Anomaly Detection You can now view Pod readiness and liveness probe information can on the Properties panel of Pods, Workloads, Clusters, and Namespaces.   Cloud service expansions We’ve extended  now extend monitoring support for the following cloud services:  Amazon SNS   AWS KDA Flink application support   AWS Glue   GCP Cloud Run  GCP Cloud SQL  GCP Load Balancers    Differentiate between Lambda and APM domains Now, you can differentiate between Lambda and APM domains, filter by Lambda entities, and view Lambda details in the unified service detail view and via the Properties panel.    Grafana plugin The new version of the Grafana plugin includes the Include All toggle option.   Infrastructure Collector The Cisco AppDynamics Infrastructure Collector now supports monitoring of Amazon ECS tasks and containers.   New artifacts New versions of various AppDynamics artifacts have been released, including:   OTel Docker images  Cluster Collector Docker images  Infrastructure Collectors Docker images  AppDynamics Operator Docker image  AppDynamics Helm charts   Observe page enhancements Enhancements have been made to entity Observe pages, including alert messages for unknown health rules and the ability to view the Violating Metrics chart for a metric expression associated with a health rule   Pattern detection for containers on Logs Pattern detection is now available for containers on the Logs page, and the Log Pattern tab has been renamed to Patterns.      Specify attribute timestamp format for HTTP requests When creating an HTTP request action, you can now specify the timestamp format for certain attributes.      Back to TOC | To Essentials   Cloud Native Application Observability* enhancement highlights NOTE | See the Cloud Native Application Observability Release Notes page for the complete v23.9 enhancement details—released September 27, 2023.  NOTE | As of 11/27/2023, now *Cisco Cloud Observability  Accounts sign-in process  The sign-in process for Cloud Native Application Observability customers has been updated. New customers will sign in through a new URL, while existing customers will continue using the existing URL. No action is required from users, who will be directed automatically to their correct login page. Anomaly Detection enabled for Kubernetes entities Anomaly Detection is now enabled for various Kubernetes entity types. This feature allows automatic detection of anomalies and provides options for customization such as linking HTTP request actions, tuning sensitivity level, and testing anomaly detection in different environments. Cloud Services Expansion   We now support monitoring the following cloud services   Amazon SNS   AWS KDA Flink application support   AWS Glue   GCP Cloud Run  GCP Cloud SQL  GCP Load Balancers   Amazon ECS for Infrastructure Collector The Cisco AppDynamics Infrastructure Collector now supports monitoring of Amazon ECS tasks and containers. Grafana plugin  The 23.9 version of the Grafana plugin includes the Include All option toggle. App Root Cause Analysis using Anomaly Detection You can now view Pod readiness and liveness probe information can on the Properties panel of Pods, Workloads, Clusters, and Namespaces. New artifacts New versions of various AppDynamics artifacts have been released, including: OTel Docker images Cluster Collector Docker images Infrastructure Collectors Docker images AppDynamics Operator Docker image AppDynamics Helm charts Observe page enhancements Enhancements have been made to entity Observe pages, including alert messages for unknown health rules and the ability to view the Violating Metrics chart for a metric expression associated with a health rule. Specify attribute timestamp format for HTTP requests When creating an HTTP request action, you can now specify the timestamp format for certain attributes.  Differentiate between Lambda and APM domains Now, you can differentiate between Lambda and APM domains, filter by Lambda entities, and view Lambda details in the unified service detail view and via the Properties panel.  Back to TOC | To Essentials   Agent enhancement highlights NOTE | See the AppDynamics v23.9 APM Platform (SaaS) Release Notes for the complete September 2023 enhancement details.  Analytics Agent  GA 23.9  September 15, 2023  This release replaces the deprecated javax.el 3.0.0 library with jakarta.el 3.0.4. Cluster Agent  GA 23.9  September 26, 2023  The enhancements in this release include:  Cluster Agent uses container ID to correlate APM entities with Infrastructure entities. For Kubernetes versions >=1.25, you must configure the auto-instrumentation configuration file because container runtime uses cgroup v2 API in Kubernetes version 1.25  onwards. See Correlate Application Containers with App Agents (For Kubernetes version 1.25).    You can use the instructions mentioned at Install Cluster Agent with OpenShift Operator Bundle and Install Infrastructure Visibility with OpenShift OperatorHub Bundle to install Cluster Agent and Infrastructure Visibility respectively with the OpenShift OperatorHub bundle.  Flutter Agent  GA 23.9 September 11, 2023  Flutter Agent is now compatible with Dio 5.1.0. IBM Integration Bus Agent  GA 23.9  September 27, 2023  With this release, Java Agent includes support for query statement on Couchbase database exit calls details.    There is now a new option, View Detection Rule in Business Transaction > Actions. Click this option to view the custom detection rule associated with a business transaction. See View Business Transactions in the documentation.  Private Synthetic Agent  GA 23.9  September 28, 2023  This release supports Private Synthetic Agent deployment in Red Hat OpenShift. See Set up PSA in Red Hat OpenShift in the documentation. .NET Agent  GA 23.9  September 29, 2023  This release includes JIT instrumentation on Azure App Service with the coordinator.  Back to TOC | To Essentials   SaaS Controller enhancement highlights NOTES | See the AppDynamics v23.9 APM Platform SaaS Controller Release Notes page for the complete September 2023 enhancements.  Alert and Respond GA 23.9 September 29, 2023 When creating or editing an email action without a template, you can now add details including the name of the email action, preferred time zone, and the To, Cc, and Bcc recipients list.   Cisco Secure Application GA 23.9 September 29, 2023 Cisco Secure Application now includes support for email-based alerts.   Cluster Monitoring GA 23.9 September 29, 2023 When monitoring failed pods, you can now hide historic pod details in the new Historical Pods section. Find it under Pods > Filters in the Cluster Details view.   View Detection Rule option GA 23.9 September 29, 2023 View the custom detection rule associated with a business transaction with the View Option Rule option, found in Business Transaction > Actions.   End User Monitoring GA 23.9 September 29, 2023  The End User Monitoring update upgrades EUM to Java 17 to ensure that Java supported services remain secure and efficient.   Back to TOC | To Essentials   Where can I find additional information about product enhancements?  In Documentation, each product category has a Release Notes page where enhancements are described in detail on an ongoing basis. Links to the most recent versions are:  Cisco Full Stack Observability  Cloud Native Application Observability  AppDynamics APM Platform 23.x  On-premises AppDynamics APM Platform  Accounts Administration AppDynamics SAP Agent  Back to TOC | To Essentials Resolved issues DID YOU KNOW? You can find ongoing lists of Resolved Issues on each Release Notes page by version. Sort the list on each page by headings, including key, product, severity, or affected version(s). Find Resolved Issues by Product here:  • Cisco Full Stack Observability (FSO) Release Notes  • Cloud Native Application Observability Release Notes  • AppDynamics APM Platform, Resolved Issues for Agents and SaaS Controller  • On-premises AppDynamics APM Platform  • Release Notes for Accounts and Licensing  • AppDynamics SAP Agent Release Notes Back to TOC | To Essentials Advisories and Notifications Upcoming End of Support for Cluster Collectors <23.10 and required upgrade for continued Kubernetes monitoring   Cluster Collectors <23.10 are deprecated with support ending January 30, 2024. After this date, monitoring Kubernetes entities via the relationship pane will require an upgrade to Cluster Collector version >=23.10.  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 CAN'T FIND WHAT YOU'RE LOOKING FOR? NEED ASSISTANCE? Connect in the Forums
Synthetic testing provides proactive email and text notification before end-user performance is affected   CONTENTS | Introduction | Video |Resources | About the presenter  Video Length: 2 ... See more...
Synthetic testing provides proactive email and text notification before end-user performance is affected   CONTENTS | Introduction | Video |Resources | About the presenter  Video Length: 2 min 46 seconds  E-commerce DevOps teams can use AppDynamics to monitor the health and performance of their applications, receiving alerts on issues before significant business impact. Devs can use AppDynamics to provide automatic email and text notifications about such issues. In this demo, see how you can harness a custom email alert notification to view anomalous synthetic transaction events within the Browser App Dashboard, drill into the Heath Rules violation page, and link to a custom dashboard to troubleshoot an unexpected increase in synthetic end-user response time for shopping cart activity.   Additional Resources  Learn more about these related Cisco AppDynamics topics in the documentation:  Configure and Manage Alerting Templates  End User Monitoring: Browser App Dashboard   Alert and Respond: Troubleshoot Health Rule Violations  Custom Dashboards Overview: Custom Dashboards   Synthetic Monitoring Overview: Synthetic Monitoring  About presenter John Helter John Helter, Senior Sales Engineer John joined Cisco AppDynamics in October of 2021 as a Federal Public Sector Solutions Engineer. Despite the opportunity being quite a collection of "firsts" (first Sales based role, first job in the "Tech Industry," and first-time changing jobs during a global pandemic), John is thrilled he took a chance and considers himself extremely fortunate to be an AppDynamo-Cisconian and to work day in and day out with such an amazing team! Primarily supporting current and potential U.S. Department of Defense customers, John is focused on the AppD On-Prem product (which is actually a self-hosted solution that can be deployed in “The Cloud,” on virtualized machines and/or within physical on-premises environments). Feel free to reach out to him if you have any AppDynamics-related on-prem questions, need deployment support, or to share as many “dad-jokes” as humanly possible!
When a payment process times out, customers may not complete their purchases. How can line-of-business application owners quantify the revenue risk? Video Length: 2 min 28 seconds  CONTENTS | ... See more...
When a payment process times out, customers may not complete their purchases. How can line-of-business application owners quantify the revenue risk? Video Length: 2 min 28 seconds  CONTENTS | Introduction | Video |Resources | About the presenter  When a payment process times out, customers may not complete their purchases. How can line-of-business application owners quantify the revenue risk? In this demo, Matt Schuetze uses AppDynamics Business iQ Analytics to quantify revenue impact for payment processing timeouts across a geographical market area. This analysis helps identify the areas where the largest revenue losses occur.   Additional Resources  Learn more about Using Analytics Data in the documentation. Check out Six Business iQ use cases that drive application and business performance on the website About presenter Matt Schuetze Matt Schuetze Field Architect Matt Schuetze is a Field Architect at Cisco on the AppDynamics product. He confers with customers and engineers to assess application tooling choices and helps clients resolve application performance problems. Matt runs the Detroit Java User Group and the AppDynamics Great Lakes User Group. His career includes 10+ years of speaking periodically at user groups and industry trade shows. He has a Master’s degree in Nuclear Engineering from MIT and a Bachelor’s degree in Engineering Physics from the University of Michigan.
Integrate AppDynamics with the CICD pipeline using queries that retrieve metrics to contain potential change failures and protect the business from their impact   CONTENTS | Introduction | Vi... See more...
Integrate AppDynamics with the CICD pipeline using queries that retrieve metrics to contain potential change failures and protect the business from their impact   CONTENTS | Introduction | Video |Resources | About the presenter  Video Length: 2 min 22 seconds  How can continuously querying *Cloud Native Application Observability using Flagger (a feature management tool) give you the key metrics you need to see whether your production environment change was successful? In this demonstration, see how Flagger—a feature management tool—can continuously query Cloud Native Application Observability for the key metrics you can use to determine whether a change was successful. Use AppDynamics’ free plugin to view these metrics in a Grafana dashboard. When Cloud Native Application Observability indicates increasing error rates after a change, see how to roll back the change or turn off the feature flag.   As of November 27, 2023, the Cisco Full-Stack Observability (FSO) Platform is now the Cisco Observability Platform, and Cloud Native Application Observability is now Cisco Cloud Observability powered by the Cisco Observability Platform. These name changes better align our products with the Cisco portfolio and with our business strategy. Additional Resources  Read more about the free Grafana plugin in the AppDynamics Blog  Learn more about Anomaly Detection in the documentation, including  Health Rules and Configuration of Alerts, under Monitor Entity Health Monitor Anomalies  Determine the root cause of an anomaly  About presenter Charles Lin Charles Lin, Cisco AppDynamics Field Domain Architect Charles is a Field Domain Architect at Cisco AppDynamics. He joined Cisco as a Senior Sales Engineer in 2019. Since then, he has helped large enterprises and financial sector customers improve their monitoring practices.   As a Field Domain Architect, he focuses on Cloud Native and Open Telemetry best practices and helping fellow team members overcome technical challenges. He holds multiple patents in the area of IT Monitoring and Operations and is a certified Cisco DevNet Associate. 
 Use AppDynamics’ built-in machine learning capabilities to conduct fast and effective root cause analysis (RCA)  CONTENTS | Introduction | Video |Resources | About the presenter  Video Length:... See more...
 Use AppDynamics’ built-in machine learning capabilities to conduct fast and effective root cause analysis (RCA)  CONTENTS | Introduction | Video |Resources | About the presenter  Video Length: 2 min 16 seconds  The root cause of a performance transaction can be complex to troubleshoot, but it does not have to be. By using AppDynamics’s built-in machine learning capabilities, we can quickly identify Health Rule violations triggered by transaction response times deviating from their baseline and then combine those with diagnostic capabilities that get us to the specific cause. We are able to drill down into the relevant snapshots to see which method and specific line of code is to blame.   In just a few moments, we demonstrate how to data mine the root cause of a performance issue by leveraging the AppDynamics AI engine to gain insights into the exact line of code causing problems.     Additional Resources  Learn more about Anomaly Detection in the documentation. About presenter Vivek Inbakumar  Vivek Imbakumar, Sales Engineer Vivek Inbakumar joined AppDynamics as a Sales Engineer in 2021. He got into the world of IT upon graduating as a computer engineer and subsequently completed his executive MBA from the University of London.  With his passion for staying close to customers combined with strong technical knowledge - sales engineering offered the best of both worlds. Based out of the Cisco Dubai office, he helps customers across the Middle East and Africa to improve their application monitoring practices.   He is also a vital member of the Cloud Native Application Observability Champions team. Here, he extends his knowledge to empower both colleagues and customers, demonstrating how AppDynamics' cutting-edge monitoring tools can revolutionize their approach to full-stack observability.  Vivek is driven by a core belief in the power of technology to transform businesses and improve lives. His commitment to understanding and meeting the unique needs of each customer sets him apart as a dedicated advocate for client success. 
Identify load and performance anomalies across all nodes in a tier with the Tier Metric Correlator. Use discoveries to create alerts that trigger events in your ITSM platform.   CONTENTS | Introduc... See more...
Identify load and performance anomalies across all nodes in a tier with the Tier Metric Correlator. Use discoveries to create alerts that trigger events in your ITSM platform.   CONTENTS | Introduction | Video | Resources | About the presenter  Video Length: 2 min 49 seconds  See how to simplify troubleshooting the seemingly random and uncorrelated issues that arise in complex app landscapes. Using AppDynamics Tier Metric Correlator to link unknown unknowns to business context, you can quickly and with minimal effort find both the problem and its impact.      NOTE | If this feature does not appear in your Controller instance, you can request it to be enabled by AppDynamics Support.   For on-premises environments, AppDynamics Tier Metric Correlator must be turned on at the Controller level.   Additional Resources  Learn more about the Tier Metric Correlator in the Documentation  AppDynamics SaaS 23.x | Tier Metric Correlator  AppDynamics APM Platform 23.x | Tier Metric Correlator  AppDynamics On-premise | Tier Metric Correlator About presenter Scott C. Young  Scott Young joined AppDynamics as a Sales Engineer in 2015 and has supported the pre-sales organization as an SE and SE Manager. He now leads the AppDynamics WW Field Architecture Organization.   This team includes a group of highly skilled and experienced Observability architects whose goals are "To be AWESOME at what we do, so we can LOVE what we do" while helping the SE and Sales teams architect solutions to some of the most complex Observability challenges. 
Minimize risk and maximize uptime with policies that continuously monitor vulnerabilities and automatically block attacks CONTENTS | Introduction | Video |Resources | About the presenter  Vid... See more...
Minimize risk and maximize uptime with policies that continuously monitor vulnerabilities and automatically block attacks CONTENTS | Introduction | Video |Resources | About the presenter  Video Length: 4 min 13 seconds  See how to use Cisco AppDynamics Secure Application to monitor vulnerabilities, finding and blocking attacks automatically. In this example, see how to configure a runtime policy that blocks the Log4Shell vulnerability from attack.     Additional Resources  Learn more about Cisco AppDynamics Secure Application: Monitoring Application Security Using Cisco Secure Application, in the documentation...  How do I use AppDynamics with Cisco Secure Application find vulnerabilities and block exploits, in the Knowledge Base   In the Blog: Protect cloud native application environments faster — based on business risk with Cisco Secure Application  How business acumen boosts application security  And more  About presenter Keith Richter  Keith Richter, APM Security Domain Architect Hailing from all around the Midwest, Keith Richter extended his peripatetic beginnings during six years in the US Navy, serving and experiencing rich cultures in remote sites worldwide. After his final deployment, Keith put down roots in Iowa, working at area companies including Sun Microsystems and EMC. He started at Cisco AppDynamics over 5 years ago, covering the Midwest as a Sales Engineer. In 2021, Keith moved into the Field Architecture team, leading a team of SMEs covering APM Agents, OTel and Security functionality within the AppD platform. The team currently focuses on supporting Sales, Product, and customers with our industry-leading Application Security and Runtime Protection capabilities.
DevOps teams can use Experience Journey Maps and Dashboards to diagnose and solve issues more quickly, while Business teams use them to gauge event costs and business impact ... See more...
DevOps teams can use Experience Journey Maps and Dashboards to diagnose and solve issues more quickly, while Business teams use them to gauge event costs and business impact   CONTENTS  Introduction | Video | About the presenter | Resources Video Length: 2 min 29 seconds  Ensure each user has the best mobile experience possible by understanding mobile user journeys. Bring teams together to understand how a user interacts with the mobile application in order to streamline operations and improve their experience.   By leveraging data collectors, teams can gain an even deeper understanding of specific events—for example, items in a lost shopping cart, along with their associated revenue. This information helps build a conversion chart, giving the business an indication of how severe a problem may be, to then help prioritize remediation efforts.  About presenter Tori Beaird (Forbess)  Tori Beaird (Forbess)Tori Beaird (Forbess) joined AppDynamics as a Sales Engineer in 2020. With an Industrial Distribution Engineering degree and a decade of musical theatre training - sales engineering offered the best of both worlds. Although she is a Texas native, she helps customers up and down the West Coast improve their application monitoring practices.   Within AppDynamics, Tori is a part of the Cisco Cloud Observability Champions team, enabling peers and customers alike on AppDynamics’ latest monitoring tool. With a passion for teaching others, Tori continues to develop and present internal training sessions to the broader Cisco organization.   When Tori isn't at work, you will find her flying Cessna 182s, volunteering with her church, and spending time with her beloved husband and friends!    Additional Resources  Learn more about Mobile Real User Monitoring and BusinessiQ and Analytics in the documentation. 
How do I automatically update event timestamps in an email template to a specific local time zone, accounting for daylight saving time?  Automatically update event timestamps of the events in an em... See more...
How do I automatically update event timestamps in an email template to a specific local time zone, accounting for daylight saving time?  Automatically update event timestamps of the events in an email template to align with a specific time zone’s daylight-saving time changes.  In this article... SaaS Controllers and their time zones Why the need for an automatic code snippet?  Limitations and Considerations  How does the code snippet work?  How to use the code snippet?  Code snippet    SaaS controllers and their time zones  SaaS customers rely on the time zone configured in the Controller to determine the offset between their local time zone and the one used by the Controller. Therefore, you need to manually modify the timestamp value in each template (email or HTTP) and keep it updated according to whether daylight saving is active or not.    Why the need for an automatic script?  Using an automatic script rather than relying on a manual process to update the timestamp value eliminates potential update gaps for twice-yearly daylight-saving time updates.  If daylight-saving time is active, customers need to manually update the timestamp value, which can be error-prone and requires being done twice a year.    Considerations and limitations While this solution implements automated updates for US daylight saving time, you can use it as a template for daylight saving schedules in any other country.  In the US:  Daylight saving begins on the first Sunday of October at 2:00 a.m.  Daylight saving ends on the second Sunday of March at 2:00 a.m.  The code currently works for full-hour offsets, but it can be updated to work with partial-hour offsets.  This implementation considers that the SaaS controller is using the UTC time zone.    How does the code snippet work?  Daylight Savings is applied during December, January, and February.  During October, the first step is to find the date of the first Sunday of the month. If the current day is on or after the first Sunday after 2:00 am, daylight saving is applied.  During March, the first step is to find the second Sunday of the month. If the current day is on or before the second Sunday before 2:00 am, daylight saving is applied.  Then, modify the time zone acronym from UTC to the local acronym.    How do I use the time change code snippet?  Define a Custom Templating Variable named localTZ, which will store the customer’s local time zone acronym (for example: ET for Eastern Time).  Define a Custom Templating Variable named offset, which stores the value of the time difference between the SaaS controller’s time zone and customer’s time zone without daylight saving.  In the template, use the code defined in section: Code  NOTE | the code is using $latestEvent.eventTime as initial time value  NOTE | The index of the months and weekdays are zero based, so January is index 0 and December is index 11, and the week starts on Sunday with 0 and ends on Saturday with 6.  Example of the variable declaration in the Custom Templating Variables Code  NOTE | If required, delete all comments.  ## Variable declaration  #set($date = $latestEvent.eventTime)  #set($month = $date.getMonth())  #set($day = $date.getDate())  #set($weekDay = $date.getDay())     ## By default, the offset is applied to the hours variable  #set ($newHours = ${date.getHours()} - $offset)  #set($daylightSavingOffset = $offset + 1)     ## In the months of January, February, and December, the daylight-saving time is applied  #if($month == 11 || $month == 0 || $month == 1)       #set($newHours = ${date.getHours()} - $daylightSavingOffset)  #end     ## In the month of October, it is required to find the first Sunday of the month to verify if the daylight saving time needs to be applied  #if($month == 10)       #set($tempDate = $latestEvent.eventTime)       #set($firstSunday = $weekDay)          ## Loop through the first 8 days of the month to find the first Sunday of the month       #foreach($tempDay in [1..8])            $tempDate.setDate($tempDay)            #set($tempWeekDay = $tempDate.getDay())               ## If the current day we are looping is Sunday we store that day and break the loop            #if($tempWeekDay == 0)                 #set($firstSunday = $tempDay)                 #break            #end       #end          ## If the current day is after the first Sunday of October, the daylight-saving time is applied       #if($day > $firstSunday)            #set($newHours = ${date.getHours()} - $daylightSavingOffset)       ## If the current day is the first Sunday of Octuber, the daylight-saving time is only applied if the current hour is or has passed 2:00 a.m       #elseif($day == $firstSunday && $newHours >= 2)            #set($newHours = ${date.getHours()} - $daylightSavingOffset)       #end  #end     ## In the month of March, it is required to find the second Sunday of the month to verify if the daylight-saving time needs to be applied  #if($month == 2)       #set($tempDate = $latestEvent.eventTime)       #set($secondSunday = $weekDay)          ## Variable use to count the number of Sundays that have been looped       #set($counter = 0)          ## Loop through the first 15 days of the month to find the second Sunday of the month       #foreach($tempDay in [1..15])            $tempDate.setDate($tempDay)            #set($tempWeekDay = $tempDate.getDay())               ## If the current day we are looping is Sunday we need to increase the counter if looped Sundays            #if($tempWeekDay == 0)                 #set($counter = $counter + 1)                    ## If the number of looped Sundays is 2, it means that the second Sunday of the month has been found, the day is stored, and the loop stopped                 #if($counter == 2)                      #set($secondSunday = $tempDay)                      #break                 #end            #end       #end          ## If the current day is before the second Sunday of March, the daylight-saving time is applied       #if($day < $secondSunday)             #set($newHours = ${date.getHours()} - $daylightSavingOffset)       ## If the current day is the second Sunday of March, the daylight-saving time is only applied if the current hour has not passed 2:00 a.m       #elseif($day == $secondSunday && $newHours < 2)            #set($newHours = ${date.getHours()} - $daylightSavingOffset)       #end  #end ## Generate the new date using the new hours with the offset  $date.setHours(${newHours})  #set ($dateString =${date.toString()})  ## Change the timezone acronym  #set ($replacedDateString=${dateString.replace('UTC',$localTZ)}) 
You can use data collectors to measure whether a new feature improves or degrades performance. CONTENTS  Introduction | Video | Resources | About the presenter  Video Length: 5 min 5 seconds  ... See more...
You can use data collectors to measure whether a new feature improves or degrades performance. CONTENTS  Introduction | Video | Resources | About the presenter  Video Length: 5 min 5 seconds  Leverage AppDynamics analytics to determine how a new feature introduced within an application proves to be an improvement or degradation. By creating and leveraging data collectors to look for a specific flag in a release, a new parameter or attribute, that indicates whether a feature is enabled, one can quickly gain insights as to whether there has been a performance improvement.   Additional Resources  Learn more about Configure Manual Data Collectors in the documentation.  About presenter Ivan Alba  Ivan AlbaLiving in Milan, Italy, Ivan is a Sales Engineer in the Southern Europe region. He handles all customer segments in Italy – from enterprise to commercial to public sector.   After starting out as an embedded software developer in the Telecom industry, he made the move to presales and sales to add a customer relationship role. A music-lover, he plays guitar and other instruments, enjoys landscape and astrophotography, and plays tennis, soccer, and many other sports.
See how you can detect memory leaks with Automatic Leak Detection, and how you may be able to resolve the issue before a restart is required.   CONTENTS | Introduction | Video |Resources | About ... See more...
See how you can detect memory leaks with Automatic Leak Detection, and how you may be able to resolve the issue before a restart is required.   CONTENTS | Introduction | Video |Resources | About the presenter  Video Length: 2 min 24 seconds  When Automatic Leak Detection is enabled, Ops teams can identify and diagnose memory leaks within the JVM and coordinate with their Dev teams to resolve the code-based causes they uncover.       Additional Resources  Learn more about Automatic Leak Detection for Java in the documentation.  About presenter Tori Beaird (Forbess)  Tori Beaird (Forbess)Tori Beaird (Forbess) joined AppDynamics as a Sales Engineer in 2020. With an Industrial Distribution Engineering degree and a decade of musical theatre training - sales engineering offered the best of both worlds. Although she is a Texas native, she helps customers up and down the West Coast improve their application monitoring practices.   Within AppDynamics, Tori is a part of the AppDynamics Cloud Native Application Observability Champions team, enabling peers and customers alike on AppDynamics’ latest monitoring tool. With a passion for teaching others, Tori continues to develop and present internal training sessions to the broader Cisco organization.   When Tori isn't at work, you will find her flying Cessna 182s, volunteering with her church, and spending time with her beloved husband and friends! 
WATCH THIS PAGE FOR UPDATES — Click the Options menu above right, then Subscribe Want to receive all monthly Product Updates? Click here, then subscribe to the series In August, v23.8.x enhanc... See more...
WATCH THIS PAGE FOR UPDATES — Click the Options menu above right, then Subscribe Want to receive all monthly Product Updates? Click here, then subscribe to the series In August, v23.8.x enhancements included FSO Platform Developer Support, *Cloud Native Application Observability,  SaaS Controller and Agent enhancements—including SAP Agent updates, and On-premises Controller upgrades. *Now, Cisco Cloud Observability 11/27/2023 In this article…  What new product enhancements are there this month? FSO | Cloud Native Application Observability | Agents | SAP | SaaS Controller | On-premises Controller |  Where can I find additional information about product enhancements?  ADVISORY | Cluster Agent Dockerfiles and Charts Github repositories are moving Resolved and known issues What else should I know about? Essentials What new product enhancements are there this month? In this article, each product enhancement highlights section below will include links to the referenced Release Notes page. Where available, links to the specific version will be included. ENHANCEMENT HIGHLIGHTS FOR: FSO | Cloud Native Application Observability |   | Agent | SaaS Controller | On-premises Controller |  Full-Stack Observability (FSO), Developer Support NOTE | There is no FSO Platform release for August 2023. For Developer Support, see the 23.8 FSO Platform Developer Support Release Notes, which includes details regarding the highlights below. FSO Enhancements  Access Management is live  New expressionVersion field available in the HealthRules template, expression version language 2. See Health Rules Schema in the FSO Developers Documentation.  NOTE | Health Rules language v1 is now deprecated  FSO Query Service API was updated to v1.3.0, and several fields were added    FSOC Updates  NOTE | FSOC has switched to golang v 1.20. If you are building it locally, you must upgrade.  New commands include:  fsoc config delete deletes a context from the fsoc config file  fsoc optimize servo-logs retrieves logs for currently running Servo agents  fsoc version recognizes locally built versions  fsoc knowledge get supports paginated results  fsoc solution status provides faster, parallel retrieval of status  fsoc melt supports typed attributes  fsoc optimize supports events, recommendations, and solution isolation  fsoc optimize delete offboards a given optimizer from optimizing its target workload, removes the configuration, frees up resources  Some fsoc solution commands have improved solution isolation support through the entype parameter    Back to TOC | To Essentials   Cloud Native Application Observability enhancement highlights NOTE | See the Cloud Native Application Observability Release Notes page for a complete list of enhancements in August 2023.  App root cause analysis with Anomaly Detection  GA 23.8.23  August 25, 2023  For entities related to BTs and Services: When you click the Anomaly Detection event on an entity’s Health Violation timeline, the anomaly call paths are now highlighted on the Flow map.  On the Flow map, easily trace call paths and examine suspected anomaly causes.  Business metrics for Business Transactions  GA 23.8.23  August 25, 2023  Visualize business insights to understand impact   Configure additional metrics—such as Average Cart Value, Total Carts Sold, and Total Cart Value—to visually correlate performance issues to business impacts, and perform segment analysis.  Cloud Services Expansion  GA 23.8.23  August 25, 2023  We now support monitoring the following cloud services   AWS DMS   More Azure services, including MariaDB (single server)  Google Cloud Platform (GCP) App Engine  Create and favorite Business Transactions  GA 23.8.23  August 25, 2023  Now, you designate favorite business transactions and also define your own. Identify and indicate which business transactions are more important to review and monitor based.  Log Collection  GA 23.8.23  August 25, 2023  The Log Collector:  Exports additional self-telemetry metrics from Filebeat, and deprecates others. See the Release Notes for a list of the Filebeat metrics exported by default. Now supports deployment on Google Kubernetes Engine (GKE) platform.  Cisco Secure Application GA 23.8.23  August 25, 2023  Security insights with Business Risk Scores   Use our Business Risk score to proactively prevent security exploits and address vulnerabilities.  Observe service-oriented investigations  GA 23.8.23  August 25, 2023  Share data with other Cloud Native Application Observability users, with specific values (Group View, Filter View, and Time Range) that remain the same when viewed. See Understand the Observe UI.  Kubernetes and App Service Monitoring  GA 23.8.23  August 25, 2023  Now, see when a pod was created for the Kubernetes entities on the Created At column of the entity list view.  Data for specific Kubernetes types are retained for 3 weeks after the entity becomes inactive:  Updates for Collectors and Artifacts  GA 23.8.23  August 25, 2023  Helm charts updated for AppDynamics Collectors and AppDynamics Operator  Orchestration Client Docker image  OTel Docker images for Linux and Windows  Cluster and Infrastructure Collectors Docker image  Back to TOC | To Essentials   Agent enhancement highlights NOTE |See the AppDynamics v23.8 APM Platform (SaaS) Release Notes and SAP Agent v23.8 Release Notes pages for the complete August 2023 enhancements.  Database Agent  GA 23.8.0  August 29, 2023  You can configure policies for the following new database events:   FAILOVER  DB_CONNECTION_DOWN  DB_CONNECTION_UP  REPLICATION_FAILURE  See Database Events Reference.  iOS Agent  GA 23.8.0  August 18, 2023  When you modify the url property of the ADEumHTTPRequestTracker object, the networkRequestCallback method returns the request and response headers.  Use the following fields to view the request and response headers:  allHeaderFields - It returns the response headers.  allRequestHeaderFields` - It returns the request headers.  Java Agent  GA 23.8.0  August 30, 2023  This release includes:  Support for OTel Java Auto-Instrumentation version 1.29.0. See Verified OTLP Open Source Versions.  Support for Apache Kafka Streams. See Java Supported Environments.  Upgrades to the following third-party components. Machine Agent  GA 23.8.0  August 28, 2023  A new option allows you to collect ServiceNow Configuration Management Database (CMDB) server tags. See Server Tagging.  There were also Bug Fixes and upgrades to third-party components aws-java-sdk-ec2, okio-jvm, and oshi-core.  .NET Agent  GA 23.8.23  August 25, 2023  Now, you can not only designate favorite business transactions, but you can also define your own. Identify and indicate which business transactions are more important to review and monitor based.  Network Agent  GA 23.8.0  August 11, 2023  Now with support for the IBM AIX operating system. See Install the Network Agent on AIX.  Python Agent  GA 23.8.0  August 11, 2023  Now with support for Open AI API monitoring. See Monitor OpenAI API with Python Agent.  The JRE and proxy libraries were updated.  SAP Agent  Several SAP releases in August were centered on bringing security insights around users, systems, and connections.  AP user login and authorization security monitoring captures and lists potentially problematic user-based security issues such as expired or unchanged passwords.   SAP system security monitoring captures KPIs as metrics (such as changed parameters and dangerous commands) and lists them in OOTB dashboards to quickly remediate.   SAP connection security monitoring identifies core connection metric issues within the ERP system and landscape for remediation.  See the v23.8 SAP Agent Release Notes page for the complete August, 2023 AppDynamics SAP Agent enhancements   And for mor more detail, refer to readme.txt files in the release zip file and individual package folders.  Other Updates  Analytics Agent v23.8.0, August 23, 2023  Apache Web Server Agent v23.8.0, August 30, 2023  C/C++ SDK v23.8 v23.8.0, August 11, 2023  Database Events v23.8.0, August 11, 2023  JavaScript Agent v23.8.0, August 11, 2023  Back to TOC | To Essentials   SaaS Controller enhancement highlights NOTES | See the AppDynamics v23.8 APM Platform SaaS Controller Release Notes page for the complete August 2023 enhancements.  Dash Studio  GA 23.8.0  August 28, 2023  Analytics metrics supported by Time Series and Metric Number widgets.  Analytics health rules supported by Health widget.  See Data Binding.    License usage  GA 23.8.0  August 14, 2023  Application Server Agents maps the number of vCPU count received from Azure App Services to corresponding licenses.  New option allows you to disable Analytics at the node level via Controller UI  See the following ThousandEyes usage information under License > Account Usage > Real User Monitoring Usage:  Tooltip that describes individual ThousandEyes events  Number of completed ThousandEyes measurements    Mutual TLS support  GA 23.8.0  August 14, 2023  AppDynamics Controller now supports the certificate change for mutual TLS authentication. See Configure and Enable Mutual TLS Authentication.    New health rule values for critical or warning criteria  GA 23.8.0  August 14, 2023  New values to define critical or warning criteria in a health rule. See Create and Configure Conditions.    Pagination in License Rule dialogs  GA 23.8.0  August 14, 2023  Listings of applications and servers within Add Rule and Edit Rule dialogs now include pagination. Loading data performance now allows infinite scrolling.    Synthetic Monitoring permission for Credential Vault monitoring  GA 23.8.0  August 28, 2023  Includes a new permission, Manage Credential Vault, to provide granular access control for managing the Credential Vault.   See Credential Vault for Web Monitoring and Credential Vault for API Monitoring    ThousandEyes integration with BRUM  GA 23.8.0  August 14, 2023  You can now manually unlink domains and stop data ingestion from ThousandEyes tests. See ThousandEyes Data Ingestion.    View affected entity name for failed HTTP request actions  GA 23.8.0  August 14, 2023  When an HTTP request action fails, you can now view the affected entity name in the resulting notification.   You can also access the affected entity’s details with the affectedEntities predefined variable in an HTTP request template or an email template. See Predefined Templating Variables.    Other Updates  SaaS Controller bug fixes   v23.8.1 (August 15, 2023), v23.8.2 (August 28, 2023)   Third-party libraries upgraded: v23.8.0 (August 14, 2023)  Jackson Databind, Nodejs, Loadash, JSoup, esapi, owasp-java-html-sanitizer, H2 Database Engine, Velocity, Google OAuth Client Library for Java, protobuf-java, Woodstox, Xstream, Apache commons, fileupload, Logback, Spring Framework    Back to TOC | To Essentials   On-prem enhancement highlights NOTE | See the On-premises Platform Release Notes pages for v23.7 and v23.8  for a complete list of the enhancements listed below.  Dash Studio  v23.7  GA July 28, 2023  Enhancements in late July 2023 provided more dashboarding capabilities and customization, including Metric Function, iFrame widget, and nested variables for tiers.  Enterprise Console  Enterprise Console v23.8 includes a new version of the Events Service, 23.7.0  EUM Server  v23.7  GA July 28, 2023  EUM Server 23.8 includes new versions of Open SSL and MySQL, now versions 3.0 and 8.x, respectively.  Private Synthetic Agent  v23.7  GA July 28, 2023  This Kubernetes container-based Private Synthetic Agent reduces infrastructure requirements by eliminating the need for an external Postgres dB. See Install the Private Synthetic Agent (Web and API monitoring)  Server action suppression  Server action suppression helps prevent alert storms when you put servers in maintenance mode.  Infrastructure-based license (IBL)  v23.7  GA July 28, 2023  New license packages confer new options to save operating costs and ease administration. See Observe License Usage and use this information to estimate your license needs.   Database visibility v23.7  GA July 28, 2023  See the extensive list of new database visibility features released in July 2023, extending: Database Monitoring Metrics, IBM dB 2, Microsoft SQL Server metrics, MySQL, Oracle Server metrics, SSL-enabled PostgresSQL dB, and more.  Fetch the audit log for the Remove literal flag in the Controller Audit Report.  In addition to changes to the UI.  Where can I find additional information about product enhancements?  In Documentation, each product category has a Release Notes page where enhancements are described in detail on an ongoing basis. Links to the most recent versions are:  Cisco Full Stack Observability  Cloud Native Application Observability  AppDynamics APM Platform 23.x  On-premises AppDynamics APM Platform  Accounts Administration AppDynamics SAP Agent  Back to TOC | To Essentials Resolved issues DID YOU KNOW? You can find ongoing lists of Resolved Issues on each Release Notes page by version. Sort the list on each page by headings, including key, product, severity, or affected version(s). Find Resolved Issues by Product here:  • Cisco Full Stack Observability (FSO) Release Notes  • Cloud Native Application Observability Release Notes  • AppDynamics APM Platform, Resolved Issues for Agents and SaaS Controller  • On-premises AppDynamics APM Platform  • Release Notes for Accounts and Licensing  • AppDynamics SAP Agent Release Notes Back to TOC | To Essentials ADVISORY | Cluster Agent Dockerfiles and Charts Github repositories are moving The AppDynamics Cluster Agent Dockerfiles and Charts Github repositories will receive maintenance support until October 31, 2023. Subsequently, the files in these repositories will be accessible through the AppDynamics download portal and the AppDynamics production artifactory, respectively.   Read more on the deprecation notices corresponding to these two Github repositories.  Back to TOC | To Essentials What else should I know about? Community Updates | University Updates |  Webinars  Community Updates  August brought a few updates to the Community. Our new site structure lays the foundation for a clearer information hierarchy. We hope it gives you a more intuitive way to find what you need in the Community.   We also launched new avatars—a better fit for the look of the site and (we hope) a pleasing change.   This Product Update series is seeing an evolution in the content layout. We’d like to make sure you can comfortably find the highlights and related resources you need.   More developments are underway! The coming weeks will bring more updates, so stay tuned on News & Announcements. So please let us know what’s working for you and what could improve! Back to TOC | To Essentials   University News Access these new self-paced courses  Sign in to AppDynamics University to access these and other courses: View License Utilization and Add Users in Cloud Observability  AppDynamics Synthetic Monitoring Overview  IoT Application Monitoring Overview  Customize AppDynamics IoT Dashboards    New Uni Updates Video Series The new Uni Updates video series will be a one-stop shop for all the latest AppDynamics education news and course offerings. Quick and engaging, you can see the first one here. Back to TOC | To Essentials   Webinars in September Improving app performance with deep database visibility    LIVE | While more than half of application performance issues originate in the database, most application teams have little or no visibility into database performance. Our upcoming webinar shows how modern DevOps teams can get that database visibility to optimize app performance.  APAC | September 27 at 8:30am IST, 11 am SGT, 2pm AEST  AMER | September 28 at 11am PST,2pm EST  Register here.  Embark on your OTel-based full‑stack observability journey    ON DEMAND | Watch our on-demand webinar to discover strategies for achieving full-stack observability across containerized, virtual, hybrid cloud native and enterprise applications with an OpenTelemetry-based solution.   Watch now!  Mitigate Business Risk with Application Security   LIVE | Learn how AppDynamics Business Risk observability helps teams stay ahead of growing security attacks, gaining security and exposure intelligence with Kenna’s vulnerability scoring and Cisco AppDynamics business transactions to detect, prioritize, and block risks from multiple sources.  Register here  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 CAN'T FIND WHAT YOU'RE LOOKING FOR? NEED ASSISTANCE? Connect in the Forums
This article discusses some of the most common issues faced when using Linux-based Private Synthetic Agent. In this article:   What are the prerequisites for debugging Linux private Synthetic... See more...
This article discusses some of the most common issues faced when using Linux-based Private Synthetic Agent. In this article:   What are the prerequisites for debugging Linux private Synthetic Agent issues?  How do I capture PSA logs to further troubleshoot issues? What errors arise from unsupported Kubernetes versions? How do I install PSA on a machine without an internet connection? How do I resolve a recurring ‘Test Agent Failed to Post Result’ error? How do I resolve the 'DNS resolution failed (ERROR)'? How do I resolve the error thrown when cluster-level permissions are missing? How do I resolve a Heimdall log error?  How do I resolve a Heimdall error on Docker-based PSA?   What are the prerequisites for debugging Linux private Synthetic Agent issues? Make sure the deployment is done on officially supported PSA platforms, prerequisites and hardware requirements: See Install the Private Synthetic Agent (Web and API Monitoring)  in the documentation, under End User Monitoring > Synthetic Monitoring  Currently, the kernel architecture we support for installing PSA (Web Mon and API Mon) is x86-64, which is also referred to as x64, x86-64,AMD64, and Intel 64. Back to TOC    How do I capture PSA logs to further troubleshoot issues?  To properly capture PSA logs, capture the pod details in separate files as instructed in the notes:  kubectl get pods --namespace <namespace> > {YOUR_PREFERRED_PATH}/pods-status.txt  kubectl get pods -o wide --all-namespaces > {YOUR_PREFERRED_PATH}/pods-status_wide.txt  kubectl describe pod -n <namespace> <pod-name> > {YOUR_PREFERRED_PATH}/describe-pod-<pod-name>.txt  kubectl logs <pod-name> --namespace <namespace> > {YOUR_PREFERRED_PATH}/logs-pod-<pod-name>.txt  Notes: Replace <pod-name> and <namespace> with your existing values.  By default, <namespace> may have a value measurement.  To get all the <pod-name>, the first command will list them for you.  Make sure to capture the output of commands 3 and 4 for all <pod-name> per names listed in command 1, in separate files to avoid overwriting the same file.  Back to TOC    What errors arise from unsupported Kubernetes versions? Below are some of the errors reported when an unsupported K8s version is used. Kubectl version | Insufficient resources for K8s | CrashLoopBackOff error | Low resource allocation to Chrome API/Agent Kubectl version You can check the installed kubectl version using "kubectl version":  INFO 1 --- [or-http-epoll-1] c.a.s.heimdall.client.ReactiveWebClient : [34927359] Response: Status: 500 Cache-Control:no-store Pragma:no-cache Content-Type:application/json X-Content-Type-Options:nosniff X-Frame-Options:DENY X-XSS-Protection:1 ; mode=block Referrer-Policy:no-referrer content-length:226 ERROR 1 --- [or-http-epoll-1] c.a.s.h.service.MeasurementService: Failed to submit measurement with id : 8b71c4f4-7541-41f8-9f6a-8e762502d117~02b75cbc-5aaf-43f6-9d1d-30e20a634977 [SEVERE][main][TcpDiscoverySpi] Failed to get registered addresses from IP finder (retrying every 2000ms; change 'reconnectDelay' to configure the frequency of retries) [maxTimeout=0] class org.apache.ignite.spi.IgniteSpiException: Failed to retrieve Ignite pods IP addresses. The error below (and in the attached txt file) is also seen: Warning Unhealthy 23m (x4 over 25m) kubelet Readiness probe failed: Get "http://10.244.0.3:8080/ignite?cmd=probe": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Normal Killing 23m (x2 over 25m) kubelet Container ignite failed liveness probe, will be restarted Warning Unhealthy 23m (x2 over 25m) kubelet Readiness probe failed: Get "http://10.244.0.3:8080/ignite?cmd=probe": EOF Warning Unhealthy 23m (x3 over 25m) kubelet Readiness probe failed: Get "http://10.244.0.3:8080/ignite?cmd=probe": dial tcp 10.244.0.3:8080: connect: connection refused Normal Pulled 23m (x2 over 25m) kubelet Container image "apacheignite/ignite:2.14.0-jdk11" already present on machine Warning Unhealthy 5m43s (x25 over 25m) kubelet Liveness probe failed: Get "http://10.244.0.3:8080/ignite?cmd=version": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning BackOff 92s (x52 over 16m) kubelet Back-off restarting failed container ignite in pod synth-ignite-psa-0_ignite(1cba5f54-7723-4be4-a7ba-ce48fc6eacaf) Back to Errors from Unsupported K8s versions |  Back to TOC  Insufficient resources provided to Kubernetes When not enough resources (CPU and Memory defined in values.yaml) are provided to the K8s env. (for example, when starting minikube).  Events Type  ===========  Reason  ===========  Age  =======  From  ==========  Message  ============ Warning  FailedScheduling  5m (x863 over 3d3h)  default-scheduler  0/1 nodes are available: 1 Insufficient cpu, 1 Insufficient memory. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod To quickly check the current resources that minikube is running with, use the following:    cat ~/.minikube/config.json | grep "Memory\|CPUs" NOTE | In case of no output, make sure to use config.json under the profile with which minikube was started.   Back to Errors from Unsupported K8s versions |  Back to TOC  CrashLoopBackOff image pulling error When you see CrashLoopBackOff or Back-off pulling image error for Minikube-based PSA, update the values.yaml heimdall > pullPolicy to Never and re-deploy PSA. This fixes the error.     For other platforms, please refer to our documentation for specific instructions by platform: Deploy the Web Monitoring PSA and API Monitoring PSA.  Events: Type ===========   Reason =======  Age ===========  From  =======  Message  =========== Normal  BackOff  3m7s (x18915 over 3d3h)  kubelet  Back-off pulling image “sum-heimdall:<<heimdall-tag>”  Back to Errors from Unsupported K8s versions |  Back to TOC  Low resource allocation to the Chrome/API Agent If you're facing slower execution of the jobs/ High Session Duration to complete the jobs are mainly because of low resources allocated to the PSA, specifically to the Chrome/API agent.     Try increasing the resources (CPU and memory) for the Chrome/API agent in values.yaml and re-deploy the PSA.  chromeAgentResources: min_cpu: "1" max_cpu: "2" min_mem: 1024Mi max_mem: 8192Mi Back to Errors from Unsupported K8s versions |  Back to TOC     How do I install PSA on a machine without an internet connection?  Use the attached document “Install PSA with minikube on an offline machine.pdf.”  You can use any machine with an active internet connection as your temporary machine. Build PSA components on that temporary machine and then export them to your target server machine without an active internet connection.  PLEASE NOTE | The steps in the provided PDF have not been tested in-house by Cisco AppDynamics Support  NOTE | Linux PSA version >= v22.9 doesn't need Postgres DB. Please refer to EUM > Synthetics >  Install the Private Synthetic Agent (Web and API Monitoring)  in our documentation.  Back to TOC     How do I resolve a recurring ‘Test Agent Failed to Post Result’ error?  If you're periodically or intermittently facing a ‘Test Agent Failed to Post Result’ error, redeploy PSA after updating values.yaml for Heimdall resources and Chrome agent resources (recommended):  heimdallResources: min_cpu : "3" max_cpu: "3" min_mem: 5Gi max_mem: 5Gi chromeAgentResources: min_cpu: "1" max_cpu: "2" min_mem: 2048Mi max_mem: 3072Mi Back to TOC    How do I resolve the 'DNS resolution failed (ERROR)'?  If you're facing a job failing with the error below: DNS resolution failed [ERROR] WebDriverException: unknown error: net::ERR_NAME_NOT_RESOLVED Then,   Log into the Heimdall pod with the below command and see if you can ping the <url>:  kubectl exec -it <heimdall-pod-name> -n <namespace> -- /bin/bash After logging in to the Heimdall pod, please run the command below to check whether the pods are able to connect or not:  curl <url>  NOTE | Curl command is available only on the Heimdall pod. Log into the Chrome agent pod using the below command to check/debug anything related to that pod:  kubectl exec -it <chrome-pod-name> -n <namespace> -- /bin/sh NOTE | In order to use any tool available for Alpine (Chrome agent pod), make sure to either remove the USER Block or add the particular install command in Chrome Agent DOCKERFILE , rebuild the image and redeploy the PSA. If you remove the USER block in Chrome Agent DOCKERFILE, the pod will be created with root permissions, and you can install any tool after logging in to the Chrome Agent pod.  Back to TOC    How do I resolve the error thrown when cluster-level permissions are missing? The error below is thrown when cluster-level permissions are missing since PSA would need cluster-level permissions to function properly: io.fabric8.kubernetes.client.KubernetesClientException: Operation: [list] for kind: [Pod] with name: [null] in namespace: [measurement] failed. ... Caused by: java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) ~[na:1.8.0_362] As PSA service accounts and roles are configured for cluster-level permissions to do certain operations on the Helm level. Having cluster-level permissions would imply that the Agent requires access to different namespaces in the cluster.  Refer to Create the Kubernetes Cluster in the documentation. The page makes note to create a cluster in the instructions, so the assumption is that you should have access to create a cluster. With only namespace level permissions, an individual won’t be able to create a cluster.  Apply the steps below to fix the issue:  TIP | If you want to permit only namespace-level permissions instead of cluster-level permissions, we suggest you use the role.yaml file attached below   Unpack Helm chart:  cd <Unzipped-PSA-directory> tar xf sum-psa-heimdall.tgz Use/Replace the attached role.yaml with sum-psa-heimdall/templates/role.yaml   Repack using the following:  helm package sum-psa-heimdall ​ Finally, redeploy the PSA using the newly packed sum-psa-heimdall.tgz.  Back to TOC    How do I resolve a Heimdall log error? If you see the error below in your Heimdall logs, try increasing the RAM on the PSA host machine, or decrease the memory assigned to minikube and values.yaml:  2023-05-30 20:43:38.768 WARN 1 --- [ main] org.apache.ignite.internal.IgniteKernal: Nodes started on local machine require more than 80% of physical RAM what can lead to significant slowdown due to swapping (please decrease JVM heap size, data region size or checkpoint buffer size) [required=2262MB, available=5120MB] [20:43:38] Nodes started on local machine require more than 80% of physical RAM that can lead to significant slowdown due to swapping (please decrease JVM heap size, data region size or checkpoint buffer size) [required=2262MB, Back to TOC  How do I resolve a Heimdall error on Docker-based PSA?  For Docker-based PSA, make sure the "docker ps" command outputs both the Heimdall and ignite containers.  To capture Heimdall logs, use the below:  // Capture heimdall container logs using the <HEIMDALL_CONTAINER-ID> to heimdall.txt file, to get <HEIMDALL_CONTAINER-ID>, run "docker ps" docker logs -n <last-n-lines> <HEIMDALL_CONTAINER-ID> > heimdall-<CONTAINER-ID>.txt Back to TOC 
I am migrating my user account to central identity using an existing email, but I can’t tell how I should proceed to finish This article provides context and instructions for completing the user ac... See more...
I am migrating my user account to central identity using an existing email, but I can’t tell how I should proceed to finish This article provides context and instructions for completing the user account migration to the AppDynamics central identity. Why is this happening? | What must I do? I can't remember my password | Step by Step Instructions | Resources Figure 1 - Migration Experience page When a user signs in successfully to a Controller account using their local username, completes the migration experience page (see Figure 1, left) by providing their email address and is presented a new login screen, they are often confused as to what to do next. Is this happening to you?  There is an easy answer. Simply sign into the new login screen using the same email address you provided above as the username. Use the password you use with AppDynamics for this email at the password prompt. NOTE | This may or may not be the same password you use to log in to your Controller. You may have set this some time ago! Feel free to use Reset Password.   Once you complete this sign-in, the username for your Controller local user account will be migrated to be your email address user account, and you will be directed to the Controller account in a logged-in state.    Why is this happening? Figure 2 – Login screen This migration process is about making sure each human user can access all AppDynamics resources with the same user identity. It will unify potentially multiple user accounts into a single user account based on the email address provided.   When you see the login screen (see Figure 2, left) after providing your email address (see Figure 1, above), it means that AppDynamics already has a user account created with that email address as the username, and we need you to prove that you own it.   Back to TOC How did I get this account?  There are several ways you could have obtained it:  You have completed training and used this account to access training   You can file support tickets and use this account for that action  You already completed migration on another Controller account.   You signed up for a self-service trial using this email address.  Your company admin created an account for you using this email address some time ago and you’ve never even used it. You may not recall, but we remember the account and need you to prove you own it.   Back to TOC What must I do? You simply enter your email address as the username, provide the password, and sign in.  What if I don't remember my password? Easy. Simply click the Reset Password link, and an email will be sent to you. Follow the instructions there and create a new password. With this new password, return to the flow and try again.  What is AppD doing to improve this experience?  We are aware of the problem and will update the experience in the coming days to include instructions to help ensure the next steps are clear.   Back to TOC I'm still confused. Can you provide an example and go through this process step-by-step? Sure. Let’s set this example up:  Your controller account: helpmeout  Your local username: legacyuser  Your email address: userone@helpmeout.com  Now for the steps: Navigate to AppDynamics using helpmeout.saas.appdynamics.com   (NOTE | This is not a real account and is just provided for this example scenario) Enter the account name of: helpmeout Enter your username of: legacyuser and click Next  Enter the password for legacyuser and click Sign in    You are presented with the migration dialog (see Figure 1, above) and are asked to enter your email. The dialog shows the email address we have on file for you and an empty confirmation email field. You may change the email address as displayed or leave it, but you must confirm it in the confirmation field.   You complete the email field as: userone@helpmeout.com and the confirmation field as userone@helpmeout.com and click Confirm    The system finds that userone@helpmeout.com already exists in the AppDynamics Identity Provider and prompts you with a login screen (see Figure 2, above) to authenticate that it’s really you. We want to make sure that you are who you say you are for security reasons.  You enter your email address as: userone@helpmeout.com and click Next. NOTE | We recommend that you check the Remember me box for future convenience.    You are presented with a password field. Enter the password for the userone@helpmeout.com user and click the Sign in button. If you don’t remember your password, click Reset password and follow the instructions to set a new password.    You will be authenticated and then will receive a message indicating that you have completed migration. It will remind you that, from now on, you will log in to the helpmeout account using the username of userone@helpmeout.com and the password you just used to authenticate. You can then click the link to the helpmeout.saas.appdynamics.com account, where you will be automatically logged in.     Congrats! You’ve completed migration and will be back to using the system as normal with the added benefit of seamless access (SSO) to other accounts that use this username as well as resources of AppDynamics like Community, University, and Support.  Back to TOC Additional resources AppDynamics Global Identity Migration Experience - FAQ   Why sign in after migration?