Conversation
6136249 to
1ec5a36
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 56a401ba80
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| @@ -0,0 +1 @@ | |||
| Please build an out-of-the-box dashboard for your integration following our best practices here: https://datadoghq.dev/integrations-core/guidelines/dashboards/#best-practices No newline at end of file | |||
There was a problem hiding this comment.
Replace dashboard placeholder with valid JSON
The dashboard file is plain text, not JSON. Any tooling that parses dashboards (for example, validation or dashboard import) expects valid JSON in assets/dashboards/*.json; with the current contents, those workflows will fail or skip this dashboard, so the integration ships without a usable dashboard. Replace the placeholder with a valid dashboard JSON (or remove the file if no dashboard is intended).
Useful? React with 👍 / 👎.
|
Hi @mrafi97, just confirming because |
|
Created DOCS-13096 for documentation team review |
|
Hi @buraizu yeah should be fine to review. My plan is to merge this to master for now as is and then later on set |
evazorro
left a comment
There was a problem hiding this comment.
Left a couple minor fixes and a couple questions!
| @@ -0,0 +1 @@ | |||
| Please build an out-of-the-box dashboard for your integration following our best practices here: https://datadoghq.dev/integrations-core/guidelines/dashboards/#best-practices No newline at end of file | |||
There was a problem hiding this comment.
@mrafi97 are you planning to add dashboards in this PR? Or will that come when you're ready to GA?
There was a problem hiding this comment.
I'm not planning on adding a dashboard on this PR, it will be added in a different PR.
Co-authored-by: Eva Parish <eva.parish@datadoghq.com>
Co-authored-by: Sarah Witt <sarah.witt@datadoghq.com>
Review from evazorro is dismissed. Related teams and files:
- documentation
- battery/manifest.json
Co-authored-by: Sarah Witt <sarah.witt@datadoghq.com>
* adding battery check tile * updating information * updating codeowners * updating readme * removing images folder * adjusting metadata.csv * fixing CI errors * fixing ddev error * updating readme * Apply suggestions from code review Co-authored-by: Eva Parish <eva.parish@datadoghq.com> * Delete battery/assets/dashboards/battery_overview.json * Apply suggestions from code review Co-authored-by: Sarah Witt <sarah.witt@datadoghq.com> * Update battery/manifest.json Co-authored-by: Sarah Witt <sarah.witt@datadoghq.com> --------- Co-authored-by: Eva Parish <eva.parish@datadoghq.com> Co-authored-by: Sarah Witt <sarah.witt@datadoghq.com> 770094e
* adding battery check tile * updating information * updating codeowners * updating readme * removing images folder * adjusting metadata.csv * fixing CI errors * fixing ddev error * updating readme * Apply suggestions from code review Co-authored-by: Eva Parish <eva.parish@datadoghq.com> * Delete battery/assets/dashboards/battery_overview.json * Apply suggestions from code review Co-authored-by: Sarah Witt <sarah.witt@datadoghq.com> * Update battery/manifest.json Co-authored-by: Sarah Witt <sarah.witt@datadoghq.com> --------- Co-authored-by: Eva Parish <eva.parish@datadoghq.com> Co-authored-by: Sarah Witt <sarah.witt@datadoghq.com> Signed-off-by: lukepatrick <lukephilips@gmail.com>
What does this PR do?
This PR adds the initial manifest and readme for the Battery check that was added in DataDog/datadog-agent#43789 and DataDog/datadog-agent#44371
Motivation
https://datadoghq.atlassian.net/browse/WINA-2204
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged