Appian Usage Insights

Overview

Gain insights into your Appian usage with an application suite specifically designed to cater for complex environment topologies and heterogenous license contracts.

Key Features & Functionality

With ‘Appian Usage Insights’:

  • Model your license contracts in the application through configuration only - no additional development required!
  • Cater for Cloud, self-managed or a mix of installation topologies.
  • Designed with the enterprise in mind, support large numbers of Appian environments, user accounts and keep track of license consumption over time.
  • Model your internal license usage using license pools mapped to user-definable business entities.
  • Visualize usage the way you want to:
    • Usage by business entity.
    • Usage by license type.
    • License pool membership.
    • License pool logins.
    • License pool membership (which user is in which license pool and, ultimately, which one consumes an actual license).
    • Logins by user (over time).
    • Capacity planning (allocated license count over time).

For more information, see https://community.appian.com/w/the-appian-playbook/2198/appian-usage-insights-faqs

Usage of this application does not permit your organization to exceed its licensed usage requirements. Your organization is required to maintain compliance with your licensing terms, and report any non-compliance to Appian per the terms of your organization’s contract with Appian.

Anonymous
Parents
  • Could you please check and confirm us about these points regarding "Appian Usage Insights Data Collector" application.

     -Data collection time period. 

    -Whether data collection can be done multiple time or not. 

    We already tried to change the value of constant "LMA_DC_INTEGER_LOGINS_INITIAL_HISTORY_HORIZON" from default value 30 days to required value 365 days, but we are not getting the expected result. Also, we have observed a strange behavior- In Data package login details are capture When first time data collection is done on a particular day, but if again data collection is done on same day then no login details are being exported to the data package. 

  • For Cloud sites, 30 days is the max as after that logs are compressed and the plugin does not collect data from compressed logs. I wouldn't recommend running collection multiple times per day - usually you'd configure this somewhere between 7 and 30 days depending on your reporting needs.

Comment
  • For Cloud sites, 30 days is the max as after that logs are compressed and the plugin does not collect data from compressed logs. I wouldn't recommend running collection multiple times per day - usually you'd configure this somewhere between 7 and 30 days depending on your reporting needs.

Children
No Data