# Understanding Analysis Count vs. Incident Count
Licensing is based on the number of analyses performed. However, within the tool interface you will see incident count displayed. This difference can sometimes raise questions or cause confusion. To make it clear, here’s how analysis and incident counts are related.
# Relationship between Analysis and Incident
Each incident represents one complete analysis session, but within that session the system can perform up to four different analyses:
GC log analysis
Thread dump analysis
Heap dump analysis (if provided or enabled)
Application log analysis
# How it works in practice
| Files provided | Analyses performed | Incident shown in tool |
|---|---|---|
| Uploading individual JVM dump | 1 (GC) or 1 (TD) or 1 (HD) or 1 (Applog) | 1 incident |
| GC + Thread Dump + App Logs | 3 (GC + TD + App Logs) | 1 incident |
| GC + Thread Dump + Heap + App Logs | 4 (GC + TD + HD + App Logs) | 1 incident |
# yc-360 Script Scenarios
When using the yc-360 Script, the number of analyses depends on whether the heap dump flag is enabled:
Heap dump flag enabled → Four analyses (GC, thread dump, heap dump, application logs) = 1 incident
Heap dump flag disabled → Three analyses (GC, thread dump, application logs) = 1 incident
# Licensing Depends on Analyses, Not Incidents
Licensing is always based on the number of analyses performed, not on the incident count shown in the tool.
In short:
1 incident = up to 4 analyses
Whether the system analyzes 1, 3, or 4 dumps, it is always represented as a single incident in the tool.
For licensing and usage tracking, always consider the analysis count as your basis.