-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Event export documentation is incomplete #23277
Labels
Comments
ptgott
added a commit
that referenced
this issue
Jan 2, 2025
Closes #23277 Document the `types`, `skip-event-types`, and `skip-session-types` event handler configuration fields. The `finish-event-handler-config.mdx` partial is the most appropriate place for this, since it already includes instructions for tailoring the user's event handler configuration.
github-merge-queue bot
pushed a commit
that referenced
this issue
Jan 3, 2025
Closes #23277 Document the `types`, `skip-event-types`, and `skip-session-types` event handler configuration fields. The `finish-event-handler-config.mdx` partial is the most appropriate place for this, since it already includes instructions for tailoring the user's event handler configuration.
github-actions bot
pushed a commit
that referenced
this issue
Jan 3, 2025
Closes #23277 Document the `types`, `skip-event-types`, and `skip-session-types` event handler configuration fields. The `finish-event-handler-config.mdx` partial is the most appropriate place for this, since it already includes instructions for tailoring the user's event handler configuration.
github-actions bot
pushed a commit
that referenced
this issue
Jan 3, 2025
Closes #23277 Document the `types`, `skip-event-types`, and `skip-session-types` event handler configuration fields. The `finish-event-handler-config.mdx` partial is the most appropriate place for this, since it already includes instructions for tailoring the user's event handler configuration.
github-actions bot
pushed a commit
that referenced
this issue
Jan 3, 2025
Closes #23277 Document the `types`, `skip-event-types`, and `skip-session-types` event handler configuration fields. The `finish-event-handler-config.mdx` partial is the most appropriate place for this, since it already includes instructions for tailoring the user's event handler configuration.
github-merge-queue bot
pushed a commit
that referenced
this issue
Jan 6, 2025
Closes #23277 Document the `types`, `skip-event-types`, and `skip-session-types` event handler configuration fields. The `finish-event-handler-config.mdx` partial is the most appropriate place for this, since it already includes instructions for tailoring the user's event handler configuration.
github-merge-queue bot
pushed a commit
that referenced
this issue
Jan 6, 2025
Closes #23277 Document the `types`, `skip-event-types`, and `skip-session-types` event handler configuration fields. The `finish-event-handler-config.mdx` partial is the most appropriate place for this, since it already includes instructions for tailoring the user's event handler configuration.
github-merge-queue bot
pushed a commit
that referenced
this issue
Jan 6, 2025
Closes #23277 Document the `types`, `skip-event-types`, and `skip-session-types` event handler configuration fields. The `finish-event-handler-config.mdx` partial is the most appropriate place for this, since it already includes instructions for tailoring the user's event handler configuration.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is no toml example that shows how to filter certain types of events in docs or in teleport-plugins repo.
Specifically, include example of how to collect and read proxied HTTP metadata? Customers would like to know who sends requests to a specific host.
There is no documentation on that anywhere.
The text was updated successfully, but these errors were encountered: