[➕ Feature]: Alert quality widgets for a dashboard

[Matvey-Kuk]

Users connect a lot of providers for Keep, and we should provide some analytics about the quality of events coming out of those providers.

I propose to add a few widgets, and an auto-provisioned dashboard called "Alert quality".

Imagine a use-case when users wants to make sure that all alert providers provide "severity", "department", "product" and "affected_customer" from the sources. This dashboard should help them.

Widgets:

• A table with a per-provider alert quality. Rows: connected providers. Columns: provider name, amount of alerts received, % of alerts correlated to incidents, % of alerts having a "field" filled. Where field is a configurable set of fields.
• % of alerts correlated to incidents
• % of alerts having a "field" filled

[Matvey-Kuk]

/bounty 200

[algora-pbc]

💎 $200 bounty • Keep (YC W23)

Steps to solve:

1. Start working: Comment /attempt #1779 with your implementation plan
2. Submit work: Create a pull request including /claim #1779 in the PR body to claim the bounty
3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to keephq/keep!

Add a bounty • Share on socials

Attempt	Started (GMT+0)	Solution
🟢 @vikashsprem	Sep 11, 2024, 9:15:28 AM	#1977

[vikashsprem]

/attempt #1779

Algora profile	Completed bounties	Tech	Active attempts	Options
@vikashsprem	1 bounty from 1 project	TypeScript, JavaScript, HTML & more		Cancel attempt

[vikashsprem]

@Matvey-Kuk Could you pls assign me? I will start working on it.

[Matvey-Kuk]

@vikashsprem absolutely! Please keep us updated on the progress :)

[rajesh-jonnalagadda]

@vikashsprem I would like to collaborate with you if that works for you. Please let me know how I can assist.

[vikashsprem]

@Matvey-Kuk should I add the "Alert Quality" dashboard as a sub-option under one of the Alerts in the sidebar?

Is the widget that should look like this (A rough overview):

Alert Quality Dashboard

Provider Name	Alerts Received	% Alerts Correlated to Incidents	% Alerts with "Severity"	% Alerts with "Department"	% Alerts with "Product"	% Alerts with "Affected Customer"
Provider A	1200	85%	95%	90%	88%	92%
Provider B	980	78%	92%	85%	83%	89%
Provider C	450	65%	88%	82%	79%	85%
Provider D	300	72%	91%	87%	84%	90%

[vishalxtyagi]

@Matvey-Kuk @vikashsprem
I noticed this open issue for the Alert Quality dashboard feature and I'm interested in contributing. Before I start working on it, I wanted to confirm a few things:

• Is this issue still available for contribution?
• As vikashsprem has already been assigned, are you open to having another contributor work on this as well? If so, would you prefer collaboration or should I wait to see if vikashsprem needs any assistance?
• If I am able to contribute, are there any specific guidelines or requirements I should be aware of before starting?

[Matvey-Kuk]

@vikashsprem you are absolutely right about the dashboard view :)

[Matvey-Kuk]

@vishalxtyagi it's up to @vikashsprem if he is open to the co-contributor :)

[algora-pbc]

💡 @vikashsprem submitted a pull request that claims the bounty. You can visit your bounty board to reward.

[rajesh-jonnalagadda]

@Matvey-Kuk We need information on this column: "% of alerts with a specified field filled."

Could you clarify where we can find the list of available fields? If possible, please provide the expected fields. Currently, we have implemented it as a filter, allowing users to select fields to add to the table.

Ideally, we should restrict users to selecting only one field, as we are aggregating based on these fields. Allowing multiple fields could be costly in terms of performance.

[Matvey-Kuk]

@rajeshj11 it's important to let users to configure the required fields because we can't predict which field is important for which customer. I suggest checking the field selector for "Feed". It's getting populated based on the content of present alerts.

[rajesh-jonnalagadda]

@rajeshj11 it's important to let users to configure the required fields because we can't predict which field is important for which customer. I suggest checking the field selector for "Feed". It's getting populated based on the content of present alerts.

@Matvey-Kuk @talboren I am a little confused about the approach.

Current Implementation:

1. We display the total received, alerts to incidents, and severity as default columns, along with a custom column named "alert with {field} %,"
2. The "alerts with {field} %" column will dynamically update based on the user's field filter selection. To optimize performance and minimize computational load on SQL, users are restricted to selecting only one field at a time.
   Reason:
   Aggregating multiple fields can be resource-intensive, particularly with large datasets.

My question is should continue with the current approach? or do we need different approach

[rajesh-jonnalagadda]

@rajeshj11 it's important to let users to configure the required fields because we can't predict which field is important for which customer. I suggest checking the field selector for "Feed". It's getting populated based on the content of present alerts.

ack, will add the other options in the filter

[Matvey-Kuk]

Reason: Aggregating multiple fields can be resource-intensive, particularly with large datasets.

Sounds valid! May I ask to add ability to add at least 3? I think 1 will be too limiting.

[rajesh-jonnalagadda]

Reason: Aggregating multiple fields can be resource-intensive, particularly with large datasets.

Sounds valid! May I ask to add ability to add at least 3? I think 1 will be too limiting.

okay

[Matvey-Kuk]

Payout for this bounty will be executed via GitHub Sponsors, not via Algora. Please activate https://github.com/sponsors/accounts for your account to receive the payout, sorry for the inconvenience

[vikashsprem]

Payout for this bounty will be executed via GitHub Sponsors, not Algora. Please activate https://github.com/sponsors/accounts for your account to receive the payout, sorry for the inconvenience

@Matvey-Kuk I have enabled sponsor option on my github account.

[Matvey-Kuk]

@vikashsprem congrats!

[rajesh-jonnalagadda]

@vikashsprem congrats!

@Matvey-Kuk We have not informed you about the split. Anyhow we will handle it internally. I will note that next, we will inform you upfront.