Instana

Instana is a web-based automated APM solution for cloud-native, multi-cloud, and hybrid cloud applications. It is used for monitoring and managing the performance of software used in microservice architectures and provides 3D visualisations of performance through graphs generated using machine learning algorithms.

In order to integrate Instana with Relyance AI you will need your API Token and Subdomain.

In Instana:

1. Login to your Instana instance.

2. Go to Settings in the left-hand navigation menu.

3. Click API Tokens in the Settings menu.

4. Click the + Add API Token link.

5. Fill in the API form to create the token. Name: Provide a meaningful name (e.g. Relyance AI) Permissions:

6. Click Save.

7. Copy your new API Token from the token dashboard.

8. The Subdomain will be the subdomain found in your Instana URL.

In the Relyance AI application:

1. Login to your Relyance account.
2. Navigate to the Settings Menu in the bottom left-hand side.
3. Select Integrations.
4. Click on the Vendor Integration tab.
5. Find the Instana integration card and click it to open its connections.
6. Under Authentication Method, choose Custom.
7. Paste the API Token and Subdomain into their respective fields.

The Authentication step asks for:

• API Token: required; held as a secret.
• Subdomain: required.

9. Click Authenticate.
10. At this point, you should see the following result on the Vendor Integrations page:

11. Congratulations, you are now connected to Instana.

If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. A credential rotated at the vendor is not picked up here. API Token is stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.
2. Check the address fields before suspecting the credentials. Subdomain identifies which tenant, region or host to talk to. A wrong value there fails authentication and looks exactly like a bad secret.

Manage this integration with Terraform

Connections for this integration can be managed as code with the Relyance Terraform provider. Non-secret fields go in auth.params; secret fields go in auth.secrets_wo, which is write-only — never stored in Terraform state. Rotate secrets by bumping auth.secrets_wo_version.

resource "relyance_integration_connection" "instana" {
  vendor = "instana"
  name   = "<your connection name>"

  auth = {
    method = "api-token"
    params = {
      subdomain = "<subdomain>"
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      api_token = var.instana_api_token
    }
    secrets_wo_version = 1
  }

  scans = { "property-inspection" = { enabled = true } }
}