AppDynamics Extensions will now 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. All dashboards can be updated and more data can be added to increase the visibility of the metrics provided by the extension.
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 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:
You need to 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 get auto-populated but there are a few fields that 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 of 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.
config.ymlunder the customDashboard section. This name should be a different name from the last dashboard and a dashboard with this name should not be present on the Controller. 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 this new dashboard which may then be used for further comparisons.
config.yml, those changes need to be replicated in the
dashboard.jsonfiles 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 these changes are not replicated, there is a good chance that the dashboard widgets that are associated with the corresponding metrics may not work.