[APM] cropped alerts table in services tab

[yngrdyn]

Relates to #143792.

When selecting a specific environment, the alert table gets filtered by the selection, but it's showing the table cropped even when there is plenty of space to show the rest of the alerts.

Steps to reproduce:

1. Create a Latency threshold rule targeting All environments and a specific service.
2. Go to services inventory and select the service you specified in the rule created
3. Go to Alerts tab
4. Filter by environment
5. See the table cropped.

Expected behavior:
Since there is still plenty of space the table should display as many alerts as can fit in the space

[elasticmachine]

Pinging @elastic/apm-ui (Team:APM)

[MiriamAparicio]

The owners of the table are Actionable observability, maybe we should let them know about this bug

[elasticmachine]

Pinging @elastic/actionable-observability (Team: Actionable Observability)

[yngrdyn]

Thank you Miriam, I added them as assignees

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[maryam-saeidi]

@yngrdyn I am trying to reproduce this error locally, did you see the issue in the build candidate? I am trying to set up APM in build candidate but I haven't been successful yet, any tips on how to do this will be appreciated. In the meantime, I tried this scenario locally on the main but didn't face the issue.

[yngrdyn]

@maryam-saeidi I was testing the scenario locally (main). It seems that it only happens when we have few items in the table

For instance, I just created this alert:

Screen.Recording.2022-11-23.at.15.20.24.mov

while this one, I created yesterday (have more items)

Screen.Recording.2022-11-23.at.15.22.10.mov

If you check my original screenshot, at that time we only had 2 alerts in the table, so it might be related to the number of items (?). For my freshly created rule we have just one alert, but i'm not able to even see it

Don't know what is the version of edge-lite but seems not to be an issue there

I'm wondering if something has changed from that version to what we have in main.

[maryam-saeidi]

@yngrdyn Would you please also add more information about the kibana version and your browser version? There is a template for reporting bugs, it will help us to be able to reproduce them.

[yngrdyn]

Kibana version:
What I found form dev Tools is: .kibana_8.7.0_001

Browser version:
Version 107.0.5304.110 (Official Build) (arm64)

[jcger]

Hi! It isn't the first time we see this issue, and it's not only happening to our alerts table but to other DataGrids too

#142340
https://github.com/elastic/sdh-security-team/issues/473

At the moment we are keeping track of EUI's findings in the second link I shared. Technically it's something we are "working" on although we haven't been able to reproduce so if you find out a reliable way to do it please let me know.

[yngrdyn]

@jcger thanks for the information. I gave all the information I know in this ticket on how to reproduce, in my case it's only happening in Chrome for the version we have in main, in safari it's working fine.
I will close this one then since we have the other one open.