Sprkl Docs
SupportSprkl websiteJoin Sprkl betaJoin Sprkl for CI
0.0.64
0.0.64
  • What is Sprkl?
  • Getting started
    • Install Sprkl
    • Instrument your code
      • Bare metal
      • Docker
      • Kubernetes
    • Start with a sample project with Docker Compose
  • Features
    • Dashboard
      • Personal vs. Global
      • Code Block Reference
    • Code markups
    • System Graph
    • Jaeger tracing
    • Jest integration
    • New! Detect runtime security vulnerabilities in your code
  • Integrations and supported stack
  • Concepts
    • Analysis
    • Instrumentation
    • Aggregations, metrics and insights
  • FAQ
  • Support
  • Sprkl for GitHub Actions
    • Overview
    • Setup
    • Pulling Sprkl data to your IDE for further debugging
  • Troubleshooting
Powered by GitBook
On this page
  • Recipe
  • Dashboard view
  1. Concepts

Analysis

PreviousConceptsNextInstrumentation

Last updated 2 years ago

Sprkl analyzes your git repository and determines which code blocks to instrument at runtime.

The analysis configuration contains many variables. The most significant one is called the "recipe":

Recipe

The sprkl recipe determines what commits we should scan upon analysis. To configure the recipe set the recipe flag:

sprkl --recipe=SELECTED_RECIPE

The available recipes are:

  1. lastPush - Uncommitted code and commits that were not pushed yet (DEFAULT).

  2. uncommitted - Uncommitted code.

  3. all - All commits (WARNING: Can impact performance severely in large repositories).

  4. recent - The most recent 100 commits. This number can also be configured; check the sprkl CLI help for guidance.

  5. mine - Commits authored by the currently configured git user.

  6. commitsList - Commits from a list provided with --commits flag.

Dashboard view