Skip to content

GRD-115796: Add limitation for MariaDB #1096

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.

Sign up for GitHub

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

Open
nida-bandukwala wants to merge 1 commit into
base: main
Choose a base branch
from
Open

GRD-115796: Add limitation for MariaDB #1096

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions filter-plugin/logstash-filter-mariadb-aws-guardium/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,6 +150,7 @@ The Guardium universal connector is the Guardium entry point for native audit lo
- clientPort and serverPort : Not available with audit logs
- For system generated LOGIN_FAILED logs, the Dbuser value not available,so we set it as "N.A.".
- Large SQL statements are truncated by AWS by default which can cause a GuardUCInvalidRecordException as the event is no longer valid.
- Currently, S‑TAP registration is restricted to one primary MU, meaning the S‑TAP and its logs appear only on the initial primary MU even when multiple primary MUs are present.

## 7. Configuring the AWS MariaDB Guardium Logstash filters in Guardium Data Security Center

Expand Down
Loading