Composite Monitor Notification Channel Dropdown Empty

[skyallenm]

Describe the bug

Related component

Other

To Reproduce

1. alert tab
2. select composite monitor
3. add trigger
4. notification channel dropdown

Expected behavior

In composite monitor Notification channel list should be display.

Additional Details

Plugins
Please list all plugins currently enabled.

Screenshots
If applicable, add screenshots to help explain your problem.

Host/Environment (please complete the following information):

• OS: [e.g. iOS]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[andrross]

@opensearch-project/triage Can you transfer this to the https://github.com/opensearch-project/OpenSearch-Dashboards repo?

[KyongSik-Yoon]

I have also same problem in "Per query monitor"
Registering two channels(mail, slack) is not appeared.
Each of channel send test success.

I'm using opensearch 2.14.0

• Channels
  

• Actions in Alerts
  

[AWSHurneyt]

@opensearch-project/opensearch-dashboards-core
Could someone transfer this to the https://github.com/opensearch-project/alerting-dashboards-plugin repo? The alerting team will take a look.

[huyaboo]

@opensearch-project/opensearch-dashboards-core
Could someone transfer this to the https://github.com/opensearch-project/alerting-dashboards-plugin repo? The alerting team will take a look.

@opensearch-project/admin ^

[AWSHurneyt]

@skyallenm and @KyongSik-Yoon Thanks for reporting this! We've tracked down the cause of this bug.

The following commit refactored the response object that gets returned by the API the Alerting UI uses to retrieve the channels.
opensearch-project/dashboards-notifications@640535e#diff-6495f662f11eb9366b891c845ddac043c64b34f3a11695a2bdb0d55f58169d4cR226

That commit was included in the 2.14 release, but the corresponding PR for the Alerting UI was not (PR #916). We're getting that fix backported so it's included in the next 2.14 patch.

In the meantime, a workaround would involve creating your monitor, and then using the UpdateMonitor API (documentation link) to add an action to your trigger.

For now, I'll close this issue as the fix will be backported today; but feel free to comment if you have additional questions.