1 2 3 Previous Next

Product Blog

72 Posts authored by: bshopp Employee

As some organizations start to either move workloads to the cloud, or as they build new apps and services natively within the cloud, the number of hybrid deployments and environments are increasing exponentially. In these hybrid environments, it’s important to remember how critical it can be to retain a single pane of glass, allowing for visibility into your applications and infrastructure.

 

With the recent release of Server & Application Monitor v6.7 (SAM), we’ve built in support for monitoring containers for Docker, Mesos, and Kubernetes, giving you visibility infrastructure wide into physical, virtual, cloud, and now container infrastructure.  Check out SAM’s product page to see all of SAMs features and supported systems and applications.  As cloud services and cloud infrastructure continues to grow and see more adoption, Server & Application Monitor needs to grow with it. In this post, we’ll discuss some of the ways we’re supporting this growth, as we highlight several new additions to support Microsoft Azure PaaS services. We’ll dive deeply into three of these new additions below. And of course, as always, please let us know any additional content you’d like to see SAM monitor.   To begin these template and others, SAM is can be download here.

 

The three new templates I am going to cover today for Azure include:

  • Azure App Service
  • Azure SQL Database
  • Azure Event Hub

 

For all three of these templates, be sure to install a couple of PowerShell modules on the system that SAM is installed, allowing you to leverage the following PowerShell commands:

  • Install-Module -Name Azure
  • Install-Module -Name AzureRM

 

Azure App Service:

Application Template can be downloaded here - Microsoft Azure App Service.apm-template

 

Prerequisites:

  1. To connect with your Azure account, the following parameters are required:

     subcriptionID,ApplicationID,TenantID, Secret Key, Application Name

     Note: Azure App to monitor, with its name and ID, should have role set as 'contributor or Reader' in the Azure access control.

    2. Application name for which metrics will be calculated.

    3. Time interval for which data has to be fetched (in hours).

    4. PowerShell version supported 5.1 or above.

 

Script Argument:

  • Login credential to access Azure Portal. Azure details have to be passed in script arguments as per prerequisite #2.

Example:

             <SubscriptionID>,<TenantID>,<ApplicationID>,secretKey=<Enter SecretKey>,<ApplicationName>,TimeRange=<Time in hrs>

  • The ApplicationID with which you are making a connection to the Azure portal (as mentioned in Credential/Prerequisites) must be registered in Azure Active Directory as a contributor role for the monitored application.

        Reference link: https://support.solarwinds.com/Success_Center/Server_Application_Monitor_(SAM)/Knowledgebase_Articles/Add_an_Azure_Active_Directory_app_for_cloud_monitoring_in_the_Orion_Platform

 

Portions of this document were originally created by and are excerpted from the following sources:

https://docs.microsoft.com/en-us/azure/app-service/web-sites-monitor   

https://docs.microsoft.com/en-us/powershell/azure/authenticate-azureps?view=azurermps-6.7.0

https://docs.microsoft.com/en-us/powershell/module/azurerm.insights/?view=azurermps-6.7.0&viewFallbackFrom=azurermps6.7.0#monitor

 

MONITORED COMPONENTS

  • Average number of bytes sent

      This monitor provides the average number of bytes sent for the given app.

      Unit: MB (Mega Bytes)

  • Total number of 2xx requests

      This monitor provides the count of requests resulting in an HTTP status code >= 200 but < 300 for the given app.

      Unit: Count

  • Total number of 3xx requests

      This monitor provides the count of requests resulting in an HTTP status code >= 300 but < 400 for the given app.

      Unit: Count

  • Total number of 401 requests

      This monitor provides the count of requests resulting in HTTP 401 status code for the given app.

      Unit: Count

  • Total number of 403 requests

      This monitor provides the count of requests resulting in HTTP 403 status code for the given app.

      Unit: Count

  • Total number of 404 requests

      This monitor provides the count of requests resulting in HTTP 404 status code for the given app.

      Unit: Count

  • Total number of 406 requests

      This monitor provides the count of requests resulting in HTTP 406 status code for the given app.

      Unit: Count

  • Total number of 4xx requests

      This monitor provides the count of requests resulting in an HTTP status code >= 400 but < 500 for the given app.

      Unit: Count

  • Total number of 5xx requests

      This monitor provides the count of requests resulting in an HTTP status code >= 500 but < 600 for the given app.

      Unit: Count

  • Total number of requests served by the app

      This monitor provides the total number of requests regardless of their resulting HTTP status code for the given app.

      Unit: Count

  • Average number of bytes received

      This monitor provides the average number of bytes received for the given app.

      Unit: MB (Mega Bytes)

  • Average memory used

      This monitor provides the average amount of memory in MBs used by the given app.

      Unit: MB (Mega Bytes)

  • Average response time

      This monitor provides the average time taken for the app to serve requests in milliseconds (ms).

      Unit: MS (Milliseconds)

 

TROUBLESHOOTING STEPS

Detailed troubleshooting steps (common for template):

  • Check that the PowerShell version is 5.1 or more and the Azure module is installed on the system where the template will run.
  • Template uses PowerShell components; script should run with administrator privilege.

Be sure to detail troubleshooting steps (specific for components).

  • Components connect with Azure using service principal authentication for which application has to be created at the Azure portal. See below link:

     https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-create-service-principals

  • Provide Azure IAM permission to the application, which was created in the last step. See below link:

     https://support.solarwinds.com/Success_Center/Server_Application_Monitor_(SAM)/Knowledgebase_Articles/Configure_Azure_IAM_permissions_for_cloud_monitoring_in_the_Orion_Platform

  • Script fetch data based on time range given in last script arguments. By default, script fetch data for the past hour. While giving the time range, make sure the data is available for the metric at that time, otherwise the component will be unable to fetch the data.

 

Azure SQL Database:

Application Template can be downloaded here: Microsoft Azure SQL Database.apm-template

 

Prerequisites:

  1. To connect with your Azure account, the following parameter is required: subcriptionID, ApplicationID, TenantID, Secret Key.

Note: Any Azure App (with its name and ID) having role as 'Read Only'.

    2. SQL Server Database name for which metrics have to be calculated.

    3. Time interval for which data has to be fetched (in hours).

    4. PowerShell version 5.0 or later.

 

Credentials:

  1. Login credential to access your Azure Portal. This has to be passed as script arguments per prerequisite #2, as listed above. e.g. <subcriptionID>, <TenantID>, <ApplicationID>, value=<Secret Key>, <Application Name>, value=<Time Interval>, <Database Name>
  2. Windows Administrator on the machine where template would be running against.    

 

Portions of this document were originally created by and are excerpted from the following sources:

https://azure.microsoft.com/en-in/blog/windows-azure-sql-database-management-with-powershell/

https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-supported-metrics

 

MONITORED COMPONENTS

  • Blocked Connections

      This metric provides the average number of firewall blocked connections established for the given SQL database during the time period specified as the polling frequency.

      Unit: Count

  • Failed Connections

      This monitor provides the average number of failed connections established for the given SQL database during the time period specified as the polling frequency.

      Unit: Count

  • Successful Connections

      This metric provides the average number of successful connections established for the given SQL database during the time period specified as the polling frequency.

      Unit: Count

  • Deadlocks

      This metric provides the average number of deadlocks established for the given SQL database during the time period specified as the polling frequency.

      Unit: Count

  • Database throughput units (DTU) limit

      This metric provides the average database throughput limit in units for the given SQL database during the time period specified as the polling frequency.

      Unit: Count

  • Database throughput units (DTU) used

      This metric provides the average database throughput units used for the given SQL database during the time period specified as the polling frequency.

      Unit: Count

  • Sessions percentage

      This metric provides the average percentage of available sessions used for the given SQL database during the time period specified as the polling frequency.

      Unit: Percent

  • Database size percentage

      This metric provides the average percentage of storage used for the given SQL database during the time period specified as the polling frequency.

      Unit: Percent

  • Total database size

      This metric provides the average for the total database size for the given SQL database during the time period specified as the polling frequency.

      Unit: Megabytes

  • Workers percentage

      This metric provides the average percentage of available workers used for the given SQL database during the time period specified as the polling frequency.

      Unit: Percent

  • Average CPU utilization

      This metric provides the average percent CPU used for the given SQL database during the time period specified as the polling frequency.

      Unit: Percent

  • Average IO utilization

      This metric provides the average percentage of data IO used for the given SQL database during the time period specified as the polling frequency.

      Unit: Percent

  • Average log utilization

      This metric provides the average percentage of log IO used for the given SQL database during the time period specified as the polling frequency.

      Unit: Percent

  • In-Memory OLTP storage percent

      This monitor provides the average In-Memory OLTP (Online Transaction Processing) storage percent for the given SQL database during the time period specified as the polling frequency.

      Unit: Percent

  • Database throughput unit (DTU) percentage

      This metric provides the average percentage of database throughput units used for the given SQL database during the time period specified as the polling frequency.

      Unit: Percent

 

Azure Event Hub:

Application Template can be downloaded from here: Microsoft Azure Event Hub Namespace.apm-template

 

Prerequisites:

  1. To connect with your Azure account, the following parameters are required: subcriptionID, ApplicationID, TenantID, Secret Key, Application Name

Note: Any Azure App (with its name and ID) having role as 'Read Only'.

 

  1. Namespace for which metrics have to be calculated.
  2. Time interval for which data has to be fetched (in hours).
  1. PowerShell version 5.0 or later.

 

Credentials:

  1. Login credential to access the Azure Portal. This has to be passed as script arguments per prerequisite #2, listed above. e.g. < subcriptionID>, < TenantID>, < ApplicationID>, value=<Secret Key>, <Application Name>, value=<Time Interval>, <Application Name>
  2. Windows Administrator on the machine where template would be running against.    

 

Portions of this document were originally created by and are excerpted from the following sources:

https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-quickstart-powershell

https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-supported-metrics

https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-metrics-azure-monitor


MONITORED COMPONENTS

  • Archive backlog messages

      This monitor provides total Archive messages in backlog for the given namespace via PowerShell cmd-let.

      Unit: Count

  • Archive message throughput

      This monitor provides total Event Hub archived message throughput for the given namespace via PowerShell cmd-let.

      Unit: Bytes

  • Archive messages

      This monitor provides total Event Hub archived messages for the given namespace via PowerShell cmd-let.

      Unit: Count

  • Incoming Bytes

      This monitor provides the total Event Hub incoming message throughput for the given namespace via PowerShell cmd-let.

      Unit: Bytes

  • Outgoing bytes

      This monitor provides the total Event Hub outgoing message throughput for the given namespace via PowerShell cmd-let.

      Unit: Bytes

  • Average Disk Seconds per Write

      Average Disk Seconds per Write is the average time of a write of data to the disk.

  • Incoming Messages

      This monitor provides the total incoming messages for the given namespace via PowerShell cmd-let.

      Unit: Count

  • Incoming Requests

      This monitor provides the Total incoming send requests for the given namespace via PowerShell cmd-let.

      Unit: Count

  • Internal Server Errors

      This monitor provides the Total internal server errors for the given namespace via PowerShell cmd-let.

      Unit: Count

  • Other Errors

      This monitor provides the total failed requests for the given namespace via PowerShell cmd-let.

      Unit: Count

  • Outgoing Messages

      This monitor provides the total outgoing messages for the given namespace via PowerShell cmd-let.

      Unit: Count

  • Successful Requests

      This monitor provides the total successful requests for the given namespace via PowerShell cmd-let.

      Unit: Count

  • Server Busy Errors

      This monitor provides the Total server busy errors for the given namespace via PowerShell cmd-let.

      Unit: Count

 

 

The SolarWinds trademarks, service marks, and logos are the exclusive property of SolarWinds Worldwide, LLC or its affiliates. All other trademarks are the property of their respective owners.

I am pleased and excited to announce the latest addition to the SolarWinds product family on the Orion® Platform, Server Configuration Monitor or SCM. For those of your that are familiar with our Network Configuration Manager product or NCM, this new product is its sibling with a focus on systems and applications.

With this new product, SolarWinds continues to deliver on our unexpected simplicity promise of building simple, powerful, and affordable products.  SCM, built on the Orion Platform, is designed to enable you to capture, visualize, and understand changes in your environment in near real-time.

With this first version, we are focused on Windows systems and enabling customers to version and diff the following elements.

  • Hardware
  • Software
  • Registry
  • Files
  • Microsoft IIS

 

While we have already delivered v1, the team is hard at work to continue to advance and expand this product as outlined in our “What We Are Working On” post.  SCM is licensed by nodes, a simple-to-understand model, and pricing is affordable to many.  Let’s walk through a couple of use cases of how you could use the product.

 

Web Application Outage:

At the same time that you receive an alert from Server & Application Monitor indicating a critical web application is down, you also begin to receive calls from users indicating they cannot access it.

 

Where do you start investigation to determine where the problem lies? 

  • Is this a networking problem?
  • Is the hardware having a problem?
  • Is this a storage or database problem?
  • Is this application running on your virtual platform and is that having an issue?

 

While investigating each of these areas, the clock is ticking and you are getting more and more calls. 

Using the SolarWinds® PerfStack dashboard for a real-time view into multiple different metrics and parameters, as highlighted in the below screenshot, I can see that right before the web application went down, a configuration change was detected.

 

 

In the data explorer, I click on the web.config link and I am immediately taken to a comparison or “diff” page showing me what changed here.  As you can see, someone went in and made some edits to this config file and now the XML structure is broken, which took down your web application.  Now you can quickly remote desktop into that machine and change this back, save the file, and get the web application back up and operational.  So, what may have taken 30-60 minutes to investigate the infrastructure and root cause was isolated and addressed typically in minutes with SCM.

 

 

Let’s briefly touch on a couple of other use cases for Server Configuration Monitor.

  • Unauthorized Software
  • Malware Security Incident
  • Hardware Change

 

THE ARCHITECTURE

So how does it work? It all depends on what you want to monitor. If you are only interested in hardware and software versioning, we can do this without an agent. However, if you want to monitor files for changes, registry, or Microsoft IIS, then you will need to deploy the Orion Agent onto this machine. If you already have the Orion Agent deployed on your machine (for example, for monitoring in SAM) SCM is an add-in package in the Orion Agent that just needs to be enabled. The key point I am making here is this is not a separate agent.

 

 

WHAT ELSE?

Don't see what you are looking for here?

 

Visit the SolarWinds Server Configuration Monitor forum.

Check out the What We're Working On for SolarWinds Server Configuration Monitor post to see what our dedicated team is already looking at.

If you don't see everything you've been wishing for there, add it to the SolarWinds SCM Feature Requests.

 

We are excited to get this out there and begin to gather input and feedback. Don’t forget you can quickly and easily install a free, fully featured 30-day trial to kick the tires yourself.

 

The SolarWinds trademarks, service marks, and logos are the exclusive property of SolarWinds Worldwide, LLC or its affiliates. All other trademarks are the property of their respective owners.

The latest version of Server & Application Monitor (SAM) is now generally available. SAM v6.7 adds some very exciting and cool new features, which I will walk through in this post. If you are an existing customer, head on over to the customer portal to get the latest bits.

 

Outside of product releases, we’re also working on creating new or enhancing existing application template content for use in SAM. We recently published some content on THWACK®, which I covered here and here.

 

As always, we love to hear your feedback and how you would like to see them enhanced and evolve to help us continue to make SAM a better product.

 

Container Monitoring:

Available in both SAM and Virtualization Manager (VMAN), we have added our first version of container monitoring for Docker, Kubernetes, and Mesos. With this enhanced visibility, SAM can now provide insight into not just your physical infrastructure, but also virtual, cloud, and now container-based workloads.

 

Serena wrote up a document on this, going step-by-step through the configuration and deployment process, but essentially what we are doing is deploying a monitoring container within the container environment you wish to monitor. The information we are collecting is available in both AppStack and PerfStack for real-time troubleshooting.

 

In a future post, we will walk through how you can use SAM application templates to monitor applications in those containers.

 

Orion Maps and AppMap with ADM

The Orion® Maps team is on a roll coming off the initial release of Orion Maps in Q2, and this quarter they have added a bunch of new features, including support for leveraging the Application Dependency functionality added in SAM 6.6 to illustrate application or service dependencies in the maps.

 

Jeff Blank wrote up a very detailed and terrific document on these map enhancements here.

 

We think that these maps are fantastic because, first, they’re dynamic. Second, besides understanding the infrastructure relationships, the maps can help you understand which services and applications are talking to what and where.

 

Below is a screen grab from Jeff’s article illustrating these dependencies in an Active Directory environment.

 

 

 

SolarWinds APM Integration

For those who have been around SolarWinds for some time, I need you to put on your amnesia hats for a minute. I know back in the early days, SAM used to be called APM as well, but this is application performance management as defined by market analysts to give you code-level visibility into your custom applications.

 

SolarWinds® APM is a new product we are offering. It is designed to offer a very tight integration with SAM, giving users insight into their IIS-based, .NET applications natively within the SAM web console. SolarWinds APM is a cloud-based product based on SolarWinds AppOptics. In the screenshot below, we are pulling that data in real-time from the APM cloud service via API into the SAM console with the SAM look and feel from a charting and visual perspective.

 

When we were first considering this product and integration, we spoke with many SAM customers about their interest in functionality like this and how this typically flowed process-wise in their environments. The overwhelming feedback from folks was that with SAM and the other Orion Platform products, they had solid visibility into the infrastructure and off-the-shelf applications, but limited visibility into custom apps. When end users would report issues about these applications, it was hard for them to determine if it truly was a problem with the application or with something else.

 

If you upgrade to SAM v6.7, under the Settings page in the product, there is a new UI option called APM Deployment Summary. If you are interested in trying this product out, you can sign up for a 30-day trial directly from within SAM. The integration will be set up for you with your SAM deployment. SolarWinds APM can also be leveraged standalone as well if that is your preference—the option is yours.

 

 

The team is already hard at work on the next version of SAM, as you can see covered here in the “What We are Working On” post. Also, please keep the feedback coming on what you think and what you would like to see in the product in the ideas section of the forum.

Hot off the heels of my previous post of new Server & Application Monitor content for Microsoft SQL and Exchange, as well as SAP HANA, we also now have some new and enhanced content for monitoring your Oracle databases.   As mentioned in my previous blog post, this will be a steady drumbeat of releasing new and enhanced monitoring content for SAM, so please keep an eye out on THWACK® and I will keep you up to date via the product blog as well.

 

First off, as of today, these templates still require the additional components be installed and added to the Orion® Server and/or poller that these databases are being monitored from. We have documentation about this already in the Success Center here - https://support.solarwinds.com/Success_Center/Server_Application_Monitor_(SAM)/Knowledgebase_Articles/Configure_SAM_to_monitor_an_Oracle_Database_Server


Oracle Database: 
https://thwack.solarwinds.com/docs/DOC-203309

This template contains newly added performance and statistics counters for Oracle Database.

 

Prerequisites: Oracle client installed on Orion APM server. This is available from the SolarWinds customer portal under Additional Downloads.

Credentials: An Oracle username and password with read access to the Oracle tables.

 

MONITORED COMPONENTS

Components without predetermined threshold values provide guidance such as "Use the lowest threshold possible" or "Use the highest threshold possible" to help you find an appropriate threshold for your application. For more information, see http://knowledgebase.solarwinds.com/kb/questions/2415.

 

  • SGA Size

     This component monitor returns the System Global Area (SGA) as the part of the system memory (RAM) shared by all the processes belonging to a single Oracle database instance.

     Unit: Bytes

     Source: https://docs.oracle.com/cd/B28359_01/server.111/b28320/dynviews_3028.htm#REFRN30233

  • PGA Size

     Program Global Area (PGA) is a private memory region that contains the data and control information for a server process. Only a server process can access the PGA. Oracle Database reads and writes information in the PGA on behalf of the server process. Oracle Database automatically sizes the PGA by dynamically adjusting the portion of the PGA memory     

     dedicated to work areas, based on 20% of the SGA memory size. The minimum value is 10MB.

     PGA memory currently allocated by the process (including free PGA memory not yet released to the operating system by the server process)

     Unit: Bytes

     Source: https://docs.oracle.com/cd/B28359_01/server.111/b28320/dynviews_2098.htm#REFRN30186

  • Buffer Pool Size

     This component monitors the buffer pool size for the Oracle Database. The default buffer pool size is determined by the DB_CACHE_SIZE initialization parameter.

     Unit: Bytes

     Source: https://docs.oracle.com/en/database/oracle/oracle-database/12.2/refrn/V-BUFFER_POOL.html#GUID-1E70B05F-6E52-44B0-AFB3-5ADDA620008D

  • Shared Pool Size

     This component monitors the shared pool area size. The shared pool is a RAM area within the RAM heap that is created at startup time, a component of the System Global Area (SGA). The size depends on the size of your RAM.

     Unit: Bytes

     Source: https://docs.oracle.com/cd/B19306_01/server.102/b14237/dynviews_2106.htm#REFRN30238

  • Buffer Pool Response Time

     This component monitors the buffer pool response time. The value should be low for good performance.

     The query below calculates response time for logical reads per second from buffer within an interval of 15 seconds.

     Unit: Seconds

     Source: https://docs.oracle.com/cd/E11882_01/server.112/e40402/dynviews_3090.htm#REFRN30343

  • Single block read response time

     This component monitors the cumulative single-block read response time at the file level in seconds. This value should be low. A high value means a high latency.

     Unit: Seconds

     Source: https://docs.oracle.com/en/database/oracle/oracle-database/12.2/refrn/V-FILESTAT.html#GUID-9DF61EA4-EF94-4F60-B966-D1B9AFEFF3E0

  • Multi block read response time

     This component monitors the cumulative multi-block read response time at file level in seconds. This value should be low. A high value means a high latency.

     Unit: Seconds

     Source: https://docs.oracle.com/en/database/oracle/oracle-database/12.2/refrn/V-FILESTAT.html#GUID-9DF61EA4-EF94-4F60-B966-D1B9AFEFF3E0

  • Log write response time

     This component monitors log write response time. The response time here includes write time + wait time that log writer spent waiting.

     Unit: Seconds

     Source: https://docs.oracle.com/cd/E18283_01/server.112/e17110/statviews_4061.htm

     https://docs.oracle.com/cd/B19306_01/server.102/b14237/statviews_3177.htm

  • Physical I/O total rate

     This component monitors the physical I/O total rate. The total rate includes read rate + write rate per sec.

     A high value means a better performance.

     Unit: Bytes/second

     Source: https://docs.oracle.com/cd/E11882_01/server.112/e40402/dynviews_3090.htm

  • Physical I/O read rate

     This component monitors the physical I/O read rate per sec.

     A high value means a better performance.

     Unit: Bytes/second

     Source: https://docs.oracle.com/cd/E11882_01/server.112/e40402/dynviews_3090.htm

  • Physical I/O write rate

     This component monitors the physical I/O write rate per sec.

     A high value means a better performance.

     Unit: Bytes/second

     Source: https://docs.oracle.com/cd/E11882_01/server.112/e40402/dynviews_3090.htm

  • Commit latency

     This component monitors latency for commits by all users. If the value is null that means the number of commits per second is 0.

     Unit: Seconds

     Source: https://docs.oracle.com/cd/E11882_01/server.112/e40402/dynviews_3090.htm

  • SQL*Net receive rate

     This component monitors SQL*Net receive rate (clients + dblinks). In other words, bytes received via SQL*Net from client + bytes received via SQL*Net from dblink.

     Unit: Bytes/second

     Source: https://docs.oracle.com/cd/B28359_01/server.111/b28320/dynviews_3086.htm

  • SQL*Net send rate

     This component monitors SQL*Net send rate (clients + dblinks). In other words, bytes sent via SQL*Net to client + bytes sent via SQL*Net to dblink.

     Unit: Bytes/second

     Source: https://docs.oracle.com/cd/B28359_01/server.111/b28320/dynviews_3086.htm

  • Active sessions total

     This component monitors the total number of active sessions at any moment.

     Unit: Count

     Source: - https://docs.oracle.com/cd/B19306_01/server.102/b14237/dynviews_2088.htm

  • Active sessions waiting

     This component monitors the number of active sessions waiting to be run.

     Unit: Count

     Source: https://docs.oracle.com/cd/B19306_01/server.102/b14237/dynviews_2088.htmCPU.

  • Active sessions working

     This component monitors the total number of active sessions currently executing on CPU.

     Unit: Count

     Source: https://docs.oracle.com/cd/B19306_01/server.102/b14237/dynviews_2088.htm

  • Blocked sessions

     This component monitors the total number of sessions blocked by other sessions.

     Unit: Count

     Source: https://docs.oracle.com/cd/E11882_01/server.112/e40402/dynviews_3017.htm

  • Connections

     This component monitors the total number of active connections at any point.

     Unit: Count

     Sources:

     https://docs.oracle.com/cd/B19306_01/server.102/b14237/dynviews_2088.htm

     https://docs.oracle.com/cd/B19306_01/server.102/b14237/dynviews_2129.htm

     https://docs.oracle.com/cd/B28359_01/server.111/b28320/dynviews_2098.htm

  • Request rate

     This component monitors the total number of incoming request per second. A high number of requests might be a reason for slow response.

     Unit: Count/second

     Source: https://docs.oracle.com/cd/E11882_01/server.112/e40402/dynviews_3090.htm

  • Database Size (size of all tablespaces)

     This component monitors the total database size (size of all table spaces) of the Oracle Database. The default value is fetched in bytes.

     Unit: Bytes

     Sources:

     https://docs.oracle.com/cd/B19306_01/server.102/b14237/statviews_3122.htm

     https://docs.oracle.com/cd/B19306_01/server.102/b14237/statviews_3083.htm

  • Database Used Space (amount actually used)

     This component monitors the total database used space.

     Unit: Bytes

     Sources:

     https://docs.oracle.com/cd/B19306_01/server.102/b14237/statviews_3122.htm

     https://docs.oracle.com/cd/B19306_01/server.102/b14237/statviews_3083.htm

  • SQL Parse to execute ratio

     This component monitors SQL parsing to execute ratio.

     The query below will calculate the ratio by dividing parse count by execution count.  A higher ratio means better performance.

     Unit: Percent

     Source: https://docs.oracle.com/cd/B28359_01/server.111/b28320/dynviews_3086.htm

 

 

Oracle Automatic Storage Management:
https://thwack.solarwinds.com/docs/DOC-203310

This template contains newly added performance and statistics counters for Oracle ASM.

 

Prerequisites: Oracle client installed on the Orion SAM server. This is available from the SolarWinds customer portal[TK5] under Additional Downloads.

Credentials: An Oracle username and password with read access to the Oracle tables.

 

MONITORED COMPONENTS

Components without predetermined threshold values provide guidance such as "Use the lowest threshold possible" or "Use the highest threshold possible" to help you find an appropriate threshold for your application. For more information, see http://knowledgebase.solarwinds.com/kb/questions/2415.

 

  • Average Write Throughput

     This component monitor fetches the value for average write throughput for all disks under ASM disk group. The returned value will only show the results since the last polling period.

     Unit: MB/second

     Source: https://docs.oracle.com/cd/B19306_01/server.102/b14237/dynviews_1019.htm#REFRN30170

  • Average Read throughput

     This component monitor fetches the value for average read throughput for all disks under ASM disk group. The returned value will only show the results since the last polling period.

     Unit: MB/second

     Source: https://docs.oracle.com/cd/B19306_01/server.102/b14237/dynviews_1019.htm#REFRN30170

  • Average write latency

     This component monitor fetches the value for average write latency per MB for all disks under ASM disk group, at any time. The returned value will only show the results since the last polling period.

     Unit: Milliseconds

     Source: https://docs.oracle.com/cd/B19306_01/server.102/b14237/dynviews_1019.htm#REFRN30170

  • average read latency

     This component monitor fetches the value for average read latency per read request for all disks under ASM disk group, at any time. The returned value will only show the results since the last polling period.

     Unit: Milliseconds

     Source: https://docs.oracle.com/cd/B19306_01/server.102/b14237/dynviews_1019.htm#REFRN30170

  • average i/o read request

     This component monitors average number of I/O read requests for the disk group. The returned value will only show the results since the last polling period.

     Unit: Count.

     Source: https://docs.oracle.com/cd/B19306_01/server.102/b14237/dynviews_1019.htm#REFRN30170

  • average i/o write request

     This component monitors average number of I/O write requests for the disk group. The returned value will only show the results since the last polling period.

     Unit: Count.

     Source: https://docs.oracle.com/cd/B19306_01/server.102/b14237/dynviews_1019.htm#REFRN30170

 

 

Oracle Dataguard:
https://thwack.solarwinds.com/docs/DOC-203308

This template contains performance and statistics counters for Oracle Dataguard.

 

Prerequisites: Oracle client installed on the Orion SAM server. This is available from the SolarWinds customer portal[TK6] under Additional Downloads.

Credentials: An Oracle username and password with read access to the Oracle tables.

 

MONITORED COMPONENTS

Components without predetermined threshold values provide guidance such as "Use the lowest threshold possible" or "Use the highest threshold possible" to help you find an appropriate threshold for your application. For more information, see http://knowledgebase.solarwinds.com/kb/questions/2415

 

  • LOG APPLY GAP

     This component monitors the number of logs the secondary server has not yet applied.

     The greater the value, the lower the protection. The returned value will only show the results since the last polling period.

     Unit: Count

     Source:

     https://docs.oracle.com/cd/B14117_01/server.101/b10755/dynviews_1126.htm

     https://docs.oracle.com/cd/B14117_01/server.101/b10755/dynviews_1011.htm

     https://docs.oracle.com/cd/B13789_01/server.101/b10755/dynviews_1015.htm

     https://docs.oracle.com/cd/B13789_01/server.101/b10755/dynviews_1054.htm

  • Log Apply LAG

     This component monitors how long it is taking the secondary to apply logs.

     The returned value will only show the results since the last polling period.

     Unit: Seconds

     Source:

     https://docs.oracle.com/cd/B14117_01/server.101/b10755/dynviews_1126.htm

     https://docs.oracle.com/cd/B14117_01/server.101/b10755/dynviews_1011.htm

     https://docs.oracle.com/cd/B13789_01/server.101/b10755/dynviews_1015.htm

     https://docs.oracle.com/cd/B13789_01/server.101/b10755/dynviews_1054.htm

  • Log Destination error.

     This component monitors the count of error(s) that have occurred on any of the destinations while applying redo logs.

     Unit: Count

     Source:

     https://docs.oracle.com/cd/B13789_01/server.101/b10755/dynviews_1061.htm

     https://docs.oracle.com/cd/B14117_01/server.101/b10755/dynviews_1011.htm

 

The SolarWinds trademarks, service marks, and logos are the exclusive property of SolarWinds Worldwide, LLC or its affiliates.  All other trademarks are the property of their respective owners.

Content is key as new applications get released to the market, as well as new versions of products that have been out there for some time. Application templates are a critical component of what makes Server & Application Monitor (SAM) great and we’re constantly taking feedback on how to enhance the content we have and what additional content folks would like to see. The following post is part 1 of more to come on net-new and enhanced application monitoring templates for Server & Application Monitor. As always, if you have comments or feedback, please let us know and if there are any application templates you would like to see that we do not offer today, please let us know.

 

SAP HANA:

SAP HANA is a net-new addition to our library. Unlike many of our other templates, there are some prerequisites to get monitoring to work properly.

 

This template can be found on THWACK® at the following URL, or, if you have SAM, you can look at the application templates page, which connects to SAM.

SAP HANA 2.0.apm-template

From the server that will be polling your HANA instances, you’ll need the 32-bit or 64-bit HANA ODBC drivers. You should be able to download these from the SAP portal. You also need the ODBC credentials to access SAP HANA 2.0 Express Edition. Note that if you install the 64-bit version, you will need to update the template to use the 64-bit job engine vs. default 32-bit.

 

