Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add event data generation to dev docs #30395

Merged
merged 3 commits into from
Apr 7, 2022

Conversation

endorama
Copy link
Member

What does this PR do?

Update developer documentation with information on how to run sample event generation from Go tests.

Why is it important?

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

@endorama endorama added the docs label Feb 15, 2022
@endorama endorama self-assigned this Feb 15, 2022
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Feb 15, 2022
@mergify
Copy link
Contributor

mergify bot commented Feb 15, 2022

This pull request does not have a backport label. Could you fix it @endorama? 🙏
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 Feb 15, 2022
@elasticmachine
Copy link
Collaborator

elasticmachine commented Feb 15, 2022

💚 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-04-07T08:35:03.203+0000

  • Duration: 19 min 43 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 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!)

@mtojek mtojek added the Team:Integrations Label for the Integrations team label Mar 21, 2022
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations (Team:Integrations)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Mar 21, 2022
@rdner
Copy link
Member

rdner commented Apr 7, 2022

@Mergifyio update

@mergify
Copy link
Contributor

mergify bot commented Apr 7, 2022

update

✅ Branch has been successfully updated

@mergify mergify bot requested a review from a team as a code owner April 7, 2022 07:51
Co-authored-by: kaiyan-sheng <kaiyan.sheng@elastic.co>
@rdner rdner merged commit f0cf71f into elastic:main Apr 7, 2022
kush-elastic pushed a commit to kush-elastic/beats that referenced this pull request May 2, 2022
docs: add test data generation info

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Co-authored-by: Denis Rechkunov <denis@rdner.de>
Co-authored-by: kaiyan-sheng <kaiyan.sheng@elastic.co>
chrisberkhout pushed a commit that referenced this pull request Jun 1, 2023
docs: add test data generation info

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Co-authored-by: Denis Rechkunov <denis@rdner.de>
Co-authored-by: kaiyan-sheng <kaiyan.sheng@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-skip Skip notification from the automated backport with mergify docs Team:Integrations Label for the Integrations team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants