Consolidate the toast message

Oct 13, 2025 by orovajewels.com 20 views

Introduction

Cloud security is a critical aspect of modern computing, and detection rules play a vital role in identifying potential security threats. In the context of 3P data, creating detection rules can be a complex process, and inconsistencies in the user experience can lead to confusion and errors. This article highlights a specific issue with the toast message displayed when creating a detection rule with 3P data, where the message differs depending on whether the link or button is clicked.

Describe the Bug

When 3P data flyout is open, users have two options to create a detection rule: a link under the Alerts heading and the Take Action button in the footer of the flyout. However, when these options are clicked, the toast message displayed is inconsistent. The link displays a warning-style toast message, while the button displays an error-style toast message with a different message.

Preconditions

To reproduce this behavior, the following preconditions must be met:

A Kibana environment with 3P CSPM data (Wiz, Aws Security Hub) is required.
The user must have access to the 3P data flyout and the Create a detection rule link and button.

To Reproduce

To reproduce the behavior, follow these steps:

Open a document 3P document flyout.
Click on the Create a detection rule link and observe the toast message.
Click on the Take Action button and select the Create a detection rule option, observing the toast message.

Current Behaviour

The current behavior is that the toast message style and message differ depending on whether the link or button is clicked. This inconsistency can lead to confusion and errors when creating detection rules.

Expected Behaviour

The expected behavior is that the toast style and messages should be the same, regardless of whether the link or button is clicked. This consistency would provide a better user experience and reduce the likelihood of errors.

Screenshots

Screenshots of the issue can be found at the following link:

https://github.com/user-attachments/assets/03384320-0b6c-4dd0-9624-c4b410194d72

Desktop Environment

The following desktop environment information is required to reproduce the issue:

OS:
Browser:
Kibana Version: 8.18/9.0
Endpoint Version:
Other Version:

Additional Context

This issue highlights the importance of consistency in user experience, particularly in critical areas such as cloud security. By addressing this inconsistency, developers can provide a better user experience and reduce the likelihood of errors when creating detection rules.

Conclusion

In conclusion, the inconsistent toast message displayed when creating a detection rule with 3P data is a critical issue that needs to be addressed. By providing a consistent user experience, developers can reduce the likelihood of errors and improve the overall security of cloud environments.

Recommendations

Based on the analysis of this issue, the following recommendations are made:

Consolidate the toast message: Ensure that the toast message style and message are the same regardless of whether the link or button is clicked.
Improve user experience: Provide a consistent user experience by ensuring that the toast message is displayed in a clear and concise manner.
Test and validate: Thoroughly test and validate the changes to ensure that the issue is resolved and the user experience is improved.

Q&A: Addressing the Inconsistent Toast Message

Q: What is the issue with the toast message when creating a detection rule with 3P data? A: The issue is that the toast message style and message differ depending on whether the link or button is clicked. This inconsistency can lead to confusion and errors when creating detection rules.

Q: What are the preconditions for reproducing this behavior? A: To reproduce this behavior, a Kibana environment with 3P CSPM data (Wiz, Aws Security Hub) is required, and the user must have access to the 3P data flyout and the Create a detection rule link and button.

Q: How can I reproduce the behavior? A: To reproduce the behavior, follow these steps:

Open a document 3P document flyout.
Click on the Create a detection rule link and observe the toast message.
Click on the Take Action button and select the Create a detection rule option, observing the toast message.

Q: What is the current behavior? A: The current behavior is that the toast message style and message differ depending on whether the link or button is clicked.

Q: What is the expected behavior? A: The expected behavior is that the toast style and messages should be the same, regardless of whether the link or button is clicked.

Q: Why is this issue important? A: This issue is important because it highlights the importance of consistency in user experience, particularly in critical areas such as cloud security. By addressing this inconsistency, developers can provide a better user experience and reduce the likelihood of errors when creating detection rules.

Q: How can I report this issue? A: To report this issue, please provide the following information:

A clear description of the issue
Screenshots of the issue
The Kibana version and endpoint version
The desktop environment information (OS, browser, etc.)

Q: What are the recommendations for addressing this issue? A: The following recommendations are made:

Consolidate the toast message: Ensure that the toast message style and message are the same regardless of whether the link or button is clicked.
Improve user experience: Provide a consistent user experience by ensuring that the toast message is displayed in a clear and concise manner.
Test and validate: Thoroughly test and validate the changes to ensure that the issue is resolved and the user experience is improved.

Q: How can I get involved in addressing this issue? A: If you are interested in addressing this issue, please:

Review the code and provide feedback
Test and validate the changes
Contribute to the development of a fix

By working together, we can provide a better user experience and improve the overall security of cloud environments.