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

fix(vcenter_parser): Add route for vCenter json parsing #414

Merged
merged 5 commits into from
Oct 10, 2023

Conversation

kuiperda
Copy link
Contributor

@kuiperda kuiperda commented Oct 5, 2023

Description of Changes

Adds a route to parse json coming from vCenter, based off #243

Please check that the PR fulfills these requirements

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • CI passes

@kuiperda kuiperda requested a review from a team as a code owner October 5, 2023 20:26
@kuiperda kuiperda requested a review from jsirianni October 5, 2023 20:26
Copy link
Member

@jsirianni jsirianni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Unless you have already, we should test the following cases:

  1. Our vcenter server still works with RFC5424
  2. Example GCVE json logs work without error.

Generally I will do something like this to test TCP based logs (assuming port 5142):

echo '{"timestamp": "2023-07-14T11:26:45.477", "severity": "info", "message' | nc localhost 5142

You can replace the json log I am using with one of the example GCVE logs that we have.

plugins/vmware_vcenter.yaml Outdated Show resolved Hide resolved
@jsirianni jsirianni self-requested a review October 6, 2023 15:46
@kuiperda kuiperda requested a review from schmikei October 10, 2023 19:50
@kuiperda kuiperda merged commit 3ffc808 into main Oct 10, 2023
@kuiperda kuiperda deleted the vcenter-json-route branch October 10, 2023 20:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants