Gitlab Integration Issue on Fleet Server

Elastic Stack Elastic Agent
1

Dear all,
I'm currently testing for sending the gitlab logs/metrics with the integration via Fleet Server on the Kibana Dashboard. As you can see on the screenshots , the agents results "HEALTHY",
But I'dont know where the issue is for not sending the logs. I've checked the ports on the firewall and all seems fine. Could you help me please? Thanks

img2
img21732×764 69.1 KB

2

Additional :

img4
img41915×856 44.9 KB

3

Thanks for reaching out, @Lorenzo_Z02.

  • Have you double-checked your integration policy? You may want to make sure that you have fields populated for log path or metrics endpoint
    and enabled: true.
  • You also may want to check the index pattern in Discover - this should be logs-gitlab.* or metrics-gitlab.* and see if anything is getting returned.

Our documentation may also be helpful here: GitLab Integration | Elastic Documentation

4

Hi Jess! I've checked

  • You also may want to check the index pattern in Discover - this should be logs-gitlab.* or metrics-gitlab.* and see if anything is getting returned.

And no results appears...

I also checked the integration policy and it's all enabled. If i have to provide more screenshots on particular pages to investigate more.

Thank you in advance!

5

The Healthy status of the agent only considers if the agent can communicate with the fleet server, it does not take into account the communication with the configured outputs.

If the agent can reach the Fleet Server, but cannot reach Elasticsearch, it will appear as Healthy, but will not be able to send any data.

Can you confirm that the agent can connect to output configured? Can you do a test a telnet from the machine with the agent to the output you are using (elasticsearch or logstash) and share the result?