-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with deregister handler, api config #6
Comments
Your host definition looks strange to me, why are you putting the port into the host? https://sensuapp.org/docs/0.23/platforms/sensu-on-ubuntu-debian.html#api-standalone-configuration |
I am running Sensu API behind a loadbalancer, with LB port 45670. 10.0.0.11 is the LB IP. I guess the question is, how do I specify a port for remote API endpoint. |
@jaykumar-jnpr hi, thanks for raising this issue. The sensu-api process and the sensu-plugin handler class both rely on the Specifically, the deregistration handler uses the I understand that you are running one or more instances of the API behind a load balancer, and that the API instances are running on port 4567 while the load balancer is listening on port 45670. If it is the case that your sensu-api instances are running on the same instances as your sensu-server, I would suggest that you consider using the defaults for the api:
When the API is actually running locally, having the server route API requests through a load balancer adds complexity that may prove problematic. As HA seems to be your aim, you may want to look at configuring your sensu-api and sensu-server instances to use redis replication and sentinels for high availability. If it is not the case that your sensu-api instances run on the same machine as sensu-server, then you can continue using your existing config on the API instances and configure the sensu-server instances to target the load balancer directly, providing the load balancer host and port in the
|
closing due to inactivity |
My api config looks like following , I am running api behind a loadbalancer
{ "api": { "host": "10.0.0.11:45670", "port": 4567, "bind": "10.0.0.10" } }
Looks like deregister is not working as expected
log snippet
The text was updated successfully, but these errors were encountered: