The storage expectations for the RocksDB DB may be different from our usual data
directory. Also, it may consume a lot more storage than other data.
This allows customizing the data directory for the builtin DS storage backend.
Note: if the cluster was already initialized using a directory path, changing that config
will have no effect. This path is currently persisted in mnesia and used when reopening
the DB.
For some reason, some tools like [ripgrep](https://github.com/BurntSushi/ripgrep) will
search `.git` when using the `-.`/`--hidden` flag, even when not using `--no-ignore-vcs`.
This leads to several unwanted results.
This is to isolate channels cleanup from other async tasks (like routes cleanup),
as channels cleanup can be quite slow under high network latency conditions.
Fixes: EMQX-11743
Fixes https://emqx.atlassian.net/browse/EMQX-11771
For the same reasons as we inject `emqx_bridge_*` applications as dependencies to
`emqx_bridge` when starting the node. Already configured connectors are started when
`emqx_connector` application starts, and may lead to crashes and noise in the logs. One
example is to configure a mongodb bridge and restart the node.
- node(default):
The only supported format_mode for PushGateway.
Return the current node's metrics.
- Without label `node_name` with content-type: `text/plain`.
- Without key `node_name` with content-type: `application/json`
- nodes_aggregated:
Return all nodes metrics Arithmetic-Sum or Logical-Sum.
See details in callback modules.
- Logical-Sum for metrics named with `xxx_enable` or `xxx_status`.
- Arithmetic-Sum for other metrics.
`node_name` field:
- Without label `node_name` with content-type: `text/plain`.
- Without key `node_name` with content-type: `application/json`
- nodes_unaggregated:
Return all nodes metrics without aggregated.
`node_name` field:
- _With_ label `node_name` with content-type: `text/plain`.
- _With_ key `node_name` with content-type: `application/json`
