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

[Beats CM] Add Search component for table assignment options #23202

Conversation

justinkambic
Copy link
Contributor

Changes

We've talked about abandoning the ability to assign beats and tags to one another from the table because the options we were using are not scalable for large numbers of beats/tags. I've added a new component for the assignment section. At the moment it's only doing exact matches for one beat, but it could be customized to do an exact or fuzzy search to find a set of beats.

sep-14-2018 13-54-26

Additionally, the way assignment components are defined has changed, and is set up to handle a variety of components in a generic way.

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@justinkambic justinkambic force-pushed the ui/add-search-assignment-control branch from 282a90d to 213bea5 Compare September 17, 2018 15:37
@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@exekias
Copy link
Contributor

exekias commented Sep 25, 2018

Just saw this, sorry. We allow the user to add some tag to all selected beats in the beats list.

This would add another way of doing that from this view, is it really needed?

@justinkambic
Copy link
Contributor Author

@exekias - my motivation for these changes is reasoned that, while there aren't likely to be thousands of tags in a configuration index, there could very well be thousands of beats. The present control simply getAlls the beats and lists them with all of their associated tags. It's not at all scalable.

This would replace that solution. If we want to go another direction, or remove the ability to assign beats to a tag entirely, that's doable as well. I felt that this was a better placeholder than what's currently in the feature branch today.

@exekias
Copy link
Contributor

exekias commented Sep 26, 2018

thank you for the explanation, that makes sense. I wonder if we should go with the later, removing this functionality. That would mean that you need to go to the beats tab to assign a tag, which is not that bad.

What do you think?

@justinkambic
Copy link
Contributor Author

@exekias I am fine with removing assignment options from this table if you and @mattapperson agree it is ok. I can modify these changes to exclude assignment options on this table.

@exekias
Copy link
Contributor

exekias commented Sep 27, 2018

SGTM, thanks!

@justinkambic
Copy link
Contributor Author

Closing this PR in favor of #23663, which better addresses the issues these changes attempted to solve.

@justinkambic justinkambic deleted the ui/add-search-assignment-control branch October 1, 2018 19:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants