[Enhancement] [Zscaler ZIA] Make enhancement in connector with best practices implementation - #4623
Merged
Merged
Conversation
…r to the convert, geo_ip, uri_parts and date processor and mapped to related ecs field
🚀 Benchmarks reportTo see the full report comment with |
🌐 Coverage report
|
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
efd6
reviewed
Nov 15, 2022
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$" |
Contributor
There was a problem hiding this comment.
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." |
Contributor
There was a problem hiding this comment.
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
approved these changes
Nov 18, 2022
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Type of change
What does this PR do?
Make enhancement in Zscaler ZIA connector with listed best practices.
Checklist
changelog.ymlfile.How to test this PR locally
Related issues
Screenshots