Hi, flyte team. I would like to ask a question about notification email. I have setup notification in values.yaml and build SQS & SNS in aws. I have checked logs that it is publishing message but it did not arriave in my mail box. would anyone can give some advice?

2022/08/18 08:08:18 /go/src/github.com/flyteorg/flyteadmin/pkg/repositories/gormimpl/execution_repo.go:61
[21.243ms] [rows:1] UPDATE "executions" SET "id"=358,"created_at"='2022-08-18 08:05:44.14',"updated_at"='2022-08-18 08:08:18.501',"execution_project"='flytesnacks',"execution_domain"='development',"execution_name"='f985b6eddf4c43d5f000',"launch_plan_id"=114,"workflow_id"=106,"phase"='SUCCEEDED',"closure"='<binary>',"spec"='<binary>',"started_at"='2022-08-18 08:05:49.251',"execution_created_at"='2022-08-18 08:05:44.139',"execution_updated_at"='2022-08-18 08:08:18.497',"duration"='2m29.245844975s',"mode"=1,"inputs_uri"='<s3://my-s3-bucket/metadata/flytesnacks/development/f985b6eddf4c43d5f000/inputs>',"user_inputs_uri"='<s3://my-s3-bucket/metadata/flytesnacks/development/f985b6eddf4c43d5f000/user_inputs>',"user"='a57ebf23-a6e8-45e7-bcb1-52b69f508f67',"state"=0 WHERE "execution_project" = 'flytesnacks' AND "execution_domain" = 'development' AND "execution_name" = 'f985b6eddf4c43d5f000'
{"json":{"exec_id":"f985b6eddf4c43d5f000","src":"execution_manager.go:1588"},"level":"debug","msg":"publishing notifications for execution [project:\"flytesnacks\" domain:\"development\" name:\"f985b6eddf4c43d5f000\" ] in state [SUCCEEDED] for notifications [[phases:SUCCEEDED email:\u003crecipients_email:\"<my email>\" \u003e ]]","ts":"2022-08-18T08:08:18Z"}
{"json":{"exec_id":"f985b6eddf4c43d5f000","src":"publisher.go:30"},"level":"debug","msg":"Publishing the following message [recipients_email:\"<my mail>\" sender_email:\"<sender mail setup in SES>\" subject_line:\"Notice: Execution \\\"flyte_fixedrate.positive_wf\\\" has succeeded in \\\"development\\\".\" body:\"Execution \\\\\\\"flyte_fixedrate.positive_wf [f985b6eddf4c43d5f000]\\\\\\\" has succeeded in \\\\\\\"development\\\\\\\". View details at \u003ca href=\\\\<http://flow.qraftpilot.com/console/projects/flytesnacks/domains/development/executions/f985b6eddf4c43d5f000>\u003e http://<flyte url>/console/projects/flytesnacks/domains/development/executions/f985b6eddf4c43d5f000\u003c/a\u003e. \\n\" ]","ts":"2022-08-18T08:08:18Z"}



{"json":{"exec_id":"faf3d92fb8453e24d000","node":"n0","src":"noop_notifications.go:32"},"level":"debug","msg":"call to noop publish with notification type [flyteidl.admin.NodeExecutionEventRequest] and proto message [event:\u003cid:\u003cnode_id:\"n0\" execution_id:\u003cproject:\"flytesnacks\" domain:\"development\" name:\"faf3d92fb8453e24d000\" \u003e \u003e producer_id:\"propeller\" phase:SUCCEEDED occurred_at:\u003cseconds:1660810338 nanos:222102672 \u003e input_uri:\"<s3://my-s3-bucket/metadata/propeller/flytesnacks-development-faf3d92fb8453e24d000/n0/data/inputs.pb>\" output_uri:\"<s3://my-s3-bucket/metadata/propeller/flytesnacks-development-faf3d92fb8453e24d000/n0/data/0/outputs.pb>\" task_node_metadata:\u003c\u003e spec_node_id:\"n0\" node_name:\"be_positive\" event_version:1 deck_uri:\"<s3://my-s3-bucket/metadata/propeller/flytesnacks-development-faf3d92fb8453e24d000/n0/data/0/deck.html>\" \u003e ]","ts":"2022-08-18T08:12:18Z"}

thank you!

It seems to be using noop notifier. Can you check notification type value in the config and if you have set it to aws

{"json":{"exec_id":"faf3d92fb8453e24d000","node":"n0","src":"noop_notifications.go:32"},"level":"debug","msg":"call to noop publish with notification type [flyteidl.admin.NodeExecutionEventRequest]

This is the setup my team did below.

workflow_notifications:

    # enabled: false

    enabled: true

    config:

      notifications:

        type: aws

        region: "ap-northeast-2"

        publisher:

          topicName: "arn:aws:sns:ap-northeast-2:<account ID>:<sns name>"

        processor:

          queueName: "<sqs name>"

          accountId: "account id"

        emailer:

          subject: "Notice: Execution \"{{ workflow.name }}\" has {{ phase }} in \"{{ domain }}\"."

          sender:  "<ses vertified mail>"

          body: >

            Execution \"{{ workflow.name }} [{{ name }}]\" has {{ phase }} in \"{{ domain }}\". View details at

            <a href=\http://<flyte url>/console/projects/{{ project }}/domains/{{ domain }}/executions/{{ name }}>

            http://<flyte url>/console/projects/{{ project }}/domains/{{ domain }}/executions/{{ name }}</a>. {{ error }}

hmm that looks ok. can you verify this by checking the same on the admin configmap .

kubectl get configmap -n <flyte-name-space> flyte-admin-base-config -o yaml

this is the configmap settings

notifications.yaml: |
    notifications:
      emailer:
        body: |
          Execution \"{{ workflow.name }} [{{ name }}]\" has {{ phase }} in \"{{ domain }}\". View details at
          <a href=\http://<flyte  url>/console/projects/{{ project }}/domains/{{ domain }}/executions/{{ name }}>
          http://<flyte url>/console/projects/{{ project }}/domains/{{ domain }}/executions/{{ name }}</a>. {{ error }}
        sender: <ses vertified mail>
        subject: 'Notice: Execution "{{ workflow.name }}" has {{ phase }} in "{{ domain
          }}".'
      processor:
        accountId: "account id"
        queueName: <sqs name>
      publisher:
        topicName: arn:aws:sns:ap-northeast-2:<account id>:<sns name>
      region: ap-northeast-2
      type: aws

Ok looks correct . After adding this change did you restart the flyteadmin pod . Also you can grep this for me in the flyteadmin pods

Using default noop notifications processor implementation for config type

Hi, I am colleague of @gifted-house-14547 and am answering your question on the behalf of him. There is no message says that it is going to use noop notifications processor. Below is my grepped log.

(base) qraft@ai-server0:~/k8s/temp$ k logs -n flyte flyteadmin-cc87d6cf6-dxhn6 | grep noop
{"json":{"src":"factory.go:104"},"level":"info","msg":"Using default noop workflow executor implementation for cloud provider type [local]","ts":"2022-08-18T10:31:14Z"}
{"json":{"exec_id":"f4648f22385a18194000","src":"noop_notifications.go:32"},"level":"debug","msg":"call to noop publish with notification type [flyteidl.admin.WorkflowExecutionEventRequest] and proto message [event:\u003cexecution_id:\u003cproject:\"flytesnacks\" domain:\"development\" name:\"f4648f22385a18194000\" \u003e producer_id:\"propeller\" phase:RUNNING occurred_at:\u003cseconds:1660818728 nanos:781959937 \u003e \u003e ]","ts":"2022-08-18T10:32:08Z"}

Logs indicate that it’s somehow reading the type as local . Do you mind restarting the admin pod and grepping for same string

I have checked the notification 10 minutes ago, there is aws_processor and it's working now. Do I have set additional things up in AWS (SNS or SQS)?

