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
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?
The text was updated successfully, but these errors were encountered:
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.
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?
The text was updated successfully, but these errors were encountered: