-
Notifications
You must be signed in to change notification settings - Fork 375
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
[New Integration] GitLab #9903
[New Integration] GitLab #9903
Conversation
🚀 Benchmarks reportTo see the full report comment with |
@tehbooom Thanks for looking into this topic. Is it possible to use use the mentioned other integrations inside the Gitlab integration as a one for all solution? I hope it's understandable what I mean. So that I don't need an integration policy for each of the components as the GitLab integration should manage all that (preferably configurable in the policy settings). |
Hey @Alphayeeeet , there have been discussions around using one ingest pipeline for two integrations however at this time it is not supported. Ive decided to not recreate the pipelines in this integration incase we do in the future move towards utilizing more than one integration pipeline for a single integration. As of now, you will need to add more integrations to the policy to fully monitor all of GitLab. |
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
💚 Build Succeeded
History
|
Quality Gate failedFailed conditions |
Two comments on this.
|
Closing since it is a duplicate of #9747. After it is merge will start to add more datastreams for this PR. |
Proposed commit message
New integration for GitLab
Some examples logs were pulled from the documentation
The other logs were pulled from a test GitLab instance using the free tier.
Not all logs from GitLab are collected since we need a dev license and more example logs.
The following logs will need to be ingested from another integration:
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues