[Dynatrace] Initial commit to introduce a Dynatrace integration to ingest data#18744
Open
adrianchen-es wants to merge 7 commits into
Open
[Dynatrace] Initial commit to introduce a Dynatrace integration to ingest data#18744adrianchen-es wants to merge 7 commits into
adrianchen-es wants to merge 7 commits into
Conversation
Contributor
Vale Linting ResultsSummary: 7 warnings, 7 suggestions found
|
| 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.
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
History
|
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message
Checklist
changelog.ymlfile.Author's Checklist
dynatrace_saas,dynatrace_managed) and input titles/descriptions match product wording expectations.owner.type/community and per–data streamrelease: experimentalmatch Elastic packaging guidance for third-party preview integrations.How to test this PR locally
Prerequisites: Docker, Elastic stack profile for
elastic-package(e.g. stack running), and theelastic-packageCLI.From the repository root (or with
-ppointing atpackages/dynatraceif your CLI supports it):Ensure each data stream’s
_dev/deploy/dockermock 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.