Can't add integrations to fleet agent policies

Elastic Stack Elastic Agent
1

Hey there
Did an airgapped installation of Elastic Package Registry
Created a new docker instance of kibana with xpack.fleet.registryUrl set to my EPR url (already installed fleet server from a docker-compose instance of kibana)
But when I want to add an integration to a fleet agent policy I don't have the "add integration" button in the integration page ...
Any help please ?
Thanks !

PS :
in the "integration" page, for example for the "Docker metrics" integration, I see only instructions on how to install the metricbeat agent from cmd line, then activate docker module from cmd line, then install docker dashboard from cmd line ... but I guess that with an integration on an elastic agent fleet policy I don't have to do all that, right ?

2

Hey there @pierro78 thanks for the question!

Please double check this setting on bottom left of the integrations UI in Kibana:

image
image1460×1120 124 KB

Selecting "beats only" will result in plain Beats tutorials being shown in the results as opposed to Elastic Agent integrations. There is a Beats tutorial for collecting Docker metrics via metricbeat that you're likely landing on.

Enabling "recommended" or "Elastic Agent only" via this toggle and searching for Docker should bring you the Docker integration, which does not require manually configuring Beats:

image
image1538×912 156 KB

1 Like
3

Thanks a lot for answering but it unfortunately doesn't work ... I had the "Recommended" toggle activated ... tried with the "Elastic Agent Only" toggle but no docker integration in there apparently ... tried another integration in "Elastic Agent Only" but no "Add integration" in the integration page ...

btw your screen shows like 405 integrations but it looks like I only have 127 on mine ... (but I had less before I installed my EPR copy)

I must have done sthg very stupid ... I watched the logs of my kibana docker container but did not see anything ...

PS :
Oh and on my "browse integrations" page I still have the small yellow message
" Kibana cannot reach the Elastic Package Registry, which provides Elastic Agent integrations"
but I guess my kibana does access my on-premise EPR as it displays 127 integrations ...

4

maybe my issue is because I installed the fleet server from a kibana instance that did not know about my on-premise EPR server ?