Blog
By Simon Skinner on 1/10/2011 1:05:56 PM • Rank (2558) • Views 2561
0

0

At last, we are in the Operations Manager Console! I have been focused with the AVICode side of the configuration that we seem to have missed out on the joys of being able to do this in Operations Manager. The marriage is not always a perfect one but for the best part of the day – to - day work it is, entering into the logical workspace of the Operations Manager makes sense to me. The ‘Single Pane’ where alerts do not get missed so why not have the .Net there also?

So then lets get going with the ritual of configuration, now in a familiar wizardry system of the ‘Microsoft way’ which to most of us makes more sense. As with most changes of configuration within Operations Manager navigate your way to the Authoring Pane then Management Pack Templates, as you can see her after running the AVICode install wizard supplied now by Microsoft. I may need to cover this in another post but this is covered in the AVIcode Manual, after the install of AVICode we see that additional templates are presented to us as ‘Enterprise xxx.xxx’.

We want to monitor a Web Application could there be a  little confusion here? Which is it, Enterprise ASP.Net Application or  Enterprise ASP.Net  Web Service? The correct answer is Enterprise ASP.Net Application as it is an Application that we can monitor .Net Applications which is a different wizard limited to .Net Applications but not ASP.Net Applications with that in mind ‘Enterprise ASP.Net Application’ makes more sense that this is the correct template to use.

 

Right click on the Enterprise ASP.Net Application template.

image

Which,  well does this ask us the same question again in a new window? OK well let’s do that again, click Enterprise ASP.Net Application so to highlight it then click next.

image

This is where we can start with the configuration of the Application, note it is all blank. Don’t panic this is normal, AVICode have invested a lot of effort in this area of the wizard, they got it right is light years ahead of previous versions. Click on the ‘Search by computer name seen in the next screenshot.

image

image

This opens a dialog box that lists the computers with ASP.Net applications, this is propagated via a discovery process earlier in the cycle during the installation or after via manual configuration.

image

Select the computer that has the Application you wish to monitor, in this case this is a fairly easy decision but worth mentioning the Application could be on a workstation or server, workstation? Yes this could be used to debug local dev workstations with IIS.

image

Once you have the computer selected click the ‘Find Now’ button reveling the “IIS Application Names”

image

Note here the Discovery Interval, in test set this to what you want but in production I would increase this to a day or more as this will have an impact on the Ops Mgr agent!

image

Here is another very important point, can you see that the Application Failure box is greyed out and the Performance is un ticked, yes this does mean that it will not pick up Application Failures, we can address this in a minute. First the why, Microsoft have ‘dulled’ the alerts coming into the Ops Mgr console by default this way we can choose what we want to be alerted on.

image

This page is where is is all going to happen, as you can see the pages is ‘brimming’ with excitement! But click the ‘Add web Page’

image

Then click the Browse button…

image

Where you will be asked for authentication

image

And here is it, worth the wait? But this is a gotcha, unless you add the ASP.Net page in you will NOT , in the Ops Mgr console see a Application Failure [a yellow stack page] BUT this would appear in the SEViewer. Lets make sense of this for a minute, Ops Mgr is the Infrastructure tool, the SEViewer is for dev.'s by default we can change this is a certain degree and things will change in future releases I am sure but for now this is the way is, I prefer this and would hope it did not change to much from this design. 

image

Select a page this is a page by page ordeal so you have to finish the wizard of this selected page before you can select another.

My advice here would be to modify the Transaction Name from in this case from www.skinner.fr_default to www.skinner.fr/default.aspx as the wizard generalizes this and you make select another pages that could end up with the the same Transaction Name.

 

image

NOTE the the Application failure box is now active so we can track the Application failures in Ops Mgr

SNAGHTMLec14cc

With our pages configured we can go onto the next one.

image

Click next the Setting Summary advises  you of the changes, confirm then click create.

image

This will create a management pack

SNAGHTMLeebec1

As well as update the Intercept Management Console

image

You Application is now visible, also note that the page you configured has shown up in the Ops Mgr Console.

SNAGHTMLf63585

Note that you you will will get a warning that you need to Recycle IIS, there is a task for this in the Task on the right hand side of the Ops Mgr console.

image

That's it your off!

 

In Part 9 we will look further into configurations with the Ops Mgr Console.

 

Simon Skinner [MVP]

Comments (1) - Comment RSS
Orinoko John wrote: on Jan 12, 2011 09:48 AM
Simon, a great series of articles, thanks very much.

I have run through the process you outline above and can see my app (the OpsMgr webconsole, of course) management pack listed in the console. The diagram view has no content other than the root node which is unmonitored. I have no "Agent State" objects, no alerts, no status, nothing in the OpsMgr console. But. In the Intercept Studio interface I have graphs, errors, trend reports, key metrics, the works.



Have I missed something? How to get the data into the OpsMgr console?



Ta



Q


Who Viewed
Who Reviewed
Categories
Related Pages
Shortened URL
http://tinyurl.com/37plbfd

Top Contributors
Featured Members
Pete Zerger
Points: 73134
Level: System Center Expert
Tommy Gunn
Points: 47653
Level: System Center Expert
Simon Skinner
Points: 40804
Level: System Center Expert
Andreas Zuckerhut
Points: 31100
Level: System Center Expert
Stefan Koell
Points: 30359
Level: System Center Expert