Logs not accessible by add-on (insecure mode)? about hassio-addons

[bertbaron]

Hi, the log is looking just fine, the messages themselves will not be logged in the Logspout log, just send through any route. Containers should also be empty, I think this will only be valid when filters are provided. My guess is that either sending the logs to the Loki endpoint fails or you are looking in the wrong place to find them.
To confirm or rule out the first option, you could enable debug logging with the following in the config (yaml format):

env:
  - name: DEBUG
    value: "true"

If there are errors sending the messages you should see them.

I will be on holiday for the next two weeks so I can not help you any further until then and have no time now to validate the logging to Grafana Cloud myself (there is a small chance that their API changed, breaking the integration). If you are stuck you might try to post a message on the ha community topic, maybe someone else will be able to help. Otherwise please remind me in a few weeks.

[bertbaron]

You are right, that is a bug indeed! Never noticed it, and I wonder if anyone uses the Loki adapter. But I will fix this asap.

[moltob]

Thank you so much, it is working now! I'll keep using Grafana now as originally intended. I'll let you know if I stumble across other issues, if I may.

Feel free to close the issue whenever it suits you.

[moltob]

Forgot to add: the addon is running in unprotected mode:

[bertbaron]

Is this still a problem for you? I tried myself and it works for me. On grafana.com, I go to 'My Account', Launch Grafana, go to Explore, select grafanacloud-<my-username>-logs (Loki). Then under label filters I can select nodename and choose ha as value.

[moltob]

Thanks a lot for checking again. I was considering using Graylog instead, but I'll give it another try. But actually now I am on vacation. So it'll be another two weeks on my end.

Using a local Loki instance worked, but the data was weird in terms of timestamps. But we'll see. I'll keep you posted.

I would prefer using Grafana, so I very much appreciate your test and support!

Picking up testing on my end once I get home.

[moltob]

I just retried. Now I do see data coming in. (Don't ask me, why this was not the case in the first attempt...). However, now I see a similar issue to a local Loki instance: It appears the timestamps sent to (or interpreted by) Loki are not the log times, but for some funny reason this seem to be the time logspout was started.

So in my case, all logs sit at this single point in time:

You can also the see the "wrong" and the "real" timestamps in the textual logs. Here some random examples logs:

When I show the labels of the first entry, the created date even shows this is a much older entry:

Here is another log entry that was just emitted:

Am I missing a timestamp mapping somewhere?

[bertbaron]

I just created a new release which includes a fix for the timestamps in the Loki adapter