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

[zscaler_zia] Remap network.protocol/scheme to valid values for uri_parts #4045

Merged
merged 3 commits into from
Aug 24, 2022

Conversation

taylor-swanson
Copy link
Contributor

@taylor-swanson taylor-swanson commented Aug 22, 2022

What does this PR do?

  • Add script processor to build URL for parsing. Script has parameters for valid
    protocols and a default protocol for a fallback. If network.protocol is valid,
    then it is used, otherwise the protocol (scheme) used for the URL will be
    the default (fallback) protocol. The original network.protocol is preserved.
  • Removed redundant processors
  • Add test cases
  • Rename test case files to comply with package spec
  • Regenerate pipeline test expected files

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

cd packages/zscaler_zia && elastic-package test

Related issues

- Add script processor to build URL for parsing. Script has parameters for valid
protocols and a default protocol for a fallback. If network.protocol is valid,
then it is used, otherwise the protocol (scheme) used for the URL will be
the default (fallback) protocol. The original network.protocol is preserved.
- Removed redundant processors
- Add test cases
- Rename test case files to comply with package spec
- Regenerate pipeline test expected files
@taylor-swanson
Copy link
Contributor Author

Side note, system test files/sample events were not regenerated due to: #4044

@elasticmachine
Copy link

elasticmachine commented Aug 22, 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-08-23T12:57:30.401+0000

  • Duration: 24 min 16 sec

Test stats 🧪

Test Results
Failed 0
Passed 68
Skipped 0
Total 68

🤖 GitHub comments

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

  • /test : Re-trigger the build.

@elasticmachine
Copy link

elasticmachine commented Aug 22, 2022

🌐 Coverage report

Name Metrics % (covered/total) Diff
Packages 100.0% (5/5) 💚
Files 100.0% (5/5) 💚 2.846
Classes 100.0% (5/5) 💚 2.846
Methods 100.0% (66/66) 💚 10.688
Lines 94.522% (1156/1223) 👍 3.659
Conditionals 100.0% (0/0) 💚

@taylor-swanson taylor-swanson marked this pull request as ready for review August 22, 2022 16:06
@taylor-swanson taylor-swanson requested a review from a team as a code owner August 22, 2022 16:06
@elasticmachine
Copy link

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

@taylor-swanson taylor-swanson changed the title [zscaler_zia] Remap network.protocol to valid values [zscaler_zia] Remap network.protocol/scheme to valid values for uri_parts Aug 22, 2022
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.

I think it's probably worth noting in the package readme that if there is not a valid scheme then the scheme is set to https.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Integration:ZscalerZIA
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[zscaler_zia] Logs with http_proxy protocol break uri_parts processor
3 participants