Build metrics#

Warning

This plugin is internal and not recommended to use.
See alternatives: Gradle Enterprise, Talaiot

How to start#

Configuring the extension

Set two mandatory properties buildType and environment. Without them plugin won't work
```
buildMetrics {
    environment.set(BuildEnvironment.CI)
    buildType.set("any string")
}
```
Add mandatory gradle properties for statsd and graphite. See modules subprojects:gradle:statsd-config, subprojects:gradle:graphite-config

Add project property avito.build.metrics.enabled=false

In Gradle extension we have appropriate flag for each metric e.g.

    buildMetrics {
        sendJvmMetrics.set(false)
    }

All metrics sent to graphite or statsd depending on our intention. Contact us for details.

The final metrics path is constructed from:

namespace prefix
- avito.stats.namespace for statsd metrics
- avito.graphite.namespace for graphite metrics
plugin prefix. It's static and equal to builds
the unique metric path. Part which different for all metrics

We use tags. And all metrics will have build_type and env tags which you set up in extension.

All actual kinds of metrics you could find by looking at BuildMetric inheritors.

Http build cache errors:
Remote cache statistics: Shows count of cacheable tasks that were requested from the remote cache. This is the same as Performance | Build cache | Remote cache | Operations | HitMiss in build scan.

These metrics give different aggregates for tasks to highlight the slowest ones.

These metrics describe a critical path. To understand the critical path better read critical path docs.

Send tasks in the critical path in ms

Elapsed time from build start till Android app build task finished in ms

We send heap and metaspace used and committed memory in KiB.

This reflects what you can find by jcmd PID GC.heap_info.
All values are measured in Kb and sent as time metrics.

Send used and total memory in KiB