9.3 - Appvance Integrations

• AIQ Integrations Knowledge Base Overview
• Configure Jenkins Integration for AIQ
• GIT - What happens if the same file is modified by 2 users
• GitHub - Creating a personal Access token
• What is Health Rules in AppDynamics Integration?
• When executed from Jenkins where the results will be stored

AIQ Integrations Knowledge Base Overview

AIQ Integrations Knowledge Base Overview

Use this overview for maintained AIQ integration articles, including CI/CD, Jira, Jenkins, source control, and external service connections.

Recommended guidance

• Keep one canonical article for each integration setup.
• Move one-off examples into troubleshooting notes only when still relevant.
• Do not include tenant-specific secrets, tokens, or internal URLs.
• Use current product names and supported authentication patterns.

Validation workflow

1. Confirm the integration is still supported and maintained.
2. Update setup, permission, and validation steps.
3. Consolidate duplicates into the canonical article.
4. Record tested environment and AIQ release assumptions.

Last updated: September 20, 2026

Configure Jenkins Integration for AIQ

Configure Jenkins Integration for AIQ

Use Jenkins integration to trigger, orchestrate, or track AIQ-related automation from a controlled CI/CD workflow.

Recommended guidance

• Use approved credentials or token management.
• Parameterize environment, suite, branch, and execution profile values.
• Avoid storing secrets directly in Jenkins job descriptions or documentation.
• Record Jenkins build URLs with AIQ execution evidence.

Validation workflow

1. Configure the Jenkins job with approved parameters.
2. Run a non-production validation build.
3. Confirm AIQ execution or integration output.
4. Document failures with Jenkins build URL, AIQ execution ID, and logs.

Last updated: September 20, 2026

GIT - What happens if the same file is modified by 2 users

There is a small possibility of a merge conflict situation. When that happens, need to delete the repository and recreate it from Appvance IQ.

Changes done by a second person trying to push will be lost.

If there is no conflict, changes done by the first person will be overwritten by changes saved by the second person.

Recommended approach

The recommended approach would be to create branches per person and merge the code to the master or the main branch.

GitHub - Creating a personal Access token

https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token

Authorizing a personal access token for use with SAML single sign-on

https://docs.github.com/en/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on

What is Health Rules in AppDynamics Integration?

Health Rules:

• Checking that option will provide details of all critical, warning and error of health rules (defined by the user) of that application.
• Health rules are created in the application itself. Users can create health rules like if there are more than 500 connections mark it as Critical, if there are more than 5000 connections, mark it as a warning etc. All these are done in AppDynamics itself
• There is an feature in AppDynamics called Health Rule violations - Users can define these over there.
• In UTP reports, it will show either as a 1 or 0 depending on the outcome.
• Users can create config files for multiple applications, Users can create one single config file to monitor multiple applications as well.
• Config files can be exported and imported based on user requirements and can be edited easily.

When executed from Jenkins where the results will be stored

All the results will be stored in DB which you can retreive using the Execution ID