[BeatsCM] Paginate beats and tags on the API

[mattapperson]

Currently CM paginates beats and tags but it does so in-memory in the browser. Each API request returns ALL beats and tags.

This PR paginates these items on an API level for drastically improved perf on large scale deployments.

Note: Depends on
#31660

Also fixes:

• [BeatsCM] beats and tags lists paginate, but then put all results on page 1 #29889
• [Beats CM] Filter results bar when cleared either by backspace or 'x' button clears all items in below table #28308

And adds a new feature of:

• Polling for updates: [Beats CM] Auto-refresh status #28616

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[mattapperson]

@justinkambic for the access issue, try clearing browser cache and optimize folder. This was an issue before I made a change to rendering. That change might not be making it through an old optimizer build

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[justinkambic]

EDIT: I accidentally conducted this test on master, but the things I pointed out happened the same way on my PR branch, so they are not related to this PR and can probably be disregarded.

So, everything I tried when doing a functional review worked ok.

My process was to:

• navigate through start-up experience
• enroll several beats
• create several tags
• associate my tags with a few beats
• associate/disassociate across multiple beats

Something worth mentioning - buttons required double-clicks in some cases (I know this has been an issue in the past, so it may be the same one), and the beats list didn't update after I enrolled beats, only if I navigated to a different page/view and back to it, seen below.

Note

• after watching this I didn't leave enough frames at the end, there were 4 beats, after enrollment 5 are displayed when I navigate back)
• you can see me needing to double-click the Done button

Aside from that this looks like it's working ok!

[justinkambic]

Something else I've noticed, I can't seem to disassociate tags from beats using the dropdown on the beats list:

This should take the tag off of the beat right?

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[justinkambic]

Ok, I went back and checked the two functional issues I had and they are fixed now. I was able to update the license of my snapshot to platinum from the management tab, and I could remove tags from beats again.

[justinkambic]

LGTM

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[ph]

1. Should I see some pagination navigation displayed when I change the number of items?

2. I've tested it locally, I have created 12 tags, I set the row per page to be 10, the list is adjusted to 10, but the rows per page still display the default of 25.

[elasticmachine]

Pinging @elastic/beats

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[ph]

LGTM, need rebase.

[ph]

Let's rebase and merge this @mattapperson

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[jbagel2]

Is this feature stalled? Or still planed for merge?

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request