-
Notifications
You must be signed in to change notification settings - Fork 817
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
feat: Server side filtering for alerts #3236
base: main
Are you sure you want to change the base?
Conversation
… filtering and pagination
…der for improved CEL handling
… for argument count in CEL method calls
…tAlerts hook for improved alert counts
…b.com/keephq/keep into 3073_server_side_filtering_for_alerts
…orting capabilities in alerts queries
…erts mutator usage
…or improved filtering
…te usages in LinkWithIcon and FacetValue
…ed logic for improved data handling
- Modified `alerts.py` to include server-side filtering logic.
…roved data accuracy
…rt count handling
…nt validation in SQL providers
…tors and date comparisons
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
15359980 | Triggered | Generic Private Key | 2a9d2f3 | keep/providers/clickhouse_provider/clickhouse-secure/certs/server.key | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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.
…facets panel interactions
…b.com/keephq/keep into 3073_server_side_filtering_for_alerts
- Implemented server-side filtering for alerts in the backend - Updated tests in `tests/test_metrics.py` to cover new filtering logic
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3236 +/- ##
==========================================
+ Coverage 42.60% 46.36% +3.76%
==========================================
Files 182 154 -28
Lines 17835 14286 -3549
==========================================
- Hits 7598 6624 -974
+ Misses 10237 7662 -2575 ☔ View full report in Codecov by Sentry. |
Closes #3073
📑 Description
✅ Checks
ℹ Additional Information