AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.


    Skip to end of metadata
    Go to start of metadata
    As part of the launch program, early adopters have access to the Cloud Native Visualization functionality for six months free of charge. After six months, a purchase of new licenses is required to continue using the functionality. AppDynamics reserves the right to charge separately for Cloud Native Visualization after the end of the six month period.

    Cloud Native Visualization introduces the AIOps platform to visualize the interactions and relationships of objects in your application infrastructure. This capability helps improve collaboration and unify the efforts of different engineering functions by creating a real-time single source of truth for monitoring your application environment.

    This illustration shows a high-level overview Cloud Native Visualization:

    This illustration shows a high-level overview Cloud Native Visualization

    Additionally, Cloud Native Visualization also introduces an improved AppDynamics user interface that includes Relationships maps, Interactions maps, and related metrics. By correlating application metrics and interactions to cloud infrastructure in a unified view, AppDynamics Cloud Native Visualization enables you to:

    • Automatically discover services associated with a cloud platform account and ingest the relevant cloud platform metrics and metadata.
    • Navigate cloud platform services in a holistic application landscape that automatically correlates the Application Performance Monitoring (APM) data with cloud platform data.
    • Surface insights on the impact of cloud provider services on an application's performance.
    • Compare key performance metadata and visualize data flow based on the application entities and interactions.
    • Interact with a set of data points on the time-series graph to capture specific values tracked by both AppDynamics APM and Amazon CloudWatch.
    • Explore the dynamic, data-flow based application object page and interactions views containing application services. 
    • Drill down to the cloud infrastructure layer to understand how these two respective topologies intersect in the context of application services.
    • View your application infrastructure data, service, and business transactions. See what infrastructure exists and where it is located, in one application landscape.

    Get Started 

    Cloud Native Visualization is available to all existing AppDynamics SaaS customers. To get started, contact your AppDynamics account representative.

    The AppDynamics User Interface and Cloud Native Visualization

    AppDynamics introduces an intuitive user interface for Cloud Native Visualization that enables you to monitor your applications using a simplified approach.

    You can now view entities and data, hosted by Amazon Web Services (AWS) in Cloud Native Visualization by connecting your Amazon account to AppDynamics. For a list of the supported AWS services, see Supported AWS Services.

    The differences between the existing AppDynamics user interface and the redesigned user interface within Cloud Native Visualization are:

    Data Model and Terminology

    With Cloud Native Visualization, AppDynamics has introduced a new data model to replace the app, tier, node hierarchy, see Tiers and NodesThe redesigned approach includes the concepts of Relationships maps, Interactions maps, Services (formerly tiers), Service Instances (formerly nodes), and Object pages. 

    Traditional AppDynamics elements such as flow maps, dashboards, and metrics, and health rules are still available to a Cloud Native Visualization user. However, to interact with these elements, you must return to the existing AppDynamics interface. The Cloud Native entities do not display in the existing AppDynamics interface.

    When Cloud Native Visualization is enabled, you access the new AppDynamics user interface from the existing Controller interface through a pin. If a pin does not exist in your user interface, then the Controller has not been properly configured for this feature. See Monitor Cloud Native Applications.

    Concepts

    Three main elements of the Cloud Native Visualization feature are Object pages, Interactions maps, and Relationships maps.

    • An Object page shows information in the context of an object or entity. This page is specific to the type of entity the user has selected, such as a service, business transaction, or database.
    • The Interactions map displays a visualization of how data is flowing in the system between different entities such as application services, databases, and load balancers where the application is the object in focus.
    • The Relationships map allows you to understand how Cloud Native entities are correlated to APM entities in one page. Additionally, it allows you to view the static topology of your hybrid APM and Cloud Platform application landscape. 

    Both the Interactions and Relationships maps enable you to click on an entity and drill down to view more detailed information about the entity. See Cloud Native Visualization UI Overview.

    Object Page

    An Object page is a view corresponding to an entity type, such as Services, Applications, or Hosts. Cloud Native Visualization models customer systems as a set of entities, relationships, interactions, and paths between those entities.

    This screenshot shows an Object page with the Inventory Service as the highlighted object in focus

    Interactions Map

    Interactions maps present a dynamic visual representation of entities and their interactions based on a specific context.

    This screenshot shows the Interactions map with the Inventory Service as the central object, entities are displayed upstream (to the left) and downstream (to the right) of the Inventory Service entity

    For example, in the illustration above, the Inventory-Service object has associated upstream objects:

    • an ecommerce-alb-38945028 instance
    • two Web-Service-B service instances
    • two Web-Service-A service instances
    • an aws-alb-us-west-1 application load balancer instance in the Amazon Web Services US-West region

    And downstream objects:

    • an INVENTORY-MySQL DB database instance
    • an api.mainsupplier.com instance
    • an api.secondarysupplier.com instance
    • an aws-rdsOracle-us-west relational database in the Amazon Web Services US-West region

    Relationships Map

    The Relationships map displays the relationships an application has to other service entities. The flexible visualization displays connections to the type and number of entities, both upstream and downstream, to the outlined object you are viewing.

    This screenshot shows the Relationships map with the Cloud-Native-Ecommerce as the highlighted object. Objects such as Business Transactions, Services, Hosts, Databases, and Load Balancers and counts of each type are displayed vertically directly below.

    Supported AWS Services

    Currently, Cloud Native Visualization supports these Amazon Web Services (AWS) services:

    • Amazon Elastic Compute Cloud (EC2)
    • Amazon Elastic Block Store (EBS)
    • Amazon Relational Database Service (RDS) including the six types of database engines:
      • Amazon Aurora
      • PostgreSQL
      • MySQL
      • MariaDB
      • Oracle
      • Microsoft SQL Server
    • Amazon Elastic Load Balancers (ELB) including three types of load balancers: 
      • Classic Load Balancers (CLB)
      • Network Load Balancers (NLB)
      • Application Load Balancers (ALB)
    • Virtual Private Cloud (VPC)

    Additional AWS services and support for other cloud platforms will be added in future versions.

    Metrics in Cloud Native Visualization

    For information about the Metrics, see Cloud Native Considerations on the Cloud Native Visualization Metrics Overview page.

    AWS CloudWatch Specific API Rate Limits per Service

    Cloud Native Visualization uses the Amazon CloudWatch APIs to provide data. AWS imposes hard rate limits on many of the AWS Service APIs. Connecting your AWS Account to AppDynamics may cause an increase in the usage and billing of these specific CloudWatch Service APIs. These hard rate limits also impact how soon you reach your rate limit. These rate limits are often presented as a 503 error: Request limit exceededSee API Request Throttling in Amazon's documentation.

    Cost

    AppDynamics makes Metadata requests every fifteen (15) minutes and metric requests every five (5) minutes. The number of metrics is dependent on the instance type. See Monitoring your usage and costs in Amazon's documentation.

    • No labels