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

[Security Solution] "Rule Execution logs" page shifts downwards on clicking on any duration for the first time only #130946

Closed
ghost opened this issue Apr 26, 2022 · 13 comments · Fixed by #130072
Assignees
Labels
8.3 candidate bug Fixes for quality problems that affect the customer experience Feature:Rule Monitoring Security Solution Detection Rule Monitoring area fixed impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v8.2.1 v8.3.0

Comments

@ghost
Copy link

ghost commented Apr 26, 2022

Describe the bug:
"Rule Execution logs" page shifts downwards on clicking on any duration (for instance: Today, This week, This month, This year) for the first time only.

Kibana/Elasticsearch Stack version:

Version: 8.2.0 BC4
Build: 52005
Commit: 9a5003d8cf0062bf24ef64d6712b44823888cc03

Pre-conditions:

  1. Elastic Search should be up and running
  2. Kibana should be up and running

Steps to reproduce:

  1. Navigate to Rules tab under Security
  2. Click on 'Create new rule' button.
  3. Enter all the fields
  4. Save and Activate the rule
  5. Wait to get the rule succeed
  6. Scroll down on the rule page
  7. Click on 'Rule execution logs' tab
  8. Click on Date picker.
  9. Select any duration (for instance: Today, This week, This month, This year).

Current behavior:

  • "Rule Execution logs" page shifts downwards on clicking on any duration (for instance: Today, This week, This month, This year) for the first time only.

Expected behavior:

  • "Rule Execution logs" page should remain static on clicking on any duration (for instance: Today, This week, This month, This year) for the first time.

Screenshots:

Rules.-.Kibana.-.Google.Chrome.2022-04-26.12-24-21.mp4
@ghost ghost added bug Fixes for quality problems that affect the customer experience triage_needed Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Apr 26, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@ghost ghost self-assigned this Apr 26, 2022
@ghost ghost added v8.2.0 impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. and removed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. labels Apr 26, 2022
@ghost ghost assigned MadameSheema and unassigned ghost Apr 26, 2022
@MadameSheema MadameSheema added Team:Detections and Resp Security Detection Response Team Team:Detection Rule Management Security Detection Rule Management Team and removed v8.2.0 labels Apr 26, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@banderror banderror added Feature:Rule Monitoring Security Solution Detection Rule Monitoring area and removed triage_needed labels Apr 27, 2022
@banderror banderror removed their assignment Apr 27, 2022
@spong
Copy link
Member

spong commented Apr 27, 2022

Yeah, this is an annoying result of not having a fixed component height or keeping the previous data while loading. This is partially fixed in #130072 as we are now setting keepPreviousData, so subsequent loads aren't as jittery (notice the page nav is pretty clean), however the page hop will still exist when reloading to content with less overall height. e.g.

@yiyangliu9286, what would be your preferred solution here -- shall we add a fixed height to the tab content container between Alerts/Exception/Rule execution logs?

@yiyangliu9286
Copy link

@spong thanks for asking this question! I'd say we shouldn't persist any page hop / page shifts downwards behaviour from happening. If I understand it correctly, do you mean that if we add a fixed height to the tab content container that will solve this issue?

@spong
Copy link
Member

spong commented Apr 28, 2022

Yeah, it's the dynamic page height that's causing this hop, so a fixed min-height on the tab containers will take care of the happy path in most situations.

For example, I added a min-height: 800 to the tab container and this is how it behaves when scrolled to the bottom of the pages and switching tabs:

You'll still notice some hop when switching from Execution Log -> Exceptions, but it's far better than the above (current) behavior.

Two things to note here though:

  1. even with min-height, hop is still going to exist when bouncing between tabs (or data fetches on the same tab) when the height goes from > 800 to min-height. You'll see this when viewing the alerts or execution log table with large rows per page, but it does feel better with a min-height since you have to scroll up a bit to even get the tabs into the viewport.
  2. Exceptions tab is within its own scroll pane, so it isn't really affected once a min-height is in place. That said, it does behave differently than Alerts/Execution Log tables, and users can only see one or two exceptions at a time, so we may want to just remove this dedicated scroll pane wrapper? What do you think @yiyangliu9286?

@spong
Copy link
Member

spong commented Apr 28, 2022

Hmmm....so one thing we could do here is have a default min-height (perhaps 800px), and then update it to be whatever the max tab content height is (e.g. when viewing the Alerts tab w/ 100 rows per page) -- that should take care of the remaining jitter. Another tweak that might be nice here is making the tabs a sticky header when scrolling.

@banderror
Copy link
Contributor

banderror commented Apr 29, 2022

Just thinking out loud: min-height could work well with infinite scroll within the logs table (instead of good old pagination), but that would require an unknown (I guess could be very high) LOE to implement this. I don't think EUI supports infinite scroll. But there are UIs in KIbana like the Logs app and Agent Logs view.

I'm not suggesting infinite scroll as a fix for this bug 🙂

@yiyangliu9286
Copy link

Thanks for all the suggestions and feedback @spong @banderror, I am wondering so it looks like setting a min-height should be our best way to solve this, correct?

@spong You mentioned that

even with min-height, hop is still going to exist when bouncing between tabs (or data fetches on the same tab) when the height goes from > 800 to min-height...when viewing the alerts or execution log table with large rows per page.

So it is possible to then set the min-height to potentially larger than 800 to allow viewing the alerts or execution log table with large rows per page be able to fit into that min-height that we set?

And for Exceptions tab, I think it's safe to just remove its own scroll pane because a scroll within a scroll feel a little bit confusing for users as well.

@spong
Copy link
Member

spong commented May 2, 2022

So it is possible to then set the min-height to potentially larger than 800 to allow viewing the alerts or execution log table with large rows per page be able to fit into that min-height that we set?

Yeah, we can do that programmatically when tab content is loaded, however the height will be recalculated when large rows per page content is loaded, so they're displaying without issue now, it would just be more-so for removing the last bit of jitter when switching between a tab with a lot of content to one with none, but it's not a huge issue since the max hop distance can't be that much anyway (between the tab current location and new 800 min-height). E.g. this is the remaining jitter with the above changes:

And for Exceptions tab, I think it's safe to just remove its own scroll pane because a scroll within a scroll feel a little bit confusing for users as well.

Resolved in 917d9cf 🎉

spong added a commit that referenced this issue May 4, 2022
… Part Deux (#130072)

## Summary

Addresses feedback and fixes identified in #126215 & #129003

##### Feedback addressed includes:
* Adds toast for restoring global query state after performing `view alerts for execution` action
<p align="center">
  <img width="500" src="https://user-images.githubusercontent.com/2946766/164511565-b77d3dc8-a8b5-4927-a947-54966a58c74f.gif" />
</p>

* Updates global SuperDatePicker to daterange of execution (+/- day) for `view alerts for execution` action (and clear all other filters)
  * See above gif
* Remove redundant `RuleExecutionStatusType` (#129003 (comment))
* Persist table state (DatePicker/StatusFilter/SortField/SortOrder/Pagination) when navigating to other tabs on the same page
<p align="center">
  <img width="500" src="https://user-images.githubusercontent.com/2946766/164512498-59416601-d967-4a27-b0cc-0715cc0662c0.gif" />
</p>

* Fix duration hours bug (`7 hours (25033167ms)` as `06:417:13:000`)
<p align="center">
  <img width="500" src="https://user-images.githubusercontent.com/2946766/164511478-bf0bb6d8-d8b7-4c86-8fbd-b60090f00555.png" />
</p> 

* Support `disabled rule` platform error (#126215 (comment))
  * Updated `getAggregateExecutionEvents` to fallback to platform status from `event.outcome` if `security_status` is empty, and also falls back to `error.message` is `security_message` is empty. This also now queries for corresponding `event.outcome` if filter is provided so that platform-only events can still be displayed when filtering.
<p align="center">
  <img width="500" src="https://user-images.githubusercontent.com/2946766/164510056-1e0bce86-8360-4d46-b591-2041457e3244.png" />
</p>

* Verify StatusFilter issue #126215 (comment)
  * Unable to reproduce, I believe the query updates around first querying for status may've fixed this?
* Provide helpful defaults for `to`/`from` and support datemath strings again (#129003 (comment))
  * Created enhancement for this here: #131095
* Adds UI Unit tests for RuleExecutionLog Table
* Finalize API Integration tests for gap remediation events
  * Test methods developed for injecting arbitrary execution events while still working with event-log RBAC. See last [API integration test](https://github.com/elastic/kibana/blob/22cc0c8dbd2a1300675caf4c6d471d211ed44858/x-pack/test/detection_engine_api_integration/security_and_spaces/tests/get_rule_execution_events.ts#L121-L166) for technique. This can further be used to inject many execution events and expand tests around pagination, sorting, filters, etc.
* Fixes `gap_duration`'s of `1-499`ms showing up as `-` instead of `0`
* Fixes restore filters action to restore either absolute or relative datepicker as it originally was
* Resolves #130946
  * Adds `min-height` to tab container
  * Removes scroll-pane from ExceptionsViewer to match Alerts/Execution Log
---

##### Remaining follow-ups:

None! 🎉 






### Checklist

Delete any items that are not applicable to this PR.

- [X] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [X] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
- [X] Any UI touched in this PR is usable by keyboard only (learn more about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [X] This renders correctly on smaller devices using a responsive layout. (You can test this [in your browser](https://www.browserstack.com/guide/responsive-testing-on-local-server))
spong added a commit to spong/kibana that referenced this issue May 4, 2022
… Part Deux (elastic#130072)

## Summary

Addresses feedback and fixes identified in elastic#126215 & elastic#129003

##### Feedback addressed includes:
* Adds toast for restoring global query state after performing `view alerts for execution` action
<p align="center">
  <img width="500" src="https://user-images.githubusercontent.com/2946766/164511565-b77d3dc8-a8b5-4927-a947-54966a58c74f.gif" />
</p>

* Updates global SuperDatePicker to daterange of execution (+/- day) for `view alerts for execution` action (and clear all other filters)
  * See above gif
* Remove redundant `RuleExecutionStatusType` (elastic#129003 (comment))
* Persist table state (DatePicker/StatusFilter/SortField/SortOrder/Pagination) when navigating to other tabs on the same page
<p align="center">
  <img width="500" src="https://user-images.githubusercontent.com/2946766/164512498-59416601-d967-4a27-b0cc-0715cc0662c0.gif" />
</p>

* Fix duration hours bug (`7 hours (25033167ms)` as `06:417:13:000`)
<p align="center">
  <img width="500" src="https://user-images.githubusercontent.com/2946766/164511478-bf0bb6d8-d8b7-4c86-8fbd-b60090f00555.png" />
</p>

* Support `disabled rule` platform error (elastic#126215 (comment))
  * Updated `getAggregateExecutionEvents` to fallback to platform status from `event.outcome` if `security_status` is empty, and also falls back to `error.message` is `security_message` is empty. This also now queries for corresponding `event.outcome` if filter is provided so that platform-only events can still be displayed when filtering.
<p align="center">
  <img width="500" src="https://user-images.githubusercontent.com/2946766/164510056-1e0bce86-8360-4d46-b591-2041457e3244.png" />
</p>

* Verify StatusFilter issue elastic#126215 (comment)
  * Unable to reproduce, I believe the query updates around first querying for status may've fixed this?
* Provide helpful defaults for `to`/`from` and support datemath strings again (elastic#129003 (comment))
  * Created enhancement for this here: elastic#131095
* Adds UI Unit tests for RuleExecutionLog Table
* Finalize API Integration tests for gap remediation events
  * Test methods developed for injecting arbitrary execution events while still working with event-log RBAC. See last [API integration test](https://github.com/elastic/kibana/blob/22cc0c8dbd2a1300675caf4c6d471d211ed44858/x-pack/test/detection_engine_api_integration/security_and_spaces/tests/get_rule_execution_events.ts#L121-L166) for technique. This can further be used to inject many execution events and expand tests around pagination, sorting, filters, etc.
* Fixes `gap_duration`'s of `1-499`ms showing up as `-` instead of `0`
* Fixes restore filters action to restore either absolute or relative datepicker as it originally was
* Resolves elastic#130946
  * Adds `min-height` to tab container
  * Removes scroll-pane from ExceptionsViewer to match Alerts/Execution Log
---

##### Remaining follow-ups:

None! 🎉

### Checklist

Delete any items that are not applicable to this PR.

- [X] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [X] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
- [X] Any UI touched in this PR is usable by keyboard only (learn more about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [X] This renders correctly on smaller devices using a responsive layout. (You can test this [in your browser](https://www.browserstack.com/guide/responsive-testing-on-local-server))

(cherry picked from commit 683463e)

# Conflicts:
#	x-pack/plugins/security_solution/cypress/tasks/alerts.ts
#	x-pack/plugins/security_solution/public/detections/pages/detection_engine/rules/details/execution_log_table/execution_log_columns.tsx
#	x-pack/plugins/security_solution/server/lib/detection_engine/rule_execution_log/event_log/event_log_reader.ts
#	x-pack/plugins/security_solution/server/lib/detection_engine/rule_execution_log/event_log/get_execution_event_aggregation/index.test.ts
#	x-pack/plugins/security_solution/server/lib/detection_engine/rule_execution_log/event_log/get_execution_event_aggregation/index.ts
#	x-pack/test/detection_engine_api_integration/utils/index_event_log_execution_events.ts
@banderror banderror reopened this May 4, 2022
spong added a commit that referenced this issue May 5, 2022
… Fixes Part Deux (#130072) (#131574)

* [Security Solution][Detections] Rule Execution Log Feedback and Fixes Part Deux (#130072)

## Summary

Addresses feedback and fixes identified in #126215 & #129003

##### Feedback addressed includes:
* Adds toast for restoring global query state after performing `view alerts for execution` action
<p align="center">
  <img width="500" src="https://user-images.githubusercontent.com/2946766/164511565-b77d3dc8-a8b5-4927-a947-54966a58c74f.gif" />
</p>

* Updates global SuperDatePicker to daterange of execution (+/- day) for `view alerts for execution` action (and clear all other filters)
  * See above gif
* Remove redundant `RuleExecutionStatusType` (#129003 (comment))
* Persist table state (DatePicker/StatusFilter/SortField/SortOrder/Pagination) when navigating to other tabs on the same page
<p align="center">
  <img width="500" src="https://user-images.githubusercontent.com/2946766/164512498-59416601-d967-4a27-b0cc-0715cc0662c0.gif" />
</p>

* Fix duration hours bug (`7 hours (25033167ms)` as `06:417:13:000`)
<p align="center">
  <img width="500" src="https://user-images.githubusercontent.com/2946766/164511478-bf0bb6d8-d8b7-4c86-8fbd-b60090f00555.png" />
</p>

* Support `disabled rule` platform error (#126215 (comment))
  * Updated `getAggregateExecutionEvents` to fallback to platform status from `event.outcome` if `security_status` is empty, and also falls back to `error.message` is `security_message` is empty. This also now queries for corresponding `event.outcome` if filter is provided so that platform-only events can still be displayed when filtering.
<p align="center">
  <img width="500" src="https://user-images.githubusercontent.com/2946766/164510056-1e0bce86-8360-4d46-b591-2041457e3244.png" />
</p>

* Verify StatusFilter issue #126215 (comment)
  * Unable to reproduce, I believe the query updates around first querying for status may've fixed this?
* Provide helpful defaults for `to`/`from` and support datemath strings again (#129003 (comment))
  * Created enhancement for this here: #131095
* Adds UI Unit tests for RuleExecutionLog Table
* Finalize API Integration tests for gap remediation events
  * Test methods developed for injecting arbitrary execution events while still working with event-log RBAC. See last [API integration test](https://github.com/elastic/kibana/blob/22cc0c8dbd2a1300675caf4c6d471d211ed44858/x-pack/test/detection_engine_api_integration/security_and_spaces/tests/get_rule_execution_events.ts#L121-L166) for technique. This can further be used to inject many execution events and expand tests around pagination, sorting, filters, etc.
* Fixes `gap_duration`'s of `1-499`ms showing up as `-` instead of `0`
* Fixes restore filters action to restore either absolute or relative datepicker as it originally was
* Resolves #130946
  * Adds `min-height` to tab container
  * Removes scroll-pane from ExceptionsViewer to match Alerts/Execution Log
---

##### Remaining follow-ups:

None! 🎉

### Checklist

Delete any items that are not applicable to this PR.

- [X] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [X] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
- [X] Any UI touched in this PR is usable by keyboard only (learn more about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [X] This renders correctly on smaller devices using a responsive layout. (You can test this [in your browser](https://www.browserstack.com/guide/responsive-testing-on-local-server))

(cherry picked from commit 683463e)

# Conflicts:
#	x-pack/plugins/security_solution/cypress/tasks/alerts.ts
#	x-pack/plugins/security_solution/public/detections/pages/detection_engine/rules/details/execution_log_table/execution_log_columns.tsx
#	x-pack/plugins/security_solution/server/lib/detection_engine/rule_execution_log/event_log/event_log_reader.ts
#	x-pack/plugins/security_solution/server/lib/detection_engine/rule_execution_log/event_log/get_execution_event_aggregation/index.test.ts
#	x-pack/plugins/security_solution/server/lib/detection_engine/rule_execution_log/event_log/get_execution_event_aggregation/index.ts
#	x-pack/test/detection_engine_api_integration/utils/index_event_log_execution_events.ts

* Fixing import
@ghost
Copy link
Author

ghost commented May 11, 2022

Hi @MadameSheema @spong,

We have validated above issue on 8.3.0 SNAPSHOT build and it's working fine ✅.

  • "Rule Execution logs" page doesn't shift downwards on clicking on any time duration for the first time.

Build info

Version: 8.3.0 SNAPSHOT
Build: 52512
Commit: df225b213b188c81888141cee2ec191424fc0649

Screenshot:

Rules.-.Kibana.-.Google.Chrome.2022-05-11.15-33-35.mp4

Hence, We are closing this issue and marking as QA Validated.

Thanks!

@ghost ghost closed this as completed May 11, 2022
@ghost ghost added the QA:Validated Issue has been validated by QA label May 11, 2022
@ghost
Copy link
Author

ghost commented May 19, 2022

Hi @MadameSheema @spong,

We have validated above issue on 8.2.1 BC1 build and it's working fine ✅.

  • "Rule Execution logs" page doesn't shift downwards on clicking on any time duration for the first time.

Build info:

Version: 8.2.1 BC1
Build: 52170
Commit: 88889128ccda6f7e13983b0087e9aaa183818473

Screenshots:

Rules.-.Kibana.-.Google.Chrome.2022-05-19.11-25-32.mp4

Thanks!

@ghost
Copy link
Author

ghost commented May 20, 2022

Hi @MadameSheema @spong,

We have validated above issue on 8.2.1 BC2 Staging build and it's working fine ✅.

  • "Rule Execution logs" page doesn't shift downwards on clicking on any time duration for the first time.

Build info:

Version: 8.2.1 BC2
Build: 52192
Commit: d4427fadd63ee9face4438cb3a4e17aaec93afe4

Screenshots:

Rules.-.Kibana.-.Google.Chrome.2022-05-20.14-06-46.mp4

Thanks!

kertal pushed a commit to kertal/kibana that referenced this issue May 24, 2022
… Part Deux (elastic#130072)

## Summary

Addresses feedback and fixes identified in elastic#126215 & elastic#129003

##### Feedback addressed includes:
* Adds toast for restoring global query state after performing `view alerts for execution` action
<p align="center">
  <img width="500" src="https://user-images.githubusercontent.com/2946766/164511565-b77d3dc8-a8b5-4927-a947-54966a58c74f.gif" />
</p>

* Updates global SuperDatePicker to daterange of execution (+/- day) for `view alerts for execution` action (and clear all other filters)
  * See above gif
* Remove redundant `RuleExecutionStatusType` (elastic#129003 (comment))
* Persist table state (DatePicker/StatusFilter/SortField/SortOrder/Pagination) when navigating to other tabs on the same page
<p align="center">
  <img width="500" src="https://user-images.githubusercontent.com/2946766/164512498-59416601-d967-4a27-b0cc-0715cc0662c0.gif" />
</p>

* Fix duration hours bug (`7 hours (25033167ms)` as `06:417:13:000`)
<p align="center">
  <img width="500" src="https://user-images.githubusercontent.com/2946766/164511478-bf0bb6d8-d8b7-4c86-8fbd-b60090f00555.png" />
</p> 

* Support `disabled rule` platform error (elastic#126215 (comment))
  * Updated `getAggregateExecutionEvents` to fallback to platform status from `event.outcome` if `security_status` is empty, and also falls back to `error.message` is `security_message` is empty. This also now queries for corresponding `event.outcome` if filter is provided so that platform-only events can still be displayed when filtering.
<p align="center">
  <img width="500" src="https://user-images.githubusercontent.com/2946766/164510056-1e0bce86-8360-4d46-b591-2041457e3244.png" />
</p>

* Verify StatusFilter issue elastic#126215 (comment)
  * Unable to reproduce, I believe the query updates around first querying for status may've fixed this?
* Provide helpful defaults for `to`/`from` and support datemath strings again (elastic#129003 (comment))
  * Created enhancement for this here: elastic#131095
* Adds UI Unit tests for RuleExecutionLog Table
* Finalize API Integration tests for gap remediation events
  * Test methods developed for injecting arbitrary execution events while still working with event-log RBAC. See last [API integration test](https://github.com/elastic/kibana/blob/22cc0c8dbd2a1300675caf4c6d471d211ed44858/x-pack/test/detection_engine_api_integration/security_and_spaces/tests/get_rule_execution_events.ts#L121-L166) for technique. This can further be used to inject many execution events and expand tests around pagination, sorting, filters, etc.
* Fixes `gap_duration`'s of `1-499`ms showing up as `-` instead of `0`
* Fixes restore filters action to restore either absolute or relative datepicker as it originally was
* Resolves elastic#130946
  * Adds `min-height` to tab container
  * Removes scroll-pane from ExceptionsViewer to match Alerts/Execution Log
---

##### Remaining follow-ups:

None! 🎉 






### Checklist

Delete any items that are not applicable to this PR.

- [X] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [X] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
- [X] Any UI touched in this PR is usable by keyboard only (learn more about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [X] This renders correctly on smaller devices using a responsive layout. (You can test this [in your browser](https://www.browserstack.com/guide/responsive-testing-on-local-server))
@ghost
Copy link
Author

ghost commented Jun 3, 2022

Hi @MadameSheema @spong,

We have validated above issue on 8.3.0 BC2 and it's working fine ✅.

  • "Rule Execution logs" page doesn't shift downwards on clicking on any time duration for the first time.

Build info:

Version: 8.3.0 BC2
Build: 53231
Commit: 25476b531ba9f32292bde85508d342aa5e1c29eb

Screenshots:

VM.Prachi.1.-.ec2-54-90-253-174.compute-1.amazonaws.com.-.Remote.Desktop.Connection.2022-06-03.13-24-13.mp4

Thanks!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8.3 candidate bug Fixes for quality problems that affect the customer experience Feature:Rule Monitoring Security Solution Detection Rule Monitoring area fixed impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v8.2.1 v8.3.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants