-
Notifications
You must be signed in to change notification settings - Fork 105
Conversation
Dieterbe
commented
Dec 4, 2016
•
edited
Loading
edited
96c915a
to
8e69b11
Compare
variants: * simple standalone with CI built binary, monitors into itself * similar, but mounts custom built binary, monitors into itself * clustered stack with kafka input and graphite for monitoring also: - remove unneeded links - re-arrange a bit - export cassandra port so you can query it from the host if you want - simplify hostnames (strip -1 everywhere) don't ask me how the wait stuff even worked before this Notably missing from this work, but available in https://github.com/raintank/raintank-docker is tooling to automatically run given workload scripts.
8e69b11
to
320e84c
Compare
note i have run the docker-standard stack and it seems to work fine, just like the previous docker stack |
graphitemon: | ||
hostname: graphitemon | ||
image: raintank/graphite | ||
ports: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this image does not exist. We were building it as part of raintank-docker.
Perhaps we should use https://hub.docker.com/r/raintank/graphite-stack/ for both graphite statsd and grafana.
carbon.conf is like default, except higher whisper create/update limits storage-schemas.conf is because we want stats at 1s
pushed a commit that uses graphite-stack. the problem is however that it only speaks https. i would like the stacks to be as consistent/similar as possible, and only differ where needed. e.g. ideally the populate.sh script should work for all stacks, meaning the same datasource config should work for all stacks. but in the other docker stacks we use graphite-api+metrictank for monitoring which only accepts plain http (https://github.com/raintank/graphite-metrictank/blob/master/pkg/Dockerfile) |
I dont understand what you are trying to say. There are 3 variants that can be deployed. "cluster", "dev" and "standard". In dev and standard, statsdaemon published directly to metrictank. In the environemnt there is only a single Graphite service, graphite-api which uses metrictank as the backend and listens on 8080. In "cluster", statsdaemon publishes to graphitemon (graphite-stack). In the environment there are two graphite services. graphitemon which listens on 443 and graphite-api which listens on 8080. At present, you are adding 2 datasources to grafana, 1 pointed to port 8080 (graphite-api) and 1 pointed to 8000, which doesnt exist. So why cant you just change the datasource using 8000 use port 443 and https? |
then the script would create a DS that is broken for the dev and standard stacks. But anyway it's not worth the time trying to go that route, I'll just set up different datasources based on which environment you're in. |
afa6c75
to
a28ae34
Compare
@woodsaj how does it look now? note:
|
4ae19cb
to
8ce01e5
Compare