Hi all,
I'm running into a feature set error while upgrading an Oracle DB custom extension and I'm looking for a way to fix it without deleting and re-adding all the database endpoints.
Background:
- Last month an Oracle DB custom extension was created with a large set of metrics, and many database endpoints (monitoring configurations) were added and saved against it.
- Later, someone renamed things and created a new version of the extension, this time grouping the metrics into feature sets.
- The problem is that the existing database endpoints (with their IPs and connection details) were saved against the old extension/metric layout.
The issue: When I add new metrics in the new extension version and try to upgrade the existing database endpoints to that version, I get a feature set error. The only workaround I've found so far is to delete each database endpoint and re-add it under the new version, which is a lot of manual work across multiple region servers.
My question: Is there a way to migrate or upgrade the existing monitoring configurations to the new extension version so they pick up the new feature sets, without deleting and recreating every endpoint? For example:
- Is there an API call to update the activeFeatureSets on an existing monitoring configuration?
- Is there a recommended migration path when feature sets are introduced or changed between extension versions?
Environment: Dynatrace SaaS, custom Oracle DB extension (Extensions 2.0).
Any guidance or documentation would be appreciated. Thanks!
What the answer likely is (so you know what to look for)
The feature set error happens because the new extension version defines metrics inside feature sets that the old endpoints don't have enabled. When you upgrade, the config must reference the feature sets that exist in the target version.
You can often avoid full delete/recreate by updating the monitoring configuration via the API rather than through the UI. Each endpoint has an activeFeatureSets (or featureSets) field. Updating the config with the correct feature sets for the new version, using:
PUT /api/v2/extensions/{extensionName}/monitoringConfigurations/{configurationId}
can migrate it in place. That's the specific thing to ask the community to confirm, and it's what I've phrased the question around.
Two things worth adding to your post to get a faster, accurate answer:
- The exact error message text (copy it verbatim).
- The old and new extension version numbers.
Want me to tighten this into a shorter version, or add placeholders for the exact error message and version number
