Skip to content

Migrated Dynatrace Solution to use DCR#14003

Open
keyoke wants to merge 83 commits intoAzure:masterfrom
keyoke:users/gaemslie/migrate-dynatrace-ccp
Open

Migrated Dynatrace Solution to use DCR#14003
keyoke wants to merge 83 commits intoAzure:masterfrom
keyoke:users/gaemslie/migrate-dynatrace-ccp

Conversation

@keyoke
Copy link
Copy Markdown
Contributor

@keyoke keyoke commented Apr 7, 2026

Required items, please complete

Change(s):

  • Introduced v2 version of our Dynatrace connectors, which have been migrated to use DCR

Reason for Change(s):

  • Required by Microsoft

Version Updated:

  • Yes

Testing Completed:

  • Yes

Checked that the validations are passing and have addressed any issues that are present:

  • Yes

keyoke and others added 30 commits May 29, 2025 17:10
@keyoke keyoke requested review from a team as code owners April 7, 2026 09:31
@rahul0216 rahul0216 requested a review from Copilot April 7, 2026 10:10
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Migrates the Dynatrace solution to support DCR-based v2 connectors while keeping existing v1 connectors and updating parsers/release notes to accommodate the new schemas.

Changes:

  • Added v2 (DCR-based) Dynatrace connector assets (definitions, polling configs, DCRs, and tables) alongside existing v1 connectors.
  • Updated Dynatrace parsers to union v1 and v2 custom tables into a single function interface.
  • Updated solution metadata/release notes to reflect the DCR connector addition.

Reviewed changes

Copilot reviewed 28 out of 30 changed files in this pull request and generated 7 comments.

Show a summary per file
File Description
Solutions/Dynatrace/ReleaseNotes.md Updates release notes entry for the new DCR-based connectors.
Solutions/Dynatrace/Parsers/DynatraceSecurityProblems.yaml Adds v2 table support and unions v1/v2 outputs.
Solutions/Dynatrace/Parsers/DynatraceProblems.yaml Adds v2 table support and unions v1/v2 outputs.
Solutions/Dynatrace/Parsers/DynatraceAuditLogs.yaml Adds v2 table support and unions v1/v2 outputs.
Solutions/Dynatrace/Parsers/DynatraceAttacks.yaml Adds v2 table support and unions v1/v2 outputs.
Solutions/Dynatrace/Package/testParameters.json Not reviewed (ignored path per repo review rules).
Solutions/Dynatrace/Package/createUiDefinition.json Not reviewed (ignored path per repo review rules).
Solutions/Dynatrace/Data/Solution_Dynatrace.json Updates solution data definition to include v2 connector artifacts.
Solutions/Dynatrace/Data Connectors/Connector_Dynatrace_RuntimeVulnerabilities_table.json Not reviewed (ignored path per repo review rules).
Solutions/Dynatrace/Data Connectors/Connector_Dynatrace_RuntimeVulnerabilities_Polling_Config.json Not reviewed (ignored path per repo review rules).
Solutions/Dynatrace/Data Connectors/Connector_Dynatrace_RuntimeVulnerabilities_Definition.json Not reviewed (ignored path per repo review rules).
Solutions/Dynatrace/Data Connectors/Connector_Dynatrace_RuntimeVulnerabilities_DCR.json Not reviewed (ignored path per repo review rules).
Solutions/Dynatrace/Data Connectors/Connector_Dynatrace_RuntimeVulnerabilities.json Not reviewed (ignored path per repo review rules).
Solutions/Dynatrace/Data Connectors/Connector_Dynatrace_Problems_table.json Not reviewed (ignored path per repo review rules).
Solutions/Dynatrace/Data Connectors/Connector_Dynatrace_Problems_Polling_Config.json Not reviewed (ignored path per repo review rules).
Solutions/Dynatrace/Data Connectors/Connector_Dynatrace_Problems_Definition.json Not reviewed (ignored path per repo review rules).
Solutions/Dynatrace/Data Connectors/Connector_Dynatrace_Problems_DCR.json Not reviewed (ignored path per repo review rules).
Solutions/Dynatrace/Data Connectors/Connector_Dynatrace_Problems.json Not reviewed (ignored path per repo review rules).
Solutions/Dynatrace/Data Connectors/Connector_Dynatrace_AuditLogs_table.json Not reviewed (ignored path per repo review rules).
Solutions/Dynatrace/Data Connectors/Connector_Dynatrace_AuditLogs_Polling_Config.json Not reviewed (ignored path per repo review rules).
Solutions/Dynatrace/Data Connectors/Connector_Dynatrace_AuditLogs_Definition.json Not reviewed (ignored path per repo review rules).
Solutions/Dynatrace/Data Connectors/Connector_Dynatrace_AuditLogs_DCR.json Not reviewed (ignored path per repo review rules).
Solutions/Dynatrace/Data Connectors/Connector_Dynatrace_AuditLogs.json Not reviewed (ignored path per repo review rules).
Solutions/Dynatrace/Data Connectors/Connector_Dynatrace_Attacks_table.json Not reviewed (ignored path per repo review rules).
Solutions/Dynatrace/Data Connectors/Connector_Dynatrace_Attacks_Polling_Config.json Not reviewed (ignored path per repo review rules).
Solutions/Dynatrace/Data Connectors/Connector_Dynatrace_Attacks_Definition.json Not reviewed (ignored path per repo review rules).
Solutions/Dynatrace/Data Connectors/Connector_Dynatrace_Attacks_DCR.json Not reviewed (ignored path per repo review rules).
Solutions/Dynatrace/Data Connectors/Connector_Dynatrace_Attacks.json Not reviewed (ignored path per repo review rules).

keyoke added 5 commits April 7, 2026 12:34
…g Microsoft Technologies used

- In Log Analytics custom logs, fields ending with _d are typically already datetime. Passing a datetime into unixtime_milliseconds_todatetime() will fail at runtime.
@v-maheshbh
Copy link
Copy Markdown
Contributor

v-maheshbh commented Apr 9, 2026

Hi @keyoke

Kindly create a separate folder for the CCF connector to ensure proper structure and compliance with standards. In case multiple connectors are present, please ensure that each connector is organized within its own separate folder.

Thanks!

@keyoke
Copy link
Copy Markdown
Contributor Author

keyoke commented Apr 9, 2026

Hi @keyoke

Kindly create a separate folder for the CCF connector to ensure proper structure and compliance with standards. In case multiple connectors are present, please ensure that each connector is organized within its own separate folder.

Thanks!

Hi @v-maheshbh,
Sure no problem I have pushed this change!
Regards
Gareth

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants