{"id":52539,"date":"2025-09-08T13:22:42","date_gmt":"2025-09-08T13:22:42","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=52539"},"modified":"2025-09-08T13:22:42","modified_gmt":"2025-09-08T13:22:42","slug":"appdyanmics-correlate-data-across-the-app-agent-machine-agent-and-database-agent","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/appdyanmics-correlate-data-across-the-app-agent-machine-agent-and-database-agent\/","title":{"rendered":"Appdyanmics: Correlate data across the App Agent, Machine Agent, and Database Agent"},"content":{"rendered":"\n

In AppDynamics, you correlate data across the App Agent<\/strong>, Machine Agent<\/strong>, and Database Agent<\/strong> by giving the Controller enough shared context to stitch them together. Here\u2019s the practical way to do it\u2014step-by-step and vendor-accurate.<\/p>\n\n\n\n

1) Use a clean entity model (names are the glue)<\/h1>\n\n\n\n

Decide and stick to a naming standard:<\/p>\n\n\n\n

    \n
  • Application<\/strong> = your business app (e.g., Wizbrand<\/code>).<\/li>\n\n\n\n
  • Tier<\/strong> = deployable service\/component (e.g., api-gateway<\/code>, payments-svc<\/code>).<\/li>\n\n\n\n
  • Node<\/strong> = an instance\/pod\/VM of a tier (e.g., payments-svc-01<\/code>).<\/li>\n<\/ul>\n\n\n\n

    These names drive correlation in the APM flow maps and dashboards.<\/p>\n\n\n\n

    Java example (App Agent):<\/strong><\/p>\n\n\n

    -Dappdynamics.agent.applicationName=Wizbrand\n-Dappdynamics.agent.tierName=payments-svc\n-Dappdynamics.agent.nodeName=payments-svc-01\n<\/code><\/span><\/pre>\n\n\n
    2) Co-locate Machine Agent and enable Server Visibility<\/h1>\n\n\n\n
    Install the Machine Agent<\/strong> on the same host\/VM\/container where your nodes run and enable Server Visibility<\/strong> (SIM). That lets the Controller automatically associate app Nodes<\/strong> with their Server<\/strong> (host) so infra metrics show up right on tier\/node drill-downs.<\/p>\n\n\n\n
    Key Machine Agent settings (controller + SIM):<\/strong><\/p>\n\n\n
    controller-host, port, account-name, access-key\nsim.enabled=true<\/span>\n# (Optional but helpful) uniqueHostId=<stable-host-identifier><\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      \n
    • In Kubernetes, prefer Cluster Agent<\/strong> + Server Visibility<\/strong> so nodes\/pods map cleanly to the infra view.<\/li>\n\n\n\n
    • Result: From an APM node, you can jump straight to CPU, memory, disk, and network for the exact host\/container backing that node.<\/li>\n<\/ul>\n\n\n\n
      3) Link database backends to Database Monitoring collectors<\/h1>\n\n\n\n
      Two things happen by default:<\/p>\n\n\n\n
        \n
      • The App Agent<\/strong> auto-detects database backends<\/strong> (JDBC, ADO.NET, etc.) as \u201cbackends\u201d on the flow map (e.g., mysql:\/\/orders-db:3306<\/code>).<\/li>\n\n\n\n
      • The Database Agent<\/strong> (a separate JVM process) runs collectors<\/strong> that connect to actual DBs and harvest SQL\/query metrics.<\/li>\n<\/ul>\n\n\n\n
        To correlate them:<\/p>\n\n\n\n
          \n
        • Configure a Database Collector<\/strong> for each DB (host\/port\/SID or service name).<\/li>\n\n\n\n
        • In the Controller, link the detected backend<\/strong> (from the app flow map) to the matching DB collector<\/strong> (host\/port\/instance must match).<\/li>\n\n\n\n
        • After linking, your application\u2019s DB flow line becomes a clickable bridge into full DB health: waits, top queries, execution plans, etc.<\/li>\n<\/ul>\n\n\n\n
          Database Agent collector example (MySQL):<\/strong><\/p>\n\n\n
          collector.name=orders-mysql\ncollector.type=MySQL\ncollector.host=orders-db.company.internal\ncollector.port=3306\ncollector.user=appd_monitor\ncollector.password=********\n<\/code><\/span><\/pre>\n\n\n
          4) Preserve cross-service correlation (headers) for microservices<\/h1>\n\n\n\n
          For calls between services (HTTP, gRPC, JMS, etc.):<\/p>\n\n\n\n
            \n
          • Ensure App Agents on both caller and callee<\/strong>.<\/li>\n\n\n\n
          • Don\u2019t strip AppDynamics correlation headers at gateways\/proxies (the agent injects these automatically).<\/li>\n\n\n\n
          • This preserves Business Transaction<\/strong> continuity across tiers so the flow map shows end-to-end<\/strong> paths, including DB calls behind each tier.<\/li>\n<\/ul>\n\n\n\n
            5) (Optional, powerful) Correlate logs & analytics to transactions<\/h1>\n\n\n\n
            If you use Log Analytics \/ Analytics Agent<\/strong>:<\/p>\n\n\n\n
              \n
            • Extract the AppDynamics Transaction\/Correlation IDs<\/strong> from logs (agents add them), then index them.<\/li>\n\n\n\n
            • You can pivot from a slow BT snapshot<\/strong> \u2192 host metrics<\/strong> \u2192 DB query<\/strong> \u2192 relevant logs<\/strong> for that exact transaction. That\u2019s \u201cneedle-in-a-stack\u201d made practical.<\/li>\n<\/ul>\n\n\n\n
              6) Quick verification checklist<\/h1>\n\n\n\n
                \n
              • APM<\/strong>: App\/Tier\/Node show up; BTs and snapshots are collected.<\/li>\n\n\n\n
              • Infra<\/strong>: From a Node page, you see CPU\/mem\/disk (Server Visibility active).<\/li>\n\n\n\n
              • DB<\/strong>: App flow map shows DB backend linked<\/strong> (click \u2192 lands in Database Monitoring).<\/li>\n\n\n\n
              • Cross-service<\/strong>: Multi-tier BTs span services (no broken links; headers intact).<\/li>\n<\/ul>\n\n\n\n
                7) Common pitfalls (and fixes)<\/h1>\n\n\n\n
                  \n
                • Different naming<\/strong> across environments \u2192 adopt and enforce a naming convention early.<\/li>\n\n\n\n
                • Machine Agent not linked<\/strong> \u2192 enable SIM and set a stable uniqueHostId<\/code> if the host identity is flaky (containers, ephemeral VMs).<\/li>\n\n\n\n
                • DB not linked<\/strong> \u2192 backend host\/port don\u2019t match collector definition; fix the collector or backend match rule so they align.<\/li>\n\n\n\n
                • Lost correlation across services<\/strong> \u2192 proxies\/load balancers stripping headers; allow AppDynamics correlation headers through.<\/li>\n<\/ul>\n\n\n\n
                  \n\n\n\n
                  TL;DR architecture<\/h2>\n\n\n\n
                    \n
                  • App Agent<\/strong> (per service instance) \u2192 traces BTs and detects DB backends.<\/li>\n\n\n\n
                  • Machine Agent<\/strong> (on same host\/pod) + Server Visibility<\/strong> \u2192 attaches infra metrics to those same Nodes\/Tiers.<\/li>\n\n\n\n
                  • Database Agent<\/strong> (central or per-env) \u2192 monitors DBs; you link<\/strong> app backends to collectors.<\/li>\n\n\n\n
                  • Result: One unified flow map where you can move App \u2192 Host \u2192 DB<\/strong> seamlessly, all tied to the same transactions.<\/li>\n<\/ul>\n\n\n\n
                    <\/p>\n","protected":false},"excerpt":{"rendered":"
                    In AppDynamics, you correlate data across the App Agent, Machine Agent, and Database Agent by giving the Controller enough shared context to stitch them together. Here\u2019s the practical way to… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[2],"tags":[],"class_list":["post-52539","post","type-post","status-publish","format-standard","hentry","category-uncategorised"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/52539","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=52539"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/52539\/revisions"}],"predecessor-version":[{"id":52540,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/52539\/revisions\/52540"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=52539"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=52539"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=52539"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}