Use Opserver to monitor your ASP (I. Introduction to OPSERVER monitoring and platform Setup)

Original: Use Opserver to monitor your ASP (one, Opserver monitoring introduction and platform building)

Objective

There have been 2 articles on how to monitor the ASP. NET Core project.

Today we mainly talk about how to monitor our ASP.

First, let's introduce what is Opserver, which is the stack Overflow (Stack Overflow is a program-related IT technology quiz site. Users can submit questions, browse questions, index related content, and use simple HTML when creating a homepage. On the questions page, no ads, sales information, JavaScript windows, etc. will pop up. ) Open Source monitoring products (using the MIT Protocol).

The StackOverflow website is based on ASP, so this open source project is used by stack overflow.

Open Source Address: https://github.com/opserver/Opserver

It supports a wide range of monitoring content, as follows:

• Server information is collected by bosun,orion or directly monitoring WMI products and systems.
• SQL clusters and Single instances
• Redis
• Elasticsearch
• Exception Log (from Stackexchange.exceptional)
• HAProxy
• Pagerduty
• CloudFlare DNS

This series focuses on how to monitor SQL Server and projects (including exception logs), and server status

Effect:

Body

This article mainly describes how to build our monitoring platform.

First we need to download this platform from GitHub (Https://github.com/opserver/Opserver).

Then, compile locally.

If you're using the TFS management tool, you should be fine. If it is another version of the management tools, may be error solution can Baidu. It's simple.

Set Opserver as the Startup Project.:

It is then generated and started. It should be an error at this time.

You are prompted not to set the Securitysettings.config error.

When we look at Web. config, we find that he specifies the file by default in Config\securitysettings.config

:

Find Config folder, you will see there are many configuration files, and all end with. Example.json.

Find our SecuritySettings.config.example file and remove the suffix example

Then open, edit. It will find the following configuration:

<securitysettingsprovider= "AD"ApiKey= "MyKey">    <!--Optional, these networks can see the overview dashboard without authentication -    <Internalnetworks>        <Networkname= "SE Internal"CIDR= "10.0.0.0/8" />    </Internalnetworks></securitysettings><!--Example of global access for everyone:<securitysettings provider= "Alladmin"/> -

This is actually about monitoring the project's login permissions configuration, you can set to AD, that is, domain control account permissions, you can also specify fixed IP access rights.

Of course, we set this to all permissions for the time being. That's the one with the bottom comment. The modified configuration is as follows:

<!-- <securitysettings provider= "AD" apikey= "MyKey" >    <InternalNetworks>        <network name= "SE Internal "cidr=" 10.0.0.0/8 "/>    </InternalNetworks></SecuritySettings>-  <provider= "alladmin"/>

Then, we continue to run the launch of our Opserver project.

You will find that you have entered the login screen:

We enter the default account name password: admin, you can login.

Notice that there are no monitoring items, because we have not configured the relevant monitoring content.

This completes our initial operation.

written in the last

The construction of the opserver is actually very simple, and next we'll show you how to monitor our SQL Server and ASP.

Use Opserver to monitor your ASP (I. Introduction to OPSERVER monitoring and platform Setup)