Monitoring ESXi Syslogs with OpsMgr 2007 R2 (Part 2) – Basic Reports

So looking at the event view in OpsMgr console is nice, but what if you need to Export syslog data and send it to support? To do this you need to create a report.

The Process

  1. First, open the OpsMgr Console’s “Reporting” page, then click the “Authored Reports” folder in the navigation pane, then click “Design a new report” in the action pane.
  2. The system should ask you to authenticate. When Microsoft Report Builder appears, choose “Event” as the source data then click “OK”.
  3. In the “Entities” section click “Event”, then in the fields section hold the control key (Ctrl) and click “Date Time”, “Event Log Title”, “Event Type Title”, and “Event Logging Computer”, then drag these selected fields to the blue square in the report page view that says, “Drag and drop custom fields”.
  4. Under “Entities” choose “Event Detail”, then drag the field “Rendered Description” to the same fields section on the report page view.
  5. The final result should look like the image below, however notice that the fields aren’t in the best order.
  6. Click and drag “Event Type Title” to the left-most position, but notice how the top bar has broken into two sections “Event Type” and “Event”. To correct this, drag “Event Type Title” to the right until a dark blue line appears, then let go. The bar will reunite.
  7. Now, choose “Filter” from the menu bar.
  8. Under Entities click “Event”, then “Event Rule”, then “Rule”. Then, drag “Rule System Name” to the right pane and click “(no values selected)” to browse for a rule.
  9. Find the rule “JPPacks.MonitorSyslogs.CollectSyslogs” on the left box, and click the “>” button to move it to the right box, then click “OK”.
  10. Verify that your settings look correct, then click “OK”.
  11. Click “Run Report” from the menu bar to see if everything works!
  12. If you have sent any test events, you should see them in the report data.
  13. Now, click “Design Report” to switch back to the report edit mode, then click “File”, “Save-As” and save your report.
  14. You should now see your report in the OpsMgr reporting website wherever you chose to save it in Step 13. Clicking the report should run it and generate data.

Limitations!

  • This report is only giving the OpsMgr event data processed through the condition detection module “System.GenericDataMapper”, and none of the PowerShell PropertyBag values we assigned. This is possible, but difficult and I haven’t yet figured it out.
  • This report is UGLY! Not even a title!
  • A couple parameters like computers to include\exclude would be wonderful.
  • Adding this to the management pack so it automatically creates on import would be awesome too.

I’ll try to come back around to the items above, but for now this satisfies my immediate need. Thanks for reading!

Advertisements

4 thoughts on “Monitoring ESXi Syslogs with OpsMgr 2007 R2 (Part 2) – Basic Reports

  1. Pingback: Monitoring ESXi Syslogs with OpsMgr 2007 R2 (Part 1) « windowsmasher

  2. Pingback: Monitoring ESXi Syslogs with OpsMgr 2007 R2 (Part 1) « Vinachip

  3. Pingback: OpsMgr 2007 Base Concepts and Helpful Links « Vinachip

  4. Pingback: Table of Contents | windowsmasher

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s