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
Analysts don't often want to scan the entire repo (running >1TB) as it is slow (rules take > 20minutes). While we can use tags, tagging the data and merging becomes cumbersome as the dataset grows with new directories.
Describe the solution you'd like
Allow analysts instead of selecting just tags, to select which subdirectory or path from where the files were indexed.
Describe alternatives you've considered
Improving the tagging method and selection process would be a stopgap - they're currently not alphabetical, and create a long list on the web ui (we have over 100 directories so 100 tags is cumbersome to sort through in one list).
The text was updated successfully, but these errors were encountered:
also, scanning specific tags doesn't seem to significantly speed up the scans, even when there are a small amount of files tagged as such, is it still scanning everything?
Feature Category
Describe the problem
Analysts don't often want to scan the entire repo (running >1TB) as it is slow (rules take > 20minutes). While we can use tags, tagging the data and merging becomes cumbersome as the dataset grows with new directories.
Describe the solution you'd like
Allow analysts instead of selecting just tags, to select which subdirectory or path from where the files were indexed.
Describe alternatives you've considered
Improving the tagging method and selection process would be a stopgap - they're currently not alphabetical, and create a long list on the web ui (we have over 100 directories so 100 tags is cumbersome to sort through in one list).
The text was updated successfully, but these errors were encountered: