* Remove nym-network-statistics from workspace
* Remove nym-network-statistics
* Cargo.lock
* Update ci workflow
* Remove code that refers to removed nym-network-statistics
* Remove more
* Remove nym-statistics-common
* Delete commented out modules
* Remove commented out code
* Remove more commented out code
* Remove more commented out stuff
* Remove unused function
Cargo is warning about
warning: profile package spec `nym-wasm-sdk` in profile `release` did not match any packages
Fix this by commenting out the profile settings for that crate as it's
currently not included in the main workspace
On every cargo command we have the set warnings:
warning: /home/jon/src/nym/nym/common/dkg/Cargo.toml: `default-features` is ignored for bls12_381, since `default-features` was not specified for `workspace.dependencies.bls12_381`, this could become a hard error in the future
warning: /home/jon/src/nym/nym/common/dkg/Cargo.toml: `default-features` is ignored for ff, since `default-features` was not specified for `workspace.dependencies.ff`, this could become a hard error in the future
warning: /home/jon/src/nym/nym/common/dkg/Cargo.toml: `default-features` is ignored for group, since `default-features` was not specified for `workspace.dependencies.group`, this could become a hard error in the future
warning: /home/jon/src/nym/nym/common/client-libs/validator-client/Cargo.toml: `default-features` is ignored for bip32, since `default-features` was not specified for `workspace.dependencies.bip32`, this could become a hard error in the future
warning: /home/jon/src/nym/nym/common/client-libs/validator-client/Cargo.toml: `default-features` is ignored for prost, since `default-features` was not specified for `workspace.dependencies.prost`, this could become a hard error in the future
warning: /home/jon/src/nym/nym/common/credentials-interface/Cargo.toml: `default-features` is ignored for bls12_381, since `default-features` was not specified for `workspace.dependencies.bls12_381`, this could become a hard error in the future
warning: /home/jon/src/nym/nym/common/credentials/Cargo.toml: `default-features` is ignored for bls12_381, since `default-features` was not specified for `workspace.dependencies.bls12_381`, this could become a hard error in the future
warning: /home/jon/src/nym/nym/common/nymcoconut/Cargo.toml: `default-features` is ignored for bls12_381, since `default-features` was not specified for `workspace.dependencies.bls12_381`, this could become a hard error in the future
warning: /home/jon/src/nym/nym/common/nymcoconut/Cargo.toml: `default-features` is ignored for ff, since `default-features` was not specified for `workspace.dependencies.ff`, this could become a hard error in the future
warning: /home/jon/src/nym/nym/common/nymcoconut/Cargo.toml: `default-features` is ignored for group, since `default-features` was not specified for `workspace.dependencies.group`, this could become a hard error in the future
This commit adds default-features = false to the workspace dependencies
to fix these. An alternative way would be to remove
`default-features = false`
in the crates, but I assume these were put there for a good reason. Also
we might have other crates outside of the main workspace that depends on
these crates having default features disabled.
* Generic prom wrapper idea
* Extend packet_statistics control with prom metrics
* Replace counters with Counters
* Add legacy mixnode api route
* fmt
* Sanitize metric names
* Format metrics
* Script to make prom targets
* More metrics
* Update script
* Make sure we dont panic in the future
* Remove fragile test
* Add metrics endpoint auth
* Remove per IP metrics
* Update target script, node_exporter setup
* Remove prom from client
* Simplify node stat
* Centralize metrice, break cpucycles temporarily
* Remove prometheus from mixnode
* Add cpu-cycles to Prom
* Further centralize Registry
* Cleanup old tracing
* Remove spurious assignment
* Move cpu-cycles to metrics
* Add features
* setup_logging before logging
* Remove cpucycle measurement in favour of time
* Cleanup, hygine