Sybase monitoring support

Hi @manthena2020 

In the first instance can you ensure your collector is upgraded to v31.200 or later.

Also its likely that the jars aren’t being loaded and will need to be added to the collector https://www.logicmonitor.com/support/terminology-syntax/scripting-support/adding-groovy-libraries and you’ll then probably need to reference them via the wrapper config

But if you can raise this via support request we can give you the appropriate detail

Kin​​​​​d regards

Paul

@manthena2020 

The files we use are called jconn42.jar & jconnect-7.7.jar

But as I’ve mentioned a few times already, if you raise a support ticket we can share them with you directly

Kind regards

Paul

Ask support to answer the questions above. If the answer isn't in the docs, ask them to put it in the docs. 

@manthena2020 

There aren’t any datasources for Sybase available out of the box, so you will need to build something yourself or have our professional services team build it for you.

You can use this doc https://www.logicmonitor.com/support/logicmodules/datasources/data-collection-methods/jdbc-data-collection which gives some explanation on how to use JDBC and create a custom datasource
 
The JDBC collector allows created datasources that query databases to collect and store data from a SQL query, alert on them, and graph them.
 
A typical jdbc command would look like this 
 
$ !jdbc url="jdbc:sybase:Tds:SERVER:PORT" username=XXX password=XXXX SQL
 
There are a few Oracle and MSSQL Datasources that may give you some ideas as a starting point

Kind regards
Paul

Almost certainly, the answer is, "Yes, LM can monitor it."

The right question is: "Does LM do Sybase monitoring OOTB or do I have to build it?" The way to know if it's available out of the box is to look for any datasources for it, either already installed in your portal or in the exchange. If none exist, you'll need to figure out how to get at the data you want and build that into one of the OOTB collection mechanisms (SNMP, WMI, JDBC, etc.). If the data isn't available through one of those methods, you'd need to see if it's available through a method that can be scripted (SSH, API, etc.). Then you'd just need to build that in. There's a whole live class (LMCD) and several on demand trainings to help with this.

Ok so JDBC is the method.

And the built in JDBC method won't work because the connection string needs the driver for Sybase, which either doesn't exist you you don't know what it is called. The driver name is a support question (which answer should be in the docs if it's not there already). 

And a scripted JDBC option requires groovy to have a Sybase driver, which the collector either doesn't have installed or you don't know what it takes to use it. That is also a support question which answer should also be in the docs. 

@manthena2020 Thanks for sharing this, a quick glance suggests the code looks ok but as I mentioned above there are some changes you need to make to your environment/collector to get this working

Please raise a support request so we can work this through with you

@manthena2020 You can raise support requests via your LogicMonitor portal, details can be found here https://www.logicmonitor.com/support/about-logicmonitor/customer-support/logicmonitor-technical-support-packages#channels

Hi @manthena2020 

Thanks for coming back on this, details for upgrading a collector can be found here https://www.logicmonitor.com/support/collectors/collector-management/managing-your-collector#upgrading

I continue to encourage you to raise a support request directly so we can fully assist you with resolving this issue

Kind regards

Paul

Hi @manthena2020 

We usually suggest having both jconn42.jar & jconnect07.7.jar in the relevant location. If you raise a support ticket we can share this with you directly.

Kind regards

Paul