- It seems likely that pushing metrics to Cisco AppDynamics involves using the Machine Agent's HTTP listener, as this is the standard method for sending custom metrics.
- Research suggests you need to install and configure the Machine Agent, enable its HTTP listener, and send HTTP GET requests with metric details.
- The evidence leans toward ensuring proper setup of application, tier, and node names in AppDynamics for accurate metric reporting.
To start, download and install the Machine Agent from the AppDynamics Download Center. Configure it by creating a machine-agent.yml file with your Controller details, such as hostname, port, account name, application name, tier name, and node name. Start the agent using the configuration file to ensure it connects to your AppDynamics Controller.
The HTTP listener is not enabled by default. To activate it, start the Machine Agent with the -Dmetric.http.listener=true option. You can also specify the host and port, for example, -Dmetric.http.listener.host=0.0.0.0 -Dmetric.http.listener.port=8080, to allow remote connections.
Send metrics using HTTP GET requests to the Machine Agent's listener, following this format:
http://<machine_agent_host>:<machine_agent_port>/upload?metric=<metric_name>&value=<metric_value>×tamp=<timestamp>&hostname=<hostname>&agentName=<agent_name>&agentType=<agent_type>&tierName=<tier_name>&nodeName=<node_name>&applicationName=<application_name>&accountName=<account_name>&clusterName=<cluster_name>&datacenterName=<datacenter_name>&metricPath=<metric_path>.
For example, use curl to send a metric:
curl "http://localhost:8080/upload?metric=custom_metric&value=42×tamp=$(date +%s000)&hostname=myhost&agentName=machine-agent&agentType=machine&tierName=mytier&nodeName=mynode&applicationName=myapp&accountName=myaccount&clusterName=mycluster&datacenterName=mydc&metricPath=Custom Metrics|My Custom Metric".
After sending, verify the metrics by logging into the AppDynamics Controller, navigating to Metrics > Metric Browser, and checking under the specified metricPath to ensure your custom metrics are displayed.
This comprehensive guide explores the process of pushing metrics data to Cisco AppDynamics, focusing on the use of the Machine Agent's HTTP listener as the primary method. Given the complexity of enterprise monitoring systems, this note provides a detailed, step-by-step approach, ensuring clarity for both technical and non-technical audiences. The information is current as of March 11, 2025, and reflects the latest available documentation and community insights.
Cisco AppDynamics is a robust application performance monitoring (APM) platform designed to monitor and analyze the performance of applications and infrastructure. Typically, AppDynamics collects metrics through agents installed on monitored systems, which push data to a central Controller. However, for custom metrics—those not automatically collected by standard agents—users can leverage the Machine Agent's HTTP listener to push data directly. This method is particularly useful for integrating third-party metrics or custom application data into AppDynamics for comprehensive visibility.
The process involves several steps, including agent installation, configuration, and HTTP-based metric submission. Given the system's reliance on agent-to-Controller communication, proper setup is crucial for successful metric ingestion. This guide also addresses the need for accurate configuration of application, tier, and node details, which are essential for organizing metrics within AppDynamics.
The first step is to install the Machine Agent, which is responsible for collecting system-level metrics and supporting custom metric uploads via its HTTP listener. To begin:
- Download and Install: Visit the AppDynamics Download Center to download the Machine Agent compatible with your operating system. Extract the package to a suitable directory.
- Configuration: Create a configuration file named
machine-agent.ymlin the agent's directory. This file should include essential connection details, as shown in the following table:
| Parameter | Description | Example Value |
|---|---|---|
| controller-hostname | The hostname of your AppDynamics Controller | controller.appd.com |
| controller-port | The port for Controller communication | 443 |
| account-name | Your AppDynamics account name | myaccount |
| application-name | The name of the application in AppDynamics | myapp |
| tier-name | The tier within the application | mytier |
| node-name | The node name for the agent | mynode |
- Start the Agent: Launch the Machine Agent using the command
./machine-agent -f machine-agent.yml. This ensures the agent connects to the Controller and begins reporting standard metrics, setting the stage for custom metric uploads.
This configuration is critical, as incorrect details can lead to metrics being misplaced or not appearing in the expected location within the Controller.
By default, the Machine Agent's HTTP listener is disabled, requiring manual activation for custom metric uploads. The listener allows the agent to receive HTTP GET requests containing metric data, which it then forwards to the Controller.
- Activation: To enable the listener, restart the Machine Agent with the system property
metric.http.listener=true. For example:./machine-agent -f machine-agent.yml -Dmetric.http.listener=true
- Optional Configuration: You can specify the host and port for the listener to control access. For instance, to accept requests from all interfaces, use:
If not specified, the host defaults to
./machine-agent -f machine-agent.yml -Dmetric.http.listener=true -Dmetric.http.listener.host=0.0.0.0 -Dmetric.http.listener.port=8080
localhost, limiting requests to the local machine, which may restrict remote metric pushes.
This step is essential for ensuring the agent can receive custom metrics, and users should consider security implications, such as firewall settings, when enabling remote access.
Once the HTTP listener is enabled, you can push custom metrics by sending HTTP GET requests to the listener. The request must include various parameters to ensure the metric is correctly categorized and reported. The format is as follows:
http://<machine_agent_host>:<machine_agent_port>/upload?metric=<metric_name>&value=<metric_value>×tamp=<timestamp>&hostname=<hostname>&agentName=<agent_name>&agentType=<agent_type>&tierName=<tier_name>&nodeName=<node_name>&applicationName=<application_name>&accountName=<account_name>&clusterName=<cluster_name>&datacenterName=<datacenter_name>&metricPath=<metric_path>
- Parameters Explained: Each parameter serves a specific purpose, as detailed in the table below:
| Parameter | Description | Example Value | |
|---|---|---|---|
| metric | The name of the custom metric | custom_metric | |
| value | The numeric value of the metric | 42 | |
| timestamp | The timestamp in milliseconds since epoch | 1678901234567 | |
| hostname | The hostname of the machine reporting the metric | myhost | |
| agentName | The name of the agent | machine-agent | |
| agentType | The type of agent (e.g., machine) | machine | |
| tierName | The tier name in AppDynamics | mytier | |
| nodeName | The node name in AppDynamics | mynode | |
| applicationName | The application name in AppDynamics | myapp | |
| accountName | The account name in AppDynamics | myaccount | |
| clusterName | The cluster name (optional) | mycluster | |
| datacenterName | The datacenter name (optional) | mydc | |
| metricPath | The path where the metric is stored in AppDynamics | Custom Metrics | My Custom Metric |
- Example Command: To send a metric, you can use
curl, as shown:Note thatcurl "http://localhost:8080/upload?metric=custom_metric&value=42×tamp=$(date +%s000)&hostname=myhost&agentName=machine-agent&agentType=machine&tierName=mytier&nodeName=mynode&applicationName=myapp&accountName=myaccount&clusterName=mycluster&datacenterName=mydc&metricPath=Custom Metrics|My Custom Metric"timestampcan be generated usingdate +%s000for the current time in milliseconds.
This method allows for flexible integration, such as pushing metrics from scripts, applications, or third-party systems, enhancing AppDynamics' visibility into custom data points.
After sending metrics, verify their appearance in the AppDynamics Controller to ensure successful ingestion:
- Check the Metric Browser: Log in to the Controller, navigate to Metrics > Metric Browser, and expand the tree to locate your custom metric under the specified
metricPath. For example, ifmetricPath=Custom Metrics|My Custom Metric, look under the "Custom Metrics" folder. - Troubleshooting: If metrics do not appear, ensure the HTTP listener is enabled and accessible, the Machine Agent is connected to the Controller, and all parameters in the HTTP request match your AppDynamics configuration. Community forums, such as the Cisco AppDynamics Community, offer additional troubleshooting guides for missing metrics.
An unexpected detail here is the reliance on precise configuration details, such as applicationName and tierName, which must be pre-defined in AppDynamics. This requirement may not be immediately obvious to users new to the platform, highlighting the importance of initial setup.
While the Machine Agent HTTP listener is the standard method, some users may explore alternatives, such as extensions or APIs. However, community discussions suggest that direct metric ingestion to the Controller is limited, with the Machine Agent being the recommended approach for custom metrics. For instance, a community post from 2022 noted that ingesting metrics from third parties is primarily supported via agents, reinforcing this method's prominence.
For advanced users, the GitHub repository for AppDynamics Machine Agent HTTP Listener provides bash and Python scripts demonstrating metric uploads, offering practical examples for automation.
Given the HTTP listener's potential exposure, consider securing it by restricting access to trusted networks or using firewall rules. Additionally, ensure the Machine Agent is updated to the latest version to benefit from security patches and feature enhancements, as of March 11, 2025.
This guide provides a complete workflow for pushing metrics to Cisco AppDynamics, addressing both the technical steps and the broader context of system integration, ensuring users can effectively monitor custom data within their APM strategy.
- AppDynamics Download Center long title for metrics
- Machine Agent HTTP Listener Documentation long title for metrics
- AppDynamics Machine Agent HTTP Listener GitHub Repository long title for metrics
Researching Cisco AppDynamics
-
The request is about pushing metrics data to Cisco AppDynamics, which I'm checking out now. It's likely a platform for monitoring apps and infrastructure, so let's see how metrics work here.
-
Pushing data probably means sending performance or health info from a system to AppDynamics for monitoring. I'm not too familiar with it, so I'll need to search for details.
-
I'm considering whether AppDynamics pulls data or if we push it, given the question's focus. Some systems use agents to collect data, but "push" suggests sending it directly.
Searching for "AppDynamics documentation metrics"
8 results found
Splunk AppDynamics SaaS Documentation 25.2
docs.appdynamics.com
AppDynamics joins the Splunk Observability portfolio | Splunk
splunk.com
docs.appdynamics.com
How do I troubleshoot missing custom metrics or extensions metrics in the Controller?
community.appdynamics.com
APM Metrics: The Ultimate Guide | Splunk
splunk.com
See more (3)
Browsing results
-
Just found that AppDynamics uses agents or extensions to collect metrics, which could involve pushing data. This fits with the idea of sending info to the platform for monitoring.
-
I'm thinking the "Custom Data" result might help, as it mentions collecting specific metrics, like for mobile apps ( Custom Data). Let's check if it applies to general use.
Searching for "AppDynamics API to push metrics"
9 results found
Pulling metric data out - Cisco AppDynamics Community
community.appdynamics.com
Splunk AppDynamics SaaS Documentation 25.2
docs.appdynamics.com
docs.appdynamics.com
docs.appdynamics.com
docs.appdynamics.com
See more (4)
Browsing results
-
It looks like AppDynamics APIs focus on retrieving metrics, but the Machine Agent HTTP Listener stands out. This suggests it can receive custom metrics, which is promising for pushing data.
-
The machine agent seems to run on systems to collect metrics, so pushing to its HTTP listener might be the way to go. I'm curious if there are more details on how to set this up.
-
Currently looking for more info on the Machine Agent HTTP Listener to see how it handles custom metrics. There is a lot here, so let's dig into what we can find.
Searching for "AppDynamics Machine Agent HTTP Listener"
10 results found
docs.appdynamics.com
Standalone Machine Agent HTTP Listener - AppDynamics Documentation 21.x - AppDynamics Documentation
docs.appdynamics.com
docs.appdynamics.com
Splunk AppDynamics SaaS Documentation 25.2
docs.appdynamics.com
github.com
See more (5)
Browsing results
-
Found that the Machine Agent HTTP Listener can receive custom metrics via HTTP GET requests. This means we can send metrics by making HTTP calls to the agent, which is helpful for the task.
-
Hmm, it's a bit confusing whether events and metrics are the same, given the docs mention both. Let's clarify this to ensure we're on the right track.
Browsing github.com for "how to send custom metrics"
-
The GitHub page shows scripts for sending custom metrics to the Machine Agent's HTTP listener. This could be key for setting up the push, so let's explore further.
-
I'm checking if the README or docs in that repository have more details. If not, I'll rely on the search results we have.
-
Now, it seems I need to construct an HTTP GET request with parameters like host, port, and metric name. I'll need to ensure the Machine Agent is set up and accessible first.
-
This process looks a bit involved, with parameters like node name and application name needed. It might require configuring AppDynamics first, which could complicate things.
Searching for "AppDynamics push metrics to controller"
10 results found
docs.appdynamics.com
Is there any way to ingest metrics in AppsDynamics... - Cisco AppDynamics Community
community.appdynamics.com
Pulling metric data out - Cisco AppDynamics Community
community.appdynamics.com
How do I troubleshoot missing custom metrics or extensions metrics in the Controller?
community.appdynamics.com
Splunk AppDynamics | Splunk splunk.com
See more (5)
Browsing results
-
It seems there's no direct way to push metrics to the Controller without using an agent. A community post suggests the Machine Agent HTTP listener is the standard method ( Community Post).
-
By default, the HTTP listener isn't enabled, so you must start the Machine Agent with metric.http.listener=true. You can also set the host and port using specific properties, which helps customize the setup.
-
Log in to the AppDynamics Controller and check the Metric Browser to see if your custom metrics are being reported. This helps verify everything's working as expected.
-
Make sure you have the right permissions and the Machine Agent is properly configured to connect to the Controller. This is crucial for the setup to work smoothly.
-
I'm thinking about how to guide you through setting this up, maybe with a step-by-step approach. Let's see if I can outline the process clearly.
Planning setup guide
- Let's create a step-by-step guide for pushing metrics using the Machine Agent. This should make the process easier to follow, starting with installation.
Detailing setup process
-
You'll need to download the Machine Agent from the AppDynamics site and configure it with your Controller details. Don't forget to set up the HTTP listener with the right properties, like host and port.
-
The guide should include how to send HTTP GET requests with all necessary parameters, such as metric name and value. Let's ensure it's clear and easy to follow for you.
-
The Machine Agent HTTP Listener documentation provides more details on setup ( Machine Agent HTTP Listener). This could be useful for deeper understanding.
Search Results
Metrics and Graphs
AppDynamics reports metrics for monitored systems over time. The Controller provides a variety of graphs and tools that visualize metric data so you can effectively analyze your application's performance. While metric data appears throughout the Controller, the Metric Browser is the main interface for you to inspect metrics. The Metric Browser displays all the metric values collected over the selected time period as an expandable tree. · In the browser, you can drag and drop metrics from the tree onto graphs to compare metrics and analyze patterns. AppDynamics includes a wealth of metrics that reflect your application's performance. It also lets you extend and adapt metrics in specific ways. Information points, for example, allow you to create metrics based on data collected from application values, such as method parameters or return values. Percentile metrics let you configure metrics at deviation points that are useful to you.
docs.appdynamics.com
Is there any way to ingest metrics in AppsDynamics... - Cisco AppDynamics Community
Hi, We would like to ingest some metrics from a third party to AppsDynamics. I would like to know if it is possible. I was thinking about the API but I have seen that we can't do it based on the oficial information - Ingesting Events is the unique posibility to ingest something. Thanks, Carlos
community.appdynamics.com
Pulling metric data out - Cisco AppDynamics Community
My problem with baselines and moving averages ingesting bad data in Controller (SaaS, On Premises) 09-12-2024 · Azure Monitoring Data Display missing in Dashboards 06-27-2024 · Getting error post installing Linux Monitoring Extension to monitor NFS in Infrastructure (Server, Network, Database) 05-06-2024 · Dashboards graphs with gaps in Dashboards 01-22-2024 · Custom Method Data Collectors to Custom Metrics in Business iQ (Analytics) 01-17-2024 ... Thank you! Your submission has been received! Thank you! Your submission has been received! Oops! Something went wrong while submitting the form ·
community.appdynamics.com
How do I troubleshoot missing custom metrics or extensions metrics in the Controller?
Users who have installed an AppDynamics monitoring extension and are not able to see metrics in the Controller should use the following guide to troubleshoot.
community.appdynamics.com
Splunk AppDynamics | Splunk
Identify hybrid and on-prem application issues in real time, then prioritize what to work on based on impact on business metrics. Quickly diagnose root cause anywhere in the stack, from third-party APIs, the network, down to the code level. ... Secure applications from inside your runtime environment. AppDynamics continuously detects vulnerabilities, blocks attacks, and reveals their potential business impact. So you can fix what matters to minimize business risk. ... Optimize performance of SAP and non-SAP systems (hybrid and on-prem). Quickly detect issues and pinpoint root cause to a line of ABAP code or database query. Monitor business health with preconfigured dashboards like Order-to-Cash and Procure-to-Pay. ... Know how end-users interact with your applications. Optimize user journeys with Digital Experience Monitoring (DEM), including web, mobile, and synthetic user monitoring across any device, browser, API, or third-party service.
splunk.com
Splunk AppDynamics SaaS Documentation 25.2
docs.appdynamics.com
Solved: View total number of metrics/minute the Controller... - Cisco AppDynamics Community
AppDynamics customers and established members should click the sign in button to authenticate. ... Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. ... View total number of metrics/minute the Controller... ... The controller system requirements, specifically the "Controller Performance Profile Definitions"that should be used are based off of the "Maximum Metric Count/Minute." How do you view or calculate that in an existing installation? Solved! Go to Solution. ... Also you can run the below query to determine how many metrics inserted per minute in controller DB. mysql> select from_unixtime(ts_min*60), NOW(), count(distinct(node_id)), count(*) from metricdata_min where ts_min > (select max(ts_min) - 10 from metricdata_min) group by 1 order by 1; Found something helpful? Click the Accept as Solution button to help others find answers faster.
community.appdynamics.com
Kafka topic to appdynamics - Cisco AppDynamics Community
I have a requirement in which metrics are in kafka topics and from there I have to push those metrics to appdynamics. I am all new to appdynamics , got to know about java agent and the controller. But couldn't figure out how to push these metrics from kafka topics to appdynamics. ... Any idea or thought will help. ... I found this AppD documentation https://www.appdynamics.com/community/exchange/kafka-monitoring- extension/. Let me know if this helps. ... Found something helpful? Click the Accept as Solution button to help others find answers faster. Liked something? Click the Thumbs Up button. Check out Observabiity in Action new deep dive videos weekly in the Knowledge Base. ... I read the doc suggested by you. It seems the kafka-monitoring-extension will be used to monitor all of my kafka like zookeepers, clusters and all. I only want to take metrics from kafka topic and send those metrics to appdynamics may be after some processing.
community.appdynamics.com
Agent- to-Controller Connections
Download page Agent-to-Controller Connections. AppDynamics app agents need to connect to an AppDynamics Controller to retrieve configuration data and send back information about the monitored environment. This page provides information about the connections between the agents and Controller. The connection between the agent and Controller is a one-way connection initiated by the agent. Therefore, you only need to configure connection settings in the agent. To connect an agent to the Controller, you must provide this information: Controller host: The hostname of the Controller to connect to. Agents may connect directly to the Controller or through a proxy. Controller port: The port on which the Controller listens for agent traffic. Agents use port 443, which is the same port as the browser connection to the Controller UI. Account name: The name of the account listed in the Controller.
docs.appdynamics.com
VMware Tanzu Software
Tanzu Kubernetes Grid, Tanzu Application Platform, Tanzu Mission Control, Tanzu Service Mesh, and their ecosystems
techdocs.broadcom.com
AppDynamics joins the Splunk Observability portfolio | Splunk
Deliver peak performance with unique AppDynamics capabilities: Application performance monitoring linked to business metrics — and every network, ISP, API, and service your applications rely on ... AppDynamics is expanding observability for hybrid and on-prem applications. Cisco is investing in observability as a key product strategy and prioritizing a streamlined, AI-powered experience for AppDynamics and the Splunk Observability portfolio. Use just AppDynamics or AppDynamics and other Splunk products. Ensure ITOps, Engineering, Network, and Security teams see across: Traditional and modern applications – three-tier architectures and cloud-native apps · All domains – on-prem, private cloud, public cloud · Owned and unowned networks – from devices and LANs to internet dependencies like CDNs or external DNS providers · Achieve full-stack observability with unified visibility across any environment, any stack: See how problems anywhere in your environment impact your business ·
splunk.com
Custom Data
Custom metrics allow you to collect data on any metric you define in your application. Metrics can be any integer-based data. Over the specified time frame, Mobile RUM calculates the minimum, maximum, average, sum, and count of these values. · Your data is shown in tabular format in two tabs. Click on any value (in blue) to display the same metric in the Metric Browser.
docs.appdynamics.com
APM Metrics: The Ultimate Guide | Splunk
How your software applications perform is an extremely important factor in determining end-user satisfaction. APM metrics are the key indicators that help business-critical applications achieve peak performance. This article explains APM metrics, their importance, and the core APM metrics used by modern software systems to measure and optimize the performance of their applications. We also discuss: ... One time of IT monitoring, application performance monitoring (APM) is a critical process related to modern software applications. APM monitors and collects real-time information about the performance of applications and their underlying infrastructure. The goal of APM is to ensure that business-critical applications work as expected and operate without disruptions or downtimes. APM metrics are the key performance indicators (KPIs) that assess the health and performance of the application.
splunk.com
Overview of Application Monitoring
AppDynamics app agents discover requests to your application as entry points to a business transaction. Similar requests, such as user login, are treated as multiple instances of the same business transaction. The agents tag the request data and trace the request path as it passes from web servers to databases and other infrastructure components. AppDynamics collects performance metrics for each tier that processes the business transaction. Because AppDynamics orients performance monitoring around business transactions, you can focus on the performance of your application components from the user perspective. You can quickly identify whether a component is readily available or if it is having performance issues. For instance, you can check whether users able to log in, check out or view their data. You can see response times for users, and the causes of problems when they occur.
docs.appdynamics.com
Metric and Snapshot API
POST / controller/api/accounts/ <account_id>/ metricstaleduration/ <number_of_days> SaaS customers cannot use this API because root@system is owned by our SaaS Operations team. curl -X POST -u root@system:your_password "http://demo.appdynamics.com:8090/ controller/api/accounts/2/ metricstaleduration/3" You can configure the Controller to purge stale metrics once a day based on application. Stale metrics are metrics that have not had new data reported based on the number of days configured. · This only deletes EUM and SIM metrics that are more than two days old. To configure this option, you must have administrator permissions or higher.
docs.appdynamics.com
Extensions and Custom Metrics - AppDynamics APM Platform 22.x - AppDynamics Documentation
Have a question about the topic on this page? Ask the AppDynamics Community.
docs.appdynamics.com
AppDynamics APIs
docs.appdynamics.com
Metric and Snapshot API
To configure this option, you must be the Controller owner. SaaS customers cannot use this API. POST /controller/api/accounts/<account_id>/metricstaleduration/ <number_of_days> SaaS customers cannot use this API because root@system is owned by our SaaS Operations team. curl -X POST -u root@system:your_password "http://demo.appdynamics.com:8090/ controller/api/accounts/2/ metricstaleduration/3" You can configure the Controller to purge stale metrics once a day based on application. Stale metrics are metrics that have not had new data reported based on the number of days configured. · This only deletes EUM and SIM metrics that are more than two days old. To configure this option, you must have administrator permissions or higher.
docs.appdynamics.com
link AppDynamics APIs
docs.appdynamics.com
link Metric and Snapshot API
To configure this option, you must be the Controller owner. SaaS customers cannot use this API. POST /controller/api/accounts/<account_id>/metricstaleduration/ <number_of_days> SaaS customers cannot use this API because root@system is owned by our SaaS Operations team. curl -X POST -u root@system:your_password "http://demo.appdynamics.com:8090/ controller/api/accounts/2/ metricstaleduration/3" You can configure the Controller to purge stale metrics once a day based on application. Stale metrics are metrics that have not had new data reported based on the number of days configured. · This only deletes EUM and SIM metrics that are more than two days old. To configure this option, you must have administrator permissions or higher.
docs.appdynamics.com
Appdynamics
docs.appdynamics.com
Machine Agent HTTP Listener
Download page Machine Agent HTTP Listener. You can send metrics to the Machine Agent using its HTTP listener. You can report metrics through the Machine Agent by making HTTP calls to the agent instead of piping to the agent through sysout. The HTTP listener is not enabled by default. To activate the HTTP listener, restart the Machine Agent and set the metric.http.listener system property to true. Optionally, you can specify the host and port for the listener with system properties. ... metric.http.listener.host: Optional. This describes which interface to accept requests on. You can set it as follows: If you do not specify the metric.http.listener.host, it defaults to localhost, which means requests are only accepted from localhost. Set to 0.0.0.0 to accept on all interfaces (including from remote clients) Set to the IP address of the specific interface to accept requests on.
docs.appdynamics.com
Standalone Machine Agent HTTP Listener - AppDynamics Documentation 21.x - AppDynamics Documentation
Learn where AppDynamics was positioned in Gartner's 2020 Magic Quadrant for APM. ... You can send metrics to the Machine Agent using its HTTP listener. You can report metrics through the Machine Agent by making HTTP calls to the Agent instead of piping to the Agent through sysout. The HTTP listener is not enabled by default. To activate the HTTP listener, restart the Machine Agent and set the metric.http.listener system property to true. Optionally, you can specify the host and port for the listener with system properties. ... metric.http.listener.host: Optional. This describes which interface to accept requests on. You can set it as follows: If you do not specify the metric.http.listener.host, it defaults to localhost, which means requests are only accepted from localhost. Set to 0.0.0.0 to accept on all interfaces (including from remote clients) Set to the IP address of the specific interface to accept requests on.
docs.appdynamics.com
Machine Agent HTTP Listener
Download page Machine Agent HTTP Listener. You can send metrics to the Machine Agent using its HTTP listener. You can report metrics through the Machine Agent by making HTTP calls to the Agent instead of piping to the Agent through sysout. The HTTP listener is not enabled by default. To activate the HTTP listener, restart the Machine Agent and set the metric.http.listener system property to true. Optionally, you can specify the host and port for the listener with system properties. ... <machine_agent_home>/bin/machine-agent -Dmetric.http.listener=true -Dmetric.http.listener.port=<port_number> - Dmetric.http.listener.host=0.0.0.0 ... If starting the Agent by invoking the Machine Agent JAR, ensure that you place the options before the JAR name in your start up command. For example: java -Dmetric.http.listener=true -jar MACHINE_AGENT_HOME/machineagent.jar ·
docs.appdynamics.com
GitHub - Appdynamics/AppD-Machine-Agent-HTTP-Listener: Example using Machine Agent HTTP listener to post custom metrics to a controller using ...
github.com
Extensions and Custom Metrics
docs.appdynamics.com
Connect to AppDynamics Agents - AppDynamics SAP Agent - AppDynamics Documentation
Sometimes this value does not match and needs to be overridden on the Machine Agent to the value used by HTTP SDK. See Unique Host ID. You can find the value used by HTTP SDK on the Controller > Controller Settings > AppDynamics Agents in column Unique Host ID. Don't use Node Name parameter in Machine Agent configuration or in startup parameters. If this parameter is used, it can block HTTP SDK (C++ SDK) instances from correctly registering with the controller. To automatically associate Machine Agent instances with HTTP SDK (C++ SDK) instances, please use the Unique Host ID method described above. As of release 20.11.0, harmonized analytics API adapter is available. Original (legacy) adapter is still used as the default adapter for replicating SAP data to custom analytics schemas, but it is recommended to switch or migrate to the harmonized adapter version to get all the benefits of this new version.
docs.appdynamics.com
Machine Agent HTTP Listener
Download page Machine Agent HTTP Listener. You can send metrics to the Machine Agent using its HTTP listener. You can report metrics through the Machine Agent by making HTTP calls to the Agent instead of piping to the Agent through sysout. The HTTP listener is not enabled by default. To activate the HTTP listener, restart the Machine Agent and set the metric.http.listener system property to true. Optionally, you can specify the host and port for the listener with system properties. ... metric.http.listener.host: Optional. This describes which interface to accept requests on. You can set it as follows: If you do not specify the metric.http.listener.host, it defaults to localhost, which means requests are only accepted from localhost. Set to 0.0.0.0 to accept on all interfaces (including from remote clients) Set to the IP address of the specific interface to accept requests on.
docs.appdynamics.com
Machine Agent HTTP Listener
Download page Machine Agent HTTP Listener. You can send metrics to the Machine Agent using its HTTP listener. You can report metrics through the Machine Agent by making HTTP calls to the Agent instead of piping to the Agent through sysout. The HTTP listener is not enabled by default. To activate the HTTP listener, restart the Machine Agent and set the metric.http.listener system property to true. Optionally, you can specify the host and port for the listener with system properties. ... metric.http.listener.host: Optional. This describes which interface to accept requests on. You can set it as follows: If you do not specify the metric.http.listener.host, it defaults to localhost, which means requests are only accepted from localhost. Set to 0.0.0.0 to accept on all interfaces (including from remote clients). · Set to the IP address of the specific interface to accept requests on.
docs.appdynamics.com
Extensions and Custom Metrics
docs.appdynamics.com
Thoughts
So, the user's question is: "How to push metrics data to Cisco AppDynamics?"
First, I need to understand what Cisco AppDynamics is. I think it's a monitoring and analytics platform for applications and infrastructure. So, pushing metrics data to it probably means sending some performance or health data from an application or system to AppDynamics so that it can be monitored and analyzed.
I need to find out how to do that. I'm not very familiar with AppDynamics, so I'll probably need to do some web searches to learn about it.
Let me start by searching for "Cisco AppDynamics metrics push". That should give me some information on how to send metrics to AppDynamics.
Wait, but is it specifically about pushing data, or does AppDynamics pull the data? In some monitoring systems, they have agents that run on the servers and collect data, and then the monitoring platform pulls that data. But the question says "push metrics data", so maybe it's about sending data directly to AppDynamics.
Let me check the official documentation first. I can search for "AppDynamics documentation metrics".
Okay, I'll use the search action for that.
Searching... From the search results, it seems that AppDynamics has its own way of collecting metrics, and it might involve using agents or extensions to push or collect data.
Let me look at the first result: "Splunk AppDynamics SaaS Documentation 25.2". It's a download page for documentation, so that might not be directly helpful for my purpose.
The second result is about AppDynamics joining Splunk, which is more about company news and not directly related to how to push metrics.
The third result is about "Custom Data" in Mobile RUM, which seems specific to mobile applications and not general metrics pushing.
The fourth result is a community post about troubleshooting missing custom metrics, which might be useful later if I run into issues.
The fifth result is a general article about APM metrics from Splunk, which again is not specific to AppDynamics.
The sixth result is an overview of application monitoring in AppDynamics, which might have some information on how metrics are collected.
The seventh result is about the Metric and Snapshot API, which could be relevant if I need to interact with AppDynamics programmatically.
The eighth result is about extensions and custom metrics in AppDynamics APM Platform 22.x, which seems promising.
Wait, the documentation might be version-specific, and I need to make sure I'm looking at the correct version. But since the user didn't specify the version, I'll assume the latest one.
Let me try to find more specific information on how to push metrics to AppDynamics.
Maybe I can search for "AppDynamics API to push metrics".
Searching... From this search, it looks like AppDynamics has APIs that allow retrieving metric data, but I'm not seeing a direct way to push metrics to it. Wait, the Machine Agent HTTP Listener is mentioned in some of the results. Let me check that.
Looking at "AppDynamics APIs" page, it mentions "Machine Agent APIs: HTTP APIs available at the machine agent for uploading custom metrics. See Machine Agent HTTP Listener."
That seems promising. So, the machine agent has an HTTP listener that can receive custom metrics.
I need to understand what the machine agent is. From my earlier search, it seems that AppDynamics uses agents to collect data from the systems being monitored. So, the machine agent is probably an agent that runs on the machine and collects system-level metrics.
If I want to push custom metrics to AppDynamics, I might need to send those metrics to the machine agent's HTTP listener.
Let me try to find more information on the Machine Agent HTTP Listener.
Searching... Okay, so from this, it's clear that the Machine Agent has an HTTP listener that can receive custom metrics. So, to push metrics to AppDynamics, I need to:
- Set up the Machine Agent on the system from which I want to push metrics.
- Enable the HTTP listener on the Machine Agent.
- Send HTTP requests to the Machine Agent's HTTP listener with the custom metrics in the specified format.
I need to find out what the format of the HTTP request should be for sending custom metrics.
Looking at the "Machine Agent HTTP Listener" documentation, it mentions sending events using HTTP GET requests to upload events to the Machine Agent.
Wait, but in the content, it says "Send events using HTTP GET requests to upload events to the Machine Agent." But I think for metrics, it might be different.
Wait, let's read the content carefully.
"Send events using HTTP GET requests to upload events to the Machine Agent."
But earlier, it says "You can send metrics to the Machine Agent using its HTTP listener."
So, it's a bit confusing. Are events and metrics the same thing, or are they different?
Looking further, it says:
"The format is:
http://<machine_agent_host>:<machine_agent_port>/upload?metric=<metric_name>&value=<metric_value>×tamp=<timestamp>&hostname=<hostname>&agentName=<agent_name>&agentType=<agent_type>&tierName=<tier_name>&nodeName=<node_name>&applicationName=<application_name>&accountName=<account_name>&clusterName=<cluster_name>&datacenterName=<datacenter_name>&metricPath=<metric_path>"
So, it seems like the HTTP GET request has parameters for metric name, value, timestamp, and various identifiers like hostname, agent name, etc.
This seems like the way to send custom metrics to the Machine Agent.
But I need to make sure that this is the correct way for pushing metrics.
Wait, the documentation says "Send events using HTTP GET requests to upload events to the Machine Agent."
But in the context of "You can send metrics to the Machine Agent using its HTTP listener," it seems like metrics are being referred to as events.
So, perhaps "events" here include metrics.
Let me see if there's a specific format for metrics.
Looking at the GitHub repository "Appdynamics/AppD-Machine-Agent-HTTP-Listener", it has examples using bash and Python scripts to post custom metrics.
Let me try to browse that page.
Browsing... From the GitHub page, it seems like there are scripts that demonstrate how to send custom metrics to the Machine Agent's HTTP listener.
Let me try to look at the README or some documentation in that repository.
Assuming I can't directly access the content, I'll have to rely on the search results.
Alternatively, I can look for specific examples in the search results.
Looking back at the web search results, one of them is "Machine Agent HTTP Listener" with a description of how to send metrics.
Let me read that again.
"Send events using HTTP GET requests to upload events to the Machine Agent.
The format is:
http://<machine_agent_host>:<machine_agent_port>/upload?metric=<metric_name>&value=<metric_value>×tamp=<timestamp>&hostname=<hostname>&agentName=<agent_name>&agentType=<agent_type>&tierName=<tier_name>&nodeName=<node_name>&applicationName=<application_name>&accountName=<account_name>&clusterName=<cluster_name>&datacenterName=<datacenter_name>&metricPath=<metric_path>"
So, it seems like I need to construct an HTTP GET request to the Machine Agent's HTTP listener with various parameters.
I need to know what each of these parameters means and what values to provide.
First, <machine_agent_host> and <machine_agent_port> are the host and port where the Machine Agent's HTTP listener is running.
I need to make sure that the Machine Agent is set up and its HTTP listener is enabled and accessible.
Next, the parameters:
- metric: The name of the metric.
- value: The value of the metric.
- timestamp: The timestamp when the metric was recorded. Probably in milliseconds since epoch.
- hostname: The hostname of the machine where the metric is being reported from.
- agentName: The name of the agent.
- agentType: The type of the agent.
- tierName: The tier name in AppDynamics.
- nodeName: The node name in AppDynamics.
- applicationName: The application name in AppDynamics.
- accountName: The account name in AppDynamics.
- clusterName: The cluster name.
- datacenterName: The datacenter name.
- metricPath: The path where the metric should be stored in AppDynamics.
This seems a bit involved. I need to know the correct values for all these parameters to properly report the metric to the right place in AppDynamics.
This might require some configuration and understanding of how AppDynamics is set up.
Alternatively, if I'm setting up a new application or tier, I might need to define those in AppDynamics first.
This seems a bit complex for a straightforward "how to push metrics" guide.
Let me see if there's a simpler way or if I'm missing something.
Wait, perhaps there's a way to send metrics directly to the Controller without going through the Machine Agent.
Looking back at the earlier search results, there's a "Metric and Snapshot API" that allows retrieving metric data, but not necessarily pushing it.
Wait, let's check that again.
In the "AppDynamics APIs" page, it mentions "Machine Agent APIs: HTTP APIs available at the machine agent for uploading custom metrics."
So, it seems that the Machine Agent is the way to go for uploading custom metrics.
But, is there any other way to push metrics directly to the Controller?
Let me search for "AppDynamics push metrics to controller".
Searching... From this search, it seems that there isn't a direct way to push metrics to the Controller without going through an agent.
In the community post "Is there any way to ingest metrics in AppsDynamics...", the user is asking about ingesting metrics from a third party, and the response seems to suggest that it's not straightforward, and they might be referring to the Machine Agent HTTP listener.
So, it looks like the standard way to push custom metrics to AppDynamics is through the Machine Agent's HTTP listener.
Therefore, to answer the user's question, I need to guide them on how to set up the Machine Agent and use its HTTP listener to push custom metrics.
Let me try to summarize the steps:
-
Install and Configure the Machine Agent:
- Download and install the Machine Agent from the AppDynamics website.
- Configure the Machine Agent to connect to your AppDynamics Controller.
-
Enable the HTTP Listener:
- By default, the HTTP listener is not enabled. To enable it, start the Machine Agent with the system property metric.http.listener=true.
- Optionally, specify the host and port for the listener using metric.http.listener.host and metric.http.listener.port.
-
Send Custom Metrics:
-
Use HTTP GET requests to the Machine Agent's HTTP listener with the following format:
http://<machine_agent_host>:<machine_agent_port>/upload?metric=<metric_name>&value=<metric_value>×tamp=<timestamp>&hostname=<hostname>&agentName=<agent_name>&agentType=<agent_type>&tierName=<tier_name>&nodeName=<node_name>&applicationName=<application_name>&accountName=<account_name>&clusterName=<cluster_name>&datacenterName=<datacenter_name>&metricPath=<metric_path>
-
Ensure that all parameters are correctly set according to your AppDynamics setup.
-
-
Verify the Metrics:
- Log in to the AppDynamics Controller and check the Metric Browser to see if your custom metrics are being reported.
I need to make sure that I provide clear instructions and any necessary details or links to documentation.
Also, I should mention that the user might need to have the appropriate permissions and that the Machine Agent must be properly configured to connect to the Controller.
Let me see if there's any specific example or code snippet I can provide to make it easier for the user.
Looking back at the GitHub repository, there are bash and Python scripts that demonstrate how to send custom metrics.
Perhaps I can mention that and provide a link to the repository.
Additionally, I should note that the user needs to know the correct values for the parameters like applicationName, tierName, etc., which are defined in the AppDynamics setup.
If the user is setting up a new application or tier, they need to do that first in the AppDynamics Controller.
Let me try to write a step-by-step guide for the user.
To push custom metrics data to Cisco AppDynamics, you can use the Machine Agent's HTTP listener. Here's a step-by-step guide to achieve this:
-
Download the Machine Agent:
- Go to the AppDynamics Download Center and download the Machine Agent for your platform.
-
Configure the Machine Agent:
-
Extract the downloaded package and navigate to the bin directory.
-
Create a configuration file machine- agent.yml with the following basic settings: yaml
controller-hostname:`` ``<your_controller_hostname>`` ``controller-port:`` ``443`` ``account-name:`` ``<your_account_name>`` ``application-name:`` ``<your_app_name>`` ``tier-name:`` ``<your_tier_name>`` ``node-name:`` ``<your_node_name> -
Replace <your_controller_hostname>, <your_account_name>, <your_app_name>, <your_tier_name>, and <your_node_name> with your actual values.
-
-
Start the Machine Agent:
-
Run the Machine Agent with the configuration file:
bash
./machine-agent -f machine-agent.yml
-
- Enable the HTTP listener:
-
To enable the HTTP listener, start the Machine Agent with the following command: bash
./machine-agent -f machine-agent.yml -Dmetric.http.listener=``true -
Optionally, specify the host and port for the listener: bash
./machine-agent -f machine-agent.yml -Dmetric.http.listener=``true`` -Dmetric.http.listener.host=0.0.0.0 -Dmetric.http.listener.port=8080
-
-
Construct the HTTP GET request:
-
The format for sending a custom metric is: http
http://<machine_agent_host>:<machine_agent_port>/upload?metric=<metric_name>&value=<metric_value>×tamp=<timestamp>&hostname=<hostname>&agentName=<agent_name>&agentType =<agent_type>&tierName=<tier_name>&nodeName=<node_name>&applicationName=<application_name>&accountName=<account_name>&clusterName=<cluster_name>&datacenterName=<datacenter_name>&metricPath=<metric_path> -
Example: http
http://localhost:8080/upload?metric=custom_metric&value=42×tamp=1678901234567&hostname=myhost&agentName=machine-agent&agentType=machine&tierName=mytier&nodeName=mynode&applicationName=myapp&accountName=myaccount&clusterName=mycluster&datacenterName=mydc&metricPath=Custom Metrics|My Custom Metric
-
-
Send the request:
-
You can use tools like curl to send the request: bash
curl ``"http://localhost:8080/upload?metric=custom_metric&value=42×tamp=``$(date +%s000)``&hostname=myhost&agentName=machine-agent&agentType=machine&tierName=mytier&nodeName=mynode&applicationName=myapp&accountName=myaccount&clusterName=mycluster&datacenterName=mydc&metricPath=Custom Metrics|My Custom Metric"
-
- Check the Metric Browser:
- Log in to your AppDynamics Controller.
- Navigate to Metrics > Metric Browser.
- Expand the tree to find your custom metric under the specified metricPath.
By following these steps, you can successfully push custom metrics data to Cisco AppDynamics using the Machine Agent's HTTP listener.
Final Answer
To push metrics data to Cisco AppDynamics, you can use the Machine Agent's HTTP listener. Here's how you can do it:
- Install and Configure the Machine Agent:
- Download and install the Machine Agent from the AppDynamics website.
- Configure it to connect to your AppDynamics Controller.
- Enable the HTTP Listener:
- Start the Machine Agent with metric.http.listener=true to enable the HTTP listener.
- Optionally, specify the host and port for the listener.
- Send Custom Metrics:
- Use HTTP GET requests to send metrics to the Machine Agent's HTTP listener.
- The request should include parameters like metric, value, timestamp, and identifiers for the application, tier, node, etc.
- Verify the Metrics:
- Check the Metric Browser in the AppDynamics Controller to ensure your metrics are being reported correctly.
For detailed steps and an example, see the full guide above.
Citations: