Hi there ppl
I'm facing an issue that I would like to know if that's possible to be accomplish, I remember when used to use nagios , that I could create a check and name it whatever I want, for example, I could create check name My-Domain-Check-Ping that basically would perform a ping to www.domain.com, simple as that, and then from the dashboard I could see that check, but alone only, not being a part of any other server or associated to any in particular, cuz I was running the check from the nagios server and no agent was required to do that.
Now with sensu/uchiwa I want to do the same, I created a new check name Compay-Ping-Site in a standalone fashion, no subscribers involved cuz I cannot install an agent on www.domain.com, it's an url not a client, but the problem is that I see the check being part of the sensu server itself along with the other checks related to the server, I want to see the check in the client list, separated from the sensu server that is running the check, if I want to see the check I have to click on the sensu-server, which is the client name I assigned to it, and I do not want that.
Is that possible? did my self clear?
Thanks
Regareds
Yes, the concept in sensu is called “Proxy Clients”:
https://sensuapp.org/docs/latest/reference/clients.html#proxy-clients
but just like nagios they still have to “run” somewhere. Often for this use-case they run on the sensu server(s). Read the docs and you will see you simply need to set:
source: www.domain.com
In the check onfiguration.
···
On Wed, Apr 26, 2017 at 1:24 PM, Net Warrior netwarrior863@gmail.com wrote:
Hi there ppl
I’m facing an issue that I would like to know if that’s possible to be accomplish, I remember when used to use nagios , that I could create a check and name it whatever I want, for example, I could create check name My-Domain-Check-Ping that basically would perform a ping to www.domain.com, simple as that, and then from the dashboard I could see that check, but alone only, not being a part of any other server or associated to any in particular, cuz I was running the check from the nagios server and no agent was required to do that.
Now with sensu/uchiwa I want to do the same, I created a new check name Compay-Ping-Site in a standalone fashion, no subscribers involved cuz I cannot install an agent on www.domain.com, it’s an url not a client, but the problem is that I see the check being part of the sensu server itself along with the other checks related to the server, I want to see the check in the client list, separated from the sensu server that is running the check, if I want to see the check I have to click on the sensu-server, which is the client name I assigned to it, and I do not want that.
Is that possible? did my self clear?
Thanks
Regareds
Hi
I updated to sensu 0.29 and configured an alert like this:
{
“checks”: {
“Company-Site-Check-Ping”: {
“command”: “/opt/sensu/embedded/bin/check-ping.rb -h www.company.com -c 4”,
“source”: “www.comany.com”,
“subscribers”: [ “company-site” ],
“interval”: 60,
“auto_resolve”: true,
“occurrences”: 3,
“refresh”: 1800,
“handlers”: [“email-me”]
}
}
}
I’m still seeing the check as another sensu-server check and not from the client list, am I missing something else? do I need to configure / define something else?
Thanks
Regards
···
El miércoles, 26 de abril de 2017, 22:54:39 (UTC-3), Kyle Anderson escribió:
Yes, the concept in sensu is called “Proxy Clients”:
https://sensuapp.org/docs/latest/reference/clients.html#proxy-clients
but just like nagios they still have to “run” somewhere. Often for this use-case they run on the sensu server(s). Read the docs and you will see you simply need to set:
source: www.domain.com
In the check onfiguration.
On Wed, Apr 26, 2017 at 1:24 PM, Net Warrior netwar...@gmail.com wrote:
Hi there ppl
I’m facing an issue that I would like to know if that’s possible to be accomplish, I remember when used to use nagios , that I could create a check and name it whatever I want, for example, I could create check name My-Domain-Check-Ping that basically would perform a ping to www.domain.com, simple as that, and then from the dashboard I could see that check, but alone only, not being a part of any other server or associated to any in particular, cuz I was running the check from the nagios server and no agent was required to do that.
Now with sensu/uchiwa I want to do the same, I created a new check name Compay-Ping-Site in a standalone fashion, no subscribers involved cuz I cannot install an agent on www.domain.com, it’s an url not a client, but the problem is that I see the check being part of the sensu server itself along with the other checks related to the server, I want to see the check in the client list, separated from the sensu server that is running the check, if I want to see the check I have to click on the sensu-server, which is the client name I assigned to it, and I do not want that.
Is that possible? did my self clear?
Thanks
Regareds
Have you restarted sensu-client and sensu-server, possibly also sensu-api?
···
On Thursday, April 27, 2017 at 5:30:52 PM UTC+2, Kernel Panic wrote:
{
“checks”: {
“Company-Site-Check-Ping”: {
“command”: “/opt/sensu/embedded/bin/check-ping.rb -h www.company.com -c 4”,
“source”: “www.comany.com”,
“subscribers”: [ “company-site” ],
“interval”: 60,
“auto_resolve”: true,
“occurrences”: 3,
“refresh”: 1800,
“handlers”: [“email-me”]
}
}
}
I’m still seeing the check as another sensu-server check and not from the client list, am I missing something else? do I need to configure / define something else?
Yes of course, the check is being part of the server itself.
Thanks!
···
On 04/27/2017 01:59 PM, Alexander Skiba wrote:
On Thursday, April 27, 2017 at 5:30:52 PM UTC+2, Kernel Panic wrote:
{
"checks": {
"Company-Site-Check-Ping": {
"command": "/opt/sensu/embedded/bin/check-ping.rb -h
www.company.com <http://www.company.com> -c 4",
"source": "www.comany.com <http://www.comany.com>",
"subscribers": [ "company-site" ],
"interval": 60,
"auto_resolve": true,
"occurrences": 3,
"refresh": 1800,
"handlers": ["email-me"]
}
}
}
I'm still seeing the check as another sensu-server check and not
from the client list, am I missing something else? do I need to
configure / define something else?
Have you restarted sensu-client and sensu-server, possibly also sensu-api?
Now, looking at the uchiwa dashboad, I noticed that the alert just triggered once, 7 hour ago!!! when I created it. maybe it's because I did not set the standalone to true?
Apart from that, it seems shat subscribers is mandatory, so in this case company-site is not defined anywhere else, do I have to configure a fake subscription?
Thanks
Regard
···
On 04/27/2017 01:59 PM, Alexander Skiba wrote:
On Thursday, April 27, 2017 at 5:30:52 PM UTC+2, Kernel Panic wrote:
{
"checks": {
"Company-Site-Check-Ping": {
"command": "/opt/sensu/embedded/bin/check-ping.rb -h
www.company.com <http://www.company.com> -c 4",
"source": "www.comany.com <http://www.comany.com>",
"subscribers": [ "company-site" ],
"interval": 60,
"auto_resolve": true,
"occurrences": 3,
"refresh": 1800,
"handlers": ["email-me"]
}
}
}
I'm still seeing the check as another sensu-server check and not
from the client list, am I missing something else? do I need to
configure / define something else?
Have you restarted sensu-client and sensu-server, possibly also sensu-api?
Good news,
Addit the standalone to true did the trick, now I can see the check as another client name in the list!!! , but in the IP address field I have unknown and instead of having "a few seconds ago" in the last checks field I have, invalid date... any idea why is that?
Thank you!
Regards
···
On 04/27/2017 01:59 PM, Alexander Skiba wrote:
On Thursday, April 27, 2017 at 5:30:52 PM UTC+2, Kernel Panic wrote:
{
"checks": {
"Company-Site-Check-Ping": {
"command": "/opt/sensu/embedded/bin/check-ping.rb -h
www.company.com <http://www.company.com> -c 4",
"source": "www.comany.com <http://www.comany.com>",
"subscribers": [ "company-site" ],
"interval": 60,
"auto_resolve": true,
"occurrences": 3,
"refresh": 1800,
"handlers": ["email-me"]
}
}
}
I'm still seeing the check as another sensu-server check and not
from the client list, am I missing something else? do I need to
configure / define something else?
Have you restarted sensu-client and sensu-server, possibly also sensu-api?
The IP address is taken from the client. Since you don’t have a “real” client but a proxy client, there is no IP address available from the client definition.
I don’t know why you would get invalid date. (maybe check if all the machines connected have NTP running and syncing their time properly?)
···
On Thursday, April 27, 2017 at 9:20:52 PM UTC+2, Kernel Panic wrote:
Good news,
Addit the standalone to true did the trick, now I can see the check as
another client name in the list!!! , but in the IP address field I have
unknown and instead of having “a few seconds ago” in the last checks
field I have, invalid date… any idea why is that?
Thank you!
Regards
On 04/27/2017 01:59 PM, Alexander Skiba wrote:
On Thursday, April 27, 2017 at 5:30:52 PM UTC+2, Kernel Panic wrote:
{
"checks": {
"Company-Site-Check-Ping": {
"command": "/opt/sensu/embedded/bin/check-ping.rb -h
[www.company.com](http://www.company.com) <[http://www.company.com](http://www.company.com)> -c 4",
"source": "[www.comany.com](http://www.comany.com) <[http://www.comany.com](http://www.comany.com)>",
"subscribers": [ "company-site" ],
"interval": 60,
"auto_resolve": true,
"occurrences": 3,
"refresh": 1800,
"handlers": ["email-me"]
}
}
}
I'm still seeing the check as another sensu-server check and not
from the client list, am I missing something else? do I need to
configure / define something else?
Have you restarted sensu-client and sensu-server, possibly also
sensu-api?
Yes, but default we have NTP configured on all server, I also added "address": ip-address to the check, but just did nothing.
Thanks
Regards
···
On 04/28/2017 10:41 AM, Alexander Skiba wrote:
The IP address is taken from the client. Since you don't have a "real" client but a proxy client, there is no IP address available from the client definition.
I don't know why you would get invalid date. (maybe check if all the machines connected have NTP running and syncing their time properly?)
On Thursday, April 27, 2017 at 9:20:52 PM UTC+2, Kernel Panic wrote:
Good news,
Addit the standalone to true did the trick, now I can see the
check as
another client name in the list!!! , but in the IP address field I
have
unknown and instead of having "a few seconds ago" in the last checks
field I have, invalid date... any idea why is that?
Thank you!
Regards
On 04/27/2017 01:59 PM, Alexander Skiba wrote:
>
> On Thursday, April 27, 2017 at 5:30:52 PM UTC+2, Kernel Panic > wrote:
>
> {
> "checks": {
> "Company-Site-Check-Ping": {
> "command": "/opt/sensu/embedded/bin/check-ping.rb -h
> www.company.com <http://www.company.com>
<http://www.company.com> -c 4",
> "source": "www.comany.com <http://www.comany.com>
<http://www.comany.com>",
> "subscribers": [ "company-site" ],
> "interval": 60,
> "auto_resolve": true,
> "occurrences": 3,
> "refresh": 1800,
> "handlers": ["email-me"]
> }
> }
> }
>
> I'm still seeing the check as another sensu-server check and
not
> from the client list, am I missing something else? do I need to
> configure / define something else?
>
> Have you restarted sensu-client and sensu-server, possibly also
> sensu-api?
That is because IP is an attribute belonging to the client, not to the check.
You can of course add the IP as a attribute to the check, but it will not be available at the same location as it would be when used traditionally.
Take Uchiwa as an example, when opening the detail view of a check: https://uchiwa.io/img/unifiedclient.gif
-
everything on the left side belongs to the client (e.g. name, ip, subscriptions)
-
everything on the right side belongs to the individual check (e.g. command, output, history)
You put the IP as an additional information to the check, so it would be available at the right side instead of the left side, where you are presumably searching for it.
···
On Friday, April 28, 2017 at 5:44:58 PM UTC+2, Kernel Panic wrote:
Yes, but default we have NTP configured on all server, I also added
“address”: ip-address to the check, but just did nothing.
