Skip to content

Update fields.yml#29609

Merged
dedemorton merged 2 commits intomainfrom
dharada-patch-1
Feb 16, 2022
Merged

Update fields.yml#29609
dedemorton merged 2 commits intomainfrom
dharada-patch-1

Conversation

@dharada
Copy link
Copy Markdown
Contributor

@dharada dharada commented Dec 27, 2021

it looks typo there. Can you take a look at this PR ?

@dharada
Update fields.yml
e9bf168 
it looks typo there. Can you take a look at this PR ?
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Dec 27, 2021
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Dec 27, 2021

This pull request does not have a backport label. Could you fix it @dharada? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v./d./d./d is the label to automatically backport to the 7./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

@mergify mergify bot added the backport-skip Skip notification from the automated backport with mergify label Dec 27, 2021
@dharada dharada added docs Team:Docs Label for the Observability docs team labels Dec 27, 2021
@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Dec 27, 2021

Pinging @elastic/obs-docs (Team:Docs)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Dec 27, 2021
@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Dec 27, 2021 •
edited by jenkins-beats-ci bot
Loading

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-02-10T23:45:00.712+0000

  • Duration: 64 min 43 sec

Test stats 🧪

Test Results
Failed 0
Passed 4683
Skipped 774
Total 5457

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@dharada dharada added the backport-v7.16.0 Automated backport with mergify label Dec 27, 2021
@mergify mergify bot removed the backport-skip Skip notification from the automated backport with mergify label Dec 27, 2021
@botelastic
Copy link
Copy Markdown

botelastic bot commented Jan 26, 2022

Hi!
We just realized that we haven't looked into this PR in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it in as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!

@botelastic botelastic bot added the Stalled label Jan 26, 2022
@dharada dharada added the Filebeat Filebeat label Jan 26, 2022
@botelastic botelastic bot removed the Stalled label Jan 26, 2022
@mergify mergify bot assigned dharada Feb 8, 2022
@dharada dharada removed their assignment Feb 9, 2022
@mergify mergify bot assigned dharada Feb 9, 2022
@dharada
Copy link
Copy Markdown
Contributor Author

dharada commented Feb 9, 2022

hello @elastic/docs do you knwo why Mergify bot assigened me to this PR ? what is expected to me ?

@dedemorton
Copy link
Copy Markdown
Contributor

dedemorton commented Feb 9, 2022

I'll get this fixed and merged. Thanks!

@dedemorton dedemorton added backport-7.17 Automated backport to the 7.17 branch with mergify backport-v8.0.0 Automated backport with mergify backport-v8.1.0 Automated backport with mergify labels Feb 9, 2022
@dedemorton
Copy link
Copy Markdown
Contributor

dedemorton commented Feb 9, 2022 •
edited
Loading

@dharada You get assigned the PR so that you remember to merge the auto backports. BTW, I'm going to add backport tags for later releases. Let me know if there was some reason you only wanted to backport this to 7.16. If the changes are already in 7.17+, it's OK...the notice file should be updated anyhow.

@dharada
Copy link
Copy Markdown
Contributor Author

dharada commented Feb 10, 2022

@dharada You get assigned the PR so that you remember to merge the auto backports. BTW, I'm going to add backport tags for later releases. Let me know if there was some reason you only wanted to backport this to 7.16. If the changes are already in 7.17+, it's OK...the notice file should be updated anyhow.

hello @dedemorton sorry I'm not familiar about labeling on PR "auto backports etc..". It was my shortsighted labeling to just put backport to 7.16 only. (I just thought docs team will handle properly in anyway.)

(If we have some document or manual to know how to do labeling, I'd like to learn it. 😄 )

you remember to merge the auto backports.

I suppose no manual handling needed from my side anymore. but please let me know if something still expected to do from my side.

@dedemorton
Copy link
Copy Markdown
Contributor

dedemorton commented Feb 10, 2022

@dharada That's right. I can take it from here. Sorry about the confusing mergify messages. It's the downside of adding automation.

And all you wanted to do was fix a typo. :-)

@dedemorton
Copy link
Copy Markdown
Contributor

dedemorton commented Feb 10, 2022

jenkins run the tests please

@dedemorton dedemorton merged commit 342c4dc into main Feb 16, 2022
@dedemorton dedemorton deleted the dharada-patch-1 branch February 16, 2022 01:35
mergify bot pushed a commit that referenced this pull request Feb 16, 2022
@dharada @dedemorton
Update fields.yml (#29609)
c39fc0a 
Co-authored-by: dedemorton <dede.morton@elastic.co>
(cherry picked from commit 342c4dc)
@mergify mergify bot mentioned this pull request Feb 16, 2022
Merged
mergify bot pushed a commit that referenced this pull request Feb 16, 2022
@dharada @dedemorton
Update fields.yml (#29609)
144801d 
Co-authored-by: dedemorton <dede.morton@elastic.co>
(cherry picked from commit 342c4dc)
@mergify mergify bot mentioned this pull request Feb 16, 2022
Merged
mergify bot pushed a commit that referenced this pull request Feb 16, 2022
@dharada @dedemorton
Update fields.yml (#29609)
d330ecf 
Co-authored-by: dedemorton <dede.morton@elastic.co>
(cherry picked from commit 342c4dc)
@mergify mergify bot mentioned this pull request Feb 16, 2022
Merged
mergify bot pushed a commit that referenced this pull request Feb 16, 2022
@dharada @dedemorton
Update fields.yml (#29609)
293ad3e 
Co-authored-by: dedemorton <dede.morton@elastic.co>
(cherry picked from commit 342c4dc)
@mergify mergify bot mentioned this pull request Feb 16, 2022
Merged
mergify bot added a commit that referenced this pull request Feb 16, 2022
@mergify @dharada
Update fields.yml (#29609) (#30420)
c05a15d 
Co-authored-by: dedemorton <dede.morton@elastic.co>
(cherry picked from commit 342c4dc)

Co-authored-by: Daisuke Harada <1519063+dharada@users.noreply.github.com>
dedemorton pushed a commit that referenced this pull request Feb 16, 2022
@mergify @dharada
Update fields.yml (#29609) (#30421)
f595656 
Co-authored-by: dedemorton <dede.morton@elastic.co>
(cherry picked from commit 342c4dc)

Co-authored-by: Daisuke Harada <1519063+dharada@users.noreply.github.com>
dedemorton pushed a commit that referenced this pull request Feb 16, 2022
@mergify @dharada
Update fields.yml (#29609) (#30422)
7aedad2 
Co-authored-by: dedemorton <dede.morton@elastic.co>
(cherry picked from commit 342c4dc)

Co-authored-by: Daisuke Harada <1519063+dharada@users.noreply.github.com>
dedemorton pushed a commit that referenced this pull request Feb 16, 2022
@mergify @dharada
Update fields.yml (#29609) (#30423)
4387615 
Co-authored-by: dedemorton <dede.morton@elastic.co>
(cherry picked from commit 342c4dc)

Co-authored-by: Daisuke Harada <1519063+dharada@users.noreply.github.com>
v1v added a commit to v1v/beats that referenced this pull request Feb 21, 2022
@v1v
Merge branch 'feature/use-with-kind-k8s-env' of github.com:v1v/beats …
c20f180 
…into feature/use-with-kind-k8s-env

* 'feature/use-with-kind-k8s-env' of github.com:v1v/beats: (52 commits)
  ci: home is declared within withBeatsEnv
  ci: use withKindEnv step
  ci: use getBranchesFromAliases and support next-patch-8 (elastic#30400)
  Update fields.yml (elastic#29609)
  Heartbeat: fix browser metrics and trace mappings (elastic#30258)
  Apply light edits to 8.0 changelog (elastic#30351)
  packetbeat/beater: make sure Npcap installation runs before interfaces are needed (elastic#30396)
  Add a ring-buffer reporter to libbeat (elastic#28750)
  Osquerybeat: Add install verification for osquerybeat (elastic#30388)
  update windows matrix support (elastic#30373)
  Refactor of metricbeat process-gathering metrics and system/process (elastic#30076)
  adjust next changelog wording (elastic#30371)
  [Metricbeat] azure: move event report into loop validDim loop (elastic#29945)
  fix: report GitHub Check before the cache (elastic#30372)
  Add support for non-unique keys in Kafka output headers (elastic#30369)
  ci: 6 major branch reached EOL (elastic#30357)
  reduce Elastic Agent shut down time by stopping processes concurrently (elastic#29650)
  [Filebeat] Add message to register encode/decode debug logs (elastic#30271)
  [libbeat] kafka message header support (elastic#29940)
  Heartbeat: set duration to zero for syntax errors (elastic#30227)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@dedemorton dedemorton dedemorton approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@dharada dharada

Labels

backport-7.17 Automated backport to the 7.17 branch with mergify backport-v7.16.0 Automated backport with mergify backport-v8.0.0 Automated backport with mergify backport-v8.1.0 Automated backport with mergify docs Filebeat Filebeat Team:Docs Label for the Observability docs team

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@dharada @elasticmachine @dedemorton