Skip to content

[Dynatrace] Initial commit to introduce a Dynatrace integration to ingest data#18744

Open
adrianchen-es wants to merge 7 commits into
elastic:mainfrom
adrianchen-es:ac-dynatrace-cel
Open

[Dynatrace] Initial commit to introduce a Dynatrace integration to ingest data#18744
adrianchen-es wants to merge 7 commits into
elastic:mainfrom
adrianchen-es:ac-dynatrace-cel

Conversation

@adrianchen-es
Copy link
Copy Markdown
Contributor

Proposed commit message

Add Dynatrace integration package (technical preview, community-supported)

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices (no dashboards in this PR)

Author's Checklist

  • Confirm policy template names (dynatrace_saas, dynatrace_managed) and input titles/descriptions match product wording expectations.
  • Confirm owner.type/community and per–data stream release: experimental match Elastic packaging guidance for third-party preview integrations.
  • Sanity-check Dynatrace API paths and query parameter names against current Dynatrace documentation for the targeted API versions.

How to test this PR locally

Prerequisites: Docker, Elastic stack profile for elastic-package (e.g. stack running), and the elastic-package CLI.

From the repository root (or with -p pointing at packages/dynatrace if your CLI supports it):

cd packages/dynatrace

# Lint / format (adjust binary path if needed)
elastic-package format
elastic-package lint

# Pipeline tests (need Elasticsearch from the active profile)
elastic-package test pipeline

# System tests (Docker agents + per–data stream mock services; slower)
elastic-package test system
# Or limit scope, for example:
elastic-package test system --data-streams audit_logs,environments,problems,tenant_problems

Ensure each data stream’s _dev/deploy/docker mock reflects the APIs that stream calls.

Related issues


Screenshots

Optional for this PR: there are no Kibana dashboards included. Future PRs can attach Fleet integration configuration screens once UX review is desired.

@adrianchen-es adrianchen-es requested a review from a team as a code owner April 30, 2026 11:37
@adrianchen-es adrianchen-es added enhancement New feature or request New Integration Issue or pull request for creating a new integration package. >enhancement labels Apr 30, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 30, 2026

Vale Linting Results

Summary: 7 warnings, 7 suggestions found

⚠️ Warnings (7)
File Line Rule Message
packages/dynatrace/docs/README.md 203 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/dynatrace/docs/README.md 210 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/dynatrace/docs/README.md 301 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.
packages/dynatrace/docs/README.md 302 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/dynatrace/docs/README.md 304 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.
packages/dynatrace/docs/README.md 480 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.
packages/dynatrace/docs/README.md 495 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
💡 Suggestions (7)
File Line Rule Message
packages/dynatrace/_dev/build/docs/README.md 12 Elastic.Ellipses In general, don't use an ellipsis.
packages/dynatrace/_dev/build/docs/README.md 21 Elastic.Ellipses In general, don't use an ellipsis.
packages/dynatrace/_dev/build/docs/README.md 21 Elastic.Ellipses In general, don't use an ellipsis.
packages/dynatrace/docs/README.md 12 Elastic.Ellipses In general, don't use an ellipsis.
packages/dynatrace/docs/README.md 21 Elastic.Ellipses In general, don't use an ellipsis.
packages/dynatrace/docs/README.md 21 Elastic.Ellipses In general, don't use an ellipsis.
packages/dynatrace/docs/README.md 493 Elastic.Wordiness Consider using 'because' instead of 'since'.

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

Comment thread packages/dynatrace/data_stream/license_usage/fields/fields.yml
Comment thread packages/dynatrace/data_stream/license_usage/fields/fields.yml Outdated
Comment thread packages/dynatrace/data_stream/tenant_problems/agent/stream/cel.yml.hbs Outdated
Comment thread packages/dynatrace/data_stream/environments/agent/stream/cel.yml.hbs Outdated
Comment thread packages/dynatrace/data_stream/problems/elasticsearch/ingest_pipeline/default.yml Outdated
@andrewkroh andrewkroh added documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. and removed New Integration Issue or pull request for creating a new integration package. labels Apr 30, 2026
@elastic-vault-github-plugin-prod
Copy link
Copy Markdown

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@elasticmachine
Copy link
Copy Markdown

💚 Build Succeeded

History

@andrewkroh andrewkroh added the New Integration Issue or pull request for creating a new integration package. label May 11, 2026
@narph narph requested a review from a team May 19, 2026 12:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. enhancement New feature or request >enhancement New Integration Issue or pull request for creating a new integration package.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants