🎉 Feature Request 🎉

What did you expect to see?

Source: As described in this forum thread, I had a missing router, which was not visible in the Dashboard and not routed by Traefik. Luckily I looked at docker-compose ps (and the Portainer UI) to wonder if the unhealthy state is connected to this and also stumbled upon a log entry:

{
  "container": "nodejs-yolo-1234506db4290d8fdff012345a72e2e94e35338111229cbd12ec12345b4bdc04",
  "level": "debug",
  "msg": "Filtering unhealthy or starting container",
  "providerName": "docker",
   "time":"2021-01-30T00:37:06+01:00"
}

Feature Request: Searching the logs would be easier, if this ☝️ log line would be extended by the following information, if available:

• rule (traefik)
• hostname (docker/-compose)
• container .Name (docker/-compose)
• router name (traefik)
• service name (traefik)

As a…

developer/ sysadmin/ dev-ops-person

I want to…

be able to find if a service is unhealthy by searching the logs for various kinds of information

so that…

I have a higher probability of finding a rare event, during debugging, of which I am not aware yet and might just stumble upon.

…and…

As an…

ops-person

I want to…

be able collect related logs about health states with as much information about the surrounding details

so that…

I can filter and group incidents and calculate reliability stats and take data driven action upon it *.

* no matter the possibly low tech stack and absence of an expensive logging tool I have at hand.

Thanks in advance!

Related: #7842