Edit:
It seems sudo metricbeat -e -d "*" was the command I was looking for. It tells me:
2021-01-05T13:59:51.818+0100 INFO instance/beat.go:645 Home path: [/usr/share/metricbeat] Config path: [/etc/metricbeat] Data path: [/var/lib/metricbeat] Logs path: [/var/log/metricbeat]
2021-01-05T13:59:51.818+0100 DEBUG [beat] instance/beat.go:697 Beat metadata path: /var/lib/metricbeat/meta.json
2021-01-05T13:59:51.818+0100 INFO instance/beat.go:653 Beat ID: 4d5b765b-26cb-4050-bed8-416aa5f320e2
2021-01-05T13:59:51.818+0100 DEBUG [docker] docker/client.go:48 Docker client will negotiate the API version on the first request.
2021-01-05T13:59:51.819+0100 DEBUG [add_cloud_metadata] add_cloud_metadata/providers.go:126 add_cloud_metadata: starting to fetch metadata, timeout=3s
2021-01-05T13:59:51.819+0100 DEBUG [add_docker_metadata] add_docker_metadata/add_docker_metadata.go:87 add_docker_metadata: docker environment not detected: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
2021-01-05T13:59:51.821+0100 DEBUG [add_cloud_metadata] add_cloud_metadata/providers.go:162 add_cloud_metadata: received disposition for gcp after 1.915709ms. result=[provider:gcp, error=failed with http status code 404, metadata={}]
2021-01-05T13:59:51.821+0100 DEBUG [add_cloud_metadata] add_cloud_metadata/providers.go:162 add_cloud_metadata: received disposition for digitalocean after 2.281275ms. result=[provider:digitalocean, error=failed with http status code 404, metadata={}]
2021-01-05T13:59:51.822+0100 DEBUG [add_cloud_metadata] add_cloud_metadata/providers.go:162 add_cloud_metadata: received disposition for aws after 2.675994ms. result=[provider:aws, error=<nil>, metadata={"account":{"id":"<id>"},"availability_zone":"eu-central-1a","image":{"id":"ami-<id>"},"instance":{"id":"i-<id>"},"machine":{"type":"<type>"},"provider":"aws","region":"eu-central-1"}]
2021-01-05T13:59:51.822+0100 DEBUG [add_cloud_metadata] add_cloud_metadata/providers.go:129 add_cloud_metadata: fetchMetadata ran for 2.812604ms
2021-01-05T13:59:51.822+0100 INFO [add_cloud_metadata] add_cloud_metadata/add_cloud_metadata.go:93 add_cloud_metadata: hosting provider type detected as aws, metadata={"account":{"id":"<id>"},"availability_zone":"eu-central-1a","image":{"id":"ami-<id>"},"instance":{"id":"i-<id>"},"machine":{"type":"<type>"},"provider":"aws","region":"eu-central-1"}
2021-01-05T13:59:51.822+0100 DEBUG [processors] processors/processor.go:120 Generated new processors: add_cloud_metadata={"account":{"id":"<id>"},"availability_zone":"eu-central-1a","image":{"id":"ami-<id>"},"instance":{"id":"i-<id>"},"machine":{"type":"<type>"},"provider":"aws","region":"eu-central-1"}, add_docker_metadata=[match_fields=[] match_pids=[process.pid, process.ppid]]
2021-01-05T13:59:51.822+0100 INFO instance/beat.go:392 metricbeat stopped.
2021-01-05T13:59:51.822+0100 ERROR instance/beat.go:956 Exiting: data path already locked by another beat. Please make sure that multiple beats are not sharing the same data path (path.data).
Exiting: data path already locked by another beat. Please make sure that multiple beats are not sharing the same data path (path.data).
Filebeat is installed but stopped. Just to be sure I added the following to my metricbeat.yml:
path.home: /usr/share/metricbeat
path.config: /etc/metricbeat
path.data: /var/lib/metricbeat
path.logs: /var/log/
But i still get the same error:
Exiting: data path already locked by another beat. Please make sure that multiple beats are not sharing the same data path (path.data).```