We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think it would help a lot if the console command for invalidating report data would take the segment id, as an option.
So instead of: /console core:invalidate-report-data --segment='eventCategory=@StringFoo;visitIp!=127.0.0.1'
/console core:invalidate-report-data --segment='eventCategory=@StringFoo;visitIp!=127.0.0.1'
We could have: /console core:invalidate-report-data --segment-id=2
/console core:invalidate-report-data --segment-id=2
Also makes sense when the core:archive command takes the segment-id as a parameter, a.k.a: ./console core:archive --force-idsegments=2
./console core:archive --force-idsegments=2
If this is a good idea, I could look into it and do a pull request. For non breaking changes we could keep the segment definition option still.
The text was updated successfully, but these errors were encountered:
Thanks for creating the issue @mikkeschiren This is a duplicate of #14763 Be great to follow that issue
Sorry, something went wrong.
No branches or pull requests
I think it would help a lot if the console command for invalidating report data would take the segment id, as an option.
So instead of:
/console core:invalidate-report-data --segment='eventCategory=@StringFoo;visitIp!=127.0.0.1'
We could have:
/console core:invalidate-report-data --segment-id=2
Also makes sense when the core:archive command takes the segment-id as a parameter, a.k.a:
./console core:archive --force-idsegments=2
If this is a good idea, I could look into it and do a pull request. For non breaking changes we could keep the segment definition option still.
The text was updated successfully, but these errors were encountered: