You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I create the pipeline with a index prefix, and the new index is overlapped with an active index in OpenSearch, then it will show me the error message: You have a deleted log pipeline that used this index prefix. If you keep creating this log pipeline will get mixed up..
The pipeline is active, and not deleted.
Expected Behavior
Change the error style popup window to warning style popup window.
Change Oops.. to Warning.
Change the text to It looks like there is an active or deleted pipeline configured with the index you entered. To proceed with creating this new pipeline and sending logs to the same index, please select "Continue Create". If you would like to use a different index prefix instead, please choose "Edit" to update.
Current Behavior
N/A
Reproduction Steps
N/A
Possible Solution
No response
Additional Information/Context
No response
Solution Version
v2.1.0
AWS Region. e.g., us-east-1
No response
Other information
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
When I create the pipeline with a index prefix, and the new index is overlapped with an active index in OpenSearch, then it will show me the error message:
You have a deleted log pipeline that used this index prefix. If you keep creating this log pipeline will get mixed up.
.The pipeline is active, and not deleted.
Expected Behavior
It looks like there is an active or deleted pipeline configured with the index you entered. To proceed with creating this new pipeline and sending logs to the same index, please select "Continue Create". If you would like to use a different index prefix instead, please choose "Edit" to update.
Current Behavior
N/A
Reproduction Steps
N/A
Possible Solution
No response
Additional Information/Context
No response
Solution Version
v2.1.0
AWS Region. e.g., us-east-1
No response
Other information
No response
The text was updated successfully, but these errors were encountered: