StackServicesEngineering metrics

Engineering metrics

Last updated: Nov 3, 2026

Rationale

Engineering metrics help Fluid Attacks understand the development process of each person and of the team. Fluid Attacks uses a combination of tools, for example, GitLab and Amazon Quick, to collect and analyze these metrics. These are the primary reasons why Fluid Attacks selected this approach and not other alternatives:

  • It is fairly easy to make custom metrics and dashboards because of these items:
    • The high standards of Fluid Attacks for code contributions and backlog management: commit messages, deltas, and issue labels
    • The engineering methodology of Fluid Attacks: micro-changes, trunk-based development, ephemeral environments, monorepo, standard commit messages, and more
    • The control of all the items above from the CI process
  • It gives custom metrics that Fluid Attacks thinks are more useful over time than known standards like DORA or DevEx. Fluid Attacks usually gets better results when it benchmarks with standard metrics.
  • It continues to let Fluid Attacks measure the metrics that the industry thinks are standard and benchmark its team.
  • It lets Fluid Attacks manage access with Okta, AWS roles, and Amazon Quick, to give dashboards only to the persons who must have them.
  • Because it is an in-house project, Fluid Attacks can customize it fully.
  • It sends periodic reports to dashboard users, with a frequency and a time that Fluid Attacks can change.
  • Fluid Attacks can filter the data of each person and of the team with fixed and custom ranges.
  • Fluid Attacks built it on services that it already uses much.

Alternatives

Fluid Attacks examined these alternatives, but it did not select them for these reasons:

  • Pluralsight Flow: Flow integrates easily with GitLab, which is the primary development platform of Fluid Attacks, and with GitHub. Thus, Fluid Attacks could track metrics for its projects. Flow gives useful information about efficiency, impact, and complexity from the code contributions of developers. It also sends weekly digests that summarize the work focus and show important contributions. Also, users can filter the data of each person and of the team with custom time ranges, and it has a REST API to export data. Its integration with Okta gives centralized authorization, and this makes security and access management better. Fluid Attacks stopped its use because, with the engineering methodology of Fluid Attacks, it is fairly easy to make custom metrics and dashboards.
  • Waydev: Waydev gives dashboards to team leaders to track the performance of each person and of the team. It measures impact with deltas, file types, and the spread of changes in the codebase. It also evaluates the efficiency of developers from their recent edits. It measures the risk and complexity of commits, and users can compare team metrics in different dashboards. Waydev gives DORA metrics, tracks MR reviews to show collaboration, and calculates the Knowledge Sharing Index (KSI). It shows MR activity over time, and it includes benchmarks. Developer Experience (DevEx) tools let users make custom surveys, and hygiene metrics help to keep good project management practices, with periodic reports. Its price is similar to the price of Pluralsight Flow. But the in-house solution of Fluid Attacks has most of its features, except commit complexity, the KSI index, and DevEx. At this time, Fluid Attacks evaluates the value of these features to decide if it must implement them in-house.
  • Jellyfish: To use all the platform, the team must track issues in Jira. Thus, Fluid Attacks would get primarily coding metrics, and GitLab already gives them. It has good features for DevFinOps and engineering focus. But at this time, Fluid Attacks gets this information from GitLab data in a custom dashboard on Amazon Quick. Its price is the same as the price of Pluralsight Flow.
  • LinearB: To use all the platform, the team must track issues in Jira. Thus, Fluid Attacks would get primarily coding metrics, and GitLab already gives them. It gives benchmarking for coding and productivity metrics. But after Fluid Attacks examined the related publications, it decided that benchmarking is not sufficiently important to change its service, because its metrics are already much better. Its price is the same as the price of Pluralsight Flow.
  • Swarmia: It does not support GitLab integration.
  • Allstacks: It gives good dashboards that use heat maps and bar charts to show the active hours of a team. But it does not have important features that Pluralsight Flow has, and it can cost 10% to 40% more for each contributor.
  • Keypup: It gives only basic analytics, and it does not have important features that Pluralsight Flow has.
  • DX: It gives qualitative and quantitative information with standard and custom metrics, and with surveys that track the experience of developers. It can cost approximately 20% more for each contributor than Pluralsight Flow.

Usage

Fluid Attacks uses its engineering metrics for these purposes:

  • To understand the work of each engineer and of the team
  • To understand its continuous integration and continuous deployment processes
  • To examine the team focus over custom timelines
  • To get information about commits, for example, their quantity of changes, time of day, and frequency (average for each day or month)
  • To make custom dashboards and metrics for its team, product, and business

ELB

Learn about ELB, an AWS service employed by Fluid Attacks to expose applications to the internet.

ePayco

Learn about ePayco, a payment service employed by Fluid Attacks to bill clients in Colombia.

On this page

RationaleAlternativesUsage