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

Consistent naming for spooling to disk feature #8016

Closed
geekpete opened this issue Aug 20, 2018 · 3 comments
Closed

Consistent naming for spooling to disk feature #8016

geekpete opened this issue Aug 20, 2018 · 3 comments
Labels
enhancement libbeat needs_team Indicates that the issue/PR needs a Team:* label Stalled

Comments

@geekpete
Copy link
Member

Hey Team,

I was wondering with the new spooling to disk feature (#6859), if there's merit in trying to be consistent with naming in relation to the already existing Persistent Queue available in Logstash?

Would naming it Beats PQ provide one less mental hurdle for users who may already be aware of Logstash PQ to immediately know what this new feature does/achieves?
Or is there some fundamental differences that this alignment might blur where we'd want to keep a distinction?

@botelastic
Copy link

botelastic bot commented Jul 9, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@botelastic botelastic bot added Stalled needs_team Indicates that the issue/PR needs a Team:* label labels Jul 9, 2020
@botelastic
Copy link

botelastic bot commented Jul 9, 2020

This issue doesn't have a Team:<team> label.

@botelastic botelastic bot closed this as completed Aug 8, 2020
@geekpete
Copy link
Member Author

It seems that File Spool Queue is fairly baked at this point?
Any direction with the unified Elastic Agent that might make this relevant again?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement libbeat needs_team Indicates that the issue/PR needs a Team:* label Stalled
Projects
None yet
Development

No branches or pull requests

1 participant