Logging doesn't populate

[douglasjthomas]

Logging doesn't populate

[hugovalente-pm]

@douglasjthomas thanks for raising this bug to us, from the look of it it seems your systems is not running or able to run systemd-journal which, atm, is our currently log integration available.
can you provide more details on where and how your agent is running on the node?

for reference: the prerequisites to be able to run this - https://learn.netdata.cloud/docs/logs/systemd-journal/#plugin-availability

we'll fix the UI to show something meaning like:

There isn't any log integration available on your node. Please check your integrations setup.
Get more information on available log integrations here.

@netdata/cloud-fe while trying to reproduce this, deploying netdata with docker remove the ro mapped volumes, case I got two different screens

1st time I went to the Logs tab

Other attempts

suggestion is to place the message mentioned above

[novykh]

Is this still an issue?

[douglasjthomas]

Looks good after the latest update. Thank you, Doug Thomas Sent with [Proton Mail](https://proton.me/) secure email.

…

On Wednesday, February 7th, 2024 at 4:34 AM, Johnny Klironomos ***@***.***> wrote: Is this still an issue? — Reply to this email directly, [view it on GitHub](#974 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/A5JZZNTX7E6OKV6MA7HWAHLYSNRCVAVCNFSM6AAAAABCA4VCRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZRHA2TGNZTGY). You are receiving this because you were mentioned.Message ID: ***@***.***>