Finer control over Slack messaging

Comments

2 comments

  • Avatar
    Art van Scheppingen

    Hi Kent,

    Thank you very much for the suggested improvements! I will have to look in what is feasible and if all the information is available through the cmon api, so I'll follow up on that.

    About the status updates on the backup: when we designed the backup scheduling in CCBot it is supposed to keep the users updated by sending status updates until it is done. I'll have a look at why it isn't sending messages then.

    Best regards,

    Art

  • Avatar
    Art van Scheppingen

    Hi Kent,

    I managed to track down the issue regarding backup notifications: there was a bug in the token handling in that routine so it never was able to retrieve the job status.

    I have made naming of the clusters in any output consistent:

    New job (818) has been scheduled on cluster 3 (MySQL Replication): backup (DEFINED)
    Finished job 818 on cluster 3 (MySQL Replication)10.10.16.11: Backup 28 completed and stored in '10.10.16.11:/vagrant/BACKUP-28/backup-full-2016-05-02_135905.xbstream.gz'.

    In this case the cluster identifier is 3 and the cluster name is "MySQL Replication".

    Unfortunately the cmon backend does not provide any details on the backup, so we can't provide more details on the backup via Hubot at the moment. We'll investigate options here.

    For now you can grab the latest version at Github:

    https://github.com/severalnines/ccbot/

    Best regards,

    Art

Please sign in to leave a comment.

Powered by Zendesk