iilyak

Just wanted to provide update on this one @jiahuili430 tried to switch to rebar3 [here #4120](https://github.com/apache/couchdb/pull/4120) and [here #4089](https://github.com/apache/couchdb/pull/4089) I took @jiahuili430 work and tried to DRY the rebar.config.script and...

> Wonder if it would make sense to add/move some functions to it as it seems a bit odd to commit an empty application. Or, do you think it's better...

Few points which would probably make https://github.com/open-telemetry/opentelemetry-erlang-api unsuitable for us: - it looks like it uses `gen_server` based backend for storing spans. This would be prohibitively slow for our case....

It looks like the author of the library we currently use [abandoning it](https://github.com/sile/passage/issues/3#issuecomment-640593654). It is really sad because it is wonderfully written with performance in mind.

We can have our own `persistent_term` like module and patch 3 lines in opentelemetry. However there might be other incompatibilities to uncover.

The `persistent_term` is quite easy (about 150 LOC) to re-implement using `merl`.

The nice thing about OpenTelemetry is that it has some integration with `seqtrace`. Although I hope it is optional since we use sensitive flags on processes which handle http request....

If we would find a way to use erlang tracing safely (without leaking sensitive data) we would be able to debug and trace system on demand even if we don't...

> write this error message onece peer hour (30 min, 5 min) and write to log "no free space error muted for 60 min". To implement it we would need...

I refactored PR to parse Version earlier and added tests