-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FOGL-6665 #789
base: develop
Are you sure you want to change the base?
FOGL-6665 #789
Conversation
…ices and corresponding support in syslog API Signed-off-by: Amandeep Singh Arora <[email protected]>
Signed-off-by: Amandeep Singh Arora <[email protected]>
Signed-off-by: Amandeep Singh Arora <[email protected]>
Signed-off-by: Amandeep Singh Arora <[email protected]>
Signed-off-by: Amandeep Singh Arora <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why have we done this?
This is not what the Jira requested and has broken lots of other functionality. I explicitly said do not mix this up with the container thing Ashwin raised.
Support bundles will now be broken, documentation is broken, we are writing log data to the must critical of filestore locations, the place we keep our data.
It also does not resolve the original issue when Fledge is producing lots of lots it got very slow - it still will with this.
Hi @MarkRiddoch, this is a separate branch (& PR) compared to my previous work (FOGL-6665 branch) which was against the original JIRA. These are experimental changes that Ashwin asked for, that we can evaluate and see if this improves the user experience for syslog filtering as provided thru' GUI. We can have the logs at an alternate location rather than ${FLEGDE_ROOT}/data/logs. Also this solution would avoid the performance penalty if the system log file has significant number of logs from non-fledge tasks/services. This solution simplifies the grep portion of grep/head/tail command. |
Signed-off-by: Amandeep Singh Arora <[email protected]>
…to FOGL-6665.2
Added changes for configuring separate syslog files for fledge/foglamp with log rotation. Logs would be placed under ${FLEDGE_ROOT}/data/logs folder. File “debug.log” would contains fledge logs of DEBUG and higher levels, & similarly for info.log, warning.log and error.log files. So now extracting fledge (service) logs is quite fast, except when filtering debug logs and there being lots of debug logs.
Still pending/questions: