To paraphrase the documentation:
Item tcp,port checks if TCP service is running and accepting connections and returns one of the following values:
I have a check on an Amazon RDS instance (TCP port 3306) on a 60 second interval that occasionally returns a 0 status.
I'm wondering why that might be happening. I might expect to see a timeout (code 2) if the instance is REALLY busy, but generally never see a service down unless we've taken it down intentionally. Does a 0 indicate that the server actively refused the connection? Is it possible that a security feature in MySQL/RDS is seeing these connections as a threat and blocking them for a short period of time since there a connect but no data request associated with it? Can anyone recommend a good reliable health check for an RDS instance?
Thanks!
Item tcp,port checks if TCP service is running and accepting connections and returns one of the following values:
- 0 - TCP service is down
- 1 - TCP service is running
- 2 - timeout
I have a check on an Amazon RDS instance (TCP port 3306) on a 60 second interval that occasionally returns a 0 status.
I'm wondering why that might be happening. I might expect to see a timeout (code 2) if the instance is REALLY busy, but generally never see a service down unless we've taken it down intentionally. Does a 0 indicate that the server actively refused the connection? Is it possible that a security feature in MySQL/RDS is seeing these connections as a threat and blocking them for a short period of time since there a connect but no data request associated with it? Can anyone recommend a good reliable health check for an RDS instance?
Thanks!