Stack Exchange – OpServer

Background

Over the years I have heard some good things about Stack Exchange’s OpServer.

But, I have also heard that it is a bit fuzzy to install.

 

Week of Training

Starting from late last week I have blocked out some hours for training.

Last Thursday was “Cyber Security” training.

Today, Monday, is “Sexual Violence & Security Harassment” training.

Just like you, it is not easy to get in Training Hours.

 

 

Tech Training

Continuing with the week of training let us install & familiarize ourselves with Stack Exchange’s Op Server.

 

Download

Downloaded the source code from here.

 

Built It

Downloaded and installed Microsoft Visual Studio 2017 Community Edition.

Re-started machine.

Once back up loaded the downloaded OpServer Solution. Built it.

 

Deployment

Deployment – Remote

Could not deploy remotely due to Firewall issue and so built a deployment package and copied to remote host over remote desktop.

 

Deployment – Local

While RDP’ed to remote host took care of the following:

  1. Installed MSDeploy
  2. Ran Opserver.deploy.cmd
  3. Review IIS Web Site via MMC
  4. Edit configuration files
    • web.config
      • appSettings
        • viewGroups
          • Add AD Groups that should have ReadOnly Access
        • AdminGroups
          • Add AD Groups that should have Admin Access
    • package configuration files
      • copied over package configuration templates
        • Config\SecuritySettings.config
        • Config\sqlSettings.json
      • customized aforementioned config files
        • Config\sqlSettings.json
          • Add each server that will be monitored

 

Usage

Launched web browser and played around

All Servers

Jobs

Instance

Top

Current Active Queries

 

Summary

There is quite a bit to like about OpServer.

It is Open Source.

It runs on Microsoft IIS and relatively easy to configure and customize.

The Source Code is available and can be reviewed and tweaked.

Nothing has to be installed on the target server.

It is very, very buzzword compliant.

Buzzword Compliance includes:

  1. Configuration via
    • web.config
    • json files
  2. Viewing SQL Queries query plan in HTML
    • JustinPealing/html-query-plan

 

Later

Later will come back and talk about building, deploying, customizing and digging deeper into the tool itself.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

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

Google+ photo

You are commenting using your Google+ 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 )

w

Connecting to %s