Skip to content
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

Open
landauermax opened this issue Jul 19, 2021 · 2 comments
Open

aminer-test output #834

landauermax opened this issue Jul 19, 2021 · 2 comments
Assignees
Labels
enhancement New feature or request low Low priority issue wontfix This will not be worked on

Comments

@landauermax
Copy link
Contributor

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.

@landauermax landauermax added enhancement New feature or request low Low priority issue labels Jul 19, 2021
@ernstleierzopf
Copy link
Contributor

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.

@landauermax
Copy link
Contributor Author

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.

@ernstleierzopf ernstleierzopf added the wontfix This will not be worked on label Jul 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request low Low priority issue wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants