Monitoring Tools
Last updated
Was this helpful?
Last updated
Was this helpful?
The following figure depicts the information to be provided to add AWS CloudWatch as an integration.
Following are the fields:
Account Name: The name of your AWS Cloudwatch user account
Access Key ID: The default access key used to communicate with AWS Cloudwatch
Secret Access Key: The default secret key used to communicate with AWS Cloudwatch
Group and Permissions: To enable access to all user groups, check the Enable all access to all the groups for this checkbox. To provide access to only selected user groups, uncheck this checkbox and select the required users from the Select Group drop down and enable the needed permissions like Edit, View or Delete.
To set up AppDynamics to work with the OpsMx ISD Verification gate feature, AppDynamics should be added as the monitoring provider.
Follow the below steps to add AppDynamics as an integration.
Fill in the following information on the above screen.
Account Name: Enter a name for the AppDynamics connection. This is the name you will select when you choose a Datasource provider during metrics configuration.
Controller Host: Enter the URL for your AppDynamics account for API access. For example, enter the full URL of your AppDynamics controller, such as https://opsmx-nfr.saas.appdynamics.com/
Permissions: To restrict permissions to this account, you can select the User Groups from the dropdown and the required checkboxes. Once the permissions are configured for a User Group, the access will be restricted to all other User Groups except for Administrators. By default, all users have access to this account.
Save: To finish configuring the AppDynamics provider, click on "Save". OpsMx ISD verifies the settings you entered. The AppDynamics provider is now added to OpsMx ISD.
The following figure depicts the information to be provided to add DataDog as an integration.
Following are the fields:
Account Name: The name of your Datadog user account
Group and Permissions: To enable access to all user groups, check the Enable all access to all the groups for this checkbox. To provide access to only selected user groups, uncheck this checkbox and select the required users from the Select Group drop down and enable the needed permissions like Edit, View or Delete.
The following figure depicts the details to be provided to add Dynatrace as an integration.
Enter the information for the following fields:
Account Name: The name of the Dynatrace user account
URL: Dynatrace URL
API Token: Dynatrace personal access token
Group and Permissions: To enable access to all user groups, check the Enable all access to all the groups for this checkbox. To provide access to only selected user groups, uncheck this checkbox and select the required users from the Select Group drop down and enable the needed permissions like Edit, View or Delete.
The following figure depicts the information to be provided to add ElasticSearch as an integration.
Following are the fields:
Account Name: The name of your Elasticsearch user account
Elastic End Point: End of the Elasticsearch URL for the account
User Name: Provide the user name for the ElasticSearch instance
Password: Provide the password for the ElasticSearch instance
Kibana End Point: Endpoint URL for the Kibana instance
Kibana User Name: Provide the username for the Kibana instance
Kibana Password: Provide the password for the Kibana instance
Group and Permissions: To enable access to all user groups, check the Enable all access to all the groups for this checkbox. To provide access to only selected user groups, uncheck this checkbox and select the required users from the Select Group drop down and enable the needed permissions like Edit, View or Delete.
The following figure depicts the information to be provided to add Graphite as an integration.
Update the following information in the above screen:
Account Name: The name of your Graphite user account
End Point: URL of the endpoint of Graphite
Group and Permissions: To enable access to all user groups, check the Enable all access to all the groups for this checkbox. To provide access to only selected user groups, uncheck this checkbox and select the required users from the Select Group drop down and enable the needed permissions like Edit, View or Delete.
The following figure depicts the information to be provided to add Graylog as an integration.
Update the following information in the above screen:
Account Name: The name of your Graylog user account
End Point: End of the Graylog URL for the account
Token: Your Graylog account access token.
Group and Permissions: To enable access to all user groups, check the Enable all access to all the groups for this checkbox. To provide access to only selected user groups, uncheck this checkbox and select the required users from the Select Group drop down and enable the needed permissions like Edit, View or Delete.
The following figure depicts the information to be provided to add New Relic as an integration.
Following are the fields:
Account Name: The name of your New Relic user account
Account Id : Provide the account ID
Query Key : Provide the query key to filter the data
Group and Permissions: To enable access to all user groups, check the Enable all access to all the groups for this checkbox. To provide access to only selected user groups, uncheck this checkbox and select the required users from the Select Group drop down and enable the needed permissions like Edit, View or Delete.
The following figure depicts the information to be provided to add Prometheus as an integration.
Following are the fields:
Account Name: The name of your Prometheus user account
End Point: The base URL to the Prometheus server
User Name: Provide the Prometheus User Name
Password: Provide the Prometheus Password
Group and Permissions: To enable access to all user groups, check the Enable all access to all the groups for this checkbox. To provide access to only selected user groups, uncheck this checkbox and select the required users from the Select Group drop down and enable the needed permissions like Edit, View or Delete.
The following figure depicts the information to be provided to add Splunk as an integration.
Following are the fields:
Account Name: The name of your Splunk user account
Splunk URL: The base URL to the Splunk server
User Name: Provide the Splunk user name
Password: Provide the Splunk password
Splunk Dashboard URL: Provide URL of the Splunk dashboard
Group and Permissions: To enable access to all user groups, check the Enable all access to all the groups for this checkbox. To provide access to only selected user groups, uncheck this checkbox and select the required users from the Select Group drop down and enable the needed permissions like Edit, View or Delete.
The following figure depicts the information to be provided to add Stackdriver as an integration.
Account Name: The name of your Stackdriver user account
Encrypted Key File: A path to a Google JSON service account that has permission to publish metrics.
Group and Permissions: To enable access to all user groups, check the Enable all access to all the groups for this checkbox. To provide access to only selected user groups, uncheck this checkbox and select the required users from the Select Group drop down and enable the needed permissions like Edit, View or Delete.
The following figure depicts the information to be provided to add SumoLogic as an integration.
Following are the fields:
Account Name: The name of your Sumologic user account
Access ID: Sumoligic access Id. You can generate Access Id (Administration > Security > Access Keys)
Access Key: Sumoligic access key. You can generate Access Id (Administration > Security > Access Keys)
Zone: Sumoligic Zone
Group and Permissions: To enable access to all user groups, check the Enable all access to all the groups for this checkbox. To provide access to only selected user groups, uncheck this checkbox and select the required users from the Select Group drop down and enable the needed permissions like Edit, View or Delete.
We have extended the list of supported monitoring tools by adding support to Tanzu Observability from VMware. Now you can use ISD to perform continuous verification on Metrics from Tanzu Observability to get real-time insights and mitigate risks during continuous delivery.
The below figure depicts the information to be provided to add VMWare Tanzu Observability as an integration.
Account Name: The name of your VMWare Tanzu Observability user account
End Point: Provide the URL of the VMWare Tanzu Observability server
Email: Provide the user authorized Email ID
API Token: Provide the API token for VMWare Tanzu Observability
Group and Permissions: To enable access to all user groups, check the Enable all access to all the groups for this checkbox. To provide access to only selected user groups, uncheck this checkbox and select the required users from the Select Group drop down and enable the needed permissions like Edit, View or Delete.
Add Monitoring Provider : Add AppDynamics as an integration. To add an integration, . Search "AppDynamics" and select AppDynamics under Monitoring Tools.
Temporary Access Token: You can generate and use the access token for API access calls into your Controller by generating the token through Administration UI. The account administrator can generate and distribute to parties/teams who need controller access. To generate the token, .
To use AppDynamics Provider for verification, .
API Key: Your organizations unique Datadog API key. See
Application Key: Your Datadog application key. See
API Key: Your account’s unique New Relic Insights API key. See .
Application Key: Your New Relic account id. See .
