Skip to content

[Enhancement] [Zscaler ZIA] Make enhancement in connector with best practices implementation - #4623

Merged
P1llus merged 3 commits into
elastic:mainfrom
vinit-chauhan:package-zscaler-zia-2.6.0
Nov 18, 2022
Merged

[Enhancement] [Zscaler ZIA] Make enhancement in connector with best practices implementation#4623
P1llus merged 3 commits into
elastic:mainfrom
vinit-chauhan:package-zscaler-zia-2.6.0

Conversation

@vinit-chauhan

Copy link
Copy Markdown
Contributor

Type of change

  • Enhancement

What does this PR do?

Make enhancement in Zscaler ZIA connector with listed best practices.

Sr. NO. Best Practices
1 Verify best practices test cases are executed
2 Verify all automated tests
3 Verify default values of port for TCP, UDP or HTTP Endpoint Input
4 Verify that the data is ingested in kibana for in interval
5 Verify all fields are correctly mapped for all Data streams
6 Verify related.ip field in datastream
7 Verify network.protocol is in lowercase form
8 Verify network.transport is in lowercase form
9 Verify format of title of dashboard
10 Verify Datastream Dashboard
11 Verify filters in visualizations
12 Verify visualizations in different browser
13 Verify README file

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

  • Clone integrations repo.
  • Install elastic package locally.
  • Start elastic stack using elastic-package.
  • Move to integrations/packages/zscaler_zia directory.
  • Run the following command to run tests.

elastic-package test

Related issues

Screenshots

image
image
image
image

…r to the convert, geo_ip, uri_parts and date processor and mapped to related ecs field
@vinit-chauhan
vinit-chauhan requested a review from a team as a code owner November 11, 2022 07:37
@elasticmachine

elasticmachine commented Nov 11, 2022

Copy link
Copy Markdown

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@elasticmachine

elasticmachine commented Nov 11, 2022

Copy link
Copy Markdown

💚 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-11-16T12:01:45.866+0000

  • Duration: 22 min 46 sec

Test stats 🧪

Test Results
Failed 0
Passed 37
Skipped 0
Total 37

🤖 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

elasticmachine commented Nov 11, 2022

Copy link
Copy Markdown

🌐 Coverage report

Name Metrics % (covered/total) Diff
Packages 100.0% (5/5) 💚
Files 100.0% (5/5) 💚 2.53
Classes 100.0% (5/5) 💚 2.53
Methods 100.0% (66/66) 💚 9.101
Lines 92.146% (1443/1566) 👍 0.449
Conditionals 100.0% (0/0) 💚
@elasticmachine

Copy link
Copy Markdown

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

Comment on lines +19 to +20
- "^ZscalerNSS: Zscaler cloud configuration connection to %{IPORHOST:destination.address}:%{NUMBER:destination.port:long} lost and unavailable for the past %{NUMBER:zscaler_zia.alerts.connection_lost_minutes:double} minutes$"
- "^ZscalerNSS: SIEM Feed connection \"%{GREEDYDATA:zscaler_zia.alerts.log_feed_name}\" to %{IPORHOST:destination.address}:%{NUMBER:destination.port:long} lost and unavailable for the past %{NUMBER:zscaler_zia.alerts.connection_lost_minutes:double} minutes$"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Single quotes here would remove the need to backslash escape the double quotes.

group: 2
description: Fields related to the cloud or infrastructure the events are coming from.
footnote: 'Examples: If Metricbeat is running on an EC2 host and fetches data from its host, the cloud info contains the data about this machine. If Metricbeat runs on a remote machine outside the cloud and fetches data from a service running in the cloud, the field contains cloud data from the machine the service is running on.'
footnote: "Examples: If Metricbeat is running on an EC2 host and fetches data from its host, the cloud info contains the data about this machine. If Metricbeat runs on a remote machine outside the cloud and fetches data from a service running in the cloud, the field contains cloud data from the machine the service is running on."

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Again I'm wondering about these changes; the ECS definition of the field uses single quotes and whitespace rather than double quotes and escape sequences. Is there a reason for this change?

@P1llus
P1llus merged commit 864f94c into elastic:main Nov 18, 2022
@vinit-chauhan
vinit-chauhan deleted the package-zscaler-zia-2.6.0 branch April 1, 2026 23:57
orestisfl pushed a commit to orestisfl/integrations that referenced this pull request May 15, 2026
…ractices implementation (elastic#4623)

* Update Aggregation visualizations to Lens, Add an on_failure processor to the convert, geo_ip, uri_parts and date processor and mapped to related ecs field

* Update changelog entry

* Resolved review comments
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:zscaler_zia Zscaler Internet Access

4 participants