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
Add overall output for aminer #288
Comments
Same as in issue #287 this can be handled with > or >> or 2> depending on the stream you want to redirect. |
Please close if you agree. |
The problem is that output components do not write error messages, e.g., when the aminer crashes due to some bug, to the file, and > is not possible when the aminer is run as a service. |
I think in that case the (debug) logfile provides or should provide (every error message should be checked again after all PR are accepted - there already exists an issue for that) the output errors. Error messages are logged at every log level. |
Does this include exceptions thrown by python? For example, there is an index out of bound exception in one of the detectors and we do not catch this exception, will the message end up in the aminer logfile? |
It includes every catched error, but I think the answer is no. If the error is not catched, it is not logged. |
However i think this is a common problem and should not be solved in code. |
Where is the systemd service defined? Is it in the repository? If so i can make the changes. |
I have found it in source/root/lib/systemd/system. What file should be used by default (for both?)? /var/log/aminer/aminer.log? |
We have discussed this and will implement it in the service configuration. |
There should be a way to write everything that the AMiner outputs in a file. For example, in the beginning of the config, a parameter StandardOutput: "/etc/aminer/output.txt" can be set, where all the output (anomalies, errors, etc) is written to in addition to the usual output components. By default, it should be None and not write anything.
The text was updated successfully, but these errors were encountered: