Insights
Open Insights in the main menu to review analysis activity, app quality trends, and the share of available apps analyzed by QSDA. When UI authentication is active, the Project Manager role is required. The reports are built from QSDA's analysis history, which is separate from the Collections List: deleting a collection does not delete its history entry.
Choose From and To dates, set Include deleted, and click Refresh to apply these filters. Include deleted is selected by default. Imported collections were analyzed elsewhere and are excluded from this installation's history reports.
Use Export next to Refresh to download the raw history for the date range as an Excel or CSV file. The export uses the From, To, and Include deleted values as currently set, even before you click Refresh; the History tab's grid filters do not apply. It contains one row per recorded run with every history field. Flag counts appear as FlagCount, the total excluding ignored flags, and InfoFlags, WarningFlags, and ErrorFlags, the totals at each level.
Trends
The Trends tab answers four questions about the apps QSDA has analyzed. Use the controls above the report to narrow it:
- Qlik server and Space / Stream - Limit the report to some servers or spaces/streams; multiple selections are supported.
- Period - Report by Month, Quarter, or Week. Date filters bound the periods shown. Earlier analyses can still contribute to a snapshot or a comparison with an app's previous analysis.
- Flag levels - Select which flag levels (Info, Warning, Error) are counted.
- Targets - Set the report targets. See Targets.
App quality is a snapshot at the end of each period: every app counts once, using its latest successful analysis.
Is the portfolio getting better?
Headline tiles summarize the latest snapshot:
- Apps analyzed - Apps in the snapshot, and how many were first analyzed in the date range.
- Apps scoring 75 or more - The share of scored apps with a healthy score, with a progress bar against the healthy apps target.
- Apps with errors - Apps whose latest analysis has Error level flags. The bar shows their share of analyzed apps.
- Apps improved - Re-analyzed apps whose latest score is higher than their first. The bar shows their share of re-analyzed apps.
- Flags resolved - Net flags removed between each re-analyzed app's first and latest analysis. A negative value means flags were added.
Three charts follow: Score bands (% of apps) splits apps into below 50, 50 to 74, and 75 and above; Flags resolved vs introduced compares each re-analysis with the app's previous analysis; and App quality, average score plots the portfolio average with a target line at 75.
A change in the portfolio average can reflect new apps entering the portfolio. Changing flag definitions or levels can also change scores and counts without an equivalent change to the Qlik app. Scores are recomputed for every recorded analysis with the current Analysis Scoring targets and weights, so a scoring change applies to the whole history.
What should developers fix next?
Flag types over time is a heat map of open flags in the latest analysis of each app at each period end, grouped by level. A falling row means the flag type is being fixed faster than it is introduced. Select an app in the apps grid below to show only that app's flags; click the x on the app filter to return to all apps.
Most common flags in first analyses shows the share of apps that had each flag type the first time they were analyzed: candidates for developer guidance or standards. Average score of new apps at their first analysis moves only when developers change their habits.
Which apps need attention?
The apps grid lists each app in the latest snapshot, lowest score first. An app not analyzed recently shows a warning on its Last analyzed date. Sort, filter, or resize the columns; select a row to filter Flag types over time to that app.
How is QSDA being used?
Analyses run splits each period's analyses into first-time and re-analyzed apps. Active users splits users into new and returning; a new user ran their first analysis in the period. The Users grid lists each user's analyses, distinct apps, re-analyses, and first and last analysis dates in the date range.
Targets
Click Targets to set the targets used in the report. Targets are stored on the QSDA server and apply to everyone who views the report.
- Target share of apps scoring 75 or more (%) - Marks the target on the Apps scoring 75 or more tile and shows whether it is met. Default 80.
- Days without analysis before an app is flagged as not analyzed recently - Sets when the apps grid warns on an app's Last analyzed date. Default 90.
Enter 0 for no target: the tile shows its bar without a target, or no app is flagged as not analyzed recently.
Coverage
Select a connection on the Coverage tab. QSDA compares the apps currently available to that connection identity with recorded analysis requests.
Selecting a connection makes it your active connection, as selecting it on the Apps page does. If the connection requires a Qlik sign-in, click Sign in to Qlik; after you sign in, QSDA returns to the Coverage tab and computes coverage for that connection.
The report shows available apps, apps analyzed ever, recent analysis coverage, a breakdown by space or stream, and Apps never analyzed. Expand a row in By space or stream to list the analyzed apps in that space or stream with their Last analyzed date. The available-app list follows the connection's access and filtering; it is not a tenant-wide inventory independent of that identity. An app counts as analyzed when history records an analysis of it on the connection's server, through any connection to that server, as on the Apps page. Coverage uses all recorded history rather than the From/To date filters.
Analyzed ever counts an available app with any retained history entry, including a queued, failed, or cancelled request. Apps never analyzed therefore means apps with no recorded request; it is not a list of apps without a successful analysis. The Last 30 days and Last 90 days counters count successful (Ready) analyses in those periods.
Deleted collections can still contribute their retained history. Apps previously analyzed on another installation and then imported do not contribute. Purging old history can reduce the reported coverage. The apps-never-analyzed grid supports filtering and sorting, with Export (Excel or CSV) and Columns in its toolbar.
Start an analysis
You can start an analysis of an app directly from Apps never analyzed:
- Click the wrench icon beside the app name to open the New Analysis card.
- Adjust the analysis options. The Bookmark list shows the app's bookmarks from the coverage connection.
- Click New Analysis to start collecting and analyzing the app.
The analysis runs on the coverage connection. If your Qlik session has expired, QSDA opens the sign-in page instead of starting the analysis; sign in, then start the analysis again.
When the analysis starts, a message above the grid confirms it, and you can follow its progress on the Apps page. The App leaves the Apps never analyzed grid. If the analysis cannot be started, the app stays in the grid and an error message appears; see the UI log for details.
History
The History tab lists recorded runs with their app, server, user, request source, status, timings, flags, scores, and other metrics. Failed or cancelled runs can be reviewed alongside successful analyses. Show additional columns using the column chooser.
Sort, group, or filter the grid to investigate activity. Right-click a data cell to Copy cell value; supported columns also offer Filter to this, retaining filters on other columns. Use Export in the toolbar to download the grid to Excel or CSV, and Columns to choose columns. The grid export contains the visible columns and filtered rows; use the page's Export for every field of every run in the date range.
Upgrades
On upgrade, QSDA backfills history from collections still present in the repository. This runs in the background, so reports may fill in after startup. It cannot reconstruct collections deleted before history recording was introduced.
CLI reporting
Use history list, history summary, history coverage, and history export for scripts and automation. See CLI history commands for filters and examples.