feat: new metric widgets

[35C4n0r]

Closes #1769
Closes #2262

📑 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

https://www.loom.com/share/aa665dee5b2c413dac14976ed62e90fe?sid=00b8c786-a87a-47d7-a17f-a6dbe74de11f

[vercel]

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

A member of the Team first needs to authorize it.

[Matvey-Kuk]

Great job!

[rajesh-jonnalagadda]

@35C4n0r What if I want to see the previous day's data? how are we handling it
cc: @Matvey-Kuk

[rajesh-jonnalagadda]

@35C4n0r What if I want to see the previous/particular day's data? how are we handling it
@Matvey-Kuk User might ask for it, right? I want to know your perspective.
cc: @talboren

[talboren]

@35C4n0r may I ask you to resolve the conflict, and run linter? For example, please note that every other component, the standard is using " instad of '.

May I also ask you to upload a video of how this feature looks like?

cc: @Matvey-Kuk - I know you approved but would love to see that ^ first.
re @rajeshj11: @Matvey-Kuk @35C4n0r I think it's a valid point. As a user I would like the dashboard to work with the timeframe I chose.

[35C4n0r]

@talboren

@35C4n0r may I ask you to resolve the conflict, and run linter?

Conflict Resolved, is the command for linter next lint ?

For example, please note that every other component, the standard is using " instad of '.

Didn't understand, can you clarify this.

May I also ask you to upload a video of how this feature looks like?

It's there in the description

cc: @Matvey-Kuk - I know you approved but would love to see that ^ first. re @rajeshj11: @Matvey-Kuk @35C4n0r I think it's a valid point. As a user I would like the dashboard to work with the timeframe I chose.

Ok, then instead of the past 24 hours, should we show the graph for per day? Thoughts?

[35C4n0r]

😅
Suddenly clicked what you're trying to say.

For example, please note that every other component, the standard is using " instad of '.

[rajesh-jonnalagadda]

@talboren

@35C4n0r may I ask you to resolve the conflict, and run linter?

Conflict Resolved, is the command for linter next lint ?

For example, please note that every other component, the standard is using " instad of '.

Didn't understand, can you clarify this.

May I also ask you to upload a video of how this feature looks like?

It's there in the description

cc: @Matvey-Kuk - I know you approved but would love to see that ^ first. re @rajeshj11: @Matvey-Kuk @35C4n0r I think it's a valid point. As a user I would like the dashboard to work with the timeframe I chose.

Ok, then instead of the past 24 hours, should we show the graph for per day? Thoughts?

@35C4n0r
We can assume a similar approach. Pagination is necessary if the time frame is extensive to prevent overloading the component.

note: not certain. please get approval from @Matvey-Kuk @talboren before you even start devlopment. The above assumption is my perspective.

[35C4n0r]

😓 @rajeshj11 that's definitely not what I meant. Let me rephrase it a bit:
Instead of showing the data for the past 24 hours starting from the current timestamp, we should display a graph that spans the selected day.

[rajesh-jonnalagadda]

😓 @rajeshj11 that's definitely not what I meant. Let me rephrase it a bit: Instead of showing the data for the past 24 hours starting from the current timestamp, we should display a graph that spans the selected day.

I understand your point, and I see it from that perspective as well. I’ve also noted in my comments that this is based purely on my assumption as a user.

[rajesh-jonnalagadda]

@35C4n0r Let @Matvey-Kuk and @talboren decide which one they want. If you're open to it, I'd like to collaborate with you to tackle this blocker together.

[codecov]

Codecov Report

Attention: Patch coverage is 19.44444% with 87 lines in your changes missing coverage. Please review.

Project coverage is 71.15%. Comparing base (7d90ae9) to head (0207516).
Report is 51 commits behind head on main.

Files with missing lines	Patch %	Lines
keep/api/core/db.py	16.66%	75 Missing ⚠️
keep/api/routes/dashboard.py	21.42%	11 Missing ⚠️
keep/api/routes/incidents.py	75.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2261      +/-   ##
==========================================
- Coverage   71.20%   71.15%   -0.06%     
==========================================
  Files         154      155       +1     
  Lines       14046    14476     +430     
==========================================
+ Hits        10002    10300     +298     
- Misses       4044     4176     +132     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[rajesh-jonnalagadda]

@35C4n0r if changes are done. Can you please add demo video if possible.

[Matvey-Kuk]

It's looking really good for me. I see tests are failing, please fix them :)

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
8134198	Triggered	Generic High Entropy Secret	9d3bab0	keep-ui/app/frigade-provider.tsx	View secret
14332896	Triggered	Generic Password	4adf359	keep/providers/graylog_provider/docker-compose.yml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[35C4n0r]

It's looking really good for me. I see tests are failing, please fix them :)

@Matvey-Kuk tests were failing sporadically, they all pass now. I've updated the docs. Lemme know if any other changes are required and let's get this PR merged :)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
keep	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 31, 2024 10:40am

[VladimirFilonov]

I think it's great!

not relevant anymore