All Apps and Add-ons

GitLab Runner monitoring

hijacob
Communicator

Hi @all,
we try to monitor our GitLab CI/CD to check if the pipelines was successful or failed. Also we need a monitor that gives us information about the Jobs status (e. g. successful or failed). Does anybody has experience with the GitLab Add-On in this context? We can't fulfill our requirements yet.
Best regards
Jacob

0 Karma

twesty
Path Finder

Hi @hijacob

This TA will collect job status as part of the GitLab:Job sourcetype. The result is stored in the status field within the returned json message.

you can always check the _internal index for MsgID="JOBLPST" to confirm that the api is being hit, providing the logging level is set to debug!

It's worthwhile noting that this functionality was introduced as part of v1.2.0. If you are using an older version, please upgrade your TA.

Thanks

Tom

0 Karma

hijacob
Communicator

Hi @twesty

Thank you for your helpful advice. But we have following problems:
In the _internal index there ist no MsgID which is named “JOBLPST” although we set the log level to debug. So the api isn’t being hit. Do you have any idea how we can fix the issue?

Thanks

Jacob

0 Karma
Get Updates on the Splunk Community!

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...

Updated Team Landing Page in Splunk Observability

We’re making some changes to the team landing page in Splunk Observability, based on your feedback. The ...