Blog

Application Usage Metering

uberAgent has been pretty good at monitoring applications for some time. It is capable of auto-grouping processes to applications and showing IOPS and other stats per application in addition to per process. All this gets even better with application usage metering.

What is Application Usage Metering?

With uberAgent’s application usage metering you are able to answer annoying questions like these:

  • We need to test our applications prior to the migration to the new OS. For starters, how many different applications do we have?
  • We have got 140 licenses for product Z. Is that enough?
  • We are ordering new servers for application A. We need 1 CPU per user – how many CPUs do we need in total?

In other words, application usage metering helps with resource planning, license compliance and sizing.

Resource Planning

Do you need to know how many applications you have? Do you need to compare usage numbers of applications or sort them according to popularity? uberAgent has the perfect dashboard for you:

uberagent-application-usage

As always, the displayed time range can be chosen freely.

License Compliance and Sizing

Whether you need to check if you have the right number of licenses for a specific application or want to plan a new deployment: it is often necessary to know application usage over a specific period of time. Nothing simpler than that. Just click any row in the table above and you will see a screen similar to this one:

uberagent-application-usage-over-time

This tells you exactly what the maximum number of users of a specific application was and how often that was reached.

Comments (4)

  1. Diego says:

    does this tool also logs which user is using an specific application? I mean the user ID, not just only the amount of users per app.

    1. Helge Klein says:

      Yes, uberAgent logs which user (ID) runs which application when.

      1. Diego says:

        Then can we build reports of user IDs accesing “X” application between 2 dates for instance? Thanks.

        1. Helge Klein says:

          Yes, absolutely. Take a look at the fields uberAgent collects for the sourcetype uberAgent:Application:ApplicationUsage. In addition to the timestamp (not listed as it is part of every Splunk event) and the host machine (same) we collect the application name, the application version, the user name (format: domain\user) and even the name of the remoting (RDS/ICA) client the user might be connecting from. The latter is important for MS Office licensing, for example.

Leave a Reply

Your email address will not be published. Required fields are marked *