Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Enrich activity logging capabilities to cover more use cases #4494

Closed
SamuelHassine opened this issue Oct 5, 2023 · 0 comments · Fixed by #4928
Closed

Enrich activity logging capabilities to cover more use cases #4494

SamuelHassine opened this issue Oct 5, 2023 · 0 comments · Fixed by #4928
Assignees
@richard-julien @SamuelHassine
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone
Release 5.12.0

Comments

@SamuelHassine
Copy link
Member

Use case

Currently, the audit / activity logging is not covering some use cases needed by customers and community members.

Example with report read:

image

What we need is to be able to:

  • Compute the distribution of most read reports by author (missing created by)
  • Compute the distribution of most read reports by marking (missing marked by)
  • Compute the distribution of most read reports by creator (missing creator_id)

Note for myself in distribution / alerting:

  • Add new distribution attributes such as context_data.input.search / context_data.input.X
@SamuelHassine SamuelHassine added feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team labels Oct 5, 2023
@SamuelHassine SamuelHassine added this to the Release 5.12.0 milestone Oct 5, 2023
@Jipegien Jipegien removed the needs triage use to identify issue needing triage from Filigran Product team label Oct 5, 2023
richard-julien added a commit that referenced this issue Oct 6, 2023
@richard-julien
[backend] Enrich activity logging capabilities to cover more use cases (
d4410b6 
#4494)
SamuelHassine pushed a commit that referenced this issue Nov 19, 2023
@richard-julien @SamuelHassine
[backend] Enrich activity logging capabilities to cover more use cases (
a89b79b 
#4494)
@SamuelHassine SamuelHassine mentioned this issue Nov 19, 2023
Merged
5 tasks
@SamuelHassine SamuelHassine linked a pull request Nov 19, 2023 that will close this issue
[backend/frontend] Log and activity tracking / statistics refactoring #4928
Merged
5 tasks
SamuelHassine added a commit that referenced this issue Nov 19, 2023
@SamuelHassine @richard-julien
[backend/frontend] Log and activity tracking / statistics refactoring (…
d975d20 
…#4494)

Co-authored-by: Julien Richard <julien.richard@filigran.io>
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Nov 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@richard-julien richard-julien

@SamuelHassine SamuelHassine

Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Milestone
Release 5.12.0
Development

Successfully merging a pull request may close this issue.

[backend/frontend] Log and activity tracking / statistics refactoring OpenCTI-Platform/opencti
3 participants
@richard-julien @SamuelHassine @Jipegien