Skip to content

feat: support session audit log #16703

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

Merged
merged 3 commits into from
Feb 26, 2025
Merged

feat: support session audit log #16703

merged 3 commits into from
Feb 26, 2025

Conversation

BrunoQuaresma
Copy link
Collaborator

Related to #15139

Demo:
Screenshot 2025-02-25 at 16 27 12

@BrunoQuaresma BrunoQuaresma self-assigned this Feb 25, 2025
@BrunoQuaresma
Copy link
Collaborator Author

@mafredri open questions:

  • We currently use the user field to fill the avatar. Since this is not related to a specific user, what kinda of avatar do you think we should use? 🤔
  • In the design that you shared in the related issue, the tooltip had a "reason" section but I can't see a related field in the audit log response.

Copy link
Member

@mafredri mafredri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From a BE/implementation perspective, this LGTM!

return (
<Pill
css={styles.statusCodePill}
type={isHttp ? httpStatusColor(code) : code === 0 ? "success" : "error"}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice fix for this!

@@ -232,6 +227,19 @@ export const AuditLogRow: FC<AuditLogRowProps> = ({
);
};

function StatusPill({ code }: { code: number }) {
const isHttp = code >= 100;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, a better measure of http status code may be whether or not this was a connect/disconnect action. Shell errors can be 0-255, but perhaps we should just mark them as 0/1 on the API side, wdyt?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm... I think it works 👍

BrunoQuaresma and others added 2 commits February 26, 2025 13:58
…LogDescription.tsx

Co-authored-by: Mathias Fredriksson <mafredri@gmail.com>
@BrunoQuaresma BrunoQuaresma merged commit f1b357d into main Feb 26, 2025
30 checks passed
@BrunoQuaresma BrunoQuaresma deleted the bq/refactor-audit-log-row branch February 26, 2025 17:13
@github-actions github-actions bot locked and limited conversation to collaborators Feb 26, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants