-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[AI-4595] DDS: Keycloak Integration V1.0.0 #19019
Conversation
Created Jira card for Docs Team editorial review. |
@thibaultkrebs 👋 could you take a peek at this again, it looks like your comment was addressed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see you don't use any date-remapper, this will results in a generated timestamp when the logs is received (doc). Are you sure you want that ?
otherwise I'll approve the PR
@audesikorav Regarding your this comment, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, some small fixes
Stale Review dismissed by prbot
* Add: keycloak Integration * Update: manifest and changelog.d for CI checks * Update: manifest.json * Test pipeline log parsing for CI * test different sample * Test log without message field * Revert pipeline sample testing log * Update: grok parser and readme minor description * Update: description in dashboard * Update: replace sample with CI pipeline formatted sample * Update: Format as per comment * Update: Address review comments on 29/11/2024 * Update: test samples with only message attribute. * Update: add results from pipeline * Update: address review comments and update __init__.py and __about__.py --------- Co-authored-by: Ilia Kurenkov <[email protected]> f223704
What does this PR do?
PR for a new integration Keycloak 1.0.0
Additional Notes
-- OOTB detection rules JSON would be shared separately with the required teams as a part of separate repository .
-- Since during the standard attribute remapping we are not preserving the source attributes as per suggested best practices, it would result in filters using these standard attributes populating the values of other integrations as well as per current datadog behavior.
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.backport/<branch-name>
label to the PR and it will automatically open a backport PR once this one is merged