Skip to content

Latest commit

 

History

History
81 lines (54 loc) · 2.4 KB

README.md

File metadata and controls

81 lines (54 loc) · 2.4 KB

#InfluxLarkbot

Description

We want to create a service that sends alert messages to a larkbot through webhook. To achieve this, we need to prepare the data to be sent as a message. We shall interact with our influxdb service and fetch data from the buckets. We clean the data and send it as a payload in a POST request to the webhook url.

Notes:

We need to control the alerts to avoid alert panic. Implement an asyncio pattern and cache influxdb results. We shall check if result in cache before sending as alarm data to bot- control rate limit. Implement celery beat to allow us control workflow run behavior.

Core Implementations

  1. Fetch data from influxdb

    • query influxdb api and pass influx query as payload
    • Call cache function

  2. Cache Function

    • Define an alarm key from influx call result
    • Check if key exists in redis db
    • If exists ignore calling sendalert function
    • If ! exists, call sendalert funtion and pass alarm message as payload

  3. SendAlert Function

    • based on cache funtion result, send POST request to webhook url
    • pass cache function result as payload

Celery Implementation

We shall use Celery as task runner and scheduler. We shall then define a celery beat to control number of runs for our workflow.

Celery Workers as Daemons

For production environment we shall set more than one worker. The workers should be daemonized so that they are started automatically at server startup.

1. create a new service definition file in /etc/systemd/system/celeryd.service
2. Create a /etc/default/celeryd configuration file
3. Create log and pid directories:

Daemonizing Celery

We need two services:
  1. Celery Beat Service
  2. Celeryd service

Create log and pid directories: sudo mkdir /var/log/celery /var/run/celery sudo chown $USER:$USER /var/log/celery /var/run/celery Reload systemctl daemon. You should run this command each time you change the service definition file.

sudo systemctl daemon-reload

Enable the services to startup at boot:

Celery Beat Service

sudo systemctl enable celeryd

Celery Beat Service

sudo systemctl enable celerybeat

Starting the services

sudo systemctl start celeryd sudo systemctl start celeryd