Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
AppDynamics extensions support automatically uploading a pre-built dashboard with every extension. This feature will help customers use an extension to extract all the listed metrics and provide an overview of how the product is doing in terms of certain key metrics. These dashboards can all be updated, and more data can be added to increase the visibility of the metrics the extension provides.
In order to upload a dashboard to the Controller, you need to provide some information about the Controller that will help the extension log in and upload the dashboard to the Controller.
Each new extension is going to be equipped with two dashboard files: one for the Standalone Machine Agent model and one for the Server and Infrastructure Monitoring (SIM) model. While configuring the extension, you will need to configure the following sections: controllerInfo and customDashboard.
This section requires you to fill out the information about the Controller, which in turn is used to make sure that the extension can establish a connection to the Controller and upload the dashboard.
The extension pulls the information in the following order from the following resources:
Update the following section in the
controllerInfo: controllerHost: "" controllerPort: "" account: "" username: "" password: "" encryptedPassword: "" encryptionKey: "" controllerSslEnabled: "" enableOrchestration: "" uniqueHostId: "" accountAccessKey: "" machinePath: "" simEnabled: "" applicationName: "" tierName: "" nodeName: ""
As you start your agent, a number of the fields will be auto-populated. But a few fields will need to be manually populated. These are:
username: "" password: ""
These fields are required for the Machine Agent to be able to log in and upload the dashboard. Once all this information is provided, populated, and validated, the extension will upload the dashboard to the Controller.
After filling it out, this section should look like this:
Similar to ControllerInfo, another section called customDashboard needs to be updated in order to make sure that a dashboard can be uploaded to the Controller from the extension.
customDashboard: enabled: true dashboardName: "Custom Dashboard" pathToSIMDashboard: "monitors/<ExtensionName>/simDashboard.json" pathToNormalDashboard: "monitors/<ExtensionName>/maDashboard.json" periodicDashboardCheckInSeconds: 300
dashboard.jsonfile and delete the current dashboard on the Controller.
After filling in both these sections and configuring the rest of the extension to its specific needs, you can start the Machine Agent to gather metrics, and check to confirm that the dashboard has been uploaded and is being populated with the correct data.
Every extension that comes with a dashboard has preconfigured metrics set to show in the dashboard. If any changes are made to the dashboard file, you will need to delete the existing dashboard present on the Controller so that the extension can upload a new copy of the dashboard with those changes.
If you would like to compare the differences after making changes to the dashboard file, bear in mind that dashboard file names on the Controller must be unique. So, you should:
config.ymlunder the customDashboard section
Once the extension hits the periodic dashboard check limit, it will again check if the dashboard with the new name is present. If not, it will upload the new dashboard which you may then use for comparison.
Each extension has specific metrics you can choose to display on the dashboard. If you would like to see other metrics, you can add them to the same dashboard (on the Controller) manually.
If any changes are made to the metric names/aliases in the
config.yml, those changes need to be replicated in the
dashboard.json files since they are preconfigured to look for metrics with the default metric names/aliases that are provided with a new copy of the extension.
If changes to the metric names/aliases in the
config.yml are not replicated, there is a good chance that the dashboard widgets associated with the corresponding metrics may not work.