I’ve got all the mail settings in my config <https...
# getting-started
d
I’ve got all the mail settings in my config https://docs.meltano.com/reference/settings#mail-server but there seems to be no way to set up a subscription for an email address to receive mail notifications?
f
Its kind of in a weird spot, afaik the only subscription right now is from the run log
So if you've got a pipeline scheduled/running and you hit the popup to view the log you'll get a notify/email input at the top of the modal.
@taylor do you know if theres any other spots where we support subbing to notifications ?
t
not to my knowledge - but that’s not implying I know it all
f
@dave_lyons incase it helps, here's what it looks like
d
I see no popup
running 1.9.4 in a container
f
If you're in the pipelines tab there's a last run column, if you've had that job run before you should be able to click on the button in that column to see the log of the run.
I'm not sure if it'll be accessible if the jobs never run before
But that same log view will have a subscription input like in my screenshot if all the settings are enabled.
d
this job has run successfully already
Also what I want is notifications when a job has failed, not when the data is ready.
I have
MELTANO_UI_NOTIFICATION="true"
in my env
when building the container
f
afaik you'll get a notification on success or failure not sure if it supports alerting only on failures.
d
That’s fine, but the email input is a no-show
f
going by https://docs.meltano.com/reference/settings#uinotification you might need both
Copy code
export MELTANO_UI_NOTIFICATION=true
export MELTANO_NOTIFICATION=true
haven't messed with it since i first set it up but fwiw - i have both in my env.
d
Is the tl;dr here basically that mail notifications is more of a WIP than a full feature?
I’ve set both
Copy code
MELTANO_NOTIFICATION="true"
MELTANO_UI_NOTIFICATION="true"
in my
.env
and still no subscription option
tried it running locally and not in a container and same thing
are mail notifications supported for all connectors? this is with a PostgreSQL extractor.
@florian.hines @taylor I see a subscriptions table in my Meltano DB, could I just
Copy code
INSERT INTO subscriptions(id,recipient,event_type,source_type,source_id,created_at) values (1, '<mailto:me@email.me|me@email.me>', 'pipeline', 'postgres', 'job_id', current_timestamp())
or something like that?
f
Is the tl;dr here basically that mail notifications is more of a WIP than a full feature?
yea, thats probably fair to say - I'm not sure if email notifications are getting much use or where they're at on the roadmap (/cc @taylor ). wyea thats probably fair to say,
Honestly not sure why you're not see'ing that field , its not limited to specific extractors.
d
ok I finally got the field but only running locally, it wasn’t working in the docker container
f
If you're feeling adventurous you could try hitting the API endpoint , might be a bit safer than just inserting it straight into the db.
d
Where’s the API endpoint documented? Missed that one.
f
You didn't miss it 😁 afaik, theres no api docs - but most of the endpoints are under orchestrations path and live in: https://gitlab.com/meltano/meltano/-/blob/master/src/meltano/api/controllers/orchestrations.py
..but its a little...rough...theres no documented payloads/responses either 😕
d
gotcha - that’s helpful.
So if I want notifications for a job that has yet to successfully complete a run even once… I should probably either hit the API or insert a new row with SQL. The button worked and I have an example row to work from now, so that’s something.
And I guess it would be presumptuous to ask about Slack notifications being close on the roadmap?
The email I finally received, by the way, got rejected by sendgrid because:
Copy code
A message was received from this address by our systems that had errors in the SMTPAPI header, and cannot be processed due to the following:

  - The ASM group ID must be a valid group id on your account. You provided 12751
How is Meltano constructing the header and getting this group ID?
@taylor @florian.hines
t
Sorry for the delay @dave_lyons - we’ve been in some meetings. I’ll say for now that Slack notifications and email-related updates are not on the near term roadmap. Thank you for opening the issue though - I’ll get it labelled and triaged appropriately
d
ty!