Anyone have a solution for exporting webCoRe logs to a file or similar and rotating at some particular interval to keep the file size reasonable? I have a few longer pistons that I'd like to have full logging to be able to really troubleshoot and/or maintain the data, but the internal webCoRE logs rotate too frequently to be useful. TIA for any ideas, appreciated.
Thanks @nh.schottfam. Appears this is the built-in webCoRE app? I haven't migrated to the built-in yet, but it's on my list of things to do. Are there any considerations to take into account when including in the HE logs? I see the defaults being set to 50, which seems low given the complexity of some pistons, and makes me wonder if even the HE logs will support enough retained webCoRE logs to be useful? Thanks again,
it should work for user install or built-in
@nh.schottfam ok thanks. I'm seeing it in the individual HE piston settings now. I guess the question I still have would be regarding any special considerations to take into account when including in the HE logs? The default seems pretty low but I'm unsure if I'll run into any negative issues if I were to raise it (taking the holistic number of pistons into account and trying to see full logging)? I freely admit, I'm not as educated as I should be on the log capacity of the hub. As always, thanks for the continued insights.
I would not turn this on for all pistons. Logging is overhead on your hub.
I would only do it for pistons that really need it, with a goal to turn it off.
@nh.schottfam thanks for the info and support. This doesn't completely solve my inquiry and use case, but it does give me an option to use if needed, so appreciated. Thanks again!
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
