--log.custom-level

Node Operators FAQ
21

If you would switch to a json format, you likely would lost an ability to see logs via UI (I suppose that you use a some kind of UI), your only option would be a shell.

1 Like
22

If I have a Windows node, how should I add this to the config.yaml file?
I tried without the starting ā€“ and the ending \ but the node do not start if the log.customā€¦ line is in the config.yaml file. :frowning:

23

Iā€™m not realy sure, but the notation is different; check the other params in config how they are written. The ā€œ=ā€ sign is replaced with ā€œ:ā€ and so on.
You could try:

log.level: info
log.custom-level: ā€œpiecestore=fatal,ā€¦ā€

ā€¦with straight quotes. Iā€™m on iPhone, I donā€™t know how are you see them.

2 Likes
24

Thank you for the hint, this one is working, no need for quote signs:

log.level: info
log.custom-level: collector=ERROR,piecestore=ERROR

3 Likes
25

Is there a way to get rid of these log entries?

2024-07-25T16:40:01Z    INFO    orders.12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs      sending {"Process": "storagenode", "count": 717}
2024-07-25T16:40:01Z    INFO    orders.12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S      sending {"Process": "storagenode", "count": 15124}
2024-07-25T16:40:01Z    INFO    orders.1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE       sending {"Process": "storagenode", "count": 745}
2024-07-25T16:40:01Z    INFO    orders.121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6      sending {"Process": "storagenode", "count": 97}
2024-07-25T16:40:01Z    INFO    orders.12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs      finished        {"Process": "storagenode"}
2024-07-25T16:40:01Z    INFO    orders.121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6      finished        {"Process": "storagenode"}
2024-07-25T16:40:02Z    INFO    orders.1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE       finished        {"Process": "storagenode"}
2024-07-25T16:40:04Z    INFO    orders.12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S      finished        {"Process": "storagenode"}

--log.custom-level=orders=WARN

doesnā€™t work

26

The ā€œordersā€ is not a separate process like the walkers. The logs are generated by the storagenode main process. So you canā€™t set a log level just for it.

2 Likes
27

If you canā€™t do by this feature, you can override the docker entrypoint and use grep to filter out the lines you donā€™t want.

For example before this was a feature: Disk usage discrepancy? - #342 by Ambifacient

1 Like
28

With the latest update to 1.111.4 my logs get spammed with these lines every minute

2024-08-29T10:20:42Z    INFO    piecestore:monitor      readability check done  {"Process": "storagenode", "Duration": "110.668Āµs"}

How to get rid of these? I already set piecestore=FATAL and added piecestore:monitor=ERROR now, but it doesnā€™t work.

29

I donā€™t know if itā€™s related to readability check interval; if this is the case, you can increase the check interval to 5 min and delay the log entries. I use 60 min on a slow node, but itā€™s not recommended. Anyway, this logging should also use a custom level.

1 Like
30

Yes, itā€™s highly not recommended, because now the node cannot detect a hardware issue when it may occur. And a hour could be enough to disqualify the node if it cannot pass any audit, especially with a 15 seconds timeout for the first attempt. This piece would be audited three more times with a GET_REPAIR though, but could it help if the HW is hanging?

31

But it will, I hope:

https://review.dev.storj.io/c/storj/storj/+/14380/1

2 Likes
32

It will show at DEBUG level now.

https://review.dev.storj.io/c/storj/storj/+/14377

2 Likes
33

What version is ā€œnowā€? Iā€™m not smart enough to read it from that link. The change is not in 1.112.2.

1 Like
34

Ver. 113. You can see the change in that tread.

1 Like
35

Thanks, but how? Can you take a screenshot and circle the version number?

36

See the release v1.113 topic here:

3 Likes