> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/reporting-framework/standard-reporting-package-release-7-4.md). # Standard Reporting Package (Release 7.4) ### Introduction The Standard Reporting package is included in client installations to give access to basic user session information such as sessions over time, sessions by application (for when client installations use multiple packages), usage (minutes) per user, etc. It also provides on screen and download access to the application logging records for more detailed review as necessary. This application is based on the LogicNets Reporting framework, and can therefore be expanded on to include a custom set of reports in addition to those provided as a courtesy. ### Filters This package comes with a set of predefined filters for selecting a subset of reporting data, as follows: * Report type (see below for descriptions) * Date range filter * Package filter, which allows you to drill down to reporting by application. This can be useful in implementations where there are multiple "protocols" mapped in LogicNets, as you could review usage stats for each one individually or overall ### Output Formats Reports are generated on screen, and with the HighCharts plug-in license, reports can be viewed as graphics, and exported as PDF, image files or CSV format. ### Data Scope, Archive & Security The Reporting package will recap application logs for the environment it is installed on. In the event that your solution involves multiple installations that require aggregation of logging data, feature 1 below will be useful. Over time, the underlying data table and views contain an increasing amount of data. To insure the system runs smoothly over multiple years of logging, feature 2 below is useful. 1. set up an automated process to periodically copy over the data to an alternate database outside of the LogicNets installation. 2. define the data removal timeframe and automatically clear out records no longer required for current reporting You could define this to keep a rolling 12, 18 or 24 months of data, for instance ### Advanced Business Reporting Note that some clients have utilized the LogicNets Assessment framework with underlying business tables instead, as an alternative to this framework. The Assessment framework executes custom modelled logic, and is suitable for detailed business reporting where a wide range of filters might be required. Speak to your LogicNets Project Manager about the best approach to building your reporting suite. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/reporting-framework/standard-reporting-package-release-7-4.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.