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’:
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.
Hi,
Yes, the collection plugin supports HA log structure.
Regards,
David
Is it safe to assume this is compatible with HA environments (i.e., login information will be retrieved for all app servers)?
Thanks
v1.1.1 Release Notes
You can request to roll back to an earlier version of a plugin via a Support Case, or alternatively there is now a newer version of the plugin (2.2.11) that fixes this issue.
Thanks David.
We are using version 2.2.10 of the Excel Tools. Since we are using Appian cloud I guess there is no easy way to move to an older version of the plugin.
Hi, are you using v2.2.10 of the Excel Tools plugin? I was able to replicate this issue (with MariaDB but I think this will apply to MySQL too) using v2.2.10 -> "Date Format must be one of the following 'yyyy-MM-dd', 'yyyy-MM-dd HH:mm:ss', 'HH:mm:ss'". I believe this is an issue with version 2.2.10 of the Excel Tools plugin, whereby the Import CSV to DB smart service fails to properly import dates. You should be able to address this by moving to the previous version (2.2.9) of the Excel Tools plugin.
I'm running into an issue when running a collection run. The node 'Import CSV to Audited Logins table' goes into error with the following message: "Date Format must be one of the following 'yyyy-MM-ddTHH:mm:ssZ','yyyy-MM-dd', 'HH:mm:ss'"However, the format in the csv contains date in the format "2020-12-14 08:00:59"
It could be that our DB's are upgraded to MariaDB which is causing this issue.
4) Currently (v1.0.1) the only export functionality included is the high level Usage by Business Entity report, which can be exported via the "Download usage by business entity" download link on the Usage Reports > Usage By Business Entity report.
3) The data collection component will collect a maximum of the last 30 days worth of login information. If you have run the collector in the last 30 days, it will collect the login information since the last time it ran. Over time as the collector is run and the collections loaded to the reporting component, you will build up login data across a longer period. The application doesn't currently support loading older, compressed login audit data. This doesn't prevent the allocation of users to licence pools (that is based on the most recent group membership collections). But it does mean that the login information displayed in the app will only become more meaningful as collections are built up over time.