[GH-ISSUE #681] When an action is executed, no alert is sent. #6252

New Issue

GiteaMirror · 2026-04-24T19:24:01-05:00

GiteaMirror commented

2026-04-24 19:24:01 -05:00

Originally created by @Razdnut on GitHub (Jul 24, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/681

I set two Actions to be executed at set times, and they were indeed executed.

However, although I set an alert to be sent, it did not go off.

Details

Originally created by @Razdnut on GitHub (Jul 24, 2025). Original GitHub issue: https://github.com/moghtech/komodo/issues/681 I set two Actions to be executed at set times, and they were indeed executed. However, although I set an alert to be sent, it did not go off. <details><summary>Details</summary> <p> <img width="360" height="104" alt="Image" src="https://github.com/user-attachments/assets/861c1001-5672-4812-8fdc-9b45c6690d4c" /> </p> </details>

GiteaMirror added the seen 👀 label 2026-04-24 19:24:01 -05:00

GiteaMirror closed this issue

2026-04-24 19:24:03 -05:00

GiteaMirror commented

2026-04-24 19:24:04 -05:00

@mbecker20 commented on GitHub (Jul 24, 2025):

What is your alerter configuration?

@mbecker20 commented on GitHub (Jul 24, 2025): What is your alerter configuration?

GiteaMirror commented

2026-04-24 19:24:05 -05:00

@Razdnut commented on GitHub (Jul 24, 2025):

What is your alerter configuration?

 [[alerter]] 
name = "ntfy" 
[alerter.config] 
enabled = true 
endpoint.type = "Ntfy"
endpoint.params.url = "https://redacted.tld/"
alert_types = [
  "ServerUnreachable",
  "ServerMem",
  "StackStateChange",
  "ServerDisk",
  "StackImageUpdateAvailable",
  "StackAutoUpdated",
  "ContainerStateChange",
  "DeploymentImageUpdateAvailable",
  "DeploymentAutoUpdated",
  "AwsBuilderTerminationFailed",
  "ResourceSyncPendingUpdates",
  "BuildFailed",
  "RepoBuildFailed"
]

For now I have bypassed the problem by creating a function that performs a POST directly to NTFY in the Actions:

Details

async function sendNtfyNotification(message: string): Promise<void> {
  const endpoint = 'https://redacted.tld';
  try {
    const res = await fetch(endpoint, {
      method: 'POST',
      headers: { 'Content-Type': 'text/plain' },
      body: message,
    });

@Razdnut commented on GitHub (Jul 24, 2025): > What is your alerter configuration? ```python [[alerter]] name = "ntfy" [alerter.config] enabled = true endpoint.type = "Ntfy" endpoint.params.url = "https://redacted.tld/" alert_types = [ "ServerUnreachable", "ServerMem", "StackStateChange", "ServerDisk", "StackImageUpdateAvailable", "StackAutoUpdated", "ContainerStateChange", "DeploymentImageUpdateAvailable", "DeploymentAutoUpdated", "AwsBuilderTerminationFailed", "ResourceSyncPendingUpdates", "BuildFailed", "RepoBuildFailed" ] ``` For now I have bypassed the problem by creating a function that performs a POST directly to NTFY in the Actions: <details><summary>Details</summary> <p> ```typescript async function sendNtfyNotification(message: string): Promise<void> { const endpoint = 'https://redacted.tld'; try { const res = await fetch(endpoint, { method: 'POST', headers: { 'Content-Type': 'text/plain' }, body: message, }); ``` </p> </details>

GiteaMirror commented

2026-04-24 19:24:06 -05:00

@mbecker20 commented on GitHub (Jul 25, 2025):

Ok I see this issue. Your alerter is missing the "ActionFailed" alert type. You didn't miss it though, this option was forgotten to be added to the UI configuration. I already fixed it here: 6c3b7cc30b

This will be included in the next release. In the meantime it looks like you are trying to add all alert types. If this is what you want, you can remove every entry in the "Alert types" list. If it is empty, it will allow through all alert types, including "ActionFailed".

If you prefer to keep enumerated list of specific alert types including "ActionFailed", you can also fix it now by adding "ActionFailed" to resource toml for the [alerter] above, and using Resource Sync.

@mbecker20 commented on GitHub (Jul 25, 2025): Ok I see this issue. Your alerter is missing the "ActionFailed" alert type. You didn't miss it though, this option was forgotten to be added to the UI configuration. I already fixed it here: https://github.com/moghtech/komodo/commit/6c3b7cc30b681d4a70dcd04a7eb30c7754eacf5e This will be included in the next release. In the meantime it looks like you are trying to add all alert types. If this is what you want, you can remove every entry in the "Alert types" list. If it is empty, it will allow through all alert types, including "ActionFailed". If you prefer to keep enumerated list of specific alert types including "ActionFailed", you can also fix it now by adding "ActionFailed" to resource toml for the [alerter] above, and using Resource Sync.

GiteaMirror commented

2026-04-24 19:24:07 -05:00

@mbecker20 commented on GitHub (Jul 25, 2025):

Just reread, actually the Alert Type you want is "ScheduleRun". For some reason I thought it was "ActionFailed". But I think you will want both added anyways. Maybe "ProcedureFailed" too. These three were all missing to configure from UI but it will be fixed in next release.

@mbecker20 commented on GitHub (Jul 25, 2025): Just reread, actually the Alert Type you want is "ScheduleRun". For some reason I thought it was "ActionFailed". But I think you will want both added anyways. Maybe "ProcedureFailed" too. These three were all missing to configure from UI but it will be fixed in next release.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/komodo#6252