feat: Added dashboard for Alert Quality

[vikashsprem]

Closes #1779
/claim #1779

📑 Description

✅ Checks

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• All the tests have passed

ℹ Additional Information

[vercel]

@vikashsprem is attempting to deploy a commit to the KeepHQ Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[Matvey-Kuk]

Hey @vikashsprem how is it going? :)

[vikashsprem]

Hey, @Matvey-Kuk going great, need some time to complete it.

[vikashsprem]

Hey @Matvey-Kuk, @rajeshj11 is also collaborating with me (To complete this issue sooner). Most of the portions are completed. Thank you.

[vikashsprem]

Hey @Matvey-Kuk, Please review this PR and let me know if any changes.

[Matvey-Kuk]

Hey @vikashsprem I see you added a separate page for this dashboard, what do you think of making it a widget for the dashboard we already have? :)

[vikashsprem]

Hey @Matvey-Kuk , Thanks for the suggestion! My concern with making it a widget is that the separate page allows us to include more detailed functionality without crowding the main dashboard. But I'm happy to discuss and find the best approach!

[Matvey-Kuk]

@vikashsprem the main dashboard has a timeframe selector, also we're planning to add more widgets to this dashboard in the future to allow users to tail dashboards to their needs.

[vikashsprem]

@Matvey-Kuk Got it, that makes sense! I'll look into transitioning the separate page into a widget.

[Matvey-Kuk]

@rajeshj11 sorry for late reply! I've checked with Tal, the thing is that once the alert pops up in Keep and it doesn't have an Installed provider, a new type of providers is getting created called "Linked Providers", they are acting as any other providers, and I think they should be represented in the table.

Could you please update the PR?

[rajesh-jonnalagadda]

@rajeshj11 sorry for late reply! I've checked with Tal, the thing is that once the alert pops up in Keep and it doesn't have an Installed provider, a new type of providers is getting created called "Linked Providers", they are acting as any other providers, and I think they should be represented in the table.

Could you please update the PR?

@Matvey-Kuk I did discuss this with @talboren. I proposed I will show all the provider type stats in separate table. Something like below.

Github(linked +installed) in a separate table.
Gitlab(linked+installed)

Should I maintain separate table. Need conformation

[Matvey-Kuk]

@rajeshj11 I didn't mean a separate table, but just to include alerts from Linked + Installed in the widget you already added :)

[rajesh-jonnalagadda]

@rajeshj11 I didn't mean a separate table, but just to include alerts from Linked + Installed in the widget you already added :)

https://www.loom.com/share/03e52b1f785d4a039e47d0aa124c41b6

please check the demo

[Matvey-Kuk]

@rajeshj11 looks cool!

[vikashsprem]

Hey @Matvey-Kuk the latest changes have been applied, Please review.

[Matvey-Kuk]

Great! I noticed a bug:

1. I click "Add Fields", add a few fields.
2. I save dashboard.
3. I reload the page.
4. I don't see fields I added.

[rajesh-jonnalagadda]

Great! I noticed a bug:

1. I click "Add Fields", add a few fields.
2. I save dashboard.
3. I reload the page.
4. I don't see fields I added.

We have not configured it like that. fields act like filters. those are not part of the configuration implementation.

[Matvey-Kuk]

@rajeshj11 wouldn't it be confusing for users?

[rajesh-jonnalagadda]

@rajeshj11 wouldn't it be confusing for users?

Yes, I agree it could cause some confusion. We can definitely work on improving this.

[rajesh-jonnalagadda]

@rajeshj11 wouldn't it be confusing for users?

@Matvey-Kuk The way we’ve implemented it—adding this in the config—would require significant effort. Should we create a subtask to address this?"

[rajesh-jonnalagadda]

@rajeshj11 wouldn't it be confusing for users?

@Matvey-Kuk The way we’ve implemented it—adding this in the config—would require significant effort. Should we create a subtask to address this?"

I have a quick alternate solution for this. We can persist the widget table filters in local storage, so even after a refresh, it will retrieve the latest filters from local storage. what do you think?

[Matvey-Kuk]

@rajeshj11 the use-case I see is someone adding fields and sending the dashboard link to a colleague. It won't work in case it will be stored in the local storage.

[vikashsprem]

Hey @Matvey-Kuk, we have made changes according to your suggestion. Please review for more, we have attached a demo video (Some blinking issues in the video not in the actual application) have a look.

https://www.loom.com/share/e8f8138b34da4836ae776088b11c406f

[Matvey-Kuk]

Great work, thank you!

[talboren]

LGTM

[github-actions]

🏆 Fantastic work @vikashsprem! Your very first PR to keep has been merged! 🎉🥳

You've just taken your first step into open-source, and we couldn't be happier to have you onboard. 🙌
If you're feeling adventurous, why not dive into another issue and keep contributing? The community would love to see more from you! 🚀

For any support, feel free to reach out on the community: https://slack.keephq.dev. Happy coding! 👩‍💻👨‍💻