Add an event for when a session recording is accessed#970
Conversation
fceb7ab to
40c15d7
Compare
| color="light" | ||
| font-size="3" | ||
| /> | ||
| App Session Started |
There was a problem hiding this comment.
Confused as to why this would be removed given this change.
There was a problem hiding this comment.
It looks like APP_SESSION_START has the same event code:
There was a problem hiding this comment.
Yeah, turns out I missed the second block of session events (gravitational/teleport#14302 (review)) - I'll change the code
kimlisa
left a comment
There was a problem hiding this comment.
i think it's worth to add instructions on how to add events on our root README, it's a very common addition (and various devs come in to add them) and the steps are all the same as well as the files touched, see example here: #561,
the instructions are also detailed in this file:
, but i guess it's hard to see428db31 to
4b0b466
Compare
|
@ryanclark is there any work left here? We can merge this at any time (backend doesn't need to be ready) |
@zmb3 Yeah it's ready to go, I'll sort it out in a couple of hours once I'm at my MacBook |
4b0b466 to
2dae3ed
Compare
This adds a new SessionRecordingAccess event that is emitted every time a session's events are queried, or if a session's events are streamed. This event is emitted by both v1 and v2 of the API, so both the web UI and tsh play will result in an event in the audit log. Implements #13880. The frontend change for supporting this event type is here - gravitational/webapps#970.
This adds a new SessionRecordingAccess event that is emitted every time a session's events are queried, or if a session's events are streamed. This event is emitted by both v1 and v2 of the API, so both the web UI and tsh play will result in an event in the audit log. Implements #13880. The frontend change for supporting this event type is here - gravitational/webapps#970.
This adds a new SessionRecordingAccess event that is emitted every time a session's events are queried, or if a session's events are streamed. This event is emitted by both v1 and v2 of the API, so both the web UI and tsh play will result in an event in the audit log. Implements #13880. The frontend change for supporting this event type is here - gravitational/webapps#970.
This adds a new SessionRecordingAccess event that is emitted every time a session's events are queried, or if a session's events are streamed. This event is emitted by both v1 and v2 of the API, so both the web UI and tsh play will result in an event in the audit log. Implements #13880. The frontend change for supporting this event type is here - gravitational/webapps#970.
Record when a session recording is accessed This adds a new SessionRecordingAccess event that is emitted every time a session's events are queried, or if a session's events are streamed. This event is emitted by both v1 and v2 of the API, so both the web UI and tsh play will result in an event in the audit log. Implements #13880. The frontend change for supporting this event type is here - gravitational/webapps#970.
As part of gravitational/teleport#13880, a new event has been added (
SESSION_RECORDING_ACCESS, codeT2011I).This adds it to the frontend so it displays correctly -