If you have an account for the SAP Support Portal (customer, partner, ask-your-administrator), just enter SAP HANA client in the search bar. Take 2.0 and select the operating system (such as Windows).

If you don’t have an SAP support account, you can also download the SAP HANA client from the Developer community, https://www.sap.com/developer/trials-downloads.htmlThis will direct you to the SAP store; it also requires an account but this one is free.


The metrics we are gathering for HANA include the following. (If you want more details on what the counters mean, how they are calculated, and any reference documentation, please see the links to the templates. In this case, for HANA,
SAP HANA 2.0.apm-template.)

 

  • CPU Utilization %
  • I/O Read Throughput in MB - DATA volume
  • I/O Read Throughput in MB - LOG Volume
  • I/O Write Throughput in MB - DATA Volume
  • I/O Write Throughput in MB - LOG Volume
  • System Memory Used %
  • Heap Memory Used %
  • Connections
  • Active Statements
  • Active Procedures
  • Table Lock Count
  • Record Lock Count
  • Blocked Transaction Count

 

Here is how this looks in SAM:

 

 

Enhanced Exchange 2016:

Next up is a set of enhancements to an existing template we already offer today, Microsoft Exchange 2016. We just added some new experience monitors as well as some component monitors within the template itself.

https://thwack.solarwinds.com/docs/DOC-203053
https://thwack.solarwinds.com/docs/DOC-203054
https://thwack.solarwinds.com/docs/DOC-203055
https://thwack.solarwinds.com/docs/DOC-203056

 

There are now four templates available for Exchange 2016.

  • Active Sync Connectivity
  • Edge Transport Role Counters & Services
  • Mailbox Role Counters & Services
  • OWA Form Login (PowerShell)

 

 

Prerequisites:

  1. WMI access to the Exchange server.
  2. Credentials: Windows Administrator on the target server.
  3. To run template “Exchange Active Sync Connectivity Template”:
      1. Exchange 2016 Management tool should also be installed on the machine. Once it’s installed, import this tool utility in PowerShell via this command:
        Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn;
      2. Double-click on Exchange Server installer. It will ask the folder where you need to save the extracted files. Once extraction is completed, go to the Scripts folder and run the script “new-testcasconnectivityuser.ps1”—this script creates the test user, which helps in fetching the output from the command “Test-ActiveSyncConnectivity” used in the script.
      3. “Test-ActiveSyncConnectivity” needs Client Access Server (CAS). You can find this server name by executing the PowerShell command “Get-ExchangeServer” and note the “Name” value.
      4. Test to ensure http://<Hostname>/powershell or https://<Hostname>/powershell should be working.
  4. To run template “Exchange 2016 OWA Form Login (PowerShell)”:
      1. Resolve the IP of the node this script will run against, make an entry of that IP in etc/hosts file.
      2. Test to ensure http://<Hostname>/owa or https://<Hostname>/owa should be working.

 

SQL 2016 on Windows:

You can read more about and download these two templates here.

https://thwack.solarwinds.com/docs/DOC-203050
https://thwack.solarwinds.com/docs/DOC-203051

 

There are now two templates available for SQL Server 2016 on Windows.

  • Analysis Services
  • Reporting Services

 

For SQL 2016 Analysis Services, we are collecting the following metrics/info.

  • Service: SQL Server Analysis Services
  • Cache: Direct hits/sec
  • Cache: Lookups/sec
  • Cache: Direct hit ratio
  • Cache: Current entries
  • Cache: Current KB
  • Cache: Inserts/sec
  • Cache: Evictions/sec
  • Cache: Misses/sec
  • Cache: KB added/sec
  • Cache: Total direct hits
  • Cache: Total evictions
  • Cache: Total filtered iterator cache hits
  • Cache: Total filtered iterator cache misses
  • Cache: Total inserts
  • Cache: Total lookups
  • Cache: Total misses
  • Connection: Current connections
  • Connection: Current user sessions
  • Connection: Requests/sec
  • Connection: Failures/sec
  • Connection: Successes/sec
  • Connection: Total failures
  • Connection: Total requests
  • Connection: Total successes
  • Data Mining Prediction: Queries/sec
  • Data Mining Prediction: Predictions/sec
  • Locks: Current latch waits
  • Locks: Current lock waits
  • Locks: Current locks
  • Locks: Lock waits/sec
  • Locks: Total deadlocks detected
  • Locks: Latch waits/sec
  • Locks: Lock denials/sec
  • Locks: Lock grants/sec
  • Locks: Lock requests/sec
  • Locks: Unlock requests/sec
  • MDX: Total NON EMPTY unoptimized
  • MDX: Total recomputes
  • MDX: Total Sonar subcubes
  • Memory: Cleaner Memory shrinkable KB
  • Memory: Cleaner Memory nonshrinkable KB
  • Memory: Cleaner Memory KB
  • Memory: Cleaner Balance/sec
  • Memory: Filestore KB
  • Memory: Filestore Writes/sec
  • Memory: Filestore IO Errors/sec
  • Memory: Quota Blocked
  • Memory: Filestore Reads/sec
  • Proactive Caching: Notifications/sec
  • Proactive Caching: Processing Cancellations/sec
  • Proc Aggregations: Temp file bytes written/sec
  • Processing: Rows read/sec
  • Processing: Rows written/sec
  • Processing: Total rows read
  • Processing: Rows converted/sec
  • Processing: Total rows converted
  • Processing: Total rows written
  • Storage Engine Query: Queries from cache direct/sec
  • Storage Engine Query: Queries from cache filtered/sec
  • Storage Engine Query: Queries from file/sec
  • Storage Engine Query: Avg time/query
  • Storage Engine Query: Measure group queries/sec
  • Storage Engine Query: Dimension queries/sec
  • Threads: Processing pool idle I/O job threads
  • Threads: Processing pool busy I/O job threads
  • Threads: Processing pool job queue length
  • Threads: Processing pool job rate

 

Here is how that will look in SAM:

 

For Reporting Services, we are collecting the following metrics/info:

  • MSRS Windows Service: Active Sessions
  • MSRS Windows Service: Cache Flushes/Sec
  • MSRS Windows Service: Cache Hits/Sec
  • MSRS Windows Service: Cache Hits/Sec (Semantic Models)
  • MSRS Windows Service: Cache Misses/Sec
  • MSRS Windows Service: Cache Misses/Sec (Semantic Models)
  • MSRS Windows Service: Delivers/Sec
  • MSRS Windows Service: Events/Sec
  • MSRS Windows Service: Memory Cache Hits/Sec
  • MSRS Windows Service: Memory Cache Miss/Sec
  • MSRS Windows Service: Reports Executed/Sec
  • MSRS Windows Service: Requests/Sec
  • MSRS Windows Service: Snapshot Updates/Sec
  • MSRS Windows Service: Total Processing Failures
  • MSRS Windows Service: Total Rejected Threads
  • MSRS Windows Service: Report Requests
  • MSRS Windows Service: First Session Requests/Sec
  • MSRS Windows Service: Next Session Requests/Sec
  • MSRS Windows Service: Total App Domain Recycles
  • MSRS Windows Service: Total Cache Flushes
  • MSRS Windows Service: Total Cache Hits
  • MSRS Windows Service: Total Cache Hits (Semantic Models)
  • MSRS Windows Service: Total Cache Misses
  • MSRS Windows Service: Total Cache Misses (Semantic Models)
  • MSRS Windows Service: Total Deliveries
  • MSRS Windows Service: Total Events
  • MSRS Windows Service: Total Memory Cache Hits
  • MSRS Windows Service: Total Memory Cache Misses
  • MSRS Windows Service: Total Reports Executed
  • MSRS Windows Service: Total Requests
  • MSRS Windows Service: Total Snapshot Updates
  • Report Server: Active Connections
  • Report Server: Bytes Received/sec
  • Report Server: Bytes Sent/sec
  • Report Server: Errors/sec
  • Report Server: Logon Attempts/sec
  • Report Server: Logon Successes/sec
  • Report Server: Memory Pressure State
  • Report Server: Memory Shrink Amount
  • Report Server: Memory Shrink Notifications/sec
  • Report Server: Requests Executing
  • Report Server: Requests/sec
  • Report Server: Tasks Queued
  • Service: SQL Server Reporting Services
  • Report Server TCP Port
  • Report Server: Bytes Received Total
  • Report Server: Bytes Sent Total
  • Report Server: Errors Total
  • Report Server: Logon Attempts Total
  • Report Server: Logon Successes Total
  • Report Server: Requests Disconnected
  • Report Server: Requests Not Authorized
  • Report Server: Requests Rejected
  • Report Server: Requests Total

 

SQL 2017 on Windows:

You can read more about and download the template here.
https://thwack.solarwinds.com/docs/DOC-203052

 

This template uses Windows performance counters to assess the status and performance of Microsoft SQL Server 2017 Analysis Services.

 

Prerequisites:

 

Below are the metrics and counters we will gather:

  • Service: SQL Server Analysis Services
  • Cache: Direct hits/sec
  • Cache: Lookups/sec
  • Cache: Direct hit ratio
  • Cache: Current entries
  • Cache: Current KB
  • Cache: Inserts/sec
  • Cache: Evictions/sec
  • Cache: Misses/sec
  • Cache: KB added/sec
  • Cache: Total direct hits
  • Cache: Total evictions
  • Cache: Total filtered iterator cache hits
  • Cache: Total filtered iterator cache misses
  • Cache: Total inserts
  • Cache: Total lookups
  • Cache: Total misses
  • Connection: Current connections
  • Connection: Current user sessions
  • Connection: Requests/sec
  • Connection: Failures/sec
  • Connection: Successes/sec
  • Connection: Total failures
  • Connection: Total requests
  • Connection: Total successes
  • Data Mining Prediction: Queries/sec
  • Data Mining Prediction: Predictions/sec
  • Locks: Current latch waits
  • Locks: Current lock waits
  • Locks: Current locks
  • Locks: Lock waits/sec
  • Locks: Total deadlocks detected
  • Locks: Latch waits/sec
  • Locks: Lock denials/sec
  • Locks: Lock grants/sec
  • Locks: Lock requests/sec
  • Locks: Unlock requests/sec
  • MDX: Total NON EMPTY unoptimized
  • MDX: Total recomputes
  • MDX: Total Sonar subcubes
  • Memory: Cleaner Memory shrinkable KB
  • Memory: Cleaner Memory nonshrinkable KB
  • Memory: Cleaner Memory KB
  • Memory: Cleaner Balance/sec
  • Memory: Filestore KB
  • Memory: Filestore Writes/sec
  • Memory: Filestore IO Errors/sec
  • Memory: Quota Blocked
  • Memory: Filestore Reads/sec
  • Proactive Caching: Notifications/sec
  • Proactive Caching: Processing Cancellations/sec
  • Proc Aggregations: Temp file bytes written/sec
  • Proc Aggregations: Current partitions
  • Proc Aggregations: Total partitions
  • Proc Aggregations: Memory size rows
  • Proc Aggregations: Memory size bytes
  • Proc Aggregations: Rows merged/sec
  • Proc Aggregations: Rows created/sec
  • Proc Aggregations: Temp file rows written/sec
  • Processing: Rows read/sec
  • Processing: Rows written/sec
  • Processing: Total rows read
  • Processing: Rows converted/sec
  • Processing: Total rows converted
  • Processing: Total rows written
  • Storage Engine Query: Queries from cache direct/sec
  • Storage Engine Query: Queries from cache filtered/sec
  • Storage Engine Query: Queries from file/sec
  • Storage Engine Query: Avg time/query
  • Storage Engine Query: Measure group queries/sec
  • Storage Engine Query: Dimension queries/sec
  • Threads: Processing pool idle I/O job threads
  • Threads: Processing pool busy I/O job threads
  • Threads: Processing pool job queue length
  • Threads: Processing pool job rate

 

The SolarWinds trademarks, service marks, and logos are the exclusive property of SolarWinds Worldwide, LLC or its affiliates.  All other trademarks are the property of their respective owners.

Applications talk to each other, and you should know who they are talking to

 

Applications constantly rely on communication between different servers to deliver data to end-users. The more applications end-users require to do their job, the greater the complexity of application environments and those communication based relationships.

With the release of Server & Application Monitor 6.6, we introduced an Orion Agent based feature, called Application Dependencies, which enables system administrators to quickly gain an understanding of which applications servers are talking to one another, as well as see related metrics, to help with troubleshooting application performance issues.

 

How do you enable it?

The ability to discover and map Application Dependencies is enabled by default. This allows SAM to actively collect inbound and outbound communication at the application process level. This is paired with an ability to collect connection related metrics (latency and packet loss), which is disabled by default. You can find all of the configuration options in the Application Connection Settings section of the Main Settings & Administration screen.

 

What does it show you?

At its core, Application Dependencies help you understand if application performance issues are associated with server resource utilization or network communication. For example, Microsoft Exchange is heavily dependent on Active Directory for authentication and other services. Application Dependencies show you the relationship, and the communication, by adding a few new resources in SAM.

 

The two main areas where you can see the Application Dependency information. One area is in a new widget that is available on application and node details pages. This widget will show you the discovered application dependencies, specific to that monitored application or node. Notice in the screen below that you can see where multiple Exchange servers have a dependency on the Active Directory server, ENG-AUS-SAM-62, and more specifically the Active Directory service that is running on it.

 

The second area where you can see Application Dependency information is in the connection details page, which is linked from the above mentioned connections widget. This will allow you to see all of the application monitors, and associated processes, process resources metrics, and ports, responsible for the discovered communication, between two specific nodes. You will also see the latency and packet loss data, if you have enabled the Connection Quality Polling component. The screen below shows the relationship between ENG-AUS-SAM-62 (Active Directory) and ENG-AUS-SAM63 (Exchange), in greater detail.

What’s going on under the covers?

There are two, new Orion Agent plug-ins that help deliver this new functionality. One is the Application Dependency Mapping plug-in, and the other is the Connection Quality Polling plug-in.

The Application Dependency Mapping plug-in is responsible for collecting the active connection data from the server. That information is then sent back to the Orion Server, where it is correlated with component monitor and node data, already being collected by SAM (Note: You must have at least one component monitor, like the process monitor, applied to the server). As SAM matches the collected data from the different application servers, it creates the connection details pages and populates the connection widget.

 

The Connection Quality Polling plug-in is responsible for a synthetic probe, which measures latency and packet loss. This accomplished by sending TCP packets to the destination server, on the specific port identified by the active connection information collected by the Application Dependency Mapping plug-in. It is important to note that the Connection Quality Polling plug-in includes the NPCAP driver for use with this synthetic probe.

 

If you would like to read more about how this feature works, you can find more information in the SAM administrator guide.

 

Is that it?

Application Dependencies is not the only feature that was released in SAM 6.6. You can read more about the other features in the release notes. You can also check out Application Dependencies, live in action, in the online demo.

Hopefully you saw my Sneak Peek blog post a couple weeks back on the Active Directory integration coming with 11.2 and are excited about it as much as I am.  If you haven't read it, I highly recommend checking it out. 

 

Also excited that the Release Candidate, (barring no last minute issues) should be available Monday.  The Release Candidate is a fully tested and supported release and you can upgrade to the RC from your previous version of DameWare.  Should you need assistance during the installation, feel free to contact SolarWinds support


If you are interested in the release candidate, either send me a direct message or please sign up here


Looking forward your feedback!

 

 

 

Coming off the release in December, in which we integrated DameWare into Web Help Desk, the team rolled straight into working on formal Active Directory integration as discussed here. With the product today, you can export a list of users from Active Directory (AD) and manually do a one-time import of those accounts into DameWare.  While this is helpful, as an Administrator of the product you still have to manage user passwords separately.

 

Based on feedback from our customers, we are enhancing this integration and I wanted to give everyone a sneak peek into how things are progressing now that we have been in beta for a couple weeks.

 

First, when you login to Central Server, you will notice the top ribbon menu is a bit different in that we added a new button and tweaked an existing button a bit as highlighted below.

New Nav.png

Let’s first walk through defining a new connection with our Active Directory server.  By clicking on the AD Import button, a wizard will be presented in which you can select if this sync/import will just be for a single time or if we want this to occur on a regular scheduled basis. Since we are leveraging Active Directory Groups, if you were to select synchronized, on the back end after the initial synchronization, then going forward we will check if new users have been added to the group since we last synchronized with Active Directory and automatically import that account into DameWare.  I will provide more details on how this works more specifically in a bit later in this post.

AD-Import-1.png

Next we specify the connection details for the Active Directory Domain, nothing out of the ordinary here to review and discuss with the exception that you can use the local domain, or any other domain for authentication.

AD-Import-2.png

Since we are leveraging Active Directory Groups, here is where we get to select one or more groups we want to import users from. For environments that have a large number of groups, we can auto filter down the list based on text typed into the dialogue below the group picker.

AD-Import-3.png

AD Groups have now been selected and the final step of the wizard allows you define which license is associated with each group and define the schedule in which we will synchronize with the Active Directory server.

AD-Import-4.png

We complete the wizard and an initial synchronization occurs if desired.  After the import is completed, you will now see a list of the users imported from AD.  Note the login name I highlighted is in domain\username format.

CS-Main.png

If you ever want to go back and edit a synchronization profile to change the schedule, groups to synchronize, etc. you can click on the AD Manager as highlighted in the first screenshot and you will be presented with a view of all the profiles that were defined and other information and actions as can be seen below.

AD-Manager.png

Your Active Directory accounts are now synchronized, so what will the experience now look like for your technicians using the product? If you are familiar with applications like SQL Studio, DameWare will have a similar experience in that you can choose either Windows or DameWare Authentication.  If you select Windows Authentication, then we will use the credentials you are logged into that machine with if you are logged into a domain.  If you “Remember last connection settings” and “Don’t show this again”, going forward when you launch the application it will perform a Single Sign On or SSO and automatically log you into the DameWare as long as that account has permissions in DameWare.

Login-Screen.png

Once logged in, if you look at the bottom of the application, as seen highlighted below, you will notice you are logged in as domain/username or in this case lab.tex\labuser.

AD-Logged-In-User.png

That’s it, pretty simple and straightforward.  We are currently running beta with a handful of customers, but if you have active maintenance and are interested in giving us some feedback, then please send me a direct message via thwack and we can set something up.

In talking with some of our more security focused and more tightly regulated customers from a compliance perspective; a common question I get asked is in regards to audit logging with DameWare.  With Mini Remote Control (MRC), there are a couple different options when it comes to logging.

 

By default, DameWare Mini Remote Control writes to the Windows Event Log.  The two events which MRC writes audit event are either attempts to connect to a remote host and disconnects from a remote host.  These Application Event Log entries contain connection information, along with specific information about the system the MRC user connected from and the username used to establish the MRC connection.

Event-Log.png

 

The next couple options are not enabled and configured by default, so for these to work, both the logging server and all remote systems must be running the MRC client agent.


If you already have MRC deployed in your environment and you want to enable this, you can configure the agents by either clicking on the highlighted icon within MRC or you can right click on the tray icon and select “Settings”.

UI-Setting.png

-OR-

Task-Menu.png

In the dialog you receive, as seen below, select the “Additional Settings” tab and click on the highlighted “Logging” button.

Agent-Setting-First.png

Once here you can either configure this agent log locally and/or log to a remote destination.  Double check and make sure the destination folder exists on the file system.  DameWare will automatically create the file, but only if the path exists.

Agent-Setting.png

If you have not deployed the DameWare agents on to your network yet, you can customize and configure the agents to have these settings by default.  In order to do this, you will need to create a new msi with our utility, which is installed by default and is called “DameWare Mini Remote Control Client Agent MSI Builder”.

 

Once you have this configured and are sending the audit events to a log file, using a comma separated file is recommended.  An example of what this would look like can be seen below.

CSV-File.png

If you have deployed and are using DameWare Central Server for over the internet or outside the firewall remote control sessions, the Central Server also writes various events to the Windows Event Log, such as licensing information, session connection and disconnection information.  In our upcoming release we will be adding active directory synchronization information.  If you need any further information on logging, you can also see a KB we have here.

 

I’m interested in hearing what other types of events or action you would like to see logged going forward, so please post any feedback to the comments section or you can always direct message me via thwack.

I am happy to introduce our latest free tool, Event Log Forwarder for WindowsIf you own an Orion family product or Kiwi Syslog, you may already be familiar with this tool, as we previously offered this as a free add-on or application you had access to as a customer.  Based on feedback from our customers and how much people love this tool we decided to make it free to all.

 

Many folks have dozens, if not hundreds of Windows Servers.  Trying to monitor the Windows Event Logs for specific errors, warnings, etc. is a pain point to ensure the servers and apps on it are running well.  Many folks may be running a Syslog server (like Orion SAM/NPM or  Kiwi Syslog) for gathering Syslog messages from your network equipment as an example or have a log management solution (like Log & Event Manager) for centralizing and analyzing all of your logs.  Event Log Forwarder for Windows helps these folks and is a lightweight app or agent you install on Windows machines which you care about looking for specific events.

 

A very basic example is failed login attempts to a Windows Server.  Someone mistypes a password and you get one or two here and there, no biggie.  However, if you see a spike and consistent pattern of failed login attempts, you are going to want to dig a bit deeper.

 

Simply define a subscription or what are the key events you care to know about and look for, as shown in the dialog below.

ELF2.png

 

When we find a match, we take that Windows Event and wrap it up as a Syslog message and based on the defined Syslog Facility you define to categorize this event, we send it off to one or more defined Syslog servers.  Depending on your environment we can send it as a standard UDP message or you can set it to use TCP as well for reliable delivery.

ELF1.png

 

That’s it, simple and easy.  Install on one Windows box or a thousand, it’s up to you.  SolarWinds Event Log Forwarder for Windows is another free tool from SolarWinds we hope everyone can use and enjoy and you can download it here.  If you have any questions or comments about this free tool, head on over to our thwack forum for this free tool.

In my many chats with customers, I’ve found they didn’t know we have tools that allow them to synchronize files across servers automatically – and we give it away for FREE!

Some history here, when we acquired Rhinosoft back many moons ago, they sold a crazy popular FTP Client called FTP Voyager.  As a part of the acquisition we decided to make this free to the world.  A hidden gem within this product was their scheduler set of functionality, which is a service that allows you to automate file transfer operations on a scheduled basis.


Once you have installed FTP Voyager, you can open this by right clicking on the task bar and selecting “Start Management Console”.

TrayMenu_On.png

 

Once you launch it you get a dialogue with some options to start from.

Main.png

 

Backup & Synchronize are purpose built wizards which ultimately create the same thing as the first option, which is create a task.

Within a task you can set it to perform many tasks and behave in different ways, for example

  • Tasks starting additional tasks
  • Email notifications on success, failure & task completion
  • Tray icon balloons for custom alerts
  • Multiple transfer sessions
  • Conditional event handling
  • Optional trace logs (with log aging) for each task
  • Custom icons & colors for each task

Task-Properties.png

The Backup wizard backs up files or folders and allows you to restore lost data due to hardware failure, software glitches, or some other cause for data loss. Many organizations perform backups of day to day activities to insure minimal downtime in case a disaster like a corrupt hard-drive occurs.

Backup.png

Synchronization focuses on keeping folders and files from/to your local machine to/from a remote server in sync. For example, web developers may use synchronization to maintain a local copy of an entire website. This allows the web developer to make changes to the website offline, and then upload those changes when they are complete.

Sync.png

I can already read your mind and predict your next question via the power of thwack.

               “This is awesome Brandon, but how do I do this in bulk or push out to many machines?”


