feat: add Graylog Provider

[35C4n0r]

Closes #2283

📑 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/faaf3fe4d3714810bf7617dd5d4fe461?sid=df16e29a-d39c-4b5c-9966-6fdd0044cab5

[vercel]

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

A member of the Team first needs to authorize it.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret 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 secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	Generic Password	e674243	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 secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
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.}

[shahargl]

Looks great so far. One question that I have - is that only self hosted graylog or also cloud?

[35C4n0r]

@shahargl, this is for self-hosted, This is the only thing I have found regarding Graylog Cloud https://go2docs.graylog.org/current/what_is_graylog/what_is_graylog_cloud.html?Highlight=cloud

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.20%. Comparing base (7d90ae9) to head (1db891e).
Report is 52 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2305      +/-   ##
==========================================
- Coverage   71.20%   71.20%   -0.01%     
==========================================
  Files         154      157       +3     
  Lines       14046    14509     +463     
==========================================
+ Hits        10002    10331     +329     
- Misses       4044     4178     +134     

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

[shahargl]

see my comments, few small things:

1. the issue with admin role (add docs if its required)
2. convention
3. please add docs about how to connect Keep as webhook without installing it so it won't need credentials at all (like google monitoring provider)

[shahargl]

@35C4n0r its close to being done, let's merge it today

[shahargl]

lgtm

[vercel]

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

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
keep	⬜️ Ignored (Inspect)	Visit Preview		Oct 29, 2024 10:10am