-
Notifications
You must be signed in to change notification settings - Fork 88
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
[BUG] Remove "Last updated by fields" from the UI #763
Comments
Looks like this is an intentional change to the SearchMonitor API. @zengyan-amazon recommended removing the |
@AWSHurneyt Removing the |
Transferring this issue to the alerting dashboards repo since this change will be on the frontend. New Goal[ ] Remove the |
I can work on this issue! |
Sorry @tanupa ! Just seeing your comment now. PR #767 addresses this issue, it's just a matter of backporting it now. If you like, you could take a look at that PR to see which automatic backports failed, and manually create backport PRs for them. Otherwise, you can ignore this issue; I'm just leaving it open because the change hasn't finished backporting. |
Hi @AWSHurneyt Could I take this issue? I have created the PRs for all the failed backports in #767 Thanks, |
@kohinoor98 please refer the original PR that solved the issue. Also when making the backports, please be cherrypick the original commit to make sure these backport commits track the original commit that fixed the problem. |
@lezzago on it! Once I will go ahead and cherry-pick the original commit. |
What is the bug?
The SearchMonitor API is not returning
user
information on a security-enabled cluster.How can one reproduce the bug?
Steps to reproduce the behavior:
What is the expected behavior?
The response should contain some user information as the alerting dashboards plugin is expected to display
Last updated by
on two pages.What is your host/environment?
Do you have any screenshots?
These two pages in the UI should display
Last updated by
; but the necessary info isn't in the API response.Do you have any additional context?
This is the API response for the monitor referenced in the screenshots above.
The text was updated successfully, but these errors were encountered: