-
Notifications
You must be signed in to change notification settings - Fork 23
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
aminer-test output #834
Comments
How should this work? Generally the user already needs some data to create the configuration in the first place. He can use this data as basis and change it a little bit. For example in the NewMatchPathValueDetector just add a character to the value and you have an anomaly. There is no way around manually choosing test-loglines for any configuration. |
I don't know yet how to realize this. The issue is just to make sure that we do not forget about the feedback we received and discuss it in the future. |
We received a feedback that it would be helpful to produce sample output for a configuration, just to see that the configuration works as expected and have an idea what the output of that config might look like. One idea would be to use a command aminer-test -c /etc/aminer/config.yml that will cause all detectors to produce one anomaly for a sample line that always yields anomalies.
The text was updated successfully, but these errors were encountered: