Pushing status of non HTTP services

[JoyceBabu]

Is it possible to push the status to the worker, for non HTTP services?

For example, I have MariaDB replication configured on a slave server, and would like to monitor it by pushing the status every few minutes.

[yunsii]

It means you want to push the status to database directly? Maybe it can be works with MariaDB client JS SDK to push data though I'm not familier with MariaDB.

[JoyceBabu]

I want to write a bash script to check the replication status, and make a HTTP request to the status page with the service status. In other words I want to push the service status to the status page, instead of the monitors retrieving it.

[JoyceBabu]

I am interested in support for non HTTP services, which will be updated directly. Currently the monitors fetch the URL for checking the service health, and log the request time. For non-http services behind a firewall, it is not possible for the status page cron job to poll the service to check its health. So, an agent on the server, running the service, should be able to update the status by calling a status page api end point.

The metric to be measured might be different for non-HTTP service. For example, for the replication service I would like to monitor the replication delay.

[yunsii]

It means you want to push a status record directly by API request. I think the best solution is creating a HTTP service to detect your DB service status?

[JoyceBabu]

It means you want to push a status record directly by API request.

That is right.

I think the best solution is creating a HTTP service to detect your DB service status?

The server is behind firewall. I cannot open a port to receive incoming connections.

[yunsii]

It occurred to me that kv namespace can be controled by RESTful API, you can directly write data with it 👌

[JoyceBabu]

That solves the issue partially.

The service monitor can only update the status when it is up, if the server is down it may not be able to do that. So if no status is received in a pre-configured period, then the service should be considered as down.

[yunsii]

If so, the related changes seems not easy. I will gradually make it happen, Also PR is welcome.

[vinnymac]

If so, the related changes seems not easy. I will gradually make it happen, Also PR is welcome.

Couldn’t we use a short (60s?) TTL to solve for this use case? If the kv store returns no value for a given key, the site can be considered down. If a value is found for the key it’s up.

Would that technique hit any usage limits on the free tier?

[yunsii]

These are two scenarios, the repo only support check status by sending a http request to service from cron worker for now. I will try to implement a new approach recently: receive a http request with specific TTL to determine servcie status 😀

[yunsii]

Would that technique hit any usage limits on the free tier?

It seems that no limit for receive http request refer to Limits

[JoyceBabu]

I ended up writing my own status page script. Not feature complete as this project. But works for my case.

https://github.com/Ennexa/status-page