standalone checks not working

Sensu Classic (EOL)
1

Hi,

I’ve installed Sensu (sensu-0.20.3-1.x86_64) on a CentOS 7 virtual machine for a proof of concept and everything is working fine, except of standalone checks, which are not executed from the clients.

This is my client configuration:
“client”: {
“name”: “server”,
“address”: “192.168.1.12”,
“memory”: {
“warning”: 15000,
“critical”: 14500
},
“subscriptions”: ,
“checks”: {
“memory”: {
“command”: “/etc/sensu/plugins/check-memory.sh -w :::memory.warning|70::: -c :::memory.critical|80:::”,
“standalone”: true,
“interval”: 15
}
}
}

``

Anyone with idea’s how to get this working?

Thanks,
Robert

2

"checks" needs to go top namespace of the dictionary. They should not
be in the client configuration:
https://sensuapp.org/docs/latest/checks#example-check-definition

(I recommend a separate file, configuration management usually sets up
one config file per check)

{
  "client": {
    "name": "server",
    "address": "192.168.1.12",
    "memory": {
      "warning": 15000,
      "critical": 14500
    },
    "subscriptions": ,
  },
  "checks": {
    "memory": {
      "command": "/etc/sensu/plugins/check-memory.sh -w
:::memory.warning|70::: -c :::memory.critical|80:::",
      "standalone": true,
      "interval": 15
    }
  }
}

···

On Sat, Oct 3, 2015 at 3:37 PM, Robert <rokn82@googlemail.com> wrote:

Hi,

I've installed Sensu (sensu-0.20.3-1.x86_64) on a CentOS 7 virtual machine
for a proof of concept and everything is working fine, except of standalone
checks, which are not executed from the clients.

This is my client configuration:
"client": {
  "name": "server",
  "address": "192.168.1.12",
  "memory": {
    "warning": 15000,
    "critical": 14500
  },
  "subscriptions": ,
  "checks": {
    "memory": {
      "command": "/etc/sensu/plugins/check-memory.sh -w
:::memory.warning|70::: -c :::memory.critical|80:::",
      "standalone": true,
      "interval": 15
    }
  }
}

Anyone with idea's how to get this working?

Thanks,
Robert

3

You are right.

That’s working.

Thanks Kyle!

···

Am Sonntag, 4. Oktober 2015 20:01:14 UTC+2 schrieb Kyle Anderson:

“checks” needs to go top namespace of the dictionary. They should not
be in the client configuration:
https://sensuapp.org/docs/latest/checks#example-check-definition

(I recommend a separate file, configuration management usually sets up
one config file per check)

{
“client”: {
“name”: “server”,
“address”: “192.168.1.12”,
“memory”: {
“warning”: 15000,
“critical”: 14500
},
“subscriptions”: ,
},
“checks”: {
“memory”: {
“command”: “/etc/sensu/plugins/check-memory.sh -w
:::memory.warning|70::: -c :::memory.critical|80:::”,
“standalone”: true,
“interval”: 15
}
}
}

On Sat, Oct 3, 2015 at 3:37 PM, Robert rok...@googlemail.com wrote:

Hi,

I’ve installed Sensu (sensu-0.20.3-1.x86_64) on a CentOS 7 virtual machine
for a proof of concept and everything is working fine, except of standalone
checks, which are not executed from the clients.

This is my client configuration:
“client”: {
“name”: “server”,
“address”: “192.168.1.12”,
“memory”: {
“warning”: 15000,
“critical”: 14500
},
“subscriptions”: ,
“checks”: {
“memory”: {
“command”: “/etc/sensu/plugins/check-memory.sh -w
:::memory.warning|70::: -c :::memory.critical|80:::”,
“standalone”: true,
“interval”: 15
}
}
}

Anyone with idea’s how to get this working?

Thanks,
Robert