Dynatrace Extension Migrator

Helps with moving the configurations of select Extensions 1.0 extensions to their 2.0 equivalents.

Requirements

Python 3.10+
An API token:
- Ust the 'Extension Development' token or provide the following scopes:
  - extensions.read
  - extensionConfigurations.read
  - extensionConfigurations.write

Installation

pip install dt-extension-migrator

Usage

Each supported EF1 extension has a subcommand e.g. dt-ext-migrator remote-unix --help

Each will have a similar set of commands for pulling the EF1 configurations and pushing the converted EF2 extensions to the Dynatrace environment.

Environment details

You can specify the Dynatrace environment URL and API token either in the --dt-url and --dt-token options or in DT_URL and DT_TOKEN environment variables (recommended).

Pulling configurations

When pulling EF1 configurations you can specify the output file (optional) and one or more "indexes" by specifying the --index option for each field you want to 'group' configurations on. For example, if you want to group just on the 'group' in the EF1 configuration you can run:

dt-ext-migrator remote-unix pull --index group

If you want to group by the group and the configured username you can run:

dt-ext-migrator remote-unix pull --index group --index username

You will have an Excel spreadsheet generated with a tab for each set of grouped dimensions you will be able to use when pushing the converted configs.

Pushing configurations

Once you have the spreadsheet generated you can use this to convert and push the configurations to their EF2 equivalents.

dt-ext-migrator remote-unix push --input-file .\custom.remote.python.remote_agent-export.xlsx --sheet group1-myuser --version 1.0.0 --ag-group ag_group-default

Tips:

The --ag-group option can be specified with or without the leading ag_group- prefix
Fields you should review/update manually will be the authentication (top-level monitoring configuration level is recommended) and the top-level 'group' setting if used

A summary will be printed after a successful push. E.g.:

2 endpoints will attempt to be added to the monitoring configuration.
Configs created successfully. Response: 200
Link to monitoring configuration: https://<environment>/ui/hub/ext/listing/registered/<extensionId>/fe14090c-4bfe-30b5-b88b-84a8e6f65607/read

The configuration will be disabled by default so you can review it, add authentication, and making any other needed chagnes before enabling.

Release files for dt-extension-migrator 0.5.7

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dt-extension-migrator 0.5.7
File	Size	Uploaded
dt_extension_migrator-0.5.7.tar.gz	68.7 kB	Nov 11, 2024	Details

Built distribution (wheel)

Table of built distributions (wheels) for dt-extension-migrator 0.5.7
File	Interpreter	ABI	Platform	Reset
dt_extension_migrator-0.5.7-py3-none-any.whl 28.5 kB Nov 11, 2024	Python 3	none	any	Details

Total release size: 97.3 kB

Release files / dt_extension_migrator-0.5.7.tar.gz

Download URL	dt_extension_migrator-0.5.7.tar.gz
Size	68.7 kB
Tags	Source
SHA-256 checksum How to use checksums	`ed482359d80dc685e690935c69ccb0cf4c368b02e7c616e5cbdfae142a209671`
BLAKE2b-256 checksum How to use checksums	`08d8fdfc20d58dac123cccc31a2366db730350bf91cc78724927ac002966fe84`
Upload date	Nov 11, 2024
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`poetry/1.8.3 CPython/3.10.12 Windows/10`

Release files / dt_extension_migrator-0.5.7-py3-none-any.whl

Download URL	dt_extension_migrator-0.5.7-py3-none-any.whl
Size	28.5 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`8a7d3f8a57b885236ea83fa5af024854061617f191604270a6d05db5838c3cc5`
BLAKE2b-256 checksum How to use checksums	`73eb42e35ee03c9ceee9f1762124a83b1bbb95a4dc6f985853a160e7dfecf2f4`
Upload date	Nov 11, 2024
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`poetry/1.8.3 CPython/3.10.12 Windows/10`