VMware Cloud Community
HansdeJongh
Enthusiast
Enthusiast

Scom Adapter no metrics

Hello,

I have installed and configured the scom adapter in vcops 5.7.2.

The first problem was that the auto discovery didnt work. but i solved that by run a manual discovery.

That gave me all the resources that i was expecting.

The problem is that they dont show any "scom" metrics.

Debug logging shows (with the first 4 lines repeating many many times..:

2013-10-13 16:09:03,788 DEBUG [Collector worker thread 10] (706) com.integrien.adapter3.scom.SCOMAdapter.getResourceKindByTypeName - MaxResourceKindLength = 50

2013-10-13 16:09:03,788 DEBUG [Collector worker thread 10] (706) com.integrien.adapter3.scom.SCOMAdapter.getResourceKindByTypeName - MaxResourceKindLength = 50

2013-10-13 16:09:03,788 DEBUG [Collector worker thread 10] (706) com.integrien.adapter3.scom.SCOMAdapter.getResourceKindByTypeName - MaxResourceKindLength = 50

2013-10-13 16:09:03,788 DEBUG [Collector worker thread 10] (706) com.integrien.adapter3.scom.SCOMAdapter.getResourceKindByTypeName - MaxResourceKindLength = 50

2013-10-13 16:09:03,788 DEBUG [Collector worker thread 10] (706) com.integrien.adapter3.scom.SCOMAdapter.onCollect - Check availability

2013-10-13 16:09:03,789 DEBUG [Collector worker thread 10] (706) com.integrien.adapter3.scom.SCOMAdapter.onCollect - Execute data query

2013-10-13 16:09:03,795 DEBUG [Collector worker thread 10] (706) com.integrien.adapter3.scom.SCOMAdapter.onCollect - Process retreived data

2013-10-13 16:09:03,795 DEBUG [Collector worker thread 10] (706) com.integrien.adapter3.scom.SCOMAdapter.processDataCollection - Number of records in result set = 0

2013-10-13 16:09:03,846 DEBUG [Collector worker thread 10] (706) com.integrien.adapter3.scom.SCOMAdapter.onCollect - Close DB connection

what am i doing wrong?

Regards

Hans

Tags (3)
Reply
0 Kudos
2 Replies
mark_j
Virtuoso
Virtuoso

What you're seeing isn't really an error, it's just a reminder of your adapter configuration. MaxResourceKindLength = 50 is the default, and it can be increased if you've got a MP with an exceedingly long name (there are a handful for IIS, etc).

This MP name is limited in length due to limits in the table field's size. Specifically, the table "resourcekind", and the column "resknd_key" indicates type character varying (200)  (last I checked this was 5.7.0). So you would be fine increasing MaxResourceKindLength to, say, 100 and ensure you're getting all of your MPs (in the scom adapter conf file).

This message wouldn't be stopping microsoft.windows.computer from collecting. Do you have the adapter instance configured to auto discover?

When you browse the "all metrics" views of the microsoft.window.computer resources, you'll see attribute groups that are listed as the MP name, then the metrics under those. You do this from the "All Metrics" views or metric selectors. Have you looked here yet? If you don't see any metrics, I would bet that when you manually imported the resources, you didn't select the option to collect.. so the resources are there, but not collecting. Do yourself a favor and start fresh.. delete the SCOM resources (not the adapter), then config the adapter to properly autodiscover resource. Kick off the adapter to collect, and you should see the resources get created, then start collecting shortly after.

If you find this or any other answer useful please mark the answer as correct or helpful.
HansdeJongh
Enthusiast
Enthusiast

thanks mark for the comprehensive reply. The solution (thanks to vmware support) was very simpel. I had to change the timezone on the adapter to GMT. Now i still have a time difference but all metric's show up.Im in gmt +1

Reply
0 Kudos