Container name not displaying in logs

[Erasure5959]

Hello @Polliog,

Thank you for your work on this project, I am enjoying it so far and like what I see.

I am facing some issues with the Docker logs. Perhaps I have misunderstood the documentation, but my interpretation of the Fluent Bit config was that the Docker container name (not ID) would show up in the GUI. Instead, I see the ID:

From the documentation, the filter config:

[FILTER]
  Name                lua
  Match               docker.*
  script              /fluent-bit/etc/extract_container_id.lua
  call                extract_container_id

[FILTER]
  Name                modify
  Match               docker.*
  Add                 level info
  Rename              log message
  Copy                container_name service

However, nowhere do I see container_name being extracted or mapped from anything else.

Have I misunderstood or done something wrong? Getting logs from containers is helpful, but the utility is lessened by having IDs rather than container or service names.

[Polliog]

Hi @Erasure5959, thanks for the detailed report, and you read the config exactly right: this was a bug on our side, not a misconfiguration on yours.

The Copy container_name service filter was copying a field that nothing ever created. The Lua script only extracted the container ID from the log filepath (/var/lib/docker/containers/<ID>/<ID>-json.log), and the container name is simply not part of that path, so the copy was a silent no-op and logs arrived with only the ID in metadata.

Fix is up in #270: extract_container_id.lua now reads the container name from the config.v2.json file Docker keeps next to each log file (already accessible through the existing read-only mount, so no compose changes needed), caches it per container, and falls back to the 12-char short ID if the file can't be read. With that in place the service field in the UI shows the actual container name.

Once the PR is merged, updating your local extract_container_id.lua to the new version and restarting the fluent-bit container is enough to pick it up; already-ingested logs keep their old values, only new logs get the name.

[Erasure5959]

Thank you @Polliog, that has fixed it.