cool . i believe this was after the restart that it got the right config . Are you still not receiving the email notification .

No, I haven't. So I consider where I have setup additional things in AWS

Can you share the updated logs from admin

here is the logs with grepping my mail

> k logs -n flyte flyteadmin-6f5c568d57-2x68w | grep <mailto:seungtae.kim@qraftec.com|seungtae.kim@qraftec.com>
{"json":{"exec_id":"f2ede5902d2074e73000","src":"publisher.go:30"},"level":"debug","msg":"Publishing the following message [recipients_email:\"<my mail>\" sender_email:\"<ses vertified mail>\" subject_line:\"Flyte: 'examples.flyte_fixedrate.positive_wf' has succeeded in 'development'.\" body:\"Execution 'examples.flyte_fixedrate.positive_wf [f2ede5902d2074e73000]' has succeeded in 'development'. View details at\\n\u003ca href=\\\\http://<flyte url>/console/projects/flytesnacks/domains/development/executions/f2ede5902d2074e73000\u003e\\nhttp://<flyte url>/console/projects/flytesnacks/domains/development/executions/f2ede5902d2074e73000\u003c/a\u003e. \\n\" ]","ts":"2022-08-19T06:03:47Z"}
{"json":{"exec_id":"fbde63dfdd160676a000","src":"execution_manager.go:1602"},"level":"debug","msg":"publishing notifications for execution [project:\"flytesnacks\" domain:\"development\" name:\"fbde63dfdd160676a000\" ] in state [SUCCEEDED] for notifications [[phases:SUCCEEDED email:\u003crecipients_email:\"<my mail>\" \u003e ]]","ts":"2022-08-19T06:13:47Z"}

Can you paste more info without grepping around that time period

oh, my team leader has restarted flyteadmin pod for notification debugging... I will send back soon

Error from server (BadRequest): container "flyteadmin" in pod "flyteadmin-6f64bf5bc5-r7m8f" is waiting to start: PodInitializing

Its still calling into noop processor. Could you share the entire log this for admin from the start because earlier you shared a log with aws_processor being registered. Did the config get reverted?

# -- Resource manager configuration
  resource_manager:
    # -- resource manager configuration
    propeller:
      resourcemanager:
        type: noop

should I change this type into aws in values.yaml?

yes

Nope, nothing reverted, my team just restarted flyteadmin pod

this is the configmap settings

```notifications.yaml: |

notifications:

emailer:

body: |

Execution \"{{ workflow.name }} [{{ name }}]\" has {{ phase }} in \"{{ domain }}\". View details at

<a href=\http://<flyte url>/console/projects/{{ project }}/domains/{{ domain }}/executions/{{ name }}>

http://<flyte url>/console/projects/{{ project }}/domains/{{ domain }}/executions/{{ name }}</a>. {{ error }}

sender: <ses vertified mail>

subject: 'Notice: Execution "{{ workflow.name }}" has {{ phase }} in "{{ domain

}}".'

processor:

accountId: "account id"

queueName: <sqs name>

publisher:

topicName: arnawssnsap northeast 2<account id>:<sns name>

region: ap-northeast-2

type: aws```

This was the config you shared earlier which looked correct . Can you check you notifications config , the one you shared now is from resourcemanager

That setting is perfectly same you shared

I have one question, below log says that I have cloud provider type 'local', and I think it's correct because I am using 'on premise' cluster. However, I want to use aws notifications even though I am on a local cluster. Is this related to anything caused not to send emails? Thanks.

{
  "json": {
    "src": "factory.go:104"
  },
  "level": "info",
  "msg": "Using default noop workflow executor implementation for cloud provider type [local]",
  "ts": "2022-08-19T07:33:01Z"
}

This one comes from different part of the configmap . Its part of workflowExecutor module and not notifications eg :

workflowExecutor:
    scheme: local
    local:

You can specify a different scheme for each module. In case of notifications its defined with type field. Can we debug this through a call since we went back and forth on this

The previous problem was there was no policy attached to the aws sns topic to send messages to sqs queue, and it is sending messages. However, now, there are logs saying that flyteadmin cannot unmarshall JSON message. My logs following below.

{
  "json": {
    "src": "aws_processor.go:52"
  },
  "level": "error",
  "msg": "failed to unmarshall JSON message [ChhzZXVuZ3RhZS5raW1AcXJhZnRlYy5jb20SEW1sb3BzQHFyYWZ0ZWMuY29tGk1GbHl0ZTogJ2V4YW1wbGVzLmZseXRlX2ZpeGVkcmF0ZS5wb3NpdGl2ZV93ZicgaGFzIHN1Y2NlZWRlZCBpbiAnZGV2ZWxvcG1lbnQnLiLgAkV4ZWN1dGlvbiAnZXhhbXBsZXMuZmx5dGVfZml4ZWRyYXRlLnBvc2l0aXZlX3dmIFtmZWUyMmVjZDM2MDE4NWMzZDAwMF0nIGhhcyBzdWNjZWVkZWQgaW4gJ2RldmVsb3BtZW50Jy4gVmlldyBkZXRhaWxzIGF0CjxhIGhyZWY9XGh0dHA6Ly9mbG93LnFyYWZ0cGlsb3QuY29tL2NvbnNvbGUvcHJvamVjdHMvZmx5dGVzbmFja3MvZG9tYWlucy9kZXZlbG9wbWVudC9leGVjdXRpb25zL2ZlZTIyZWNkMzYwMTg1YzNkMDAwPgpodHRwOi8vZmxvdy5xcmFmdHBpbG90LmNvbS9jb25zb2xlL3Byb2plY3RzL2ZseXRlc25hY2tzL2RvbWFpbnMvZGV2ZWxvcG1lbnQvZXhlY3V0aW9ucy9mZWUyMmVjZDM2MDE4NWMzZDAwMDwvYT4uIAo=] from processor with err: invalid character 'C' looking for beginning of value",
  "ts": "2022-08-22T08:48:26Z"
}

Because I saw there was an option in

flyteadmin/pkg/async/notifications/factory.go

which is

enable64decoding

, I changed it to false but no luck. Strange thing is the message is entirely encoded in base64, but the

flyteadmin

expects it to be JSON formatted at first, and then later it decodes messages using base64.

Can you check one thing for me . What is the value of

Raw message delivery

on the sqs subscription from sns topic

interesting, do we capture this in the docs that we should not enable raw message delivery?

Nope we dont have this mentioned but wanted to confirm that is indeed the case

@icy-agent-73298 many thanks to help me and @astonishing-whale-4005 to solve notification problem. We finally solve the issue now and it works successfully. there was user's access policy issue in IAM.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "VisualEditor0",
      "Effect": "Allow",
      "Action": "sqs:*",
      "Resource": "*"
    },
    {
      "Sid": "VisualEditor1",
      "Effect": "Allow",
      "Action": "sns:*",
      "Resource": "arn:aws:sns:<aws region>:<account>:<sns service name>"
    },
    {
      "Sid": "VisualEditor2",
      "Effect": "Allow",
      "Action": "ses:*",
      "Resource": "*"
    }
  ]
}

we have checked SNS & SQS work without problems before, but don't know why emails not arrived. I think the policy setting should be added in this docs, https://docs.flyte.org/projects/cookbook/en/latest/auto/deployment/lp_notifications.html Thank you!

Would you be able to help with doc contribution for this .that would really help the community . Also did you need to disable raw message delivery

yeah, we have deactivated raw message delivery, the email comes without any base64 values

Cool would be great if you can mention this also in the doc contribution along with the gaps you saw.

I have more better idea of notification with Grafana alert rule. prometheus collects metrics of flyte, which means grafana checks each pod's status and if pod status becomes pending, failure, or completed, we can send mail through grafana. I think this is the easiest way to send email.

Yeah thats also easier if you don’t want to setup notification infra . cc : @acceptable-policeman-57188 to check if these metrics can be relied on for notification or can they be lossy .