Skip to main content

IDE Usage KPI

The IDE Usage Over Time KPI provides visibility into how your development teams are using different Integrated Development Environments (IDEs) to trigger scans. It highlights both:

  • The number of scans triggered from each IDE

  • The number of distinct users initiating those scans

This data is broken down by IDE type and visualized over time to help track usage trends and developer engagement with scan tools.

This KPI helps you answer:

  • Which IDEs are most commonly used for scans?

  • How has IDE usage evolved over time?

  • How many unique users are actively scanning from each IDE?

What It Shows

The KPI tracks two key metrics:

  • Number of scans: Total scan executions from each IDE, over time.

  • Number of distinct users: Unique users who triggered at least one scan from each IDE, over time.

Supported IDE Categories

Scans are grouped into the following IDE categories:

  • Visual Studio Code

  • Visual Studio

  • JetBrains (e.g., IntelliJ IDEA, PyCharm, WebStorm)

  • Eclipse

  • Others – any unsupported or unrecognized IDEs fall into this group.

Timeframe and Granularity

This KPI uses the dashboard's global timeframe filter to control the data range and auto-adjusts granularity for clarity and performance:

Timeframe

Data Grouped By

Last day

Every 2 hours

Last week

Daily

Last month

Every 3 days

Last 3 months

Weekly

Last 3 months

Every 3 weeks

Last year

Monthly

For example, selecting Last 3 months will display weekly data points per IDE.

Use Cases

  • Adoption tracking – Spot trends in IDE popularity across teams.

  • Usage optimization – Identify IDEs that may need better support or documentation.

  • Developer engagement – Measure how many users are actively scanning and from which tools.