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

[infoblox_nios] Handle bad values in IP and Date fields #4489

Merged
merged 2 commits into from
Oct 26, 2022

Conversation

vinit-chauhan
Copy link
Contributor

@vinit-chauhan vinit-chauhan commented Oct 21, 2022

Type of change

  • Enhancement

What does this PR do?

This PR adds support for handling bad values in IP and Date fields. Below is the table showing the more updates on this PR.

No. Updates
1 Add support of on_failure processor in convert processor
2 Add support of on_failure processor in date processor
3 Remove saved library visualizations

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.

How to test this PR locally

Screenshots

Pipeline test
System test
Static Test
asset test

Related issues

@elasticmachine
Copy link

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@elasticmachine
Copy link

elasticmachine commented Oct 21, 2022

🚀 Benchmarks report

Package infoblox_nios 👍(1) 💚(0) 💔(0)

Expand to view
Data stream Previous EPS New EPS Diff (%) Result
log 1650.17 1700.68 50.51 (3.06%) 👍

To see the full report comment with /test benchmark fullreport

@elasticmachine
Copy link

elasticmachine commented Oct 21, 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-10-21T18:00:54.768+0000

  • Duration: 15 min 22 sec

Test stats 🧪

Test Results
Failed 0
Passed 20
Skipped 0
Total 20

🤖 GitHub comments

Expand to view the GitHub comments

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

  • /test : Re-trigger the build.

@elasticmachine
Copy link

🌐 Coverage report

Name Metrics % (covered/total) Diff
Packages 100.0% (1/1) 💚
Files 100.0% (4/4) 💚 2.547
Classes 100.0% (4/4) 💚 2.547
Methods 100.0% (40/40) 💚 9.779
Lines 95.625% (612/640) 👍 4.108
Conditionals 100.0% (0/0) 💚

@vinit-chauhan
Copy link
Contributor Author

/test benchmark fullreport

Copy link
Contributor

@efd6 efd6 left a comment

Choose a reason for hiding this comment

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

This LGTM, but it would be good to know why the non-semantic changes were made.

@@ -17,51 +17,75 @@ processors:
- rename:
field: _conf.tz_offset
target_field: event.timezone
if: "ctx?._conf?.tz_offset != null && ctx._conf.tz_offset != 'local'"
if: ctx?._conf?.tz_offset != null && ctx._conf.tz_offset != 'local'
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
if: ctx?._conf?.tz_offset != null && ctx._conf.tz_offset != 'local'
if: ctx._conf?.tz_offset != null && ctx._conf.tz_offset != 'local'

@@ -1,43 +1,48 @@
# newer versions go on top
- version: "1.3.1"
- version: '1.3.2'
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a reason for the ~global replace of " with '?

@taylor-swanson
Copy link
Contributor

I have an SDH waiting on this fix. If there are no other blockers, could we get this merged? I'll merge it tomorrow if no one beats me to it by then.

@efd6 efd6 merged commit d3b646f into elastic:main Oct 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Integration:infoblox_nios Infoblox NIOS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants