Available Integrations
ISD-Argo offers integration with many CI/CD Tools. Integrations can help your team coordinate and control your CI/CD process by supporting integrations with Monitoring tools.
Available integrations are as follows:
AWS Cloudwatch
The following figure depicts the information to be supplied to add AWS CloudWatch as an integration.
Update the following information on the above screen.
Account Name: Name of the AWS Cloudwatch account to operate on
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
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.
AppDynamics
The following figure depicts the information to be supplied to add AppDynamics as an integration.
Update 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/
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, refer here.
Datadog
The following figure depicts the information to be supplied to add DataDog as an integration.
Update the following information on the above screen:
Account Name: Name of the Datadog account to operate on
API Key: Your organization's unique Datadog API key. Refer here.
Application Key: Your Datadog application key. Refer here.
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.
Dynatrace
The following figure depicts the information to be supplied to add Dynatrace as an integration.
Update the following information on the above screen:
Account Name: Name of the Dynatrace account to operate on
URL: Dynatrace URL for the account to operate on
API Token: Your Dynatrace account access token.
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.
ElasticSearch
The following figure depicts the information to be supplied to add ElasticSearch as an integration.
Update the following information on the above screen:
Account Name: Name of the Elastic account to operate on
Elastic End Point: End of the Elasticsearch URL for the account to operate on
User Name(Optional): Provider the user name for the ElasticSearch instance
Password(Optional): Provider the password for the ElasticSearch instance
Kibana End Point(Optional): Endpoint URL for the Kibana instance
Kibana User Name(Optional): Provide the username for the Kibana instance
Kibana Password(Optional): Provide the password for the Kibana instance
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.
Graphite
The following figure depicts the information to be supplied to add Graphite as an integration.
Update the following information on the above screen:
Account Name: Name of the Graphite account to operate on
End Point: End of the Graphite URL for the account to operate on
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.
Graylog
The following figure depicts the information to be supplied to add Graylog as an integration.
Update the following information on the above screen:
Account Name: Name of the Graylog account to operate on
End Point: End of the Graylog URL for the account to operate on
Token: Your Graylog account access token.
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.
NewRelic
The following figure depicts the information to be supplied to add New Relic as an integration.
Update the following information on the above screen:
Account Name: Name of the New Relic account to operate on
API Key: Your account’s unique New Relic Insights API key. Refer here.
Application Key: Your New Relic Application key.
Account ID: Your New Relic account id. Refer here.
Query Key: Your New Relic Query key.
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.
Prometheus
The following figure depicts the information to be supplied to add Prometheus as an integration.
Update the following information on the above screen:
Account Name: Name of the New Relic account to operate on
End Point: The base URL to the Prometheus server
User Name(Optional): Provide Prometheus User Name
Password(Optional): Provide Prometheus Password
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.
Splunk
The following figure depicts the information to be supplied to add Splunk as an integration.
Update the following information on the above screen:
Account Name: Name of the Splunk account to operate on
Splunk URL: The base URL to the Splunk server
User Name(Optional): Provide Splunk user name
Password(Optional): Provide Splunk password
Splunk Dashboard URL(Optional): Provide URL of the Splunk dashboard
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.
Stackdriver
The following figure depicts the information to be supplied to add Stackdriver as an integration.
Update the following information on the above screen:
Account Name: Name of the Stackdriver account to operate on
Encrypted Key File: A path to a Google JSON service account that has permission to publish metrics.
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.
SumoLogic
The following figure depicts the information to be supplied to add SumoLogic as an integration.
Update the following information on the above screen:
Account Name: Name of the Sumologic account to operate on
Access ID: Sumoligic access Id. You can generate an Access Id (Administration > Security > Access Keys)
Access Key: Sumoligic access key. You can generate an Access Id (Administration > Security > Access Keys)
Zone: Sumoligic Zone
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.
VMWare Tanzu Observability
We have extended the list of supported monitoring tools by adding support to Tanzu Observability from VMware. Now you can use OEA 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.
Update the following information on the above screen:
Account Name: Name of the VMWare Tanzu Observability account to operate on
End Point: Provide the URL of the VMWare Tanzu Observability server
Email: VMWare Tanzu Observability email id
API Token: Provide the API token for VMWare Tanzu Observability
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.
Last updated
