Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Orion MP is not writing data in SCOM DW

Hello all,

So far, we have integrated SolarWinds 9.1 with SCOM 2007 SP1 using Orion MP, which was first big step. Our goal was to collect performance metrics such as CPULoad and PercentMemUsed (For Non Microsoft products) from SolarWinds and keep it in SCOM-DW repository for reporting.

It looks like "Collect Device Data from Orion" does the collection of the above mentioned metrics. This rule is targeted against "SolarWinds.Orion.SCOM.Node" and "SolarWinds.Orion.SCOM.Interface" objects. We are only interested in Node metrics. So the format of the perf counter that is collected by the rule to my understanding is "Object\Counter\Instance" as shown below:

- SolarWinds.Orion.SCOM.Node\CPULoad\10.10.10.1- SolarWinds.Orion.SCOM.Node\PercentMemUsed\10.10.10.1

It looks like "Collect Device Data from Orion" rule is supposed to write data in OperationsManager and OperationsManagerDW databases. I verified this by opening the MP where it is clearly evident that the rule is writing to both DB:

<WriteAction ID="WriteToDW" TypeID="SCDW!Microsoft.SystemCenter.DataWarehouse.PublishPerformanceData" /> .

I also verified that the CPULoad and PercentMemUsed data are written only to OperationsManager database. However, I don't see the same data in DataWarehouse. Has anyone come across this issue, is there an easy way to verify that the Orion data is written to DW and how do I fix this? Thanks in advance. Dipu

Find more posts tagged with

Accepted answers

All comments

FormerMember

We didn't test it against the OperationsManagerDW databases, just the standard OpsMgr database.

dbantawa

Denny,

Thanks for your reply and it looks like it is a known problem. I was researching on the net and I found information below (underlined) from this link: http://blogs.msdn.com/mariussutara/archive/2008/01/24/momscriptapi-createtypedpropertybag-method.aspx

I found out what OpsMgr have problems with moving performance data to DW if this data was collected by ONE rule with more then ONE counter.

Here is MS answer: DW does not support multiple object/counter pairs collected by one rule (multiple instances is Ok). You’d need to create as many rules as the number of object/counter pairs you wish to collect.

So if we create individual collection rules for each counter the problem will be resolved. Orion only use one rule for multiple counters. I thought I would be able to create multiple collection rules so I tried. However, first, I was unable to target my rule against variable $MPElement$ and second I was in big dilemma what type of collection rule I should be using SNMP based, WMI based (certainly looks like this is not correct) or Windows based (this one seems incorrect too). It is understandable why you used variable which is populated with discovered instance and attributes dynamically. Can you please help us create multiple collection rules? This way we will not only be able to monitor but also report against Orion collected metrics via SCOM. Thank you again.

Dipu

dbantawa

Denny,

It looks like the way SCOM and Orion is integrated as follows:

- There are corresponding connectors at Orion Management Server (Orion Information Service) and SCOM RMS (Orion MP Service) end

- SCOM monitoring starts after the devices and interfaces are selected. This actually creates a configuration file which is used for monitoring and collecting key performance and availability metrics.

- The data is collected by Orion connector and passed on to the connector on SCOM RMS in an XML format every 2 mins approx.

- The XML file contains all the performance data which is then collected by a rule (looks like programmatically) and inserted into SCOM DB and not DW (Please refer my previous response)

I just dumped these findings here so that it might help in our troubleshooting. Thanks in advance.

Dipu

FormerMember

I can't really troubleshoot this one from Thwack. Can you open a Support ticket and reference this thread.

dbantawa

We opened a case yesterday and the Case # is 67751. I will keep you all posted if we fix or find a work around. Thanks.