Basic Usage Reporting

When usage reporting is turned on, the following details are reported back to LabKey:

  • Low Level Reporting
    • Build number
    • VCS (svn) URL, if known
    • OS name
    • Java version
    • Java vendor and vm name
    • The max heap size for the JVM
    • Tomcat version
    • Database platform (SQL Server or Postgres)
    • DB version
    • Flow temp table count
    • JDBC driver
    • JDBC driver version
    • Unique ids for server & server session
    • Enterprise pipeline enabled?
    • Was a graphical installer used?
    • Total users
    • Total users logged in in last 30 days
    • Total project count
    • Total folder count
    • Distribution name
    • Configured usage reporting level
    • Configured exception reporting level
    • Total logins in last 30 days
    • Total logouts in last 30 days
    • Average user session length in last 30 days
    • Number of days in the last 30 in which user logged in

  • Medium Level Reporting: Includes all of the information from "Low" level usage reporting, plus:
    • Web site description
    • Site admin email
    • Organization name
    • Site short name
    • Logo link
    • List of installed modules
    • Number of hits for pages in each module
    • Number of TargetedMS runs
    • Number of folders of each folder type
    • ETL run count
    • SQL dialect count for external data sources (MS SQL, Postgres, Oracle, MySql, SAS)
    • Assay design and run counts
    • Sample Set counts
    • Total List Count
    • Study count
    • Dataset count
    • Auto reloaded study count
    • Report type counts
    • Survey design count
    • Survey taken count
    • (For Premium Editions) Folder counts for PHI settings usage (terms of use, PHI activity set, PHI roles required, PHI query logging behavior)

Exception Reporting

When exception reporting is turned on, the following details are reported back to LabKey:

  • Low Level Reporting
    • Build number
    • VCS (svn) URL, if known
    • OS name
    • Java version
    • The max heap size for the JVM
    • Tomcat version
    • Database platform (SQL Server or Postgres)
    • DB version
    • JDBC driver
    • JDBC driver version
    • Unique ids for server & server session
    • Enterprise pipeline enabled?
    • Was a graphical installer used?
    • Distribution name
    • Configured usage reporting level
    • Configured exception reporting level
    • Stack trace
    • SQL state (when there is a SQL exception)
    • Web browser
    • Controller
    • Action

  • Medium Level Reporting: Includes all of the information from "Low" level exception reporting, plus:
    • Exception message
    • Request URL
    • Referrer URL

  • High Level Reporting: Includes all of the information from "Medium" level exception reporting, plus:
    • User email

Resources

Related Topics

Discussion

Was this content helpful?

Log in or register an account to provide feedback


previousnext
 
expand all collapse all