2009/9/21 Melanie Pfefer :
> Hi,
>
> it is a ASE server, not mssql. Usually to connect to ASE, we define the
> server in interfaces file. The issue here is that in Sybase, the hostname can
> be while the servername can be B (a totally different name). The
> same host can also have anoth
for each ASE server:
define service{
host_name jupiter
address 10.0.0.6
service_description Sybase check
check_command check_sybase!JUPITER%
}
and the command is defined:
define command{
command_name
On Sep 21, 2009, at 5:41 AM, Melanie Pfefer wrote:
> So I need from you advice on how to proceed. In nagios, we have
> HOSTNAME only (along with its IP address).
>
> How to integrate the servername also in nagios?
Pass the servername as an argument from the service definition ($ARGx$
macro).
Hi,
it is a ASE server, not mssql. Usually to connect to ASE, we define the server
in interfaces file. The issue here is that in Sybase, the hostname can be
while the servername can be B (a totally different name). The same host can
also have another ASE server.
You mentionned port num
2009/9/18 Melanie Pfefer :
> Hi
>
> I have a shell script that connects to each SQL server I have.
>
> I want to integrate this is nagios 2.
>
> However, I noticed that nagios relies on HOSTNAME and HOSTADDRESS and
> HOSTGROUP. While I am more interested in the servername: For example, I could
>
Hi
I have a shell script that connects to each SQL server I have.
I want to integrate this is nagios 2.
However, I noticed that nagios relies on HOSTNAME and HOSTADDRESS and
HOSTGROUP. While I am more interested in the servername: For example, I could
have 2 sql servers hosted on the same mach
