Add FluentBit pipeline for Keycloak account events.#49
Draft
Conversation
Process Keycloak authentication events (logins, token introspections, registrations) received from the Accounts Celery worker and forward them to PostHog. Events arrive at /telemetry/keycloak and are processed by a Lua filter and then sent to the PostHog batch API.
Member
Author
|
My understanding is that the VPC Peering needs to be done in a two step process? |
Member
Author
|
Hmm. I'm not sure this is the correct approach. On further investigation, it doesn't seem like it's going to be possible for fluent-bit to enrich Stalwart-sourced events with keycloak uuids without adding additional connections to other resources. If, instead, product analytics are routed through thunderbird-accounts and then directly to posthog, it's easy to enrich any submitted events with any data we want since acocunts has access to basically everything. Given that, I'm not sure what value fluent-bit is providing to this pipeline. |
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.
Process Keycloak authentication events (logins, token introspections, registrations) received from the Accounts Celery worker and forward them to PostHog. Events arrive at /telemetry/keycloak and are processed by a Lua filter and then sent to the PostHog batch API.