AWSHurneyt

Transferring this issue to the alerting dashboards repo since this change will be on the frontend. #### New Goal [ ] Remove the `Last updated by` fields from the UI...

> 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...

Manual backport of PR https://github.com/opensearch-project/alerting-dashboards-plugin/pull/767

@mjsell1234 would you mind rebasing that development branch so that it's up to date with the current [main](https://github.com/opensearch-project/alerting-dashboards-plugin/tree/main) branch? That should trigger the test workflows again, which will let us...

> @AWSHurneyt Do we think this can be labeled as "Good first issue"? (I don't have permission to add labels). @kamingleung Yeah, that sounds fine. I've added the label.

I've added this PR to our sprint board so the team can get it reviewed, and closed out.

Hi @sapir2239, We don't currently support this, but a workaround could involve defining an additional trigger for the monitor. For example, if the `happy` state for your use case is...

With the changes made to `query_level_monitor_spec.js` in PR https://github.com/opensearch-project/opensearch-dashboards-functional-test/pull/622, the second test in the list doesn't appear to be failing periodically anymore. I've scratched it off the list, but we...

Reopening issue as flaky test 5 still seems to be an issue as seen in PR https://github.com/opensearch-project/alerting-dashboards-plugin/pull/767

Related issue https://github.com/opensearch-project/alerting-dashboards-plugin/issues/762