Switch from slackbot to email from desi cluster. #177
Conversation
|
I have tested email to slack from |
| # Post it. | ||
| slackerror=$(curl -X POST -H 'Content-type: application/json' --data "$(cat ${slackjson})" ${slack_web_hook}) | ||
| echo "Slack API post ${slackerror}" >> "${logfile}" | ||
| cat ${logfile} | mailx -s "Focalplane sync: ${logdate}" ${slack_email} |
There was a problem hiding this comment.
Are you concerned about the cumulative file sizes being posted to slack (rather than a snippet showing pass/fail and the path of the full log)? Not sure if there are any constraints to worry about.
There was a problem hiding this comment.
Good point @tskisner. We're paying more attention to the contents of the messages with the full logs being sent, but the larger logs can exceed 50k in size. Before I merge the PR, I'll check to see if the cumulative effect could cause a problem in slack.
There was a problem hiding this comment.
After a conversation with @weaverba137, I think we'll send the full logs to slack for the time being. If the file size becomes an issue, we'll email an abbreviated report instead.
Inform the DESI survey-ops slack channel of the focal plane sync status using an email rather than the now-obsolete slack webhook.
Requires the environment variable
DESI_SLACK_MAIL_DESIMODEL_SYNCto be defined in the.bash_profileof thedatasystemsuser. The variable should point to the email used for survey-ops (see the channel integrations menu in slack).