graphite-dev team mailing list archive

[Curt Kersey <question212686@xxxxxxxxxxxxxxxxxxxxx>]

Question #212686 on Graphite changed:
https://answers.launchpad.net/graphite/+question/212686

    Status: Answered => Open

Curt Kersey is still having a problem:
Nicholas,
Thanks for testing and getting back to me.  I apologize for my delay, but I took time to update software to the latest version in the trunk.  Looks like there were some changes along the way (I was running vanilla 0.9.10 release) that helped me to get closer; however, I am still not able to get this working.

I have looked for a more detailed overview of setting up the Carbon
Aggregation than is at http://graphite.readthedocs.org/en/1.0/config-
carbon.html, but I cannot find it.  I want to make sure that I am
fundamentally setting it up correctly.

Currently, I have the following in my carbon.conf file.  I made a few
more changes than you suggested, but only to simplify the configuration.
I am not using a relay, so I could remove that section completely to
stick with my 'more simple' theme.

[cache]
LOCAL_DATA_DIR = /raid/whisper/
USER = carbon
MAX_CACHE_SIZE = inf
MAX_UPDATES_PER_SECOND = inf
MAX_CREATES_PER_MINUTE = inf
PICKLE_RECEIVER_INTERFACE = 0.0.0.0
PICKLE_RECEIVER_PORT = 2004
USE_INSECURE_UNPICKLER = False
CACHE_QUERY_INTERFACE = 0.0.0.0
CACHE_QUERY_PORT = 7002
USE_FLOW_CONTROL = True
LOG_UPDATES = False
WHISPER_AUTOFLUSH = False


[relay]
LINE_RECEIVER_INTERFACE = 0.0.0.0
LINE_RECEIVER_PORT = 2013
PICKLE_RECEIVER_INTERFACE = 0.0.0.0
PICKLE_RECEIVER_PORT = 2014
RELAY_METHOD = rules
REPLICATION_FACTOR = 1
DESTINATIONS = 127.0.0.1:2004
MAX_DATAPOINTS_PER_MESSAGE = 500
MAX_QUEUE_SIZE = 10000
USE_FLOW_CONTROL = True


[aggregator]
ENABLE_UDP_LISTENER = True
UDP_RECEIVER_INTERFACE = 0.0.0.0
UDP_RECEIVER_PORT = 2003
DESTINATIONS = 127.0.0.1:2004
REPLICATION_FACTOR = 1
MAX_QUEUE_SIZE = 10000
USE_FLOW_CONTROL = True
MAX_DATAPOINTS_PER_MESSAGE = 500
MAX_AGGREGATION_INTERVALS = 5

In order to start the system, I start the carbon-aggregator.py by typing the following:
    /opt/graphite/bin/carbon-aggegator.py start

I can see from the log files that it is starting.  If I do a 'ss -a', I
can also see the daemons running.  I then start sending a diagnostic
metric; however, that metric  never has a value in the database -- it
always has null values when I query it via the render interface.  I do
not believe the metric is ever getting stored -- either it is not
forwarded to the pickle port correctly or it is getting dropped
somewhere.  I want my carbon cache and carbon aggregator server to be
the same.

Relating to the networking daemons that are running -- I can see the
Pickler port is running on a TCP port.  The connection from the
localhost to itself is visible when I do the command 'ss -a -t'.  I also
get a log message in the carbon-aggregator-a/clients.log that
connectionMade.

One more bit of information, I have the following files in the conf directory, but they are just empty files.  I was hoping to get this working in a simple case, then add rules to make it more complicated:
    aggregation-rules.conf
    rewrite-rules.conf
    storage-aggregation.conf

Questions:
1- Is it possible to aggregate & store values on the same host?

2- Do I need something in  the configuration files I have now that are
empty?

3- How can I see what data the pickle port is receiving, so I can debug
what is going on?

4- Is there a document to give an example of how to setup the
aggregation?

Note: I am happy to contribute a document to show how my setup is
working once it is complete.

--Curt

-- 
You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.