Generate configuration
The Generate Configuration page produces configuration artifacts and supports the NoCode configuration type.
The Generate Configuration page produces configuration artifacts for review and deployment. Input requirements vary based on the selected configuration type.
Currently, the Migration tool supports the NoCode configuration type. For the NoCode configuration type, select an Splunk AppDynamics source connection and an application.
Access the generate configs page
Access the Generate Configs page from Splunk Observability Cloud.
- Log in to the Splunk Observability Cloud.
- Select Data Management > Migration Tool.
- In the left navigation panel, expand Artifacts and select Configs.
- The Generate Configs page opens with the configuration form and the Submitted Configs table.
Generate a configuration
Generate a NoCode configuration by selecting a type, source connection, application, and optional name.
Configuration generation form details
Reference information for the fields, controls, table columns, and statuses in the configuration generation form.
Use the form to configure and generate a new configuration file.
Config type selector
Select the Config Type drop-down to select the type of configuration you want to generate.
| Config type | Description |
|---|---|
|
NoCode Configuration |
NoCode Configuration converts your Splunk AppDynamics Java POJO Business Transaction detection rules into tier-specific YAML files, which you download as a single ZIP archive. This process does not create a single, generic Splunk Observability Cloud configuration file. Review the generated file before deployment. |
NoCode Configuration type.
Configuration fields for NoCode type
After you select a config type, view the following details:
| Field | Description |
|---|---|
|
Add source connection |
The Splunk AppDynamics source connection from which the system reads the application’s monitoring setup. The drop-down lists source connections configured on the Connections page and displays the connection name and Controller URL. |
|
Application |
The Splunk AppDynamics application for which you want to generate a configuration. Select the drop-down to browse or enter text to search through discovered applications. |
|
Config name (optional) |
A custom name for the configuration job. If you leave it blank, the system auto-generates a name using the application name and timestamp. |
Generate configuration
Select the Generate Config button to start generating the configuration. The system connects to the selected Splunk AppDynamics Controller, reads the application’s monitoring configuration, and generates the corresponding Splunk Observability Cloud configuration file. The system displays the generated configuration in the Submitted Configs table after it submits the request. The job moves through various stages: Submitted, Generating, Ready, or Failed.
Configuration list
The section lists the generated configurations in a searchable, filterable table.
Search and filter controls
| Control | Description |
|---|---|
|
Search by Name |
Filters configurations by name as you type. |
|
All config types |
Filters configurations by config type, such as NoCode Configuration. |
|
All Status |
Filters configurations by status, such as All Status, Submitted, Generating, Ready, or Failed. |
|
Refresh |
Reloads the table to show the latest configuration status. |
Configs table columns
The table displays the following information:
| Column | Description |
|---|---|
|
Config Name |
The custom or auto-generated name of the configuration. |
|
Config Type |
The generated configuration type, such as NoCode Configuration. |
|
Source Connection |
The Splunk AppDynamics source connection used to generate the configuration. |
|
Status |
The current status of the configuration generation job. |
|
Created by |
The user who generated the configuration. |
|
Created at |
The date and time when the system generated the configuration. |
|
Actions |
Includes the download action for retrieving the generated configuration file. |
Configuration statuses
| Status | Description | Action |
|---|---|---|
| Submitted | The system received the configuration request and queued it for processing. | - |
| Generating | The system actively generates the configuration file from the selected Splunk AppDynamics application. | - |
| Ready | The system generated the configuration successfully and made it available for download. | Select the download icon in the Actions column. |
| Failed | The configuration generation failed, often because of an expired token, unreachable Controller, or insufficient permissions. | Verify the source connection and regenerate the configuration. |
To confirm configuration-generation activity, review the Configuration entries on the Audit Logs page. After a NoCode configuration-generation job reaches Ready or Failed, the audit entry records the outcome, action, user, and timestamp.
Use generated configurations
Use the downloaded NoCode configuration archive to configure the Java application and validate telemetry.
For NoCode Configuration, the downloaded artifact contains tier-specific YAML files in a ZIP archive.
-
Extract the ZIP archive: Download the generated NoCode configuration and extract the ZIP file to view the tier-specific YAML files.
-
Select the applicable tier YAML: Select the YAML file that matches the application tier you want to instrument.
-
Make the YAML available to the Java application: Place the selected YAML file in a location that the Java application can access at startup.
-
Configure the Java agent to load the YAML: Update the Splunk OpenTelemetry Java agent configuration so the agent loads the selected tier YAML when the application starts.
-
Restart the application: Restart the Java application so the updated Java agent configuration takes effect.
-
Validate telemetry in Splunk APM: Verify that traces are received and that the expected Business Transactions are represented in Splunk Observability Cloud.