Here’s the bare minimum you would need to have for a fully configured FTP Voyager Scheduler configuration with no end user interaction.

  1. Deploy FTP Voyager via your favorite app deployment application or leveraging GPO
  2. The registration ID: C:\ProgramData\RhinoSoft\FTP Voyager\FTPVoyagerID.txt
  3. Pre-configured Scheduled tasks: C:\ProgramData\RhinoSoft\FTP Voyager\Scheduler.Archive
  4. Pre-configured site profiles for Scheduler: C:\ProgramData\RhinoSoft\FTP Voyager\FTPVoyager.Archive
  5. Pre-configured transfer settings for Scheduler:  C:\ProgramData\RhinoSoft\FTP Voyager\FTPVoyagerSettings.Archive

 

This assumes that all machines receiving these files use the same file system structure defined in the tasks, that all required folders for those tasks already exist, etc.

    NOTE: When doing #3 and #4, you must copy them from the same machine, as the items configured in step #3 uses values present in #4 to link the two together. If different machines are used to generate the data, the values will not link properly.


That’s it, simple as that.  Whether you want to deploy this on one of your machines or many in your environment, now you can have your files automatically backed up or synchronized to your Serv-U server for safe keeping.

One evening this week, I was reading the latest in tech news on Engadget and Re/code about yet another organization whose network and data had been compromised. With businesses like Target, Home Depot, and even JP Morgan Chase falling victim to Advanced Persistent Threats I wondered what controls, processes and procedures these organization had to monitor suspicious activity and the sharing and storing of sensitive files. Add concerns with compliance requirements like those mandated by PCI and HIPAA, and you end up with a severe migraine.

 

There are logs, logs everywhere with tons of data and there are solutions in the SIEM space which analyze all of these logs from a security perspective, but this is typically reactive in nature. Organizations need proactive protection of data while it resides on the corporate networks – they need encryption of data at rest.

 

Reality is, you need protection, both in transit and at rest.  Serv-U MFT Server protects data while it is in transit using SSL and SSH. Serv-U Gateway, the reverse proxy add-on which prevents the storage of data in the DMZ, further reduces risk.  However, data-at-rest encryption is another important part of the picture, protecting data while it resides on network storage or on a server.

 

Image 1.png

Serv-U.png

There are several options available to customers who are seeking to provide this additional layer of security on their network. Typically, encrypted file systems are the optimal choice as they are usually easiest to deploy. Depending on the platform you want to secure, there are a couple different options.

 

Image 3.png

You can leverage EFS or Encrypting File System, which is a feature already built into many Windows versions including the newest versions of Windows and Windows Server.  There is another feature within Windows in regards to file encryption called BitLocker, but don’t confuse this with Cryptolocker. You can read more about BitLocker vs. EFS here.

EFS.jpg

If you are looking for non-Windows options or even other Windows options that are not created by Microsoft, historically many folks used an open source program called TrueCrypt, but active development for this recently ended.  You can still use this product, but just know that any new issues will not be fixed.  With this being said, this code base has been forked and in the process of being turned into a free product called CipherShed, which will work on Windows, Mac OS and GNU/Linux.

 

If any of the above don’t fit the bill for you, here are some other options for you to look at and consider.

 

Combining Serv-U with one of the options listed above ensures that you data is completely secure, both in-transit and at rest.

Over the coming weeks I will be posting a series of blog posts on common misconception, questions, issues etc. that I have run into over the years that we have been offering the Failover Engine.  The most common question I do get asked is "what exactly is the difference between high availability vs. disaster recovery".

 

I will provide a more in depth explanation below, but the best and quickest way to remember this is:

  • High Availability = LAN
  • Disaster Recovery = WAN


Some groundwork before I jump into the more in depth explanation, the Failover Engine works in a Active-Passive setup, meaning only one server has the SolarWinds services started and running.  The Failover Engine is not an Active-Active solution, meaning both servers have the SolarWinds services started and running.  With that in mind, for this post I will refer to each server as the following

  • Primary or Active server = SolarWinds services are active and running
  • Secondary or Passive server = SolarWinds services are not active and running

 

High Availability

As also illustrated below in the first image, the High Availability (HA) role is normally deployed in a LAN where communications are configured with the Public IP Address being shared by both the active/primary and passive/secondary servers. The active/primary server makes the Public IP visible and available to the network while the passive/secondary server leverages a packet filter installed by the Failover Engine on to hide the server and prevent network access since two machines with the same IP cannot be on the network at the same time.


In the event of a failure on the active/primary server the packet filter is removed from the passive/secondary server making it now assume the role as the active/primary server while simultaneously adding the packet filter to the server that was originally the active/primary server making it the passive/secondary server. Since both servers are sharing the Public IP address, DNS updating is not required.

 

SWBlogLAN.png

Disaster Recovery:

When deployed in a Disaster Recovery role, the active/primary server and the passive/secondary server operates over a Wide Area Network (WAN) in different subnets. As a result, the active/primary and passive/secondary servers are configured with different Public IP addresses. In the event of a failover, the Failover Engine automatically updates DNS with the IP address of passive/secondary, so to the end users they just continue to access the SolarWinds server with the same DNS name they always use.

SWBlogWAN-1.png

Any questions or comments, please ask in the comment section.

Wait no more, the Enterprise Operations Console or EOC Release Candidate is here with some goodies.

 

Enhanced Module Support

With this release we added support for both User Device Tracker (UDT) and IP Address Manager (IPAM), which you can see below for each.

UDT.jpg

IPAM.jpg

Support for Orion Groups

We already support Orion Network Performance Monitor (NPM) & Server & Application Monitor (SAM) in EOC, but we have added support for a feature of theirs called Groups now into EOC as well.

Groups.jpg

New Look & Feel

Orion introduced tabs a release or two ago and with this release EOC now has them as well.  We also took some customer feedback in which users had difficulty determining if they were still in EOC or had left EOC into the given Orion server they had drilled into.  This should not occur anymore as the color scheme should be clear.  If you see the white header, you are in EOC and if you see the black header, you have drilled into an Orion server.

 

We have also added better error handling to let you know if for some reason we have lost polling connectivity with any of the Orion servers with banner notifications as you can see below.

EOC-1.jpg

 

If you are a customer under active maintenance, you should see the EOC Release Candidate or RC in your Customer Portal.

 

Release Candidates are fully supported by our support staff, so you can call in with any issues and you can also post questions, comments etc. on the forum here

I am pleased to announce the General Availability of Engineers Toolset 10.9.

 

LAUNCH PAD – THE NEXT GENERATION

With this release, we have expanded on a concept we introduced a while back called the Launch Pad, but this one is on steroids.  Some things you will notice right off the bat are a Google-like search to help guide you in finding the right tool to solve the problem you are currently working.

Second is organization.  As you see on the left hand side with the folders, these are customizable and you can even create your own folders and organize which tools are in them in a way that makes sense to you and how you work.

This leads me to the third and one of my favorite things about the new Launch Pad - the ability to import other tools.  Ex. If you own DameWare MRC or use PuTTY or any other tool outside of toolset, you can import or link them to the Launch Pad, which includes entering a description (which is then exposed to the search described above) and adding them to the folders.

The new Launch Pad should be your one stop shop for all your tools based troubleshooting needs, whether the tool comes from SolarWinds, is Open Source, or you purchased from another vendor.


Toolset 10.9.png


BUT WAIT, THERE’S MORE…..

For many years, many of the older tools only worked with Cisco. Which back in the late 90’s made sense, but this is a different world today.  With this being said, we have expanded device support for many of our tools to other Cisco OS’s but also Juniper, which was the most highly requested vendor.  Going forward we plan to add more based on your demand. 


Juniper Support (JunOS)

  • Interface Monitors
  • CPU monitoring
  • Memory Monitoring
  • Router CPU Load
  • Advanced CPU Load
  • Netflow Realtime
  • Switch Port Mapper
  • IP Network Browser
  • Neighbor Map

Nexus Support

  • Interface Monitors
  • CPU Monitors
  • Memory Monitors
  • Router CPU Load
  • Advanced CPU Load

 

With any release there are also bug fixes, so head over to the customer portal to download this version if you are on active maintenance.

Filter Blog

By date: By tag:

SolarWinds uses cookies on its websites to make your online experience easier and better. By using our website, you consent to our use of cookies. For more information on cookies, see our cookie policy.