'Slow resolver detected' logspam and inability to look at systemd logs

[TheCraiggers]

I've got a small server hosting a matrix stack, and when I look at the sysapi container logs it's just spamming this "slow resolver detected" message over and over ever few seconds:

Also, and I don't know if this is related or a different issue, but that same server is seemingly unable to look at any logs from the systemd journal. This is extra irritating because all the docker logs are turned off and sent to journal instead. Searching hasn't turned anything up yet, so I thought I'd ask here to see if you have ideas.

[Krillsson]

Set

graphQl:
  instrumentation: false

in configuration.yml to silence those logs

[Krillsson]

In application properties set

# set all logging to error level
logging.level.root=ERROR
# set bash commands to print out input output
logging.level.com.krillsson.sysapi.bash=DEBUG

And it will print out the commands it's using and the output it gets back from systemctl

[TheCraiggers]

Set

graphQl:
instrumentation: false

in configuration.yml to silence those logs

That value is already false. Aside from setting self-discovery to false, I haven't changed anything from the defaults.

In application properties set

set all logging to error level

logging.level.root=ERROR

set bash commands to print out input output

logging.level.com.krillsson.sysapi.bash=DEBUG

And it will print out the commands it's using and the output it gets back from systemctl

I've done so, but so far I don't see anything amiss. I see it does a /bin/sh -c systemctl show --no-pager $service to get general stats about the service, but I don't see anything in the sys-api logs about even trying to get service logs, nevermind trying and generating an error. Is there a certain string I can grep for to make certain?

[Krillsson]

The agent lists all services available on the system. And then to browse its logs it reads out the logs for a given service.

How does the container logs in journal work. Is there a "service" attached to it? Or is it something different?

[TheCraiggers]

Yes, there's a service for each of them. Also, I wasn't very clear here, but it's all services that fail to show logs. Not a single systemd service on this server will show its logs in the tool. It's not just the ones that are attached to containers.