Skip to content

Commit

Permalink
update readme as per pr comments
Browse files Browse the repository at this point in the history
  • Loading branch information
kcreddy committed Jul 26, 2024
1 parent ac8f92c commit f617242
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion packages/bitdefender/_dev/build/docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ BitDefender products for home users are not supported.

The package collects BitDefender GravityZone push notification transported events sent in `jsonrpc`, `qradar`, or `splunk` format.

The `jsonrpc` format is recommended default but the ingest pipeline will attempt to detect if `qradar` or `splunk` format events have been received and process them accordingly.
The `jsonrpc` format is recommended default, but the ingest pipeline will attempt to detect if `qradar` or `splunk` format events have been received and process them accordingly.

The integration can also collect the push notification configuration and statistics by polling the BitDefender GravityZone API.

Expand Down
2 changes: 1 addition & 1 deletion packages/bitdefender/docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ BitDefender products for home users are not supported.

The package collects BitDefender GravityZone push notification transported events sent in `jsonrpc`, `qradar`, or `splunk` format.

The `jsonrpc` format is recommended default but the ingest pipeline will attempt to detect if `qradar` or `splunk` format events have been received and process them accordingly.
The `jsonrpc` format is recommended default, but the ingest pipeline will attempt to detect if `qradar` or `splunk` format events have been received and process them accordingly.

The integration can also collect the push notification configuration and statistics by polling the BitDefender GravityZone API.

Expand Down

0 comments on commit f617242

Please sign in to comment.