Processors
The Elasticsearch processor can fordward execution logs to an ES cluster. It need an already available Elasticsearch installation that is visible in the same network of the target node. The output logs of the job execution will be stored in the indicated ES instace. Configuration { "processors": { "elasticsearch": { "url": "http://localhost:9200", //comma separated list of Elasticsearch hosts urls (default: http://localhost:9200) "index": "dkron_logs", //desired index name (default: dkron_logs) "forward": "false" //forward logs to the next processor (default: false) } } }
The Email processor provides flexibility to job email notifications. Configuration of the email processor is stored in a file named dkron-processor-email.yml in the same locations as dkron.yml, and should include a list of providers, it can include any number of providers. Example: provider1: host: smtp.myprovider.com port: 25 username: myusername password: mypassword from: [email protected] subjectPrefix: '[Staging] ' host and port are the minimum required parameters for provider config, and also emails for the job configuration.
The Slack processor provides slack notifications with multiple configurations and rich format. Configuration of the slack processor is stored in a file named dkron-processor-slack.yml in the same locations as dkron.yml, and should include a list of teams, it can include any number of teams. Example: team1: webhook_url: https://hooks.slack.com/services/XXXXXXXXXXXXXXXXXXX bot_name: Dkron Production Then configure each job with the following options: Example: { "processors": { "slack": { "team": "team1", "channel": "#cron-production", "onSuccess": "true" } } } By default the slack procesor doesn’t send notifications on job success, the onSuccess parameter, enables it, like in the previous example.