By default, the duration for storing log messages was set to 7 days (168 hours).
We have a requirement to be able to trace the log further back. Sometimes we need to check which entries a job has caused weeks later.
We have now increased the duration to 2 weeks (336 hours) (Preferences - Application data). However, I have the feeling that it takes much longer to open the log in the browser.
We would like to increase the duration even further, but we are afraid that at some point this will no longer be performant enough.
Are there any guidelines or empirical values as to how long the duration can be set?
Or is it better to activate logging to a CSV file in the "Logging" area? When activating it, I get a message that this function should only be activated when requested by Enfocus support. And the CSV files are apparently only saved for as long as the log database is set.
Thanks for your support,
Peter
Is there a (sensible) upper limit for log messages?
Is there a (sensible) upper limit for log messages?
Media asset and production specialist
Group Communications / System Operations
Phoenix Contact GmbH & Co. KG
www.phoenixcontact.com
Group Communications / System Operations
Phoenix Contact GmbH & Co. KG
www.phoenixcontact.com
- Soul Forge
- Member
- Posts: 61
- Joined: Wed Jul 12, 2023 5:25 pm
Re: Is there a (sensible) upper limit for log messages?
Well, if it's about tracking jobs there are multiple apps on the appstore that allow you to save logs related to a job on text files.
But if you want ALL switch logs, even when it's not about jobs, I guess it would only be achievable through scripts.
If it's really important and something you guys can't live without, you could learn scripting or hire someone to make a script for you!
https://www.enfocus.com/en/appstore/appmatch
But if you want ALL switch logs, even when it's not about jobs, I guess it would only be achievable through scripts.
If it's really important and something you guys can't live without, you could learn scripting or hire someone to make a script for you!
https://www.enfocus.com/en/appstore/appmatch
Re: Is there a (sensible) upper limit for log messages?
We keep the logs in the database (Preferences––>Application data––>Keep log messages…) for a week. For a while we tried to keep several weeks worth of logs in the database and that definitely affected performance.
We've also enabled csv logging (Preferences––>Logging––>Log to csv file) and have Switch keep those files for 90 days. Switch automatically limits the csv file sizes to roughly 2.5 MB of data so there are quite many files, but using some text editors' "search in files" functionalities or other tools makes it easy enough to find earlier log entries when needed. The message about only activating logging when requested by Enfocus support refers to the "Log debug messages" option so normal CSV logging is fine.
We've also enabled csv logging (Preferences––>Logging––>Log to csv file) and have Switch keep those files for 90 days. Switch automatically limits the csv file sizes to roughly 2.5 MB of data so there are quite many files, but using some text editors' "search in files" functionalities or other tools makes it easy enough to find earlier log entries when needed. The message about only activating logging when requested by Enfocus support refers to the "Log debug messages" option so normal CSV logging is fine.
- magnussandstrom
- Advanced member
- Posts: 510
- Joined: Thu Jul 30, 2020 6:34 pm
- Location: Sweden
- Contact:
Re: Is there a (sensible) upper limit for log messages?
We only keep logs in Switch for 48h. But..
..we have added a generic log export as csv on all our flows using the app 'Create file from template'. We can search the csv logs with FileLocator Pro to quickly find what we are looking for like.
Have job X been processed?
What flow have job X been going through?
Who submitted job X?
What parameters was choosen on job X?
Have job X been archived?
etc..
..we have added a generic log export as csv on all our flows using the app 'Create file from template'. We can search the csv logs with FileLocator Pro to quickly find what we are looking for like.
Have job X been processed?
What flow have job X been going through?
Who submitted job X?
What parameters was choosen on job X?
Have job X been archived?
etc..