Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Following are the release details:
Latest Release- September 2021 - New Trends (Global Trends and Project Trends) dashboard, and more
June 2021- Support for new Social Media Metrics data source, and more
May 2021- Support for GitHub reviews, Google groups, Circle CI data sources, and more
The LFX Insights, September 2021 release delivers support for the new Trends dashboards that provides a comprehensive analytics of project performance, in the form of metrics, for all projects and project-groups. The metrics computed for the trends dashboard are more focused towards the code development areas such as, contributors, commits, lines of code, change requests, and issue management.
A global trends dashboard, the default landing page, for LFX Insights shows data aggregated across all the onboarded projects on LFX Insights. These data visualizations help project teams understand project performance and monitor the health of the project.
Global Trends: Shows aggregated performance data of all projects onboarded to Insights.
Project Group Trends: Shows aggregated performance data of all sub projects under the project group or foundation.
Individual Project Trends: Shows aggregated performance data of the individual project.
Project Card View: You can still see the old project card view by clicking View All Projects tab or search for the project using Search Projects filed.
Enhancement of project and project group landing page: The project and project group landing page shows the Trends dashboard when you click on a project card. This makes it easier to view aggregated metrics data for a project group, and to view sub groups under the project group.
You can view all the sub projects under a project group, navigate to the sub project page by clicking a sub project, and search for a sub project using the Search project field.
High level aggregated all-time stats at the project level: The aggregated statistics across key code and ecosystem related metrics at each project level are displayed which is an extension to the previous high level statistics that were available only at the project group level.
New Navigation menu: Effective changes to the navigation menu to clearly reflect the data sources under each category. For example, a new menu option called Collaboration Metrics is added that includes data sources that fall under Chat, Mailing Lists and Documentation categories while Earned Media is available as a separate option.
The Summary dashboards are available, as before, under each menu option for Technical Metrics and Collaboration Metrics respectively.
Insights platform shows Trends dashboard, and project and project group cards, in alphabetical order, that show relevant data associated with the project or project group. Navigate to a project or project-group to see the overall project activities.
Global Trends: Shows overall project performance for all project-groups and projects.
View All Projects: Lists all the projects onboarded to LFX Insights. Project group card displays stack of individual projects..
Compare Projects: Lets you compare key code related metrics for a project or between projects.
Search projects field: Lets you search a project or project group.
Enroll Project: Lets you enroll a project into LFX Insights by creating a support ticket on LFX Help Center.
Get Help: Click Doc to navigate to the Insights user documentation page, and Support to create a support ticket on LFX if you face any issues with LFX Insights.
A project is a standalone project maintained by The Linux Foundation. Under View All Projects, click the project name or Go to Overview to navigate to the project dashboard.
Each project card shows the following information:
Project name identifies the project by name.
Description briefly describes the project. Click the excerpt to see the entire description.
Contributors shows the total number of contributors to the project.
Contributions shows the total number of lines of codes that are changed in the project. It includes lines of code added, modified, and deleted.
Commits shows the total number of commits to the project.
Repositories shows the total number of repositories created for the project.
Lines of Code shows total number of lines of code added and modified for the project repository.
A project group is a group of individual projects. Click the name or click Go to Projects to see the trends dashboard and sub-projects under the project group. For details, see Project Group. To view the sub projects of a project group, and navigate to a sub project, click View Sub Projects from the top right corner to view the list of sub projects.
Each card shows the following information:
Name of the project group.
Description briefly describes the project group. Click the excerpt to see full description.
Contributors shows the total number of contributors to the project.
Contributions shows the total number of lines of codes that are changed in the project. It includes lines of code added, modified, and deleted.
Lines of Code shows total number of lines of code added and modified for the project repositories.
View Identities and Affiliations: Displayed to only Administrators after they sign in to Insights.
The LFX Insights, Jun 2021 release delivers support for new data source— Social Media Metrics. In this release, Insights supports only twitter to track and visualize twitter data. In the upcoming releases, Insights will provide support for Facebook and LinkedIn.
While navigating from top to bottom on dashboards, click from the down right corner to reach to the top of the page.
Data Sources shows the logos of different data sources, such as for GitHub and/or Gerrit, for Jira, or for Slack, and so on.
Projects shows the logos of sub-projects under the project group.
On a project dashboard, click Get Short URL, and click the icon next to the URL to copy the link of a respective dashboard for a project.
To know how the social media data are calculated, refer to .
For details about social media metrics dashboards, .
Trends dashboards provide analytics of project performance, ecosystem and data source related metrics, such as how many total contributors are contributing to your project, number of commits, total number of code backlogs, issues, and many more for a project. These performance-related data are grouped into different blocks of metrics.
You can filter data by time range. For details about filtering data, see Filter Data.
Note: If you filter data by time range on Trends dashboard for a sub project of a project group, then the selected Trends time range will also reflect on the other sub projects of the project group.
Global Trends dashboards provide high level analytics of project performance for all the projects onboarded to Insights. **** The performance-related data are grouped into different blocks of metrics.
Following are the twelve most important Key Performance Indicators (KPIs) of all projects, displayed at the top:\
Project Trends dashboards provide analytics of project performance data, such as how many contributors are contributing to your project, total number of code backlogs, issues, and many more for the project. These performance-related data are grouped into different blocks of metrics.
Based on the project's configured data sources, following key project performance indicators are displayed at the top:
Total number of unique commits
Number of repositories being monitored
Total number of lines of code added and modified
Total number of Pull Requests / Changesets submitted
Total number of builds being monitored
Total number of emails sent
Total number of relevant mentions on social media channels
Total number of issues submitted
Total number of messages sent in different chat platforms of the project
Total number of project relevant document pages created on confluence, and
Total number of container images downloaded
Click the icons for each metric to view details about the metrics. No Data is displayed for a metric if the relevant data source is not configured for the project.
Navigate to another project of the project group by selecting a project from View Sub Projects drop-down list under the project group name on the top right corner of the overview card.
Contributor Strength: Shows graphs that display total number of contributors on a periodic basis during the selected time range, and represents a periodic growth in the aggregated count of unique contributors analyzed during the selected time range.
The grey colored rectangular card shows the following data in each slide:
The increment number in percentage
Monthly average contributor strength, and
The exact time period during which the numbers increased the most.
Contributor Growth And Retention: Shows total count of contributors, active contributors, inactive contributors, and percentage of churn rate on a periodic basis during the selected time range. It also shows graphs representing the increment/decrement in active and inactive contributor numbers.
Active contributors are those who have performed any code related activity, such as creating a PR or submitting a changeset or an issue, during the last 6 months.
If a contributor has not done any contribution to the project in the last 6 months, they are considered inactive.
Churn rate is calculated as:Total Inactive Contributors recorded at the end of the time period/ (Total Active Contributors recorded at the start + Total New Contributors who joined during the selected time period)
The grey colored rectangular card shows the following data in each slide:
Monthly average count of active contributors during the selected time range
Time period during which number of active contributors increased the most
Monthly average count of inactive contributors
Time period that records the most inactive contributors, and
Decrement percentage of active contributors during the selected time range
Commits Growth: Shows graphs that display the total number of unique commits on a periodic basis during the selected time range, growth percentage of commits, and monthly average number of code commits by active contributors for the selected time range.
New Contributor Growth: Shows periodic bar graphs that display the total number of new contributors joining the projects during the selected time range, and represents a periodic growth/decline in the count of new contributors during the selected time range. Note: New contributor is considered as someone who performed their first code activity during the selected time period.
The grey colored rectangular card shows the following data in each slide:
Increment/decrement percentage rate of code contributors during the time range
Average monthly count of new contributors, and
Time periods that record highest and lowest number of new contributors joining the project during the selected time range.
Commits By New Contributors: Shows periodic graphs that display the count of **** total number of commits by new contributors during the selected time range. Hover over the points for a quarter to see the number of commits by new contributors for the quarter. Note: New contributor is considered as someone who performed their first code activity during the selected time period.
The grey colored rectangular card shows the following data in each slide:
Increment/decrement percentage rate of code commits by new contributors during the time range, and
Monthly average number of commits by new contributors
LOC Added And Deleted: Shows periodic graphs that display the number of the total lines of code added and deleted for each unique commit during the selected time range.
The grey colored rectangular card shows the following data in each slide:
Increment/decrement percentage rate of lines of code changed per commit during the time range, and
Churn rate of lines of code per commit, weekly and monthly average number of lines of code added to all repositories during the time range
Contributor Role Distribution: Shows graphs, in pie chart and line graph formats, that display the count of the total number of pull request creators, reviewers and approvers aggregated across unique PR and changesets over the selected time range.
The grey colored rectangular card shows the following data in each slide:
Monthly average number of submitters and reviewers for pull requests and changesets during the time period
Monthly average ratio between reviewers and submitters of pull requests and changesets, and
percentage of pull requests submitted and reviewed by core maintainers during the selected time range
Code Pipeline: Shows total count of unique commits (pull requests or changesets) submitted, reviewed, approved and merged across all projects during the selected time range.
The grey colored rectangular card shows the following data in each slide:
Percentage of approved changes out of the total number of changes submitted
Percentage of changes merged out of the total number of reviewed changes, percentage of changes merged without approval, and
Percentage of risky changes found during review that are not merged
PR Cycle Time: Shows the sum of the average time taken in each step of the pull request or changeset cycle.
Work in Progress: time taken for first review
Review: time in reviewing the changes
Merge: time taken to merge changes to the release branch
The grey colored rectangular card shows the following data in each slide:
Median time taken to first review a pull request, and
Median time taken to first approve a pull request during the selected time range
PR Merge Efficiency: Shows graph that displays total time taken to merge a pull request. The time periods are divided into four slots: less than 1 day, between 1-7 days, between 7-30 days and greater than 30 days.
The grey colored rectangular card shows the following data in each slide:
Number of the pull requests merged during each time slot
The average merge efficiency time and percentage of pull requests that are merged within a week
Issues Backlog: Shows a graph that represents the total number of issues in the backlog that are in Open and Resolved (includes both closed and done) states during the selected time range. Note: GitHub issues in open state are also considered as backlog.
The grey colored rectangular card shows the following data in each slide:
Monthly average number of backlog issues
Percentage of increment/decrement in new issues submitted
Average number of resolved issues, and
Average number of activities recorded in the issue management system during the selected time range
Issues Resolution Efficiency: Shows graph that represents the median time taken to resolve (close or reject) an open issue. The time periods are divided into four slots: less than 1 day, between 1-7 days, between 7-30 days and greater than 30 days.
The grey colored rectangular card shows the following data in each slide:
Showing the number of issues resolved during each time slot, and
Mean time taken to first react to an Issue during the selected time range
Builds Stats: Shows a pie chart that displays the number of builds executed over time by their statuses: Successful Builds, Failed Builds, Unstable Builds, and Aborted Builds.
The grey colored rectangular card shows the following data in each slide:
The increment/decrement percentage in the success rate of all builds during the selected time range
Percentage rate in the increment/decrement of builds per day
Average number of builds executed per day, and
Percentage rate in the increment/decrement of average build duration time taken during the selected time range
Active Communication Channel: Shows different communication platforms the community is using the most. It displays the number of messages shared on a communication platform on a periodic basis.
The grey colored rectangular card shows the following data in each slide:
Average number of chats and emails sent per month
Average number of community members who participated in the conversations per month, and
The communication platform that is used the most by community members during the selected time range
Organizational Engagement: Shows colored circular dots that represent the percentage of commits made by affiliated contributors, unaffiliated contributors and independent contributors during the selected time range.
The grey colored rectangular card shows the following data in each slide:
Total number of organizations who participated in code commits
Number of organizations that contributed to 50% of the total commits
Average number of commits contributed by individual contributors, and
Average number of commits contributed by unaffiliated contributors during the selected time range.
For different time periods, different strategies are used to collect, aggregate, and visualize Trends data. Depending upon the selected time period, the data are displayed with different numbers of break points, also called buckets. Following are the different time periods, of Trends dashboard, and the strategies used to aggregate data for each of the time period:
This shows aggregated data for the last 3 months from the current date. The data are aggregated based on a specific interval in days of a month, and are displayed with 12 breakpoints (also called buckets).
This shows aggregated data for last the 6 months from the current date. The data are aggregated based on a specific interval in days of a month, like it is for 3 months, and are displayed with 12 breakpoints.
This shows aggregated data for last one year from the current date. The data are aggregated monthly, and are displayed with 12 breakpoints.
This shows aggregated data for the last two years from the current date. The data are aggregated quarterly, and are displayed with 8 breakpoints.
This shows aggregated data for the last three years from the current date. The data are aggregated every 4th month, and are displayed with 9 breakpoints.
This shows aggregated data for the last five years from the current date. The data are aggregated half-yearly (every 6th month), and are displayed with 10 breakpoints.
This shows aggregated data for last the ten years from the current date. The data are aggregated on a yearly basis, and are displayed with 10 breakpoints.
This shows aggregated data from the year 2000 till the current year and date. The data are aggregated yearly, but are displayed with numbers of breakpoints based on the current year. For example, if the current year is 2021, the break points will start from 2000 to 2021, showing 20 breakpoints.
You can download a metric card in image (.png) format by clicking the download button from the top right corner of the card. It is applicable to all the metrics cards displayed in Insights. Following is an example:
The LFX Insights, May 2021 release delivers support for new data sources and metrics— GitHub Reviews, Changeset Reviews metrics as source control systems, Circle CI as build system, and Google Groups as Email system to visualize project related communication activities. Gerrit Changeset Approval and GitHub PR Efficiency dashboards are enhanced for better clarity of project data.
The following new features are added in May 2021 release of LFX Insights:
Metrics | Definition |
---|---|
For more information on added features, see
New GitHub Reviews Dashboard and an improved GitHub Efficiency Dashboard are added to provide more clarity around pull request merge times. GitHub Efficiency Dashboard is redesigned to help project maintainers set goals around PR merge times. For details about new visualizations of GitHub PR, see and .
Google Groups addition expands Insights email coverage. It provides richer context around what the community is talking about, and help project community managers to better engage and acknowledge their community members. To know amore about how google groups data is onboarded, see **** For details about visualizations, see .
Circle CI Dashboards: LFX Insights supports a new build system— CircleCI, providing various builds related-metrics right on the Insights dashboard for your project, helping you monitor your project’s build pipeline and improve workflow efficiency. For details about visualizations, see .
Gerrit Changesets Dashboards are redesigned to help project maintainers analyze and set goals around changeset approvals and merge times. For details about the added/enhanced visualizations, see .
Total lines of Code
Combined count of lines of code across each repository for all the projects.
Commits
Total number of unique commits.
Average lines of code added weekly
Average number of lines of code added weekly across unique commits for all the projects during the selected time range.
Average Lines of code deleted weekly
Average number of lines of code deleted weekly across unique commits for all the projects during the selected time range.
Code Contributors
Total number of unique developers across commits, PRs, changesets and issues aggregated for all projects.
Contributing Companies
Total number of affiliated companies (only unique numbers) contributing towards commits, PRs, changesets and issues aggregated for all projects.
Repositories
Total number of unique repositories actively monitored across all projects.
Pull Requests
Total number of PRs / Changesets ( includes both open and merged/closed/rejected) across all projects of Insights.
Logged Issues
Total number of issues that are submitted and closed (includes rejected) across all projects.
Project Builds
Total number of project builds across all projects.
Container downloads
Total number of docker image downloads aggregated for each docker image across all projects.
Email messages sent
Total number of email messages monitored across all projects.
By default, Bot commit is filtered, and can't be included for Summary dashboard.
Summary provides a high-level metrics about each data source for which the project is configured. Following are activities for quick navigation:
****Technical Metrics:
Following dashboards are displayed under Technical Metrics:
Source Control shows analytic overview of git commits for a selected time range. Default time range is Last 90 Days. You can select a time range to view data for the selected time range.
Clicking Go To Overview and View All takes you to the respective dashboard of Commits > Overview page.
Commits shows the following information:
Lines Of Code Changed represents total number of lines changed—added, updated, and deleted—for a selected time range.
Commits represents total number of commits for a selected time range.
Contributors represents the number of contributors for the project
No Of Sub Projects represents total number of sub projects (added git repositories) under a project.
Repositories represents total number of repositories of the project. This includes the number of repositories of sub projects.
Top 10 Contributors By Commits lists the top ten individuals—that contribute most to the project— by name, total number of lines of codes changed that includes lines of codes added and modified, number and percentage of commits. Click View All to navigate to the Commits > Overview page.
Top 10 Companies By Commits shows a doughnut chart that represents **** top ten companies that contribute most to the project.
Unknown as a company name shows number/percentage of codes submitted by those contributors who are not affiliated with any organization.
Others represents a group that combines all other companies that come after top nine companies that contributes more.
Pull Requests/Changesets shows analytic overview of pull request information of GitHub repositories and/or information about changesets and patchsets per changeset for Gerrit.
Data is not available for a Git data source that is not configured for Insights.
Gerrit shows total number of changesets (both open and closed), number of open changestes, average time in hours to merge changesets, average time in days for first review of changeset, and total number of approved changesets for a selected time range.
Clicking Go To Overview and View All under Gerrit takes you to the respective table/graph/chart of Gerrit Changesets > Overview section.
GitHub shows total number of pull requests (both open and closed), number of open pull requests, average time in hours to merge pull requests, and average time in hours pull requests were open for a selected time range.
Clicking Go To Overview and View All under Gerrit takes you to the respective table/chart/graph of GitHub PR > Overview section.
Top 10 Contributors By PRs (for GitHub) **** or Top 10 Contributors By Changesets (for Gerrit) **** lists the top ten individuals—that contribute most to the project— by name, total number of pull requests or changestes, and percentage of commits out of the total number of commits by the community.
Top 10 Companies By PRs (for GitHub) **** or Top 10 Companies By Changesets (for Gerrit) **** shows a doughnut chart that represents **** top ten companies that contribute most to the project.
Mouse over a color in the doughnut chart to view company name and number of commits made by the company.
Unknown as a company name shows number/percentage of codes submitted by those contributors who are not affiliated with any organization.
Others represents a group that combines all other companies that come after top nine companies that contributes more.
Issue Management shows analytic overview of issue management platforms used by a project, such as Jira, GitHub Issues, and Bugzilla.
Jira shows total number issues that includes both open and closed issues, total number of submitters, number of open issues, average time in days the issues are open, and time in days for which a stacked area chart compares the number of issues and unique contributors per calendar period.
Clicking Go To Overview and View All under Jira takes you to the respective table/chart/graph of Jira > Overview section.
GitHub Issues shows total number issues that includes both open and closed issues, total number of submitters, number of open issues, average time in days the issues are open and average time in days the issues took to be resolved.
Clicking Go To Overview and View All under Github Issues takes you to the respective table/chart/graph of GitHub Issues > Overview section.
Bugzilla shows total number issues that includes both open and closed issues, total number of submitters, number of open issues, total time in days the issues are open, and time in days issues took to be closed.
Clicking Go To Overview and View All under Bugzilla takes you to the respective table/chart/graph of Bugzilla > Overview section.
Top 10 Contributors By Issues Submitted lists the top ten individuals— that contribute most to the project— by name, total number of issues, and percentage of issues out of the total number of issues submitted by the community members.
Top 10 Companies By Issues Submitted shows a doughnut chart that represents top ten companies that contribute most to the project.
Unknown as a company name shows number/percentage of issues submitted by those contributors who are not affiliated with any organization.
Others represents a group that combines all other companies that come after top nine companies that contributes more.
Following an example of Issue Management overview section for a project that uses Jira, GitHub Issues, and Bugzilla to manage issues:
CI/CD **** shows an analytic overview of the number of total builds, jobs, failed builds, job categories, and average build duration in minutes. Clicking Go To Overview and View All under CI/CD takes you to the respective table/chart/graph of Jenkins > Overview and CircleCI > Overview sections respectively.
Top 10 Jobs lists the top ten jobs by name, number, and percentage.
Build Results for Jenkins and Jobs Results for CircleCI shows a doughnut chart that represents total number of builds for all the build results, such as Success, Failure, Unstable, and Aborted. Click a result to exclude the data. Click again to include.
Registry shows total number of median pulls, average stars for images, increase number in pull count, and star counts for DockerHub. Clicking Go To Overview and View All opens the respective table/chart/graph of Docker > Overview section.
Top 10 images By Pull Count lists the top ten pulls by name, number, and percentage.
Top 10 images By Star Count lists the top ten stars by name, number, and percentage.
Mouse over a color in the chart to view company name and number of commits made by the company. Click a company name to exclude company data. Click again to add the company data. Following is an example:
Click a company name to exclude company data. Click again to add the company data. Following is an example:
Mouse over a color in the doughnut chart to view company name and number of commits made by the company. Click a company name to exclude company data. Click again to add the company data. Following is an example:
Source Control dashboards show analytics for git commits based on a project's configuration:
The data on Source Control dashboards do not include commits by Bots and empty commits. By default, Bot commit is filtered, . For details, see Filter Data.
Technical Metrics is displayed for all the projects, and shows details for the following data sources:
By default, Bots and Changesets Only are filtered. Dashboard shows data only for number of changesets, not for comments, approvals, and other values. Empty changesets— Changesets that have value as zero— are also filtered. To add/manage filters, see Add and Manage Data Filters.
The Gerrit Changesets dashboards represent a set of metrics that shows detailed information about changesets and patchsets per changeset. Following are the various dashboards of Gerrit data source:
By default, Bots and Changesets Only filters are applied. To apply more filters, see add and manage data filters.
Overview shows visualizations that provide information about changeset statuses, submitters, and organizations. Changeset information per organization and repository is also shown.
Filter lets you filter the dashboard data by author name, organization name, and repository. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows total number of changeset submitters, repositories the changesets belong to, new changesets, merged changesets, and total number of abandoned changesets.
Changeset Percentage By Status shows a doughnut chart that represents the total number of changesets in the project by status: MERGED, ABANDONED, NEW, DRAFT. Mouse over a color in the chart to see the status, total number, and percentage of changesets by status.
Changeset Percentage By Organization shows a doughnut chart that represents the total number and percentage of changesets submitted by an organization over time. Mouse over a color in the chart to see details.
Changesets By Status shows stacked line graphs that represent the increase or decrease in the number of changesets by status—MERGED, ABANDONED, NEW, DRAFT— that were started per day. Mouse over a color in the graph to see the status along with its number, and the date the changesets was started.
Changeset Submitters shows stacked line graphs that represent increase or decrease in the total number of changeset submitters over time along with the number of organizations the submitters belong to. Mouse over a color in the graph to see the numbers for a date.
Patchsets per Changeset shows stacked line graphs that represent the 50th, 75th, and 95th percentile of patchsets created per changeset in a given timeframe. Mouse over a color in the graph to see number of patchsets.
Changesets By Organizations shows a stacked bar graph that represents the number of changesets submitted by an organization over time. Mouse over a color in the graph to see details.
Submitters shows a table that lists name of the submitters, total number of changesets submitted by the submitter, total number of new, merged, and abandoned changesets per submitter. It also lists average number of patchsets over total number of changesets submitted by a submitter over time.
Organizations shows a table that lists organization names, number of submitters from the organization, total number of changesets submitted by the organization's submitters, number of changesets in different stages, such as new, merged, and abandoned, and average number of patchsets over total number of changesets submitted by an organization over time.
Repositories shows a table that lists name of the repository, total number of changesets submitted to the repository, number of contributors who submitted changesets to the repository, number of changesets in different stages, such as new, merged, and abandoned, and average number of patchsets over total number of changesets submitted by to the repository over time.
Latest Changeset Activity shows a table that lists changeset URL, changeset submitter's name, affiliated organization of the changeset submitter, status of the changeset, number of patchsets created for the changeset, and date and time when the changeset was updated.
Efficiency offers an overall view of understanding and optimizing project efficiency in closing/merging Gerrit Changesets.
Filter lets you filter the project data by organization name, author name, and repository name. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows a cluster of
50th percentile of Time To Merge (Days): The number of days it took to merge 50 percent of the changesets.
95th percentile of Time To Merge (Days): The number of days it took to merge 95 percent of the changesets.
Merged Changesets: Total number of changesets merged over time.
Organizations: Total number of organizations whose submitters authored the merged changesets.
Submitters: Total number of submitters whose changesets were merged.
Repositories: Total number of repositories the merged changesets belonged to.
50th Percentile of Time To Merge By Repo shows a cloud of top 10 repositories for which it took the most time for 50% of the changesets to get merged. Click a repository to filter the dashboard data to view metrics related to the repository.
Time to Merge shows line graphs that represent number of changesets that took certain amount of time to get merged. These time slots are divided into four categories, such as less than 1 day, 1 to 7 days, 7 to 30 days, and more than 30 days. Hover mouse over the graph to view number of of PRs along with the time taken to get merged.
Less than 1 day: The number of changesets merged in less than one day.
1 to 7 days: The number of changesets merged in more than one day but less than seven days.
7 to 30 days: The number of changesets merged in more than seven days but less than thirty days.
More than 30 days: The number of changesets merged in more than thirty days.
Repositories shows a table that lists repositories, total number of merged changesets along with the time it took for 50% and 95% of the changesets to get merged per repository. Click a repository to navigate to GitHub to view details.
Timing shows information about open and closed changesets over time. The dashboard focuses on how long changesets remain open. Statistical information provides closing times and also tables with the latest and the oldest changesets.
Filter lets you filter the dashboard data by repository, author who submitted changesets, and author who approved the changesets. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of changeset submitters, number of new, merged, and abandoned changesets, and average number of days the changesets are open, and average number of days it took for the changesets to be merged.
Changesets By Organization shows a doughnut chart that represent number and percentage of changesets submitted by an organization over a time period. Mouse over a color to view details related to an organization.
Median Time To Merge (Days) shows line graphs that represent the increase or decrease in time it takes for 50 percent of the changesets to be merged.
Submitters shows line graphs that represent the increase or decrease in the number of changeset submitters and their affiliated organizations over time.
Median Time To First Review shows line graphs that represent the 50th percentile of days it takes for a changeset to get reviewed in a given timeframe.
Organizations shows a table that lists organization name, number of submitters from the organization, number changesets submitted by the organization's submitters, number of changesets in different stages, such as new, merged and abandoned, average number of patchsets submitted per total changesets, and average number of days it took to merge the changesets for an organization.
Submitters shows a table that lists name of the submitters, total number of changesets submitted by the submitter, number of changesets in different stages, such as new, merged and abandoned, average number of patchsets submitted by the submitter over time, and average number of days it took to merge the changesets submitted by a submitter.
Repositories shows a table that lists repository name, total number of changesets submitted to the repository, total number of submitters, number of changesets (submitted to the repository) in different stages, such as new, merged and abandoned , average number of patchsets per changesets over time, and average number of days it took to merge the changesets for a repository.
Backlog focuses on open changesets (data is retrieved at the moment of dashboard creation), their accumulated time, and associated organizations.
Filter lets you filter the dashboard data by author name, organization name, and repository. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows total number of new changesets that are in open state, number of repositories where the new changesets are submitted, and are in open state, and average number of days changesets have been in open state.
Changeset Backlog Percentage By Organization shows a doughnut chart that displays number and percentage of changesets created by on organization over time. Mouse over a color to view details.
Backlog (New Changesets) shows a table that provides a summary of oldest changesets that are in open states, and are waiting to be closed. It lists changeset URLs for the project. For each changeset, the table shows the summary, the submitter name, the date and time the changeset was created, and how long (in days) the changeset have been in open state. Click a URL to go to the changeset in the project.
Backlog shows line graphs that displays the number of new changesets created over time.
Backlog By Submitters shows a table that provides summary of new changesets created by individual submitters. It lists submitter's names, number of changesets and average number of patchsets created by the submitter, and average number of days the changesets have been in open state.
Backlog By Organizations shows a table that provides summary of new changesets created by organizations. It lists organizations' names, number of submitters of the organization, number of changesets and average number of patchsets created by the organizations' submitters, and average number of days the changesets have been in open state.
Backlog By Repositories shows a table that provides summary of new changesets submitted to repositories. It lists repository names, number of submitters to the repository, number of changesets and average number of patchsets submitted to the repository, and average number of days the changesets have been in open state for a repository.
Approvals shows statistics about changesets that are approved. The dashboard shows reviewers, repository names, numbers of respective data, and so on.
Filter lets you filter the dashboard data by repository, author who submitted changesets and author who approved changesets. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows
Approvals: Sum of all approvals given on all the changesets
Changesets Approved: Number of changesets that were given an approval
Approvers: The number of reviewers that approved the changesets
Approvals By Organization shows a doughnut chart that represents the number and percentage of changesets that are approved by the authors of the organization. Mouse over a color in the chart to view details.
Reviewers Over Time shows a graph that represents total number of reviewers who reviewed changesets for the project over time.
Approvals Over Time shows graphs that represent number of changesets in different states over time. Mouse over a color to view details.
Activity by Repository shows a table that lists name of the repository, total number of changesets, patchsets, and approved changesets per repository.
Approvals Done by Reviewer shows a table that lists reviewer name, number of changes approved by the reviewer, and number of code review ratings (-2, -1, 1, 2) given by the reviewer for the repository over time.
Approvals by Reviewer Organization shows a table that provides summary of organizations that approved changesets. It lists name of the organization that approved changesets, number of changesets approved by the organization, and number of code review ratings (-2, -1, 1, 2) given by the reviewers of the organization over time.
Approvals Received shows a table that provides summary of changeset submitters who received maximum number of approvals. It lists name of the changeset submitter, number of approvals received by the submitter, and number of code review ratings (-2, -1, 1, 2) received by the submitter over time.
Reviews shows metrics about reviewed changesets. The dashboard shows reviewers, repository names, numbers of respective data, and so on.
Filter lets you filter the dashboard data by reviewer name, organization name, and repository. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of changesets, total number of individuals who reviewed changesets, total number approved changesets, total number of review comments received for the submitted changesets, and average time in days it took to review the first changeset.
Repos By Review Activity shows a cloud of top 10 repositories where maximum number of review activities happened. Click a repository to view the dashboard data specific to the repository.
Review Types shows a doughnut chart that represents the total number and percentage of changesets in the project by review status: Comment, Approval, Patchset, and Changeset. Mouse over a color in the chart to see the status, total number, and percentage of changesets by review status.
Median Time to First Review shows a graph that displays 50th percentile of days it takes for a changeset to get a review in a given timeframe_._ Mouse over a color in the graph to see the data.
Changesets Merged Without Approval shows graph that displays number of changesets that are merged without going through a approval process, over a period of time.
Repository Changeset Review Summary shows a table that displays review activity per repository, and lets you sort values by repository name, number of submitters and reviewers per repository, total number of changesets submitted to the repository, number review comments and approvals received for changesets per repository.
Organization Changeset Review Summary shows a table that displays review activities per organization, and lets you sort values by organization name, number of submitters and reviewers of an organization, total number of changesets submitted by an organization, number review comments and approvals given by an organization's submitters over time.
Reviewer Activity shows a table that displays activities by top reviewers. It list reviewer name, reviewer's organization name, number of changesets and patchsets reviewed by the reviewer, number of review comments given, number of changesets approved by the reviewer along with the total number of activities done by the reviewer.
The Commits dashboard represents a set of metrics that shows high level information, such as total number of commits, authors, repositories, and so on for all repositories of the project.
Overview shows information about commits in Git repositories. For each commit, Git stores information about who and when authored the commit (author), and about the organization that included the commit in the repository.
Filter lets you filter the dashboard data by author name, organization name, and repository. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the number of Commits, Authors, and Repositories of the project.
Commits Percentage By Organization shows a doughnut chart that represents the total number of commits by organization for the project. Mouse over a color in the chart to see the total number of commits by the organization, and the percentage of commits out of the total commits for the project.
Lines Changed Percentage By Organization shows a doughnut chart that represents the total number of lines of code changed by an organization for the project. Mouse over a color in the chart to see the total number of lines of code changed by the organization, and the percentage out of the total lines of code that are changed for the project.
Active Contributors shows a bar graph that represents the number of contributors per day over time. Mouse over a color in the graph to see the total number of contributors for a date.
Commits shows a bar graph that represents the number of commits per day for the project over time. Mouse over a color in the graph to see the total number of commits for a date.
Commits by Time Zone shows a bar graph with a count of commits per Coordinated Universal Time (UTC) time zone. Dates and times (author time, committer time) in Git use the time zone of the computer where the contributor performed the action. This data is used to display time zone information. Mouse over a color in the graph to see the total number of commits for each time zone.
Commits By Organization shows a bar graph that represents the number of commits by an organization per day over time. Mouse over a color in the graph to see the total number of contributors of an organization including organization's name for a date.
Lines of Code Changed By Organization shows a bar graph that represents the number of lines of code changed by an organization per day over time. Mouse over a color in the graph to see the organization's name, date, and total number of lines of code changed by the organization.
Authors shows a table that lists author name, number of commits by the author, number of projects the author has committed code to, number of lines the author has added and removed codes, and the average number of files the author has worked over time.
Organizations shows a table that lists:
Organization: name of organization
Commits: number of commits made by the organization
Authors: number of authors of the organization who made commits
Touched Files: number of files the organization has contributed towards
Added Lines: number of added lines to the code base
Removed Lines: number of removed lines from the code base
Projects: number of projects the organization is contributing towards
Repositories: number of repositories of the project the organization is contributing towards, and
Avg Lines/Commit: average number of lines added or commits made by the organization over time
Repositories shows a table that lists repository name with links, number of commits made to the repository, number of authors contributed to the repository, number of organizations contributed to the repository, number of lined added and removed to/from the code base of the repository, average number of files touched or commits made to the repository over time.
Projects shows a table that lists project names, number of commits, authors, repositories, number of added lines, removed lines, average number of lines committed, and average number of files committed per project.
Organization Commits shows a table that lets you sort values by commit hash, organization name, repository URL, author name, and date.
Click to copy the path of respective dashboards.
By default, Empty Commits (Commits with Zero value) and Bots are filtered, however, you can include these filter values by navigating to the filter section of dashboard. For details, see .
Pull Request Management show analytics for the following data sources based on a project's source control platform:
Issue Management dashboards show overview, backlog, effort, and timing analytics of the following issue tracking platforms:
By default, Bot Commits are filtered, however, you can include the filter values by navigating to the filter section of dashboard. For details, see Add and Manage Data Filters.
Following are the various dashboards of GitHub Issues:
Overview shows information about issues in project repositories and who submitted the issues and when. For each commit, information about the corresponding organization is also provided.
Filter lets you filter the dashboard data by author name, organization name, and repository. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of issues, submitters, and repositories for the project.
Issues by Organization Over Time shows a stacked bar graph that represents the number of issues created by organizations per day.
Issues by Status Over Time shows a stacked bar graph that represents the number of open and closed issues over time.
Issues Percentage by Organization shows a doughnut chart that represents the total number of issues created by each organization over time. Mouse over a color (organization) in the chart to see the organization name, total number and percentage of issues.
Issue Submitters Over Time shows a bar graph that shows the number of submitters of issues per day over time.
Issues By Submitters shows a table that lists submitter name, total number of issues raised by the submitter, number of issues that are in open and closed state out of the total issues, number of repositories the submitter worked upon, and average number of days it took to close the issues raised by the submitter.
Issues By Organizations shows a table that organization name, total number of issues raised by the organization, number of issues in open and closed states, number of submitters, and average number of days the it took to close the issues raised by the organization.
Issues By Repositories shows a table that lists project's repository links, total number of issues, number of issues in open and closed states for the repository, number of submitters, and average number of days it took to close the issues. You can select a repository to view its details in GitHub.
Efficiency offers an overall view of understanding and optimizing project efficiency in closing GitHub issues.
Filter lets you filter the project data by organization name, author name, repository name, and repository URL. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows a cluster of
Total number of closed issues
Number of submitters whose issues are closed
Number organizations that helped in closing the issues
Repositories of the project to which the closed issues belong to
Number of days it took to close 50 percentage of the issues, and
Number of days it took to close 95 percentage of the issues over time
50th percentile of Time To Close By Repo shows a cluster of top 10 repositories names for which it took most time to close 50% of the issues.
Time to Close shows line graphs that represent number of issues that took certain amount of time to get closed. These time slots are divided into four categories, such as less than 1 day, 1 to 7 days, 7 to 30 days, and more than 30 days. Hover mouse over the graph to view number of of PRs along with the time taken to get merged.
Less than 1 day: The number of pull requests merged in less than one day.
1 to 7 days: The number of pull requests merged in more than one day but less than seven days.
7 to 30 days: The number of pull requests merged in more than seven days but less than thirty days.
More than 30 days: The number of pull requests merged in more than thirty days.
Repositories shows a table that lists repository link, time it took for 50% and 95% of the issues to get closed per repository. Click a repository to navigate to GitHub to view details.
Timing shows information about open and closed issues in time. The dashboard focuses on how long Issues remain open. Statistical information provides closing times and also tables with the latest and the oldest Issues.
Filter lets you filter the dashboard data by author name, organization name, and repository. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of issues, submitters, assignees, average number of days issues in open state have been in open, and average number of days it takes to close issues.
Issues By Status shows a doughnut chart that represents the total number of issues over time by status: closed or open. Mouse over a color in the graph to see the status, the total number of issue for the status, and the date.
Issues By Organization shows doughnut chart that represents the total number of issues (closed and open) by an organization over time. Mouse over a color in the chart to see organization name, total number of issue for the organization, and date.
Median Time Open (Days) shows a graph that represents number of days for which 50% of issues, out of total issues that are created on a particular day, are open.
Submitters Over Time shows line graphs that represent the total number of individual submitters and submitters per organizations over time in the project. Mouse over a color in the graph to see the status, total number of submitters and the date.
Submitters shows a table of submitters and their corresponding number of Issues, Repositories, and Avg. Open Days.
Organizations shows a table that lists organization name, total number of submitters from the organization, number of open and closed issues, and average number of days it took to close the issues per organization.
Repositories shows a table listing repositories, total number of issues per repository along with the number of open and closed issues , and average number of days it took to close the issues per repository.
Backlog focuses on open issues, their accumulated time, and associated organization.
Filter lets you filter the dashboard data by author name, organization name, repository name and URL. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows total number of issues in open state, total number of repositories with issues in open state, and average number of days issues have been in open state.
Backlog shows a line graph that represents the number of issues that are open on a particular day. Mouse over a color in the graph to see the total number of issues on a date.
Backlog (Open Issues) shows a table that lists summary, URL, date on which the issue was open, and average number of days the issue was in open state. Click the URL to view details.
Open Issues Statistics Summary shows the total number of Open Issues, Accumulated time in days for Open issues, and Average Time Open per Issue.
Percentage of Issues Opened By Organizations shows a doughnut chart that represents the total number of issues opened per organization. Mouse over a color in the chart to see the total number and percentage of issues raised by an organization.
Issues In Open By Submitters shows a table that lists name of the submitter, total number of issues raised by the submitter, number of repositories the submitter worked upon, and average number of days the issues were in open state per submitter.
Issues In Open By Organization shows a table that lists name of the organization, total number of issues submitted by the organization, number of submitters from the organization, and average number of days the issues were in open state per organization.
Click to copy the path of respective dashboards.
By default, Bot Commits are filtered, however, you can include the filter value by navigating to the filter section of dashboard. For details, see Add and Manage Data Filters.
The Bugzilla dashboard is available from the Issue Management drop-down list, and represents the following dashboards:
Overview shows information about issues and submitters in Bugzilla organizations.
Filter lets you filter the dashboard data by submitter name, organization name, and project. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Issues shows the total number of Issues, Submitters, and Products.
Issues by Status Over Time shows a stacked bar graph that represents the number of issues by status per day over time such as: RESOLVED, CONFIRMED, IN_PROGRESS, VERIFIED, UNCONFIRMED. Mouse over a color in the graph to see the total number of issues by status that occurred on a date.
Submitters by Organization shows a doughnut chart that represents the total number of submitters in the project by organization. Mouse over a color in the chart to see the total number of submitters for the organization, and their percentage of the project's organization.
Projects shows a table that lets you sort values by Organizations, Issues, Submitters, Assignees, Avg. Time to close (days) and Avg. Updates.
Submitters Over Time shows a bar graph that represents the number of submitters per day over time. Mouse over a color in the graph to see the total number of submitters that occurred on a date.
Submitters shows a table that lets you sort values by Submitter, Issues, Products, and Avg. Open Days.
Issues by Organization Over Time shows a stacked bar graph that represents the number of issues by organization per day over time. Mouse over a color in the graph to see the total number of issues that occurred on a date for the organization.
Organizations shows a table that lets you sort values by organization name, number of issues, submitters, assignees, average time to close (days) issues, and average updates per product.
Backlog focuses on open issues, their accumulated time, and associated organizations.
Open Issues Statistics shows total number of open issues, accumulated time in days for all open issues, and average time in days an issue is open.
Issues waiting to be closed shows a stacked bar graph that represents number of issues (that are not closed) per day by status: New, Unconfirmed, Assigned, and so on. These statuses are color coded. Mouse over a color in the graph to see the total number of issues by status that occurred on a date.
Backlog shows a table that lets you sort values by title, URL, number of comments, updates, days of open, and date of open for an issue backlog.
Accumulated Time (days): Issues waiting to be closed shows a bar graph that represents cumulative number of days for which individual issues were open, on a date. Mouse over a color in the graph to see the data.
Assignee Organizations shows a doughnut chart that represents the assigned organizations that have open issues to be closed. Mouse over a color in the chart to see the total number of assignees for the organization, and their percentage.
Backlog Submitters shows a table that lets you sort values by submitter name, number of issues, average time in days the issue was open for the submitter, and number of projects the submitter is associated with.
Projects shows a table that lets you sort values by project name, number of open issues, and average time in days the issues are open.
bugzilla_openissues_per_organization shows a table that lets you sort values by organization name, number of open issues, and average time in days the issues are open for an organization.
Timing shows information about open and closed issues in time and lets you focus on how long Issues remain open. Statistical information shows the 50th percentile of median time open in days. The number indicates the median number of days that issues were open. This number indicates that 50 percent of the issues were open longer than the total number and 50 percent of the issues were below the total number. A 50th percentile is the same as a median.
Summary shows the total number of Issues, Submitters, Assignees, 50th percentile of Median Open Days.
Median Open Time (days) shows a stacked bar graph that represents number of days for which the median or 50th percentile of total issues that were created per day over time, are open. Mouse over a color in the graph to see the median number of days issues were open on a date.
80 percent Open Time (days) shows a stacked bar graph that represents number of days for which the 80th percentile of total number of issues that were created per day, are open. Mouse over a color in the graph to see the 80th percentile number of days issues were open on a date.
Issues shows a stacked bar graph that represents the total number of issues over time in the project by status: closed, open, resolved, in progress, and so on. Mouse over a color in the graph to see the status, the total number of issue for the status, and the date.
Issue By Status shows a doughnut chart that represents the total number of issues in the project by status: closed, open, resolved, in progress, and so on. Statuses are color code. Mouse over a color in the chart to see the status, total number of issues for the status, and the percentage of that status.
Issues Assigned by Organization shows a doughnut chart that represents the total number of issues assigned by an organization. Mouse over a color in the chart to see the number of issues, and their percentage for an organization.
Issues By Resolution shows a doughnut chart that represents the number and percentage of issues by resolution status—Fixed, Duplicate, Invalid, Notabug. Mouse over a color to see the data.
Issues By Severity shows a doughnut chart that represents the number and percentage of issues by severity status—normal, enhancement, critical, major. Mouse over a color to see the data.
Submitters shows
a bar graph that represents the total number of submitters over time for the project. Mouse over a color in the graph to see total number of submitters for a date.
a table of submitters and their corresponding number of Issues, products, and Avg. Open Days.
Organizations shows a table that lets you sort values by organization name, number of open issues, submitters, assignees, and verage time in days issues are open for an organization.
Projects shows a table that lets you sort values by project name, number of open issues, submitters, assignees, products, and verage time in days issues are open for an organization.
Products shows a table that lets you sort values by product name, number of open issues, submitters, assignees, and average time in days issues are open.
Latest Issues shows a table listing issues by Title, Product, Submitter, URL, Id, and Created on. The default sort is by most recently created issue.
Click to copy the path of respective dashboards.
The Jenkins dashboards under CI/CD drop-down list represents a set of metrics that show overview analysis of Jenkins data. Following are the various dashboards of Jenkins:
Overview shows an overview of Jenkins build and job data over time.
Filter lets you filter the dashboard data by job name. Select values from the drop-down list, and click Apply changes to filter the dashboard as per selection.
Summary shows the number of builds, jobs, nodes, and average time of build duration in minute for a project.
Builds Over Time shows a bar graph that represents the total number of builds per day over time.
Build Results Percentage shows a stacked bar graph that represents the percentage of build results—Success and Failures— per day over time. The build results are color coded. Mouse over a color to see the percentage of build result for a day.
Build Results By Categories shows a doughnut chart that represents the total number of builds in the project by status: SUCCESS, FAILURE, UNSTABLE, ABORTED. Mouse over a color in the chart to see the status, total number of builds for the status, and the percentage of the project's builds for that status.
Active Nodes Over Time shows a bar graph that represents the number of active nodes per day over time. Mouse over a color to see the number of active nodes for a day.
Nodes shows a table that lists name of node, number of builds, median or 50th percentile of duration in minute, and total duration in minute per node.
Builds shows a table that lets you sort values by build date and time, job name with build number (job_build), URLs for build and job, type of result, node on which the job is built, and time taken in minutes to execute the build.
Jobs shows data about Jenkins jobs such as duration, successes, and failures over time.
Filter lets you filter the dashboard data by job name. Select values from the drop-down list, and click Apply changes to filter the dashboard as per selection.
Summary shows the number of build results—Success, Failure, Unstable, Aborted.
Results shows a doughnut chart that represents the total number of jobs in the project by status: SUCCESS, FAILURE, UNSTABLE, ABORTED. Mouse over a color in the chart to see the status, total number of jobs for the status, and the percentage of the project's jobs for that status.
Jobs Per Branch shows a doughnut chart that represents the total number of jobs per branch. Mouse over a color to see the branch name, total number of jobs per branch, and percentage of jobs out of total jobs in project.
Jobs shows a bar graph that represents the number of jobs per day over time. Mouse over a color to see the total number of jobs per day.
Duration Trend shows the time in minutes for the total number of jobs per day over time and a trend line to show an increase, decrease, or stability in the job time.
Avg. Build Duration Over Time Per Job shows a stacked bar graph that represents the average time in minutes taken for the execution of a job per day. Mouse over a color to see the job names per day and average time taken for a job .
Jobs shows a table that lets you sort values by job name, number of builds per job, 50th percentile of build duration in minutes, total build duration in minutes, number of success and failure results.
Job Categories shows data about Jenkins jobs that are grouped into certain categories in a project.
Filter lets you filter the dashboard data by job name. Select values from the drop-down list, and click Apply changes to filter the dashboard as per selection.
Summary shows number of builds, jobs, nodes, and job categories for a project.
Jobs Evolution shows a stacked bar graph that represents number of builds executed per day.
Categories shows a table that lists name of categories the jobs are grouped to, total number of jobs and builds per category, and number of build results per success and failures.
Results Across Top Categories shows number of builds per category by status: SUCCESS, FAILURE, UNSTABLE, ABORTED. Top categories are listed based on the total number of builds per category.
Nodes shows an overview of Jenkins build and job data over time. It shows a table that lists and lets you sort values by node name, number of builds per node, 50th percentile of build duration in minutes, total build duration in minutes, success and failure counts of builds per node.
Build Data shows an overview of Jenkins build data over time
Builds shows a table that lets you sort values by build name, build result such as Success, Failure, and so on per build, node where the build happened, time taken in minutes for the build to be executed, and date and time when the build happened.
The CircleCI dashboards under CI/CD drop-down list represents a set of metrics that show overview analysis of CircleCI build system data. Following are the various dashboards of CircleCI:
Overview shows total number of pipelines, workflows, and jobs for the project.
Job status percentage shows a doughnut chart that displays build jobs by status: success, failed and cancelled. Mouse over a color to view number and percentage of build jobs.
Workflow status percentage shows a doughnut chart that displays workflows of build jobs by status: success, failed, cancelled, and other. Other includes statuses such as running, not run, on hold, and so on. Mouse over a color to view number and percentage of workflows.
Job status trend shows line graphs that display total number of jobs per status on a timely basis. Mouse over the graph to view numbers.
Workflow duration trend shows line graphs that display minimum and maximum time (in minutes) taken to complete a workflow. It also displays the average time (in minutes) taken by 50% of the total number of workflows to be completed.
Workflow Duration (minutes) 95th Percentile shows a bar graph that displays time taken in minutes to complete 95% of total build jobs created per day.
Workflow status by author shows a table that lists name of authors, total number of workflows (by status) created by the author: success, failed, cancelled, and approved.
Workflow status by organization shows a table that lists name of organizations the authors belong to, total number of workflows (by status) created by the authors of the organization: success, failed, and cancelled.
Workflow status by origin repository shows a table that lists origin repositories where the build job is created, target repository, number of build jobs by status: success, failed, and cancelled.
Job run count shows table that lists the job number, related project name, and number of times the job was run to complete the workflow.
Jobs Overview shows total number of build jobs over time along with how many jobs are success, failed, and cancelled over time.
Job Status shows a doughnut chart that displays number and percentage of build jobs over time. Mouse over a color to view details.
Job Status on a time series shows a colored bar graph that displays timely total count of jobs along with the how many job numbers are success, failed, and cancelled over time.
Jobs status trend shows line graphs that represent gradual increase or decrease of the build jobs by status, such as how many jobs are success, failed or cancelled over time. Mouse over a point in the graph to view details.
Job duration trend shows line graphs that represent gradual increase or decrease in maximum and minimum time taken in minutes to complete the build jobs. It also shows average time taken in minutes to complete 50% of the total jobs created over time. Mouse over a point in the graph to view details.
Job duration-Max, Median and Min shows a colored bar graph that displays maximum and minimum time taken in minutes to complete the build jobs created over time. It also shows average time taken in minutes to complete 50% of the total jobs created over time. Mouse over a color in the graph to view details.
Job executor type shows a doughnut chart that displays number and percentage of jobs executed using a particular containerization technology, such as Docker. Mouse over a color to view details.
Job executor instance size shows a doughnut chart that displays number and percentage of completed jobs by size, such as large, medium, xlarge, and so on.
Workflow Overview shows total number of workflows over time along with how many workflows are success, failed, and cancelled over time.
Workflow duration trend shows line graphs that represent gradual increase or decrease in maximum and minimum time taken in minutes to complete the workflows. It also shows average time taken in minutes to complete 50% of the total workflows created over time. Mouse over a point in the graph to view details.
Workflow Status on a time series shows a colored bar graph that displays timely total count of workflows along with how many workflows are success, failed, and cancelled over time.
Workflow status by orgs shows a table that lists organization name, and how many workflows run by the organization are in success, failed, and cancelled states over time.
Workflow by orgs shows a colored doughnut chart that represents different organizations, and total number of workflows run by the organization irrespective of the workflow statuses. Mouse over a color to view details.
Workflow status by circle maintainers shows a table that lists workflow author names along with the how many workflows are success, failed, cancelled, and approved per author.
Workflow status by repositories shows a table that lists origin repository where the workflow is created, target repository along with the how many workflows are success, failed, and cancelled.
MTTR in last 90 days by Workflow in Hours shows a table that displays how much time (in hours) it took for a workflow to recover from the failed state. Mean Time To Recover (MTTR) displays data only for last 90 days.
Click to share the path of respective dashboards.
Registry shows metrics of Docker Hub container images.
The DockerHub dashboard is available from Registry **** drop-down list, and represents a set of metrics that provide information about DockerHub container images.
Overview shows high-level information about docker images.
Filter lets you filter the dashboard data by docker image. Select values from the drop-down list, and click Apply changes to filter the dashboard as per selection.
DockerHub shows the total number of Docker Images, 50th percentile of Median Stars by Image, and 50th percentile of Median Pulls by Image.
Top Image Pulls shows a doughnut chart that represents top docker images. Mouse over a color in the chart to view details, such as docker image name, number, and its percentage.
Total Stars shows a table that represents total number of stars per calendar period. Mouse over to view details for a calendar date.
Total Pulls shows a table that represents total number of pulls per calendar period. Mouse over to view details for a calendar date.
Pull Trends shows a comparison of pull counts and trends for a calendar period.
Images shows a table that lets you sort values by Docker Image, Stars, and Pulls.
By default, Bot commit is filtered, and can't be included for Summary dashboard.
Summary provides a high-level metrics about each data source for which the project is configured. Following are activities for quick navigation:
Chat Room **** shows an analytic overview of Slack and RocketChat channels used by a project.
Slack shows total number of messages, channels, participants, replies, and reactions over time. Clicking Go To Overview and View All under Slack takes you to the respective table/chart/graph of Slack > Overview section.
RocketChat shows total number of messages, channels, participants, replies, and reactions over time. Clicking Go To Overview and View All under RocketChat takes you to the respective table/chart/graph of RocketChat > Overview section.
Top 10 Message Senders lists the top ten individuals—who communicate most in the project— by name, number of messages, and percentage of messages out of the total number of messages shared by the community.
Top 10 Channels lists the top ten slack channels where most amount of communication is happening. It shows the channel name, number of messages per channel, and percentage of messages per channel. Following is an example of chat room dashboard:
Mailing List shows an analytic overview of email communication channels, such as Groups.io or Pipermail:
Groupsio shows total number of emails, groups, companies, authors, and average number of messages communicated over time.
Google Groups shows a richer context around how frequently the community is interacting. **** Project community managers can use metrics like “Daily Active Users”, “Emails by Organization”, and even “Top Trending Topics” to better engage and acknowledge their community members. For detail metrics, see Google Groups.
Piper Mail shows total number of emails, mailing lists, companies, authors, and average number of messages communicated over time.
Top 10 Email Senders lists the top ten individuals—who communicate most in the project— by name, number of emails, and percentage of emails out of the total number of emails shared by the community.
Top 10 Mailing Lists lists the top ten email lists where most number of communication is happening. It shows the list name, number of emails per list, and percentage of emails per list.
Documentation shows an analytic overview of project's confluence pages for a selected time range. It shows total number of confluence pages created/edited, total number comments in the form of feedback or conversation on confluence pages, total number of editors who contributed to create/edit or provide feedback/comment on the confluence pages, and average number of editors per day.
Top 10 Editors lists the top ten individuals— who makes most number of edits/updates— by name, number of pages edited by the individual, and percentage of contribution out of the total document contribution by the community members.
Top 10 Companies lists the top ten companies— that contribute most to the project— by name, total number of editions, and percentage.
Earned Media shows analytic overview of how many times consumers (unique users) searched, mentioned, and shared project related articles or blogs on different media platforms, such as facebook, linkedin, blog sites, news publishing websites, and so on. The data includes various metrics, such as geographical data, sentiment analysis, SEO metrics, social media sharing/mentions, publishers, and so on.
Total Shares shows how many times a project's search results are shared by consumers on different social media platforms. This also shows number of shares on individual social media platforms.
Top 10 Publishers lists top ten media houses and blog sites that mention most about the project in the form of articles and blog posts. It includes the number and percentage of mentions about your project.
Key Messages shows a doughnut chart that displays how many times the project and its competitors' search results are mentioned by consumers (unique users). Mouse over a color in the chart to see the number of mentions for a project out of the total mentions. For example, Linux Foundation is mentioned 4.88k times by consumers on different media platforms out of the total 6.52k times including its competitors' mentions as per the following data.
The Rocket Chat dashboard represents a set of metrics that shows analytics about Rocket Chat communication channel.
Overview shows high-level information about how developers use Rocket Chat. For example, you can see the channels in which people send the most messages. You can sort channels by the number of messages, participants, replies, and other values.
Filter lets you filter the dashboard data by author name and organization name. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of Channels, Messages, Participants, Replies, and Reactions, of the project over time.
Trending Reactions shows a doughnut chart that represents the total number of reactions in the project per reaction value. Mouse over a color in the chart to see the total number of reactions for each reaction value, and their percentage of the project's total reactions.
Top Trending Terms shows a term cloud of the top 20 terms that participants used. Click a term to show the corresponding data in the dashboard.
Messages shows a bar graph that represents the number of messages per day over time. Mouse over a color in the graph to see the total number of messages for a date.
Messages By Organization shows a doughnut chart that represents the total number of messages in the project per organization. Mouse over a color in the chart to see the total number of messages for each organization, and their percentage of the project's total messages.
Active Participants shows a bar graph that represents the number of participants per day over time. Mouse over a color in the graph to see the total number of participants for a date.
Top Participating Organizations shows a table that lets you sort values by organization name, number of channels, messages, and participants of an organization.
Top Participants shows a table that lets you sort values by Participants, Avatar, Messages, Channels, date and time for first and last comments.
Collaboration Metrics dashboard is displayed based on LF SSO account, and is accessible to:
Individuals of member companies of The Linux Foundation.
Insights project administrators who have access to manage contributor affiliations in Insights.
Project maintainers or members of any formally elected committees like the Marketing Outreach Committee, Technical Oversight Committee, and so on.
Following screen is displayed when you are not signed in or you don't have access to Ecosystem Trends dashboard. Click Go to My Profile to navigate to the Individual Dashboard to update your organization, as described in Edit My Information.
Following are the data sources configured under Collaboration Metrics:
The Groupsio dashboard is available from the Mailing List drop-down list, and represents a set of metrics that shows information about the groups.io communication channel.
Overview shows a high-level information about email activity of groups for a project.
Filter lets you filter the dashboard data by author name and organization name. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of Emails (that includes both sent and received), Participants, and Lists over time.
Participants By Organization shows a doughnut chart that represents the total number of individuals per organization who have sent the messages/emails. Mouse over a color in the chart to see the organization name, total number and percentage of individuals of that organization out of the total number of authors who have sent emails/messages.
Active Participants shows a bar graph that represents the total number of participants per day over time. Mouse over a color to see the total number of participants for a particular day.
Messages Sent shows a bar graph that represents the total number of messages per day over time. Mouse over a color to see the total number of messages for a particular day.
Messages By Timezone shows a bar graph with a count of messages per Coordinated Universal Time (UTC) time zone. Mouse over a color in the graph to see the total number of messages for each time zone.
Top Participating Authors shows a table that lists participant names, number of messages per participant, date and time of first and last message sent by the participant.
Top Participating Organizations shows a table that lists organization name, number of messages shared by the organization, and number of participants of the organization.
Recent Messages shows a table lists the recent date and time when the message was sent, subject of the message, and the participant name who sent the message.
Top Mailinglist shows a table that lists links of top 5 mailing lists, number of emails, senders, and organizations associated with the mailing list.
By default, Bot Commits are filtered, however, you can include the filter value by navigating to the filter section of dashboard. For details, see .
Top Trending Subjects shows a subject cloud of most discussed topics/subjects in the channel. Click a subject to view the corresponding data in dashboard. Close or delete the filter to see default values.
By default, Bot Commits are filtered, however, you can include the filter value by navigating to the filter section of dashboard. For details, see Add and Manage Data Filters.
Pipermail dashboard is available from the Mailing List drop-down list, and represents a set of metrics that shows email details about Pipermail communication channel.
Overview shows high-level information about email activity in projects, and who sent emails and when. Information about the corresponding organization is also provided.
Filter lets you filter the dashboard data by author name and organization name. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of Emails, Senders, and Mailing Lists over time.
Emails shows a bar graph that represents the number of emails over time. Mouse over a color in the graph to see the total number of emails for a date.
Email Senders shows a bar graph that represents the number of email senders per day over time. Mouse over a color in the graph to see the total number of email senders for a date.
Emails by Time Zone shows a bar graph with a count of emails per Coordinated Universal Time (UTC) time zone. Dates and times use the time zone of the computer where the sender mailed the email. This data is used to display time zone information. Mouse over a color in the graph to see the total number of emails for each time zone.
Emails By Organizations shows a doughnut chart that represents the total number of emails by each organization. Mouse over a color (organization) in the chart to see the organization name, total number of emails, and the percentage of the project's emails.
Emails By Organizations Per Day shows a stacked bar graph that represents the number of emails by organization over time. Mouse over a color in the graph to see the total number of emails for the organization and the date.
Email Senders shows a table that lets you sort values by Email Sender, Emails, Projects, Mailing Lists, and Avg. Characters.
Mailing Lists shows a table that lets you sort values by Mailing List, Emails, Senders, and Organizations.
Earned Media shows analytical overview of how many times consumers (unique users based on UUID) searched, mentioned, and shared project related articles or blogs on different media platforms, starting from Facebook, Linked to blog sites and news publishing websites. This helps project administrators, companies and organizations to understand software development projects through quantitative analysis of social media activity, and processes. Earned Media includes various metrics, such as geographical data, sentiment analysis, SEO metrics, social media sharing/mentions, publishers, and so on.
Search engine optimization (SEO) is the process of optimizing a website's online content so that it is displayed as a top result on search engines for a certain keyword of the website. __ Depending upon the number of visitors to project's website, the impact is determined. This analysis helps project administrators decide how well they can build SEO friendly website to attract more unique users.
SEO Impact displays the impact of a project's website on search page rankings. SEO Impact is ranked on a scale from 1-100, with a higher score meaning a better position in search results.
Number of Mentions shows how many times a project related article or blog is mentioned over different media types based on project's search term (keyword). One article/blog is equal to one mention even if the search terms are used more than once in the article/blog.
Non-PR Referral Traffic shows periodic analysis of how many times your website is visited from other articles and blog posts with backlinks for your website. This doesn't include data if a user visits your website directly using website URL.
Total Coverage vs. Total Web Traffic shows the potential impact your total news coverage has on your total website traffic_._ These values are color coded. Total coverage or total sessions shows periodic analysis of how many times your website is visited from both PR and Non-PR activities. Total coverage is based on your search value, and includes traffic from articles and blog posts with and without backlinks.
Affiliation Management becomes enable for you after you request and, are granted access to your specific projects.
Prerequisites: You must have a Single Sign-On (SSO) account. Create an account if you do not have an SSO account.
1. Sign in to LFX Insights, and navigate to a project group or individual project dashboard.
2. From the navigation bar, click Request To Edit Affiliations.
3. Provide details in the form that appears.
4. Click Create.
You are notified when you are granted access. After you are granted access, use your SSO account credentials to sign in and, search and manage contributors' affiliations.
Affiliation is a close association or connection to an organization, company, and so on. An example of affiliation is being a contributor to a community organization. Or, a contributor could belong to two or more companies that are related through common ownership but are treated as one. In this case, a single contributor might have multiple identities such as two different company emails. Data affiliation connects or associates these identities.
Insights uses Identities and Affiliations to handle data affiliations as follows:
Open source projects rely on a variety of data sources and tools to support and coordinate development activities, for example:
Git repositories, such as Gerrit or GitHub projects
Issue trackers such as Jira, GitHub Issues or Bugzilla
Messaging tools such as Slack, Groups.io or mailing lists
Build tools such as Jenkins
Project contributors can access the tools using different identities, for example: email, username. In Insights, each contributor has a profile. A profile has personal details and can include multiple identities and organization affiliations.
An identity can be a combination of email address, full name, or username. Examples of identities are "commit signatures" (that is, full names and email addresses) of committers and authors in Git repositories. However, the identities used by the same profile (contributor) may differ across the tools used in the project. A project profile might use more than one identity for the same tool (for example, in version control systems and mailing lists). In addition, an identity can be shared by project profiles, such as during pair programming (that is, the same email address for both profiles).
Insights manages identities across sources allowing identities to be affiliated, for example, a company and organization affiliation. In a database, identity and affiliation data is stored across domains. INSIGHTS evaluates individual contributions to open source projects by tracking the unique identities of profiles and their related information such as country and organization. Projects then produce meaningful statistics about their communities, because individual contributions are not underestimated.
An analysis of the enriched information (identities, affiliation, bot status, and so on) allows for a correct count of developers and others in software development. INSIGHTS retrieves the data, stores it in databases, analyzes it, and produces dashboards for visualizing the resulting information. The results let you measure any project as a whole using aggregated data of more than one type.
Edit a profile to add or update contributor information. You can mark a profile as a bot to indicate that the activity may not be worth counting. By doing so, contributions for this profile will not be counted in dashboards.
To Edit a Profile:
1. Click a project of interest.
2. Click Identities & Affiliations.
3. Select a profile from the Top Unaffiliated Contributors list or search for a profile that you want to edit.
4. Click a row that corresponds to a name of interest.
5. From User Profile Details section, click Edit. ****The Name, E-mail, and Bot fields become editable.
6. Update any of the Personal Details and click Save Changes.
Compare Project Health Dashboard is a tool that lets you compare key code related metrics for a project or between projects (at the most you can compare 10 projects side-by-side). These metrics come from a variety of data sources that can be broadly categorized into Version Control System and Issue Management System, and include supported systems, such as Git, Github, Gerrit, Jira and Bugzilla.
The dashboard serves two purposes:
Comparing the key metrics for the same project for different time periods.
Comparing the key metrics between multiple projects for the selected time period.
Note: For better comparing of metrics between projects, compare projects that have the same data sources as version control or issue management systems. If you compare projects that use different data sources, the side-by-side comparison will not be available, and metrics will show separately. For example if you compare between Onap and Yocto, Onap uses Jira and Yocto uses Bugzilla as issue management systems, the comparison of these two metrics will not be displayed side-by-side, rather will show separately.
The Following data sources display various metrics as described below:
Days Since Last Commit: Number of days there has not been any code contributions to the project.
Last Commit Date: Day when there was a last code contribution to the project.
Number of Commits: Total number of code commits to the project for the selected time range.
Number of total code contributors: Total number of contributors to the project for the selected time range.
Percent of commits from the top organization: Displays name of the organization that contributed most number of code changes to the project. It also displays the percentage of code commits from the organization compared to the total number of commits made to the project by all the organizations.
Percent of commit contributors from the top organization: Displays name of the organization from which maximum number of contributors committed code changes. It also displays the percentage of contributors from the organization compared to the total number of contributors to the project.
Percent of commits by affiliated contributors: Displays percentage of code contributions made by those contributors who are affiliated with organizations. It means these percentage of contributions are not from "Unknown" authors.
Percent of affiliated contributors: Displays percentage of contributors who are affiliated with organizations. It means these percentage of contributors are not tagged "Unknown".
Number of contributors reviewing PRs: Total number of contributors who are currently reviewing the pull requests for the project for a selected time range.
Number of PRs rejected: Total number of pull requests that are rejected for a selected time period.
Organization reviewing most PRs: Displays name of the organization whose contributors are reviewing most number of pull requests. It also displays the percentage of reviews done by the organization in relation to the total reviews done by other organizations to the project.
Average PR lead time (time in days for a PR to get merged): Displays average number of days it took for a PR to get merged.
Number of contributors merging PRs: Total number of contributors, for a selected time range, who are merging the pull requests.
Number of new contributors merging PRs (it is displayed for a selected time range): Total number of new contributors, over a selected time range, who are merging PRs.
Number of PRs closed: Total number of pull requests that are closed for a selected time range.
Number of PRs opened: Total number of pull requests that are newly created over a selected time range.
Number of PRs merged: Total number of pull requests that are merged over a selected time range.
Opened to closed rate: Displays the ratio between numbers of open and closed PRs during the selected time period.
Percent of contributors merging PRs from the top organization: Displays name of the organization from which maximum number of contributors are merging pull requests for a selected time range. It also displays the percentage of contributors from the organization compared to the total number of contributors to the project.
Percent of PRs merged from the top organization: Displays name of the organization whose contributors have merged maximum number of pull requests for a selected time range. It also displays the percentage of PRs merged by the organization compared to the total number of PRs merged by all the organizations.
Number of contributors merging changesets: Total number of contributors, for a selected time range, who merged the changesets.
Number of new contributors merging changesets (it is displayed for a selected time range): Total number of new contributors, for a selected time range, who are merging changesets.
Number of changesets merged: Total number of changesets merged over a selected time range.
Number of changesets approved: Total number of changesets approved over a selected time range.
Number of changesets opened: Total number of changesets that are newly created over a selected time range.
Number of changesets closed: Total number of changesets that are closed over a selected time range.
Opened to closed rate: Displays the ratio between numbers of open and closed changesets during the selected time period.
Percent of contributors merging changesets from the top organization: Displays name of the organization from which maximum number of contributors are merging changesets for a selected time range. It also displays the percentage of contributors from the organization compared to the total number of contributors to the project.
Percent of changesets merged from the top organization: Displays name of the organization whose contributors have merged maximum number of changesets for a selected time range. It also displays the percentage of changesets merged by the organization compared to the total number of changesets merged by all the organizations.
75th Percentile of time issue in open state: Total number of days for which 75% of the total GitHub issues are in open state.
95th Percentile of time issue in open state: Total number of days for which 95% of the total GitHub issues are in open state.
Median time issue in open state: Average number of days for which the issues are in open state.
Number of issues closed: Total number of issues that are closed over a selected time range.
Number of issues opened: Total number of issues that are created over a selected time range.
Opened to closed rate: Displays the ratio between numbers of open and closed GitHub Issues during the selected time period.
Each section displays the following metrics:
Total number of issues: Total number of issues created over a selected time range.
Number of submitters: Total number issue submitters for a selected time range.
Number of assignees: Number authors, over a selected time range, who are assigned with the created issues.
75th Percentile of time issue in open state: Total number of days for which 75% of the total issues are in open state.
95th Percentile of time issue in open state: Total number of days for which 95% of the total issues are in open state.
Median time issue in open state: Average number of days for which the issues are in open state.
Total Number of reopened issues: Total number of issues that are re-opened over a selected time range.
Total Number of issues in closed/completed state: Total number of issues that are closed or completed over a selected time range.
Total Number of issues in open/to-do state: Total number of issues that are in open or to-do state over a selected time range.
Open to closed rate: Displays the ratio between numbers of open and closed Jira or Bugzilla issues during the selected time period.
Percent of issues submitted from the top organization: Displays name of the organization whose contributors are submitting maximum number of issues over a selected time range. It also displays the percentage of issues submitted by the organization compared to the total number of issues submitted to the project by all organizations.
Percent of submitters from the top organization: Displays name of the organization from which maximum number of contributors submitted issues for a selected time range. It also displays the percentage of issue submitters from the organization compared to the total number of submitters of the project from all organizations.
1. Go to https://insights.lfx.linuxfoundation.org/
2. From the top left corner, click Compare Project Health.
3. Type and select a project in the Search Projects field.
4. Click +Project to add a new field to select and compare projects. Note: Default time range is “All”. Select a time range from the available options to change the metrics for the time period.
A data marker represents a single data value on bar graphs, stacked bar graphs, doughnut charts, and so on. You can change the color of a data marker to meet your needs.
Click the color you want to use. The data marker refreshes to show the color that you chose.
Organizations are shared accounts where open source projects can collaborate across many projects at once. Affiliation Management lets you:
Affiliate a profile with one or more organizations and for a specific enrollment period—this means that Insights counts the affiliated profile data in various organization charts and graphs.
Delete an organization affiliation—this means that Insights does not count the affiliated profile data in organization charts and graphs.
Select a project name of interest.
Click Identities & Affiliations.
Select a profile from Top Unaffiliated Contributors list or search for a profile.
Click a row that corresponds to a name of interest. Profile Information appears.
Navigate to Organization Affiliation. Organizations and their corresponding enrollment dates are listed.
Continue to add or delete organization affiliations:
An organization affiliation relates a profile (unique identity) and an organization. An enrollment specifies that the person is associated with (employed at) an organization during a certain period.
1. Click Add New. The Add an Enrollment pane appears. Note: Organization Name and Start date are mandatory fields.
2. In the Organization Name field, start typing the name you want to add and select a name from the drop-down list that appears. (Click X next to the field to cancel your selection.) Note: If organization name doesn't appear from list, click Add new Organization from the option shown.
3. Specify an enrollment period by selecting start and end dates. Enter in a date field or click the down arrow to open a calendar and select a date. You can change the enrollment period at anytime.
4. Click Add Enrollment. The organization is listed in Affiliations.
Click Delete next to the organization that you want to withdraw.
Click Delete on the Confirm dialog that appears.
The organization affiliation is deleted.
You can update only enrollment dates.
Click Update next to the organization for which you want to update the enrollment dates.
Change enrollment dates, and click Update Enrollment Dates. The organization affiliation is updated.
On a chart legend, click the color of the individual data marker that you want to change. A color chart appears:
The Help Center offers various options to help you get the assistance you need.
Sign in to the Linux Foundation Help Center.
Select LFX Insights, and click an option based on your request type.
Complete the ticket form fields and click Create. You are notified with your ticket information.
Troubleshooting helps you solve problematic symptoms in your INSIGHTS implementation.
Insights scans do not occur automatically and/or general errors occur.
Sign in to the Linux Foundation Help Center.
Select LFX Insights, and click a relevant option for your issue.
Complete the ticket form fields requesting the repository change that you want and click Create.
Important: Do not perform any of the following repository actions, which can impact Insights data scans negatively.
Delete a repository—may cause general errors. The minimum impact is that the repository will no longer be scanned.
Create a repository creation—the repository is not scanned automatically.
Update a public repository to be a private repository—may cause general errors. The minimum impact is that the repository will no longer be scanned.
Update a private repository to be public repository—the repository is not scanned automatically.
If you notice that the slack data for your project is not getting updated or reporting stale data, it might be due to the following reasons:
Issue 1 : If the slack application named insights-bot-service
is uninstalled from the workspace.
Resolution 1 : Contact your project's slack-workspace administrator to ensure that the app insights-bot-service
is installed. If not then, search for the app on the slack market place and get it installed. Once the app is installed, please contact the LFX support desk so that the new token can be updated at our end as well.
Issue 2: If the events for the insights-bot-service
slack application are turned off.
Resolution 2: Contact the slack workspace administrator to turn on the events reported by the insights-bot-service
as that is the only way the data is fetched into LFX Insights platform.
Issue 3: If the insights-bot-service
bot is removed from the channel.
Resolution 3: Workspace administrators must add the bot back to the channel.
Roles: Developers, Community Managers
Where: GitHub Pull Requests dashboard is available from the Source Control drop-down list.
Insights lets you look at the pull request contributions to the project and answer questions such as:
Who contributes to the community by submitting pull requests?
How responsive is the project to changes?
Who does the bulk of the work?
Which organizations submit pull requests for the project?
Follow these steps:
From the Source Control drop-down list, select GitHub > Pull Requests.
A dashboard shows information about pull requests for a project and organization, and information about who submitted the pull request and when. For details, see Source Control > GitHub > Pull Requests.
Use the visualizations to understand the project activity and other aspects of the pull requests:
As a developer, you can see how active a project is and the average duration that pull requests remain open. In Pull Request by Status Over Time, you note a recurring pattern of pull requests that remain open too long within a certain time frame. The length of time pull requests remain open can indicate how responsive and welcoming your project maintainers are to outside contributors. If a pull request sits for too long without response, potential contributors may go to other projects. In addition, pull request metrics depend on the size of the project. Small projects might keep the number of open pull requests at 10 or fewer. Keeping pull requests at this limit would be challenging for large projects that have lots of community input compared to the number of maintainers. Reviewing pull requests takes time so large projects tend to have longer open duration than small projects. This data helps you decide if this is a project in which you want to spend your time.
As a project maintainer, you can see the number of pull requests by submitters, organizations, and repositories. In Organizations, you look for the organization that is doing the bulk of the development effort.
Useful options let you perform actions on a visualization, such as exporting data from a table. Visualizations provide an option where appropriate.
1. Open a dashboard and then go to a visualization of interest.
Following example shows data specifically for a selected organization:
Following example shows dashboard where an organization's data is removed/filtered.
3. Click a common icon or item as available to:
Insights uses the following common terms in the product documentation and in the user interface:
In GitHub, approve is a review status when someone submits feedback and approves merging the changes proposed in the pull request.
An author is the person who originally wrote a piece of code in Git.
A backlog is a list of all things that need to be done within a project.
Backlog Management Index (BMI) is the number of closed issues divided by the number of open ones in a given period of time.
A Git branch is an independent line of development. A branch lets you isolate your work from others. Changes in the primary branch or other branches do not affect your branch, unless you decide to pull the latest changes from those branches.
Bugzilla is an open source defect tracking tool that can be used for managing software development.
In GitHub, comment is a review status when someone submits feedback without approving the changes proposed in the pull request.
A commit is an individual change to a file or set of files. A committer is anyone who made a commit or pull request on behalf of the original author.
Atlassian Confluence is a content tool that teams use to collaborate and share knowledge. Confluence lets users create pages and blogs, which all team members can comment on and edit.
A Contributor is someone (typically a developer) who contributes code to a GitHub/Gerrit/GitLab project.
A contribution is a review, comment, commit, issue, or pull request. A contributor is someone from the outside not on the core development team of the project that wants to contribute some changes to a project, but does not have collaborator access.
Churn rate is defined as the total number of inactive contributors. It is calculated as:
Total Inactive Contributors recorded at the end of the time period/ (Total Active Contributors recorded at the start + Total New Contributors who joined during the selected time period)
A dashboard is a data visualization that displays analytics metrics and important data points for an organization, a project, and other data on a single page.
Data affiliation connects or associates identities. Affiliation is a close association or connection to an organization, company, and so on. An example of affiliation is being a member of a community organization. Or, a member could belong to two or more companies that are related through common ownership, but are treated as one. In this case, a single member might have multiple identities such as two different company emails.
Data sources are the collaboration tools or the remote servers that are used by projects to drive the development of a project. For example, in a database management system, the primary data source is the database, which can be located in a disk or a remote server. The data source for a computer program can be a file, a data sheet, a spreadsheet, an XML file or even hard-coded data within the program.
Free and Open Source Software (FOSS) development is software developed by informal collaborative networks of programmers.
Gerrit is a free web-based team code collaboration tool. Software developers in a team can review each other's modifications on their source code using a Web browser and approve or reject those changes. Gerrit integrates closely with Git.
Git is an open source program for tracking changes in source code during software development.
GitHub is a web-based hosting service for version control using Git.
In Identity Management, an identity is a record (tuple) composed of a name, email, username, and the name of the source from where it was extracted.
In GitHub, an issue is a suggested improvement, task, or question that is related to the repository. Anyone can create an issue (for public repositories). Issues are moderated by repository collaborators.
Jenkins is an open source continuous integration software tool for testing and reporting on changes in a code base in real time.
Jira is an issue tracking product that allows bug tracking and agile project management.
A label is a classifying name or phrase on a project that identifies subjects for the project repositories.
A mailing list is a list of email addresses that allows for a wide distribution of information to many Internet users.
A new contributor is someone who has never contributed to the project before, and is contributing for the first time.
In GitHub, onion model analysis defines the number and identity of core, regular, and casual contributors. These contributors are individuals who have done 80 percent (core), 15 percent (regular), and 5 percent (casual) of the contributions to a project.
The open source community is a body of programmers who develop and participate in computer programs in which the source code is available to the general public for use or modification from its original design. open source code is a collaborative effort, where programmers improve the source code and share the changes within the community.
In GitHub, an organization is a collection of user accounts that own repositories. Organizations let businesses and open source projects collaborate across many projects at once.
A patch is a set of changes to a computer program to update, fix, or improve it the program. In Git, a patch is a small file that indicates what was changed in a repository.
Public domain project—A non-Linux Foundation project that is managed independently of the Linux Foundation, but that is participating in one or more Linux Foundation services (for example, Express Gateway, Vue.js).
Member project—A Linux Foundation project that maintains its own governance and membership (for example, Cloud Native Computing Foundation or LF Networking).
Member subproject—A Linux Foundation project whose governance and membership is managed using a parent member project, but may also provide its own limited, more focused, governance (for example, Kubernetes).
A pull request (PR) is a proposed change to a repository that is submitted by a user and accepted or rejected by repository collaborators.
A push refers to sending your committed changes to a remote repository. A pusher is someone who sends committed changes to a remote repository, such as a repository hosted on GitHub.
A repository is an element in GitHub that contains all the project files (including documentation) and stores each file's revision history.
Review Efficiency Index (REI) is the number of closed pull requests divided by the number of open ones in a given period of time.
Slack is a cloud-based set of team collaboration tools and services.
A submit is an action that lets you comment on a pull request, approve proposed changes, or request changes that must be addressed before the pull request can be merged. A submitter is someone who performs the submit.
Unaffiliated contributors are those contributors who are contributing (or have contributed) to the project but their organization association is still 'Unknown'.
Unique commits are identified based on the SHA (Secure Hash Algorithm) associated with a commit. For multiple entries for a single commit, the number of unique commits are considered as one because unique commits are filtered based on the unique SHA of the commit.
The repositories based on their unique names. It refers to the complete path (also called origin) of the repository URL.
Universally Unique Identifier. The author UUID is given by LFX Insights based on the GitHub username, name, and email address of a contributor.
A visualization is data that is represented in a visual context such as a graph or chart. Patterns, trends, and correlations can be exposed in a data visualization.
Click a project name of interest that shows the GitHub logounder data sources.
2. For a doughnut chart visualization, click a value or organization as shown below, and then click to view data specifically for the selected value or to remove its data for a dashboard.
Icon | Description |
---|
It refers to those who are contributing to the project or contributed to the project in the last six month from the current date.
A who is committing code or participating in the project on behalf of an organization.
It refers to those who did not contribute to the project in the last six month from the current date.
Individual are those who are contributing to the project in an individual capacity, such as freelancers, and do not have affiliation to any organization.
A project defines any open source collaborative effort, which can be a specific repository (for example, ), a coalition of like projects (for example, LF Energy), or a formal organization, for example, Cloud Native Computing Foundation). Other project definitions follow:
Nonmember project—A Linux Foundation project that does not maintain its own formal governance and membership, but is instead directly managed by the Linux Foundation, for example .
Contribution by contributors/developers based on their s. For example, if ten contributors have pushed 20 commits each, the number of unique contributors will be considered as 10, not 200 as it is the total number of commits.
Options:
Full screen: Expands a visualization to full screen. |
Toggles the list view |
Show and hide a legend. |
Sort the column data in ascending or descending order. |
Export and download data to a Comma-Separated Values (CSV) file.
|
Open the corresponding URL. |
Role: Developer, Project Manager, Community Manager
Where: GitHub issue dashboards are available from the Issue Management drop-down list.
Users who cannot submit a pull request, but encounter problems with code can submit their bugs and feature requests as issues. The number of issues, and how they are addressed, can indicate your projects’ levels of user adoption as well as how responsive maintainers are to user needs. This number depends on how issues are tracked. Consider that issues may remain open longer for a project that uses GitHub issues only for bugs rather than one that uses issues for bugs and feature requests.
This example demonstrates how you can view GitHub issues and then analyze how efficiently a project and its organizations handle the issues. How quickly a project closes issues can determine if you want to participate in the project. INSIGHTS lets you see how efficiently organizations and projects close issues.
Follow these steps:
From the Issue Management drop-down list, select GitHub > PR Efficiency. A dashboard shows GitHub efficiency data. For details see, Issue Management > GitHub > PR Efficiency.
BMI shows a multi-line graph that represents the Backlog Management Index (BMI). BMI is the number of closed issues divided by the number of open ones in a given period of time. Moving Avg. is set to 8 weeks to identify changes in trends. Average is also shown as a reference. BMI values greater than 1 mean the community is closing more issues than those they are opening. Values less than 1 mean the opposite—more issues are open than those closed during a given time frame. Mouse over this graph or Lead Time to show a line that displays the date and time at the top of the legend.
This data can help you determine if the project is one in which you want to participate.
Roles: Developer, Project Manager
Where: Jira dashboards are available from the Issue Management drop-down list.
You are interested in participating in a project, but first, you want to see if the project has an accumulation of uncompleted work that needs to be dealt with in the backlog.
Do these steps:
From the Issue Management drop-down list, select Jira > Backlog. A dashboard focuses on open issues, their accumulated time, and associated organization. For details, see Jira > Backlog.
View statistics about open issues in Open Issues Statistics. These statistics give you a summary of open issues in the backlog.
Find more information in the dashboard such as who the submitters are and the average days open of the issues that they submit. For example, you might notice a recurring pattern of issues that accumulate in a certain time frame.
This data can help you decide if this is a project in which you want to spend your time.
You use Confluence for your project documentation. You are interested in getting information about Confluence activities such as the top edited pages and top editors. This information helps you identify where your documentation effort is focused and by whom.
Do these steps:
Click a project name of interest.
Use the visualizations to understand aspects of documentation activities and pages.
Click a project name of interest that shows the GitHub logounder data sources.
On Efficiency Closing GitHub Issues window, select an organization and project from drop-down lists, and click Apply changes.
Use the resulting data to understand how efficiently issues are handled. For example, red for Time to Close indicates that committers are not attending to issues or that contributors are not providing fixes.
Repositories table shows the average time for GitHub issues to be closed for each repository in a project. Repositories with many open issues can indicate security problems.
Click a project name on a project of interest that shows the Jira logo .
Look at the data in Issues waiting to be closed and Accumulated Time (days): Issues waiting to be closed to learn about the number of issues by status over time.
From the Documentation drop-down list, select Confluence > Overview. The Overview dashboard shows information about Confluence activities. For details, see .
Roles: Project Manager
Where: Bugzilla dashboards are available from the Issue Management drop-down list.
As a project manager, your team uses Bugzilla for bug tracking and for project management. You are interested in getting an overview of issues and submitters in your projects. You want to see who is submitting issues (bugs).
Do these steps:
Click a project name of interest.
From the Project Management drop-down list, select Bugzilla > Overview. A dashboard shows information about issues and submitters in Bugzilla organizations. For details, see Bugzilla > Overview.
Use the visualizations to understand aspects of Bugzilla tracking and project management. You go to Submitters to see who submits the most issues and the average open days for the issues.
Roles: Developer, Community Manager, Project Manager
Where: Communication dashboards are available from the Chat Room and Mailing List drop-down lists.
Chat Room provides metrics of slack activity, and Mailing List provides metrics of Groups.io and Pipermail. A mailing list is a common way for project community members to interact with others in a project. Mailing lists are often set up so that all members can send to the list. Members can ask questions and get help or provide information to others on the list. A busy mailing list can be a good indicator of the health of community engagement in the project. For our analysis, we will consider Pipermail as an example here.
Do these steps:
Click a project name of interest.
From the Mailing List drop-down list, select Pipermail > Overview. A dashboard shows information about email activity in projects and who sent emails and when. Information about the corresponding organization is also provided. For detail, see Pipermail > Overview.
Use the visualizations to understand aspects of mailing list activities for the project. Any conversation or discussion in a mailing list can be helpful to a project by solving bugs or even providing potential seeds for new features, new products, and so on. For example, you might be interested how active an organization's mailing list is—look at the analytics for the organization such as the Emails By Organizations doughnut chart: In another example, you hold in high esteem a community member and want to see if this person participates actively in the project—look at the Email Senders analytics.
Community Leaderboard helps you to analyze who contributes most and adds value to your project. LFX Insights analyzes and displays different identities, such as author name, the affiliated organization name, email address, number of commits, and many more data for each contributor of a project.
Note: Only project managers can view email addresses of contributors.
Community Leaderboard shows an Active Community Contributor board table that shows details about active contributors, and lets you download the table data to a CSV file.
Active Community Contributor board displays an aggregated data of individual contributors for three major data sources—Code based (Git and Gerrit), Issue Tracker (Jira, GitHub Issues, and Bugzilla), and Wiki page (confluence). Columns, such as Commits, LOC Added, LOC Modified, and LOC Deleted provide data of git repositories.
By default, data is displayed for Code data source. Select other data sources to view related data.
Search within Contributor Board lets you quickly search for contributor's details with author name and organization name. As an administrator for a project, you can also search details with email addresses of contributors of the project.
You can also quickly search a page by entering the age number in the Page number filed at the bottom right corner.
Click Export to download the table data to a .csv
file.
The Active Community Leaderboard Table lets you sort by values except Author Name, Organization name, and Email Id of contributors.
Name | Description |
---|
Author Name | Name of the contributor |
Organization | Name of affiliated organization |
Email Id | Email address of the contributor Note: Only Project Administrators, after signing in, can view Email Ids of contributors. |
Code | Following metrics are shown under Code data source. |
Commits | Total number of codes committed by the contributor to git repositories over time. |
**** | LOC Added | Total number of lines of code added by the contributor to git repositories over time. |
**** | LOC Modified | Total number of lines of code modified by the contributor on git repositories over time. |
**** | LOC Deleted | Total number of lines of code deleted by the contributor on git repository over time. |
GitHub PRs | Following metrics are shown under GitHub PRs data source. |
PRs Created | Total number of pull requests created by the contributor over time. |
PRs Open | Number of pull requests, out of all created PRs by the contributor, that are in open state over time. |
PRs Closed | Number of pull requests, out of all created PRs by the contributor, that are closed over time. |
PRs Merged | Number of pull requests, out of all created PRs by the contributor, that are merged over time. |
PRs Reviewed | Total number of pull requests reviewed by the contributor over time. |
PRs Approved | Total number of pull requests approved by the contributor over time. |
PRs Review Comments | Total number of review comments given by the contributor for all pull requests. |
PRs Comment Activity | Total number of review comments, code comments, and conversation comments given by the contributor for PRs. |
Gerrit | Following metrics are shown under Gerrit data source. |
Approvals | Total number of Gerrit changesets approved by the contributor. |
Active Changesets | Total number of Gerrit changesets, submitted by the contributor, that are in active state. |
Merged Changesets | Number of changesets, out of all submitted changesets by the contributor, that are merged over time. |
Review Comments | Total number of review comments given by the contributor for all changesets. |
Jira | Following metrics are shown under Jira issue management data source. |
Comments | Total number of comments given by the contributor for Jira issues. |
Issues Assigned | Total number of Jira issues assigned to the contributor over time. |
Issues Created | Total number of Jira issues created by the contributor. |
Issues Closed | Number of Jira issues, out of total issues created by the contributor, that are closed over time. |
Issues Avg Days In Open | Average number of days for which the Jira issues created by the contributor are in open state. |
GitHub Issues | Following metrics are shown under GitHub issue management data source. |
Issues Avg Days In Open | Average number of days for which the GitHub issues created by the contributor are in open state. |
Issues Created | Total number of GitHub issues created by the contributor. |
Issues Assigned | Total number of GitHub issues assigned to the contributor over time. |
Issues Closed | Number of GitHub issues, out of total issues created by the contributor, that are closed over time. |
**** | Issues Comments | Total number of comments given by the contributor for Jira issues. |
Bugzilla | Following metrics are shown under Bugzilla issue management data source. |
Issues Assigned | Total number of issues assigned to the contributor in Bugzilla over time. |
Issues Created | Total number of issues created by the contributor in Bugzilla over time. |
Issues Closed | Number of Bugzilla issues, out of total issues created by the contributor, that are closed over time. |
Issues Avg Days In Open | Average number of days for which the issues created by the contributor in Bugzilla, are in open state. |
Confluence | Following metrics are shown under Confluence wiki page doc management data source. |
Comments | Total number of comments give by the contributor on confluence over time. |
Posts | Total number blog posts created by the contributor over time. |
**** | Pages Created | Total number of confluence pages created by the contributor over time. |
Pages Edited | Total number of confluence pages edited by the contributor over time. |
Attachments | Total number of documents or files of any format the contributor attached to confluence pages over time. |
Last Update | Date when the contributor had contributed for the last time to wiki pages on confluence. |
**** | Days since Last Documentation | Total number of days since the contributor has not contributed anything to wiki pages on confluence. |
LFX Insights collects data for a project, segregates them to different data sources, such as source control for code related data, issue management for issues statuses, documentation for confluence and wiki pages, CI/CD for build systems, and so on. It represents these data on different visualization dashboards, such as graphs, charts, and tables.
Data sources are the collaboration tools or the remote servers that are used by projects to drive the development of a project. For example, in a database management system, the primary data source is the database, which can be located in a disk or a remote server. The data source for a computer program can be a file, a data sheet, a spreadsheet, an XML file or even hard-coded data within the program.
The Linux Foundation supports various data sources string from source control systems to social media platforms to collect and visualize project's data. For details, see Supported Data Sources.
No, Insights does not monitor forked repositories. A repository that is forked from another public repository contains commits from upstream projects and the current version of Insights cannot correctly differentiate between the contributions done on the forked repository and those coming from upstream. Hence, as a rule Insights does not monitor forked repositories.
In case if a repository that was being monitored**,** and later is deleted, then we will keep the data from the old repository as historical endpoints, and the data will be reflected on the dashboards when queried for the time period during which there were activities on that repository.
Anyone can see reports for projects that are on LFX platform. However, only project maintainers can see information related to affiliation management, and email ids of contributors.
It helps open source project maintainers monitor their project activity, total and individual contribution towards the project, active contributor lists, any unaffiliated contributors, and so on. This helps maintainers to solve problems effectively such as coding activity, code review backlog, performance, bottleneck identification, issue resolution, and so on.
Yes, if your project is set up on Linux Foundation's SFDC (Sales Force Dot Com) database, then LFX Insights automatically collects and visualizes data on graphs, charts, tables, and other customized dashboards.
With our latest upgrade to the github service, we are collecting more data than ever before**,** and producing many more metrics, such as detailed reviewer data and better efficiency statistics that were absent in the earlier versions. Since this upgrade affected the structure of the github data and the schema of the database, any github repository endpoint that can no longer be reached because they might have been deleted forever, and will not be included in our metrics reporting as we have no way to sync data for sync endpoints. If the repositories are renamed, then we can still process the data for the endpoint and there will be no loss in the data thus collected.
The Insights agents for google groups are designed to monitor the mailing lists by becoming a subscriber of those mailing lists, and reporting back to our servers all the emails that have been communicated. Once we have the raw emails, we enrich the data, and present them on the Insights dashboard for google groups. It involves two processes: Getting the archived data from project administrators, and syncing the email on a daily basis.
Getting the archived data for all the google groups mailing list: In this step, project administrators must provide a zipped archive (attached to a support help desk ticket) of the most recent emails for the mailing lists that we monitor in LFX Insights as our Insights agents cannot collect data from the past where our agent was not a part of the mailing list. If a new google group mailing list is created, the project administrator must inform the Insights team so that we can add our agent to the mailing list to monitor the activity.
Syncing emails everyday: Once we receive the archives, we import all the emails, and from that time onwards, we regularly sync all the emails as by then our google group agent will be a part of the mailing lists.
While onboarding a project for social media, the project administrators or community managers must provide the project's search terms that they want to track, social media handles, hashtags, and so on. Once we het the search terms, we use the respective social media (Twitter in this release) APIs to collect tweets or posts of last two years which are relevant to the project based on the provided search-terms. After onboarding is completed, our social media tool regularly syncs all the tweets and posts for the project.
Unaffiliated contributions are not counted under any organization, and are grouped as Unknown. LFX highly recommends to affiliate top contributors of your project.
No, affiliation data is linked to profiles, and profiles are visible across all the projects that they are part of. So, affiliation data for profiles are also visible across projects that they are part of.
Insight calculates contribution data based on commit hash. So, if a pull request or changeset is submitted to two different branches with the same commit hash identification number, Insight counts it as a single contribution, eliminating duplication of data.
Navigate to Technical Metrics > Source Control > Commits > Overview dashboard for your project, and filter the dashboard with the name of the organization as Individual - No Account. Scroll down to the Submitters metric to know the names and contribution details of the individual contributors.
No, you do not require permission to see the Trends dashboard. **** Anyone who navigates to these dashboards can view them without requiring an LF SSO (LFID) login or permission.
Trends metric data is aggregated based on time frames with different breakpoints, also called buckets. For example, for 1 year, the metrics are aggregated monthly with twelve breakpoints, for 2 years, they are aggregated quarterly with twelve break points, and so on. For details, see Time-Based Data Aggregation Methods.
Trends metrics are displayed depending upon the data sources that are configured for your project. If a project is not configured for a certain data source, the related metrics are not displayed on Project Trends.
Data sources are the collaboration tools or the remote servers that are used to drive the development of a project. LFX Insights accesses such data sources, collects data for a project, segregates them to different sections, such as source control for code related data, issue management for issues statuses, documentation for confluence and wiki pages, CI/CD for Jenkins, and so on.
Insights supports the following data sources based on their categories:
Insights supports Git, GitHub, and Gerrit for tracking and visualizing project's source code analytics. For details, see Source Control.
Following are the various issue tracking system data sources currently supported by Insights:
Insights supports Jenkins and CircleCI as two of the popular build system data sources.
Insights supports Pipermail, Groups.io, and Google Groups as email systems to visualize project related communication activities.
Insights supports chat room platforms, such as Slack and Rocket Chat to analyze the project related communication activities.
Insights supports Confluence for tracking and visualizing project's documentation. For details, see Confluence.
Insights supports Twitter as social media platform to visualize project's high-level insights from the project's twitter account.
Insights supports Cision to track and analyze the health of project's audience engagement, such as how frequently project is talked about in social media channels, how many times the project and the project relevant content is searched, and so on. For details, see Earned Media.
Insights supports DockerHub to track container images.
The Linux Foundation is developing Insights tool to support the following data sources in the next release:
The Linux Foundation is releasing soon the support for social media platforms, such as Facebook and LinkedIn.
The Linux Foundation is working towards supporting the following data sources very soon:
The Linux Foundation is releasing soon the support for some more popular build system data sources, such as Travis CI (Continuous Integration), GitLab CI, GitHub Actions, to name a few.
The Linux Foundation is developing Insights tool to support GitHub Team Discussions.
By default, Bot commit is filtered. To add/manage filters, see Add and Manage Data Filters.
The GitHub PR dashboards represent a set of metrics that shows pull request information of GitHub repositories of the project. Following are the various dashboards of GitHub PR:
By default, Bot commits are filtered. To apply more filters, see add and manage data filters.
Overview shows all the information about pull requests for a project.
Filter lets you filter the dashboard data by author name, organization name, repository name, and repository URL. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of pull requests, submitters, and repositories of the project over time.
Most Used PR Labels shows a cluster of top 10 Pull request labels. Click a label to filter the project dashboard to view label related details. Click the cross mark next to a label in the Add Filter navigation bar to remove the filter.
Submitters Over Time shows a bar graph that represents the number of pull request submitters per day over time. Mouse over a color in the graph to see the total number of submitters that occurred on a date.
Pull Requests By Organization shows a doughnut chart that represents the total number of pull requests per organization over a time range. Mouse over a color (organization) in the chart to see the organization name, total number and percentage of pull requests.
PRs Created Over Time shows a periodic line graph that displays the number of Pull Requests created over time. Hover mouse over the graph to view the date and number of PRs created on the date.
Pull Requests By Submitters shows a table that lists submitter name, number of pull requests by the submitter, number of repositories the submitter submitted PRs to, number of merged, rejected and open PRs by the submitter, and average number of days taken to merge the submitter's PRs.
Pull Request by Organization shows a table that lists and lets you sort values by organization name, number of Pull Requests submitted by the organization over time, total number of submitters of the organization, and number of repositories to which the submitters of the organization have submitted PRs .
Pull Requests By Repositories shows a table that lists and lets you sort values by repository link, number of pull requests per repository, number of PR submitters for the repository, and average time taken in days to merge the PRs. You can select a repository to view details on GitHub.
Efficiency offers an overall view of understanding and optimizing project efficiency in closing GitHub Pull Requests.
Filter lets you filter the project data by organization name, author name, repository name, and repository URL. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows a cluster of
50th percentile of Time To Merge (Days): The number of days it took to merge 50 percent of the pull requests.
95th percentile of Time To Merge (Days): The number of days it took to merge 95 percent of the pull requests.
Merged PRs: Total number of pull requests merged.
Organizations: Total number of organizations whose submitters authored the merged pull requests.
Submitters: Total number of submitters whose pull requests were merged.
Repositories: Total number of repositories the merged pull requests belonged to.
50th percentile of Time To Close By Repo shows a cluster of top 10 repositories names for which it took most time to merge 50% of the pull requests.
Time to Merge shows a graph that displays number of Pull Requests that took certain amount of time to get merged. These time slots are divided into four categories, such as less than 1 day, 1 to 7 days, 7 to 30 days, and more than 30 days. Hover mouse over the graph to view number of of PRs along with the time taken to get merged.
Less than 1 day: The number of pull requests merged in less than one day.
1 to 7 days: The number of pull requests merged in more than one day but less than seven days.
7 to 30 days: The number of pull requests merged in more than seven days but less than thirty days.
More than 30 days: The number of pull requests merged in more than thirty days.
Repositories shows a table that lists repositories, total number of PRs merged along with the time it took for 50% and 95% of the PRs to get merged per repository. Click a repository to navigate to GitHub to view details.
Timing shows information about open and closed pull requests in time. The dashboard focuses on how long pull requests remain open. Statistical information provides closing times and also tables with the latest and the oldest pull requests.
Filter lets you filter the dashboard data by author name, organization name, repository name, and repository URL. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of Pull Requests, Submitters, Assignees, Average number of days the PRs are in open state, and average number of days taken to merge Pull Requests.
Pull Requests by Organization shows a doughnut chart that represents the total number and percentage of pull requests submitted by organizations. Mouse over a color in the chart to see the total number and percentage of pull requests submitted by the organization.
Median Time to Merge (Days) shows a line graph that represents number of days it took for 50% of open pull requests (out of all PRs created on a date) to get merged . Mouse over a color in the graph to see the number.
Submitters shows line graphs that represent the number of submitters and organizations who raised pull request over time. Mouse over a color in the graph to view the date and number of organizations and submitters that created PRs.
Median Time To First Review shows a line graph that displays the number days it takes for 50% of the pull request to get their first review over time.
Median Time To First Approval shows a line graph that displays the number days it takes for 50% of the pull request to get their first approval over time.
Submitters shows a table that lists name of submitters, number of pull requests raised by the submitter, number of repositories the submitter worked upon, total number pull requests raised by the submitter by status, such as merged, rejected and open states, and average time in days it takes to merge the pull request submitted by the submitter.
Organizations shows a table that lists organization name, total number of pull requests submitted by the organization along with number of PRs by status, such as merged, rejected and open state, and average time taken in days to merge the PRs per organization.
Repositories shows a table that lists and let you sort values by repositories, number of pull requests along with number of PRs by status, such as merged, rejected and open state, submitters, and average time taken to merge the PRs per repository.
Backlog focuses on open pull requests (data is retrieved at the moment of dashboard creation), their accumulated time, associated organizations and submitters.
Filter lets you filter the dashboard data by author name, organization name, repository name and URL. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows total number of pull requests in open state, total number of repositories having pull requests in open state, and average number of days pull requests have been in open state.
Pull Request Backlog Percentage By Organizations shows a pie chart that displays the number and percentage of pull requests in open state by organization. Mouse over a color in the chart to view details.
Backlog (Open Pull Requests) shows a table that provides a summary of oldest PRs that are in open states, and are waiting to be closed. It lists PR URLs for the project. For each PR, the table shows the summary, date and time the PR was created, and how long (in days) the PR have been in open state. Click a URL to go to the changeset in the project.
Backlog shows a line graph that represents the number of pull requests that are open on a particular day. Mouse over a color in the graph to see the total number of pull requests on a date.
Backlog By Submitters shows a table that lists submitter name, number of pull requests raised by the submitter, number of repositories the submitter worked upon, and average time in days the pull requests are in open state for a submitter.
Backlog By Organizations shows a table that lists organization name, number of pull requests raised by the organization, number of submitters from the organization, number of repositories the submitters of the organization worked upon, and average number of days the pull requests raised by the organization are in open state.
Backlog By Repositories shows a table that lists repository URL, number of pull requests raised, number of submitters, and average number of days the pull requests are in open state per repository.
Reviews provides an overall analysis of reviewed pull requests, approved ones, dismissals, average time to first review, approve, and so on along with the associated organizations and reviewers.
Filter lets you filter the dashboard data by reviewer name, organization name, repository name and URL. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the following details:
Submitted: Total number of PRs created (submitted) and reviewed across all monitored repositories.
Reviewers: Total number of unique PR reviewers across all monitored repositories.
Approvals: Total number of approvals received on all submitted PRs.
Changes Requested: Total number of 'Request Changes' received on all submitted PRs.
Review Comments: Total number of Comments received on all submitted PRs.
Dismissed: Total number of PR reviews being dismissed.
Avg. Time to First Review: The average time it took to get the first review on the PR across all submitted PRS.
Repos By Review Activity shows a cluster of top 10 repositories on which most review activity happened. Click a repo to view dashboard data specific to the repository.
PR Review States shows a doughnut chart that displays the number and percentage of pull request reviews by state, such as commented, approved, changes requested, and dismissed. Mouse over a color to view details.
Median Time To First Review shows a line graph that displays the 50th percentile of days it takes for a pull request to get a review in a given timeframe. Mouse over the graph to view details.
Median Time To First Approval shows a line graph that displays the 50th percentile of days it takes for a pull request to get an approval in a given timeframe. Mouse over the graph to view details.
PRs Merged Without Approval shows a line graph that shows the number of pull requests merged without approval on a particular day. Mouse over the graph to view details.
Repository PR Review Summary shows a table that lists repository URL, number of submitters, reviewers, review comments received per repository, and number of approved, changes requested, and dismissed PRs per repository over time.
Organization PR Review Summary shows a table that lists organization name, total number of pull requests raised by the organization, number of reviewers, review comments received for PRs raised by the organization, and number of approved, changes requested, and dismissed PRs per organization over time.
Reviewer Activity shows a table that lists reviewer names, total number of activity by the reviewer, number of approved, changes requested, review comments and dismissed PRs per reviewer over time. Total Activity is the sum of all activities done by the reviewer, such as how many PRs they approved, provided comments for, dismissed, and requested changes.
Latest PRs Review Activity shows a table that lists GitHub pull request link, date on which the PR is created, and if the PR is approved or dismissed, or any number of review comments and changes requested for the PR. Numbers as one and zero are used to indicate true or false for approved and dismissed PRs.
Click to copy the path of respective dashboards.
CI/CD dashboards show continuous integration, build and job analytics for the project. For details, see:
By default, Bot Commits and Issues Only are filtered. Dashboard shows data only for number of issues, not for comments, and other values. You can include these filter values by navigating to the filter section of dashboard. For details, see Add and Manage Data Filters.
The Jira dashboards under Issue Management represents a set of metrics that shows an analysis of Jira issues . Following are the various dashboards of Jira dashboard:
Overview shows information about issues in repositories and who submitted the issues and when. For each commit, information about the corresponding organization is also provided.
Filter lets you filter the dashboard data by submitter name, organization name, and project. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows total number of issues, submitters , and projects.
Backlog shows a line graph shows the total number of issues in open state over time.
Issues by Status shows a stacked bar graph that represents the number of issues by status per day over time. Issue statuses are color code. Mouse over a color in the graph to see the total number of issues by status that occurred on a date.
Issues Assigned To Organization shows a stacked bar graph that represents the number of issues assigned to an organization per day over time. Organizations are color code. Mouse over a color in the graph to see the total number of issues assigned to the organization on a date.
Issues Submitted By Organization shows a stacked bar graph that represents the number of issues submitted by an organization per day over time. Organizations are color code. Mouse over a color in the graph to see the total number of issues submitted by the organization on a date.
Submitters hows a bar graph that represents the number of submitters per day over time. Mouse over a color in the graph to see the total number of submitters and the date.
Submitters by Organization shows a doughnut chart that represents the organizations that submitted issues (not unique issues; it includes activities on issues, such as comments, approvals, and so on) in the project. Mouse over a color in the chart to see the total number of submitters for the organization, and their percentage of the project's organization.
Assignees by Organization shows a doughnut chart that represents the organizations that are assigned with the issues (not unique issues; it includes activities on issues, such as comments, approvals, and so on) in the project. Mouse over a color in the chart to see the total number of assignees for the organization, and their percentage of the project's organization.
Assignees shows:
a stacked bar graph that represents total number of assignees for a calendar period. Mouse over a color in the graph to see total number of assignees for a date.
a table that lets you sort values by assignees names, number of issues, projects, reporters, and average time in days the issues were open before they were closed.
Submitters shows a table that lets you sort values by submitters names, number of issues, projects, assignees, and average number of days the issues were open per submitter over time .
Issues By Projects shows a table that lets you sort values by project name, number of issues, submitters, assignees, average number of watchers, and average time in days to close the issues over time.
Issues By Organization shows a table that lets you sort values by organization name, number of issues, submitters, assignees, average number of watchers, and average time in days to close the issues over time.
Effort shows data about authors and assignees, and their effort in hours per project and organization.
Filter lets you filter the dashboard data by submitter name, organization name, and project. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of Items, Authors, Assignees, Total Hours Estimated, Total Hours Remaining, and Total Hours Logged for the project.
Assigned Organizations shows a doughnut chart that represents the total number of assignees per organization. Mouse over a color in the chart to see the total number of assignees per organization, and the percentage of assignees for that organization out of the total assignees.
Estimated by Repository shows a doughnut chart that represents the total number of estimated hours per repository. Mouse over a color in the chart to see the total number of estimated hours per repository, and the percentage of estimated hours for that repository out of the total hours.
Logged by Repository shows a doughnut chart that represents the total number of logged hours per repository. Mouse over a color in the chart to see the total number of logged hours per repository, and the percentage of logged hours for that repository out of the total hours.
Effort (hours) shows a stacked bar graph that represents the effort expressed in the number of estimated, remaining, and logged hours over time. Mouse over a color in the graph to see the total number of hours: Estimated, Remaining, or Logged for a date.
Effort (hours, cumulative sum) shows a multi-line graph that represents the effort expressed in the number of time estimated, time remaining and time logged hours over time. Mouse over a color in the graph to see a vertical line that represents the time and date, and shows the total number of hours: Estimated, Remaining, or Logged for that date.
Averages and Medians shows a table that lets you sort values by Avg. Hours Estimated, Avg. Hours Remaining, Avg. Hours Logged, 50th percentile of Median Hours Estimated, 50th percentile of Median Hours Remaining, and 50th percentile of Median Hours Logged. The 50th percentile number indicates the median number of hours estimated or remaining. A 50th percentile is the same as a median.
Remaining by Repository shows a doughnut chart that represents the total number of remaining hours per repository. Mouse over a color in the chart to see the total number of remaining hours per repository, and the percentage of remaining hours for that repository out of the total hours.
Effort by Author and Assignee (hours) shows a table that lets you sort values by authors, assignees, URL, and estimated, remaining, and logged hours.
Effort by Organization (hours) shows a table that lets you sort values by organization name, number of issues, submitters, assignees, average number of watchers, Avg. Estimated Time (hours), Avg. Logged Time (hours), and Avg. Remaining Time (hours) per organization,.
Effort by Repository (hours) shows a table that lets you sort values by Repository, Issues, Submitters, Assignees, Avg. Num. Watchers, Avg. Estimated Time (hours), Avg. Logged Time (hours), and Avg. Remaining Time (hours).
Timing shows information about open and closed issues in time and lets you focus on how long Issues remain open. Statistical information shows the 50th percentile of median time open in days. The number indicates the median number of days that issues were open. This number indicates that 50 percent of the issues were open longer than that number and 50 percent of the issues were below that number. A 50th percentile is the same as a median.
Filter lets you filter the dashboard data by submitter name, organization name, and project. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of Issues, Submitters, Assignees, 50th percentile of Median Open Days, and Avg. Open Days.
Issues Open in Median shows a bar graph that represents number of days for which the median number of total issues that were created per day over time, are open. Mouse over a color in the graph to see the median number of days issues were open on a date.
Issues Open (best 80 percent of them) shows a bar graph that represents number of days for which the 80th percentile of total number of issues that were created per day over time, are open. Mouse over a color in the graph to see the 80th percentile number of days issues were open on a date.
Issue Count By Status shows a doughnut chart that represents the total number of issues in the project by status: closed, open, to do, and so on. Statuses are color code. Mouse over a color in the chart to see the status, total number of issues for the status, and the percentage of the project's issues for that status.
Organizations shows a table that lets you sort values by organization name, number of issues, submitters, assignees, 50th percentile of Median Time Open Days, and 50th percentile of Median Changes per organization over time.
Projects shows a table that lets you sort values by project name, number of issues, submitters, assignees, 50th percentile of Median Time Open Days, and 50th percentile of Median Changes per project over time.
Issues shows a table that lets you sort values by Summary, Submitter, Status, Project, +Info, Open Date, and Open Days.
Backlog focuses on open issues, their accumulated time, and associated organization.
Filter lets you filter the dashboard data by submitter name, organization name, and project. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of open issues, accumulated time in days while issues were open, and the average time in days per open issue over time.
Open Issues By Projects shows a table that lets you sort values by project name, number of issues and average time in days the issue were open over time.
Accumulated Time (days): Issues waiting to be closed shows a bar graph that represents cumulative number of days for which individual issues were open, on a date. Mouse over a color in the graph to see the data.
Issues waiting to be closed shows a stacked bar graph that represents number of issues (that are not closed) per day by status: Open, In Progress, To Do, and so on. These statuses are color coded. Mouse over a color in the graph to see the total number of issues by status that occurred on a date.
Issues In Backlog By Organizations shows a table that lets you sort values by organization name, number of issues, average time in days the issues were open per organization over time, and average number of watchers for issues over time.
Backlog Assignees By Organizations shows a doughnut chart that represents the assigned organizations that have open issues to be closed. Mouse over a color in the chart to see the total number of assignees for the organization, and their percentage.
Issues Submitters shows a table that lets you sort values by submitter name, number of issues, average time in days the issue was open for the submitter, and number of projects the submitter is associated with.
Issue Backlog Summary shows a table that lets you sort values by title, Info, repository, submitter, and total number of days the issue backlog was open. The default sort is by the greatest number of open days.
Click to copy the path of respective dashboards.
Chat Room dashboards show communication activities on Slack and Rocket Chat.
By default, Severe Activity and Bot Commits are filtered, however, you can include these filter values by navigating to the filter section of dashboard. For details, see Add and Manage Data Filters.
If you notice that the slack data for your project is not getting updated or reporting stale data, refer to the resolutions as mentioned in the troubleshooting page.
The slack dashboard is available from the Chat Room drop-down list, and represents a set of metrics that shows information about the slack communication channel.
Overview shows high-level information about how developers use Slack. For example, you can see the channels in which people send the most messages. You can sort channels by the number of messages, participants, replies, and other values.
Filter lets you filter the dashboard data by author name and organization name. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of Channels, Messages, Participants, Replies, Reactions, and Attachments of the project over time.
Trending Reactions shows a doughnut chart that represents the total number of reactions in the project per reaction value. Mouse over a color in the chart to see the total number of reactions for each reaction, and their percentage of the project's total reactions.
Top Trending Terms shows a term cloud of the top 20 terms that participants used. Click a term to show the corresponding data in the dashboard.
Messages by Time Zone shows a bar graph with a count of messages per Coordinated Universal Time (UTC) time zone. Mouse over a color in the graph to see the total number of messages for each time zone.
Messages shows a bar graph that represents the number of messages per day over time. Mouse over a color in the graph to see the total number of messages for a date.
Messages By Organization shows a doughnut chart that represents the total number of messages in the project per organization. Mouse over a color in the chart to see the total number of messages for each organization, and their percentage of the project's total messages.
Top Participating Organizations shows a table that lets you sort values by organization name, number of channels, messages, and participants of an organization.
Top Participants shows a table that lets you sort values by Participants, Avatar, Messages, Channels, date and time for first and last comments.
Active Participants shows a bar graph that represents the number of participants per day over time. Mouse over a color in the graph to see the total number of participants for a date.
Channels shows a table that lets you sort values by Channel, Topic, Purpose, Messages, Participants, Members, Replies, General, Starred, and Archived.
The Google Groups dashboard is available from the Mailing List drop-down list, and represents a set of metrics that shows information about the google groups communication channel. Following are the various dashboards of Google Groups:
By default, Bot Commits are filtered for, however, you can include the filter value by navigating to the filter section of dashboard. For details, see Add and Manage Data Filters.
Filter lets you filter the dashboard data by group name, origin google groups channel, and project name. Select values from the drop down lists, and click Apply Changes.
Summary shows total number of emails received across all monitored groups, total number of email senders to all monitored groups, the number of monitored groups in this project, and the count of the total number of topics across all monitored groups.
Emails Per Month shows a line graph that displays the gradual increase or decrease in the total number emails shared per month. Mouse over a point in the graph to view details.
Active Monthly Participants shows a line graph that displays the gradual increase or decrease in the total number participants that communicated over time. Mouse over a point in the graph to view details.
Emails Per Timezone shows a line graph that displays the gradual increase or decrease in the total number emails shared for the project over time. Mouse over a point in the graph to view details.
Top 5 Most Active Orgs By Emails Sent shows top 5 organizations that participate in communication, and line graphs that displays gradual increase or decrease in the number of emails sent by the organizations over time. Mouse over a point in the graph to view details.
Top 10 Orgs By Email Sent shows a doughnut chart that displays the top 10 organizations that sent maximum number emails in the channels. It also shows the percentage of emails received for monitored groups by the organizations.
Groups shows a table that lists name and URL of the groups where maximum number of communications are happening along with how many emails sent in the group, and total number of participants and organizations that participated in the conversations.
Active Participants shows a table that lists name of the persons who sent emails along with how many emails the participant sent, and in how many groups the email is shared.
Filter lets you filter the dashboard data by group name, origin google groups channel name, and project name. Select values from the drop down lists, and click Apply Changes.
Topics Trend Per Week displays a line graph that shows the gradual increase or decrease in the number of topics discussed per week for monitored groups over time. Mouse over a point in the graph to view details.
Activity Per Topic shows a table that lists top 10 most active topics, related google group names, and number of emails shared along with number of participants per topic.
Top 10 Active Topics shows a doughnut chart that displays top 10 active topics on which maximum communication is happening along with the number and percentage of discussions per topic for monitored groups. Mouse over a color in the chart to view details.
Documentation dashboards show activity analytics about editions, revisions, editors, organizations, and projects.
By default, Bot Commits are filtered, however, you can include the filter value by navigating to the filter section of dashboard. For details, see Add and Manage Data Filters.
The Confluence dashboard is available from the Documentation drop-down list, and represents a set of metrics that shows information about confluence pages.
Overview shows information about Confluence documentation reviews, including editions, revisions, editors, organizations, and projects.
Filter lets you filter the dashboard data by author name and organization name. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of Pages, Comments, and Editors.
Top Edited Pages shows a table that lets you sort values by Page, URL, Editions, and Editors. Click + Info to open the corresponding page.
Activity shows a stacked bar graph that represents the number of New Pages, Page Edits, and Blog Posts for the project over time. Mouse over a color in the graph to see the total number of new pages, page edits, and blog posts for a date.
Editors Per Day shows a bar graph that represents the number of editors for the project over time. Mouse over a color in the graph to see the total number of editors for a date.
Top Editors shows a table that lets you sort values by Editor, Page Edits, New Pages, Comments, Blog Posts, Attachments, and Last Action Date.
Last Actions shows a table that lets you sort values by Summary, URL, Action Type, and Action Date. Click + Info to open the corresponding page.
Last Created Pages shows a table that lets you sort values by Last Created Page, URL, Creation Date, and Editions. Click + Info to open the corresponding page.
Click to copy the path of confluence dashboard.
Mailing List shows communication activities on Pipermail, Groups.io, and Google Groups.
Share of Voice shows an analysis on how much content a project's main search terms are returning compared to its competitors' contents. This helps to understand a project's brand coverage compared to its competitors' on different media platforms, and on different verticals of the industry. More brand coverage shows greater popularity and authority among users and customers.
Share of Voice Comparison shows a pie chart that represents how much content is returned for a product's main search title compared to any other search term. This chart helps to compare and understand market coverage of a brand compared to its competitors. Hover mouse over a color to view main search title, number and percentage of mentions for a brand's main search title, and current status: Ascending or Descending.
Share of Voice Over Time shows an interpreting graph that represents tracking of a brand's total coverage for its main search title compared to its competitors main search term that you enter in Share of Voice Comparison widget. Brand titles are color coded. Hover mouse over individual data points to view date when the data is interpreted, number of mentions and coverage sources for a brand.
Sentiment shows a bar graph that represents users' feedback for a product's content. It shows how many mentions in the form of a piece of writing have positive, neutral or negative feedbacks from users and customers. This helps to gauge public opinion and monitor brand reputation. Sentiment uses Natural Language Processing (NLP) and supports 16 languages.
Key Messages Comparison shows a pie chart that displays how many times a brand's key phrases are mentioned with its main search term or the brand name itself. Key messages are color coded. Hover mouse over a color to see key message name, number and percentage of mentions of a key phrase for your brand coverage.
Sentiment Over Time shows an interpreting graph that represents tracking of users' sentiments over a period of time for product's content. Hover mouse over individual data points to view date, number and sentiment type: Positive, Neutral or Negative. Sentiment types are color coded.
The Social Media Metrics dashboards provide high-level insights from the project's social media accounts and list of target search terms (keywords, hashtags, and so on). Social media metrics are organized into the dashboard types outlined below, which can be viewed by data range, such as 30 days, 90 days, 6 months, and so on. By default, the Twitter Overview page is displayed when you navigate to the project’s social media metrics dashboards.
Note: Insights currently supports Twitter data only. Future releases will include data from other social media sources, such as Facebook and LinkedIn, and we will update this page accordingly.
Following are the five Social Media Metrics dashboards for Twitter:
Overview: High-level overview of the project's channel-level performance.
Hashtags Summary: Analysis of hashtags included in the project’s twitter posts.
Links (URL) Summary: Analysis of the URLs included in the project’s social media posts.
Languages Summary: Breakdown of the project’s social media posts by language.
Contributors Summary: Overview of social media users (contributors or influencers) who are engaged with the project’s social media posts or have mentioned their account.
If Access is available to members of the project appears:
Ensure that you have signed in to the portal.
If you have already signed in, then click Go to My Profile to update your company information on your profile settings page. Navigate back to the project's social media metrics dashboard and refresh the page.
It provides a high-level overview of the project’s channel-level performance, including follower metrics, post summary, and a breakdown of top hashtags. Following are the various sections and metrics displayed on this dashboard:
Section Summaries: Each section includes a summary of key metrics. These are visualized as metric blocks, which include the following details:
Name of the metric
Metric value
% change over time (based on time range selected)
Metric results-over-time graph (set in daily increments for the time range selected). Click the mini graph to view detailed results over time.
It displays key metrics related to the project’s Twitter accounts, including:
Followers: The total number of followers for the project's Twitter account(s).
Following: The total number of accounts that the project’s Twitter accounts(s) follow.
Total Tweets: The number of tweets published in the selected time range.
Total Retweets: The number of times that tweets posted by the project have been retweeted in the selected time range.
It provides an overview of the total and average number of tweets posted over a period of time. Click View Details to view detailed information of each metric.
AVG TWEETS/HOUR: Average number of tweets posted per hour in a time range.
POTENTIAL IMPRESSIONS/TWEET: Average number of potential impressions per tweet. Potential Impressions are the total number of views possible (both direct and amplified) for posts with hashtags based on how many timelines your post showed up in.
POTENTIAL IMPRESSIONS/HOUR: Average number of potential impressions per hour for all the tweets posted in a selected time range. Potential Impressions are the total number of views possible (both direct and amplified) for posts with hashtags based on how many timelines your post showed up in.
RETWEET RATE: It is the average rate at which a tweet is retweeted in a time range. It is calculated by dividing the number of total retweets with total tweets posted in a selected time range.
Tweet Breakdown displays colored bar graphs that represent the number of tweets and retweets on a periodic basis. Hover over the colors to view the numbers. Click TWEETS or RETWEETS from the bottom of the graph to filter the graph; click again to remove the filter.
Top Tweets displays a table that lists top 10 tweets ordered by potential impressions, and provides details of the tweets.
Tweets: Top 10 tweets that have the most number of impressions. It shows the tweet, the user’s name who tweeted along with the date, and a link to the tweet. Click the link to view details on twitter.
Tweet Summary: Displays the the following:
Retweets: Number of times the tweet is retweeted in a time range.
Replies: Number of replies received on the tweet in a time range.
Potential Impressions: Displays the total number of views possible (both direct and amplified) for posts with hashtags based on how many timelines your post showed up in. Click View Breakdown that displays the following data:
Potential DIR. Impression: Potential direct impression is the potential of the direct reach of the tweet without it being amplified. It's directly proportional to the number of followers of the twitter profile.
Potential AMP. Impression: Potential amplified impression is the indirect reach of the tweet. It displays the number of views for the total number of retweets of a tweet. If a tweet is not retweeted, it means it is never amplified, and potential amplified impression displays zero.
Total Potential Impressions: Sum of both potential direct impressions and potential amplified impressions.
The dashboard provides an overview of hashtag usage and performance across the project’s Twitter posts and related conversations (i.e., retweets). Click View Details to view more information on each metric. Following are the various sections and metrics displayed on this dashboard.
Hashtags Summary displays an overview of key metrics related to hashtag usage and performance.
# OF HASHTAGS: Displays the total number of hashtags used in the project’s Twitter posts over a period of time.
AVERAGE # OF TWEETS PER CONTRIBUTOR: Displays average number of tweets posted by a contributor in the time range.
# OF CONTRIBUTORS: Displays total number of users who participated in the conversation, tweet or retweet of the top trending hashtags.
POTENTIAL IMPRESSIONS: Displays the total number of views possible (both direct and amplified) for posts with hashtags based on how many timelines your post showed up in.
Top Hashtags displays a table that lists top trending hashtags ordered by highest potential impressions (includes both direct and amplified impressions). It lists top trending hashtags, total number of tweets, retweets, contributors, and potential impressions for a given hashtag.
This dashboard provides an overview of link (URLs) usage and performance across the project’s Twitter posts and related conversations (i.e., retweets). Click View Details to view more information on each metric. Following are the various sections and metrics displayed on this dashboard.
Links (URLs) Summary displays an overview of key metrics related to URLs usage and performance.
# OF URLs: Displays total number of URLs used in the project’s Twitter posts over a period of time.
# OF RETWEETS: Displays total number of retweets of the project’s Twitter posts that include URLs.
# OF CONTRIBUTORS: Displays total number of users who mentioned the URLs in tweets and retweets.
POTENTIAL IMPRESSIONS: Displays the total number of views possible (both direct and amplified) for posts with hashtags based on how many timelines your post showed up in.
Top URLs By Tweets show horizontal progress bars that represent the top 10 URLs ordered by number of times they are mentioned in the tweets over a period of time.
Top URLs displays a table that lists top 10 URLs ordered by total number of potential impressions (include both direct and amplified impressions). It provides links to the URLs, displays total number of contributors who tweeted or retweeted the URL along with the number of tweets and retweets by contributors in the time range.
This dashboard provides an overview of the languages used across the project’s Twitter posts and related conversations (i.e., retweets), as well as content performance by language. Click View Details to view more information on each metric. Following are the various sections and metrics displayed on this dashboard.
# OF LANGUAGES: Displays total number of languages used in the tweets and retweets in a time range.
# OF CONTRIBUTORS: Displays the total number of contributors for the project's Twitter posts over a period of time.
POTENTIAL AMP. IMPRESSIONS: It is the indirect reach of the tweet. If a tweet is not retweeted, it means it is never amplified, and potential amplified impression displays zero.
POTENTIAL DIR. IMPRESSIONS: It is the potential of the direct reach of the tweet without it being amplified. It's directly proportional to the number of followers of the twitter profile.
Top Languages By Tweets displays curved line graphs representing the languages that are most used in tweets and retweets over a period of time. Click a language from the bottom of the graph to filter the graph, click again to remove the filter. Hover over a point in the graph to view the number of times a language is used in a time range.
This dashboard provides an overview of social media users (contributors or influencers) who are engaged with the project’s Twitter posts or have mentioned their account. An engagement can be a like, comment, or retweet. The various sections and metrics displayed on this dashboard are detailed below.
# OF CONTRIBUTORS: Displays the total number of users (in a time range) who tweeted and retweeted contents related to the project, and replied to the tweets and retweets relevant to the project. This is calculated by measuring unique engagements, such as likes, comments, or retweets.
# OF RETWEETS: Displays the total number of times the project’s Twitter posts have been retweeted in the time range.
AVERAGE # OF TWEETS: Displays average number of tweets posted in a time range. It is calculated by dividing the total number of tweets with the total number contributors for the time range.
# OF POTENTIAL IMPRESSIONS: Displays the total number of direct and amplified impressions for the tweets and retweets by all the contributors in a time range.
User Mentions displays horizontal progress bars that represent the twitter handles that are mentioned the most in the project’s tweets in a selected time range.
Top Contributors displays a table that lists the top 10 Twitter handles ordered by highest number of potential impressions (include both direct and amplified impressions) for the tweets and retweets by that user.
Contributors: Lists the profile names along with the links. Click a profile to navigate to the profile’s twitter page.
Contributions: Displays number of followers of the profile, total number of tweets by the user mentioning the project’s relevant terms, and sum of potential direct impressions of all the tweets posted in a time range.
Engagement: Displays total number of retweets gained for all the tweets by the user. It also displays the retweet rate by the user. Retweet Rate is the average number of times the user’s posted tweets are retweeted by other users. It is calculated by dividing the total number of retweets with the total number of tweets for a time range.
Amplification: Displays the number of potential amplified impressions, and multiplier values for the tweets and retweets by the user. Multiplier value is calculated by dividing potential amplified impressions with direct impressions for a time range. It is used to interpret by what factor a contributor's tweets are getting amplified.
No Data Source Configured appears if a project is not configured for social media metrics analysis. Click Create Jira Ticket to provide project related search terms and other details to let Insights provide high-level overview of your twitter account.
Likes over time displays a bar graph that represents the number of likes received on the tweets in a time range. It displays the data on a periodic basis for a selected time range. Hover over the graph to view the number of likes received in that period.
Retweets over time displays a simple line graph that represents the increase or decrease in number of retweets over time. It displays the data on a periodic basis for a selected time range. Hover over a point in the graph to view the number of retweets in that period.
Tweet Frequency displays a shaded line graph that represents the total number of tweets posted over a time period. It displays the data on a periodic basis for a selected time range. Hover over a point in the graph to view the number of tweets in that period.
Top Hashtags displays a cloud of top trending hashtags used in the project’s Twitter posts and related conversations. Hover over a hashtag to view the number of times it has been mentioned in tweets and retweets within the selected time range.
Top Hashtags Breakdown displays a pie chart that represents the breakdown of top trending hashtags ordered by percentage and number of times the hashtag is mentioned in tweets and retweets. Hover over a color in the chart to view the hashtag name, and number of times it has been mentioned in tweets and retweets within the selected time range.
Languages Impressions displays a table representing the languages (used in the tweets and retweets) ordered by highest number of potential total impressions over a period of time. It lists the top 10 languages, total number of tweets, retweets, and replies that used the language. It also displays the potential direct impressions and potential amplified impressions for the language over a period of time.
Earned Media Content shows an analysis of how many potential audiences your content is reachable to, the monetization value for your content, top publishers, and so on.
Aggregate Readership and Ad Equivalency shows a table that lets you sort values by media type, readership, readership percentage, and Ad equivalency. Aggregate readership is the total audience potential reach for a given search query over a specific period of time. __ Ad Equivalency shows the monetization value for your content.
Highest Readership shows a table that displays top ten articles for your search query, link to view article, and potential readership value that is total potential audience reach.
Top Publishers by Impact shows a table that displays list of top publishers related to a given search query based on their impact score and total number of mentions.
Only Project Administrators can view, after signing in to insights, Identities & Affiliations for their project if they have access. If you do not have access, click Request To Edit Affiliations from navigation bar to request for access.
Only Project Administrators can manage affiliations of contributors for their projects.
Contributors who are not affiliated with any organization are counted as Unknown for Insight dashboard visualizations at organization level contribution.
As a project manager, you can manage different identities, such as email address and username of each contributor for a project, and affiliate their identities with the organizations they are associated with. If a profile does not have an affiliation with an identity or organization, its contributions are not counted in various Insights dashboards. To address this problem, Affiliation Management manages contributor identities including capabilities for merging identities and other data related to them such as affiliation to organizations. Affiliation Management identifies missing affiliations and helps you address them too.
Important: You must request and be granted access to edit affiliations before you can manage unaffiliated contributors. After you are granted access, navigate to the project dashboard. Identities & Affiliations is displayed on the navigation bar beside Community Leaderboard.
****Data Affiliation
Prerequisites: Ensure that you have access to Identities & Affiliations for project.
To View and Address Unaffiliated Contributors:
Click a project of interest.
Click Identities & Affiliations.
A menu provides the following options:
Home lists the top unaffiliated contributors, and lets you search profiles.
Blacklist lists shows blacklisted email addresses in alphabetical order, lets you search and add an email address to the blacklist, and remove an email address from blacklist.
Top Unaffiliated Contributors list the top-ten contributors with the greatest numbers of contributions that have no affiliation.
Missing affiliations for this contributor's profile might cause inaccurate counts for your project statistics.
1. Search a profile by typing the name in the field or under Top Unaffiliated Contributors, click the name of the contributor or hover mouse over Commits number for the contributor of interest and click search.
Note: The unique identity of the profile is displayed with all the details, such as Name, Email, Affiliations, Bot, Country, Last Modified On, and # specifying the number of identities associated with the person.
Searching a contributor by clicking his/her name under Top Unaffiliated Contributors, shows the unique identity of the contributor's profile.
Searching a contributor by entering his/her name in the Search Profiles field, shows all the identities associated with the profile.
2. Click the name under Name column to see identities associated with the profile.
3. Continue to Step 5 of Merge or Un-merge an Identity Profile.
4. Select Home and scan Top Unaffiliated Contributors. The contributor name is no longer listed because you have addressed the missing affiliations.
Due to a lag in the list refresh, names can remain in a Top Unaffiliated list even after you have addressed the missing affiliation. Check the list again later.
Earned Media Mentions shows regional analysis of how many times a brand name is mentioned or referenced on different media platforms. Mention volumes help to understand success of SEO and marketing for a brand.
Note: Mentions refer to articles or blogs. Even if a brand name or its main search terms are mentioned multiple times in one article, it is considered as one mention.
Location Selector lets you select country and state to view mention volume for the selected geographical region.
U.S. Mentions by Location shows geographical map of United States that displays number of mentions for the brand in different states of United States. Size and color associated with a number represent volume of mentions. Hover mouse over a number to see state name and number of mentions in the state.
Social Amplification shows how many times a brand's content is shared on different social media platforms. It helps to understand the reach of your brand so that you can optimize your content for better reach to the audiences.
Total Mentions shows an interpreting graph that displays periodic tracking of total mentions for a selected time range. Earned mentions indicates number of mentions over paid media platforms, such as news channels, news papers, blog sites, and so on whereas Social mentions indicates number of mentions over social media platforms, such as Facebook, LinkedIn, Twitter, and so on.
U.S. Mentions by City and State shows brand coverage in number of mentions by states and cities of United States.
International Mentions shows a bar graph that represents a brand's international coverage in different countries. Hover mouse over a country's grah to view how many times a brand is mentioned in the country over a selected time.
U.S. vs International Mentions shows a pie chart the displays number and percentage of mentions in United States compared to other countries in total.
Internal Mentions by Locations shows world geographical map that displays number of mentions for the brand in various countries. Size and color associated with a number represent volume of mentions. Hover mouse over a number to see country name and number of brand mentions in the country.
On Trends dashboard, you can select a time range form the time range bar to filter data. By default, the time range value is set to last 3 years on the time range bar. For more details, see Time-Based Data Aggregation Methods.
Note: 2000-PRESENT shows data from the year 2000 till date.
If you want to filter metrics data on project dashboards, then refer to the following process.
1. Open a project dashboard and click Select Time Range. The Time Range picker opens. Default time range is Last 90 days.
2. Select a quick filter to apply a time range and a value:
Quick shows preset time range values. Select a value, such as This Month, This Year, and so on, and click Apply.
Clicking Reset changes the time range to default value–last 90 Days.
Calendar lets you enter the start date and end date in the MM-DD-YY, HH:MM:SS format. Click Apply to see the project summary for the selected date and time.
The data refreshes to match your time range selection, and the value you selected shows next to the Time Range.
Note: If you filter data by selecting a time range for a project group, then the selected time range will be applicable for sub projects of the project group.
LFX Insights aggregates data and creates comprehensive dashboards from specific data sources. Dashboards include relevant visualizations that display analytic metrics and important data points. You can select and open a dashboard from drop-down lists corresponding to each data source.
A drop-down list is only available when a related data source is configured for the project.
To Filter Data:
1. From a project overview page, click a data source, for example Pull Requests / Changesets.
2. Select a dashboard from the drop-down list: The selected dashboard appears and shows relevant visualizations.
3. On a selected dashboard, navigate to the Filter visualization card, select values from the drop-down lists, and click Apply Changes to filter the dashboard data.
Apply changes: Filters the dashboard as per selected values
Cancel changes: If there are filter values selected before, it shows the previously selected filter values in the respective drop-down fields. If there are no filter values selected before, it cancels the present values.
Clear from: It clears all the filter values, and lets you add new values in the respective drop-down fields.
An identity is a record (tuple) composed of a name, email, username, and the name of the source from where it was extracted. Records are converted to unique identifiers.
Each unique identity has a profile that summarizes the user data. The profile can be linked to more than one identity and you can merge an identity to the profile.
Important:
LF Insights automatically merges a new identity to an existing profile if the new identity has the same email address and name that of the existing profile in the relational database.
LF Insights supports names with special characters while checking for an identity:
Single Apostrophe (')
Double Apostrophe (")
Dejan Mijić
Ján Srni?ek, and so on
To Manage an Identity:
Select a project name of interest.
Click Identities & Affiliations.
Select a profile from Top Unaffiliated Contributor list or search for a profile.
Click a row that corresponds to a name of interest.
Navigate to Identity Management. The profile identities are listed. Each identity shows Name, E-mail, Username, Source, and an Unmerge button. Note: Unmerge CTA button is not displayed:
If there is only one identity associated with the profile
for the unique profile to which identities are merged
Continue to merge or unmerge an identity profile:
An identity relates a profile with a unique identity.
1. Click Add New. The Add an Identity pane appears:
2. Type a name or email in the Search field, and press Enter. Matching results appear.
3. Find the unaffiliated identity (Affiliations is blank) that you want to add, and click Add on the row.
4. Click X to close the window. The added identity is listed in Profile Identities.
After you add a unique identity to a profile, the identity appears under Identity Management .
Click Unmerge, and confirm **** to unmerge the unique identity from the user profile.
You can search by a name or keyword to find specific profiles. The search results let you identify what data (for example, Email or Affiliations) is not provided in a profile, and that you might want to add.
To Search a Profile:
1. Click a project of interest.
2. Click Identities & Affiliations.
3. In Search Profiles field, enter a name or keyword and click Search.
Profile results show Name, Email, Affiliations, Bot, Country, Last Modified, and #. The following column headers require explanation:
Affiliations shows the name of the organization that is affiliated with the profile.
Number (#) shows the number of identities associated with the profile.
4. (Optional) Continue to .
On a dashboard, you can add a filter for the data results and display only the data that contain a particular value. You can also create negative filters that exclude data that contain the specified value. Filtering makes it easier for you to focus on specific information on a dashboard. The applied filters are shown in the query bar. Negative filters start with NOT in red.
After you add a filter, you can manage it by applying quick actions on the filter label such as excluding matches, and editing or removing the filter.
On a data source dashboard, for example Technical Metrics > Source Control > Commits > Overview, click + Add filter.
Click in the Filter field and:
Select an operator from the Operator drop-down list
Type or select a filter value in the Value field. Note: You can turn on the Create Custom label? key to open Custom label field that lets you enter a label value that identifies your filter subject.
Click Save. The filter label appears in the query bar.
Enable all enables all the disabled filters.
Disable all disables the filters without removing them. Strike-through indicates that filters are disabled.
Pin all pins the filters. Pinned filters persist when you switch contexts. For example, you can pin a filter in one dashboard and it remains in place when you switch to another dashboard. A filter is based on a particular index field—if the indices being searched do not contain the field in a pinned filter, it has no effect.
Unpin all disables all pinned filters.
Invert inclusion switches the positive filters to negative filters and vice-versa.
Invert enabled/disabled switches the enabled filters to disabled filters and vice-versa.
Remove all removes all the filters from the action bar.
The Edit filter option lets you manually update a filter and specify a label for it.
To edit a filter:
Click Save.
To manage a filter:
Click the filter that you want to manage, and select any of the action buttons to manage a filter:
Pin across all apps pins a filter across all applications in one dashboard. It remains in place when you switch to another dashboard.
Important: A filter is based on a particular index field—if the indices being searched do not contain the field in a pinned filter, it has no effect on the dashboard.
Edit filter opens the Edit filter dialog.
Include results includes items that match the specified field value. Exclude results option shows when you click Include results.
Exclude results excludes items that match the specified field value. Include results option shows when you click Exclude results.
Temporarily disable disables the filter without removing it. Strike-through indicates that a filter is disabled. Re-enable option shows when you click Temporarily disable.
Select a filter from the Field drop-down list.
Click Edit as Query DSL to build a filter using Elastic search Query DSL. You can create positive and negative operators and filter on whether or not a field is present. \
(Optional) Click to display and hide the CHANGE ALL FILTERS options as shown in the following example:
Click the filter that you want to edit and click Edit filter: The Edit filter dialog appears. \
Edit the filter by clicking Edit as Query DSL and following the instructions to edit a filter. \
Delete removes the filter. Note: You can click × next to a filter to delete it.
You can use the Inspect option to learn more about the data.
Select Inspect. A dialog appears with options.
Mouse over a visualization, and click **** ****The Options dialog appears.
Select an option: Data or Requests. Data shows a table and lets you download the table data to a CSV file. Requests shows the Statistics, Request, or Response for the data in tabs.
Refer the following to filter different metrics cards:
On a project dashboard, click Get Short URL, and click the icon next to the URL to copy the link of a respective dashboard for a project.
For a pie chart as mentioned below, eliminate data by clicking the corresponding legend caption. Click the caption again to include the data.
Click sparklines to open a bar chart that displays data per calendar period. Following example shows lines of code changed per calendar period.
Click numbers on a data card to view the respective dashboard. Following is an example of Lines of Code Changed:
You can refer to these examples to get started using INSIGHTS. These examples provide simple steps that represent how to find the dashboards and data you need.
Role: Technical Manager
Where: Jenkins dashboards are available from the CI/CD drop-down list.
As a technical manager of a project, you have concerns about aspects of your Jenkins jobs and builds. You want to understand what jobs and their corresponding builds have long duration times or high percentages of failures or instabilities so your team can work to increase efficiency. You may also want to know how quickly the builds are getting fixed, or if some test cases are permanently failing and either need updating or reviewing.
Do these steps:
Click a project name of interest.
From the CI/CD drop-down list, select Jenkins > Overview. A dashboard show Jenkins overview data. For details, see Jenkins > Overview.
Use the visualizations to understand various build aspects of the project. For example, each new build must go through a series of steps including compilation, testing, and validation. You want these steps to be optimized to ensure that changes are delivered quickly. The longer the build process takes, the longer it takes for changes to make their way into production. The Builds table shows the total time to complete a build (in seconds). By seeing the build time for a particular job, you can understand the build process and monitor it for abnormalities. If a build ends too quickly or takes too long, it could indicate a problem with the build server or the build pipeline.
From the CI/CD drop-down list, select Jenkins > Jobs. A dashboard show Jenkins job data. For details, see Jenkins > Jobs.
Use the visualizations to understand various job aspects of the project. Success/Failures in percentage is useful because it shows the ratio of successful jobs to unsuccessful jobs, and how healthy your jobs are in builds. You can see the build and job health as a total and see how it has changed over time.
A blacklist prevents an email address from being merged with other identities.
To Blacklist an Email Address:
1. Select a project name of interest.
2. Click Identities & Affiliations.
3. Select Blacklist from the menu.
4. (Optional) Enter an email address in the Search by email field and click Search. Email results list matches.
5. In the New blacklist email field, enter the email address that you want to add, and click Add.
6. Click Ok on the Success confirmation dialog that appears. The Email blacklist shows the added email address.
You can delete an email address from the Blacklist. This action means that this email address can be merged with other identities.
From Blacklist menu, click Delete on the row of the email address that you want to delete from the blacklist.
Click Delete on the Confirm dialog that appears.
Click Ok on the Success confirmation dialog that appears.