You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
How should this work?
First of all we do not know all the analysis components and their states (what did they learn?)
Second we do not know what the data has too look like to pass all parsers. It is impossible to create those outputs for analysers like the VTD or VCD.
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: