m3
m3 copied to clipboard
m3db
M3 monorepo - Distributed TSDB, Aggregator and Query Engine, Prometheus Sidecar, Graphite Compatible, Metrics Platform
## General Issues We are evaluating m3db as a replacemnt for Graphite datasource and followed the single node installation https://m3db.io/docs/quickstart/binaries/ https://m3db.io/docs/integrations/graphite/ But when I try to send a metric via...
https://github.com/m3db/m3/pull/4087 will put M3 on an alpha release of etcd. We will ensure that this is fine before landing, but once we can, we should get onto a stable version.
**What this PR does / why we need it**: I followed the [M3 aggregator setup guide](https://m3db.io/v1.0/docs/how_to/aggregator/) but got some errors. Errors went away if I create the topic after initializing...
I have been running the m3aggregator for more than 1 hour. But the shard state is still INITIALIZING. That's why i can not scale. ``` $ curl http://localhost:7201/api/v1/services/m3aggregator/placement { "placement":{...
Currently, if user added a node to placement, then cluster is hard to fix up. I can not do anything to fix this condition if just by m3db api. For...
# Filing M3 Issues ## General Issues site/content/operational_guide)/namespace_configuration.md The advanced example: curl -X POST :/api/v1/services/m3db/namespace -d '{ "name": "default_unaggregated", "options": { "bootstrapEnabled": true, "flushEnabled": true, "writesToCommitLog": true, "cleanupEnabled": true, "snapshotEnabled":...
# Filing M3 Issues ## General Issues site/content/integrations)/graphite.md contains information about setting the debug configuration option. This does not work and has been obsoleted. Please fix the doc (I believe...
deployment a cluster, node config: m3_1.4.2_linux_amd64.tar.gz node1 ``` "coordinator": "listenAddress": "0.0.0.0:7201" "local": "namespaces": - "namespace": "default" "retention": "48h" "type": "unaggregated" "logging": "level": "info" "metrics": "extended": "none" "prometheus": "handlerPath": "/metrics" "listenAddress":...
https://m3db.io/docs/operational_guide/mapping_rollup/ Based on this documentation, I tried to use the rules for unaggregated namespace: m3coordinator: ``` ... clusters: - namespaces: - namespace: default retention: 744h type: unaggregated - namespace: metrics_5m_90d...
