Kronicle Live Demo

This is a live demo for Kronicle. Kronicle is an open source system for visualising and documenting a tech stack, including software and infrastructure.

Interesting pages in the demo:

  1. An interactive, dynamically generated dependencies diagram that shows all the components in the demo tech stack and how they connect to each other. Try hovering over items in the diagram and using the filters on the right hand side.
  2. A list of all the components in the demo tech stack. Try using the filters on the right hand side.
  3. Kronicle fully supports OpenAPI specs. Kronicle can download OpenAPI specs hosted on a service's endpoint (e.g. with Springdoc) and then hostes a copy of those OpenAPI specs. Click a link in the Link column on that page to view an individual OpenAPI spec rendered using Redoc.
  4. A list of all the components owned by a team
  5. Dependencies diagram for an individual component. Use the radius dropdown on the right hand side to see more of the tech stack that surrounds the component.
  6. A component's page which shows the "key software" used by the component and other important information. Kronicle automatically scans Gradle build scripts (npm support coming soon) to find the key software used by the component.
  7. All the tech debt for the tech stack
  8. All the cross functional requirements (NFRs) for a team
  9. Response times for any components using Zipkin for distributed tracing.
Kronicle
Kronicle contains the following:
Areas 2 Teams 7 Components 20 Tech Debts 2 Test Results 160
Scanners
Scanners dynamically add data to Kronicle at runtime:
git

If a component includes a repo URL, the scanner will create a local clone of the component's Git repo. The local Git repo clones are typically used as an input to other scanners

gradle

Scans a component's codebase for any Gradle build scripts and collects information like Gradle version and software used

java-import

Scans a component's codebase and finds the names of all Java types imported by Java import statements

key-software

Processes all software found by other scanners and looks for certain configured key software to find what version(s), if any, a component uses. Key software is typically things like Gradle and Spring Boot

lines-of-code

Scans a component's codebase, finding all the file extensions for textual files in the codebase and calculates the total number of lines of text for each of those file extensions

openapi

This does two things: a) scan's a component's codebase for any YAML or JSON files that contain OpenAPI specs and b) uses any OpenAPI spec URLs specified in a component's metadata

readme

Scans a component's codebase for a README file at the root of the codebase

sonarqube

Scans a component's codebase looking for any references to SonarQube project keys. For any references it finds, it will call the SonarQube server's API to retrieve all the latest metrics for those SonarQube projects

to-do

Scans a component's codebase looking for any TODO comments that look like // TODO: or # TODO:

zipkin

Scans a Zipkin Server instance using its Zipkin API endpoints

Platforms
The following platforms are associated with components in Kronicle:
Tags
The components in Kronicle are tagged with the following:
backend 10 customer-pii-at-rest 4 frontend 2
Kronicle App v0.1.87