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.

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

[Feature] Monitor executions and consumption #442

Open
piaudonn opened this issue Apr 30, 2024 · 1 comment
Open

[Feature] Monitor executions and consumption #442

piaudonn opened this issue Apr 30, 2024 · 1 comment
Assignees
Labels
pending-triage Submitted issue needing triage workbook STAT Information workbook

Comments

@piaudonn
Copy link
Collaborator

As we had a workbook in STATv1 to keep track of what was there and gather stats, it would be nice to have that with STATv2.
At least as an option deployment option. @briandelmsft we discussed the option to send logs to a custom table? Should we offer the option?

@piaudonn piaudonn added pending-triage Submitted issue needing triage workbook STAT Information workbook labels Apr 30, 2024
@piaudonn piaudonn self-assigned this Apr 30, 2024
@briandelmsft
Copy link
Owner

@piaudonn I'm interested in that option yes, I think we need to really think through all the possible use cases of it carefully as well as the schema of the table.

For use cases I think the workbook can give us that stats but also give us a nicer layout for the enrichments themselves as an alternate to incident comments which could be read out of the custom table.

Additionally, we could potentially have integrations with UEBA entity timeline, for example with the KQL module if it finds something, maybe that should show up on the users entity timeline? maybe other modules as well

Are there other things we could/should keep in mind when planning this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending-triage Submitted issue needing triage workbook STAT Information workbook
Projects
None yet
Development

No branches or pull requests

2 participants