Follow Mike's blog
Archives for the month of: June, 2016

DESCRIPTION:

It helps to make sure your Database Availability Group(s) are healthy and replicated so they are ready to failover in the event of a problem. Copies are often in different sites for “site resiliency”

DAG

 

INSTRUCTIONS:

  • Download this DataSource file and add it into your LogicMonitor account (Settings > Datasources > Add > From file)
  • Make sure your collector computer has Microsoft’s Exchange Mgmt tools installed (here for Exchange 2013)
  • Set these properties on each Exchange server so it applies and can authenticate
    • ex.fqdn  (the name of the Exchange server)
    • ex.user (a username that has Exchange permissions)
    • ex.pass  (the password for this user)

DESCRIPTION:

Sometimes it’s important to monitor the speed of a file copy. I wrote this datasource because a customer wanted to monitor the time to copy a file from their London office to their Baltimore office. I chose to script it in PowerShell. To detect problems, I set it to alert if the file doesn’t exist and I set it to alert if the target file is not the same size as the source file. For his 10MB test file, I set the time thresholds to
>3 seconds = warning
>5 seconds = error
>7 seconds = critical

but you can easily adjust as needed.

INSTRUCTIONS:

  1. Download this DataSource file. Add it to your LogicMonitor account  (Settings > Datasources > Add > From file)
  2. On the device add a property called “copy_file” to specify the file you want to copy (e.g.  \\server2\share1\test-file.zip )
  3. Adjust the alert threshold if necessary.
  4. As usual, don’t forget to test. I suggest you look at the “Raw data” tab to make sure the numbers look correct.

File-copy-time

 

Below is an example link that takes you directly to a dashboard without requiring login. Basically you must specify your company/account, and username & password in the URL. I recommend you minimize the risk by making sure the user has a role of READ-ONLY or just permissions to the dashboard(s) you want. I suggest you use a password that only uses URL friendly characters ( letters, numbers, and  _ – ~ and .  )

To get and build this URL, navigate to your desired dashboard and add the portion

?c=your_account&u=some_username&p=your_password

in the middle (after the index.jsp and before the #dashboard=XX)

EXAMPLE:

https://acme.logicmonitor.com/santaba/uiv3/dashboard/index.jsp?c=acme&u=customer1&p=Abc-1234#dashboard=21

 

DESCRIPTION

It’s helpful sometimes to know the database names and the sizes of each, available space, user count, status. This uses the JDBC database connection method to get a list of databases as ‘instances’ then it gets detailed info on each of these databases. I filtered out the system default databases of master, model, msdb, and tempdb but you can change that. In Nov 2016 I updated this so it also works with Azure SQL. This was mainly due to the fact that Azure doesn’t let you specify master.sysdatabases. Instead it uses sys.databases.  I also changed it to use SQL authentication which is commonly used with Azure.

INSTRUCTIONS:

  1. Download this DataSource file and add it into your LogicMonitor account (Settings > DataSources > Add > From file ). It’s set to apply to all Windows servers but it will only show where there are instances (where the database query succeeds).
  2. On the device, set properties for jdbc.mssql.user and jdbc.mssql.pass if you use SQL authentication or change the URL/connection-string to use “integratedAuthentication=true” and remove the user= & password= .
  3. If desired, create threshold(s) to alert you.

SQL

DESCRIPTION:

This shows you how to configure Windows so that you can overcome the limitation of many monitoring tools that retrieve events because most of them can only retrieve from the “basic 4 logs” (ie  System, Application, Security, Setup).  Unfortunately, back in the Windows Vista (circa 2007) days, Microsoft changed the event log architecture slightly and made an additional type of logs called “Application and Services” which many software vendors now use. This “subscription” feature can be used to copy events that occur into the new logs to one of the basic 4 mentioned above. In most cases, it’s appropriate to use the “Application” log.

INSTRUCTIONS:

Please see all the steps in this video I made: