How to delete the sensu client from being monitered using Sensu API and How to add again using API


#1

I am deleting the sensu-client using API as Below

curl -s -i -X DELETE http://xxxxxxxx:4567/clients/clientname

HTTP/1.1 202 Accepted

Access-Control-Allow-Credentials: true

Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept, Authorization

Access-Control-Allow-Methods: GET, POST, PUT, DELETE, OPTIONS

Access-Control-Allow-Origin: *

Connection: close

Content-length: 21

Content-type: application/json

{“issued”:1472737806}

But still I am able to see the client in UCHIWA and see the logs being generated …

Whats the issue here?

Can someone suggest me how to remove client using sensu API and add it again using Sensu API


#2

As long as a Sensu client is running it will send client keepalives on a 20-second interval. When the Sensu server receives a client keepalive for a client that is not in the client registry it automatically creates a new client. This could explain why a client you have deleted via the API is restored.

I hope this helps!

···

On Thursday, September 1, 2016 at 7:00:19 AM UTC-7, IMRAN SHAIK wrote:

I am deleting the sensu-client using API as Below

curl -s -i -X DELETE http://xxxxxxxx:4567/clients/clientname

HTTP/1.1 202 Accepted

Access-Control-Allow-Credentials: true

Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept, Authorization

Access-Control-Allow-Methods: GET, POST, PUT, DELETE, OPTIONS

Access-Control-Allow-Origin: *

Connection: close

Content-length: 21

Content-type: application/json

{“issued”:1472737806}

But still I am able to see the client in UCHIWA and see the logs being generated …

Whats the issue here?

Can someone suggest me how to remove client using sensu API and add it again using Sensu API