Monitor non-http services

[guillaumemeyer]

Many services are providing non-http healthcheck methods, such as:

• Redis
• Postgres

It would be a nice addition to be able to monitor these services. Looks like it could be an extension of the TCP probes...

[dennypradipta]

Yeah, I've seen other services such as EaseProbe that could check MySQL/MongoDB/Redis/Postgres status. I think it's a nice idea

[guillaumemeyer]

Got a few questions regarding Redis probes...

How to include the id or the name of the probe in the alert message?
I have a probe defined as:

  - id: redis
    name: Redis
    description: Redis
    interval: 1
    incidentThreshold: 1
    recoveryThreshold: 3
    redis:
      - host: $REDIS_HOST
        port: $REDIS_PORT
        password: $REDIS_PASSWORD
    alerts:
      - assertion: response.time > 500 # in milliseconds
        message: Redis response is slow, took {{ response.time }}ms

When the response time is exceeded, the message includes "Redis" as it's defined. But when another error occurs, such as "connect ECONNREFUSED", the error message send by email is just "Host cannot be reached", without any indication of the probe that failed...

How to specify to use TLS for Redis connection?
My suggestion would be to support a uri property (just like postgres) to specify a full connection string, from which we could specify redis: or rediss: as a prefix to enable/disable TLS connection.

[guillaumemeyer]

Another question for Postgres... I can't make it work with servers that have ssl enabled (Such as Azure by default).
Tried different connection string formats, but it looks like the sslmode parameter is ignored:

- uri: "postgresql://$DB_APPLICATION_USER:$DB_APPLICATION_PASSWORD@$DB_APPLICATION_HOST:$DB_APPLICATION_PORT/$DB_APPLICATION_DATABASE_NAME?ssl=true&sslmode=$DB_APPLICATION_SSL_MODE"
- uri: "postgresql://$DB_APPLICATION_HOST:$DB_APPLICATION_PORT/$DB_APPLICATION_DATABASE_NAME?sslmode=$DB_APPLICATION_SSL_MODE&user=$DB_APPLICATION_USER&password=$DB_APPLICATION_PASSWORD"

Returns msg:SSL connection is required. Please specify SSL options and retry.

[sapiderman]

Hi @guillaumemeyer,

Thanks for all the feedbacks, much appreciated. Let me try to address them.
About the SSL, right now all connections to the database are plain vanilla. Support to transparantly add options are on the roadmap. Likewise we'll take a look at redis connections too. We'll let you know!

[sapiderman]

For the missing info on redis, we've created a ticket #962. Fixing it ASAP.

[guillaumemeyer]

Hi, any update about Postgres?