This is a run through of configuring Server Side monitoring of web applications with SCOM 2012.
Open the .NET Application Performance Monitoring template, in the Operations Manager 2012 console, in the navigation pane, click the Authoring button, click Management Pack Templates, click .NET Application Performance Monitoring.
In the Tasks pane, click the Add Monitoring Wizard.
In the Add Monitoring Wizard on the Monitoring Type page, select .NET Application Performance Monitoring, and then click Next. This template allows you to monitor ASP.NET applications and web services hosted in IIS7.
On the General Properties page, enter a friendly name and description for the application group you are creating. In the Select destination management pack menu, select the management pack that will store the settings that are specific to this instance of the template.
On the What to Monitor page, in the Environment menu, select the environment you want to monitor your application in: None, Production, Staging, Test, Development, or new. Typically, you will want to pair the environment tag with the server group you are monitoring. Tip – If you have no need to monitor multiple versions of the same applications, such as production instances and staging instances, you can leave the environment tag set to None.
On the What to Monitor page, in the Application components section, click Add. On the Object Search page that opens, use the Look for menu and Filter by text box to narrow your search, and then click Search for a list of the application components you can monitor. From the search results, select the application components you want to monitor, click Add, and then click OK.
The application components you selected are now displayed as members of the application group you are going to monitor – To limit the scope of monitoring to a group of servers, on the What to Monitor page, in the Monitored Servers section, Select the server group you want to limit monitoring to from the Available Groups search results list, and click OK to add it to your target server group to monitor.
Tip – The Targeted servers group allows you to configure monitoring using one set of thresholds for one set of application servers and a different set of thresholds for another set of application servers. To configure monitoring for the second set of computers, run the template again and use the alternate Targeted servers group.
On the Server-Side Configuration page, decide how you want to configure your monitoring. You have options to:
Do not Enable client side monitoring at this time – it is important to check that client side monitoring is suitable for the application first.
On the Summary page, review your monitoring configuration for your application group. Note and resolve any warnings. For details about a warning, hover over the warning icon. Then you’re done. You’ll see your configured template appear in the templates pane.
After server-side monitoring has been configured, you might need to restart IIS or recycle the application pools to finalize the configuration of the applications for monitoring. If a restart or recycle is required, you will receive an alert and can use the task link in the knowledge base to perform the necessary action.
Note – After you restart IIS, an application will not begin to be monitored until it is used.
Performance Views
Alerts, Alert Context
Tags: APM (Avicode)
[...] Part 2 – Server Side Monitoring [...]
Do you know off any good way to generate alerts? I use nopCommerce for test and demo.
I use NOPCommerce and Stock Trader for demonstrations and I find the easiest way is to either:
1) Set very low thresholds
2) Edit a web page to throw an error
Tablet…
[...]Installing Avicode (APM) Monitoring – Server Side // Designing Integrated Solutions[...]…
I don’t even understand how I ended up here, however I thought this put up was once good. I do not recognise who you might be but certainly you are going to a well-known blogger when you are not already. Cheers!