)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":7537,"name":"Matthew Macdonald-Wallace","email":"mmw@hp.com","username":"macdomat"},"change_message_id":"99e4eefceaa7f607099d33de548acc32dfaca14d","unresolved":false,"context_lines":[{"line_number":5,"context_line":"CommitDate: 2014-06-30 09:43:29 +0200"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Add spec for graphite publisher"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Change-Id: Ie0c8ee71dee008654e597b5bc1a2af3bbfa3ace6"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"baada198_fc2fd63c","line":8,"updated":"2014-07-07 07:41:41.000000000","message":"Nit pick, but could we have the blueprint link in here please? At present there is no way to link the blueprint to this review and I thought that work had been abandoned! :(","commit_id":"139c80cd6da09a011309bc66fb416feb1e2d841c"}],"specs/juno/graphite-publisher.rst":[{"author":{"_account_id":7156,"name":"Mathieu Gagné","email":"mgagne@calavera.ca","username":"mgagne"},"change_message_id":"a706876b921e784fd3c0f4e29bbf10e291377650","unresolved":false,"context_lines":[{"line_number":21,"context_line":"a solution that will still allow us to get the usage metrics easily."},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"An analysis showed that we already have monitoring and metering implemented,"},{"line_number":24,"context_line":"and we are interested in only the data from ceilometer-compute agent. During"},{"line_number":25,"context_line":"the OpenStack summit in Atlanta, many of the other operators that we"},{"line_number":26,"context_line":"talked with were interested to implement this solution and looking forward to"},{"line_number":27,"context_line":"get the working code and provide feedback."}],"source_content_type":"text/x-rst","patch_set":2,"id":"baada198_79fb3c48","line":24,"updated":"2014-07-24 01:51:16.000000000","message":"Could you explain the advantages (and compromises) of implementing graphite support at the publisher level instead of at the dispatcher level? What if I want more than ceilometer-compute agent metrics in Graphite?\n\nI came across this spec [1] which suggests adding Gnocchi support (TimeSeries Database) as a dispatcher instead of a publisher.\n\n[1] https://review.openstack.org/#/c/106088/","commit_id":"139c80cd6da09a011309bc66fb416feb1e2d841c"},{"author":{"_account_id":136,"name":"Tim Bell","email":"tim.bell@cern.ch","username":"tim-bell"},"change_message_id":"9ce0260ac1fc083f32e68fbcd197b8c66d7ecfe7","unresolved":false,"context_lines":[{"line_number":39,"context_line":""},{"line_number":40,"context_line":"This will allow all big cloud operators to still continue using the collection"},{"line_number":41,"context_line":"component of ceilometer but offload the metrics, aggregation, graphing part to"},{"line_number":42,"context_line":"graphite which is well suited for exactly this."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"Alternatives"},{"line_number":45,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab895d6_3c4bc7b1","line":42,"updated":"2014-06-30 10:46:15.000000000","message":"Is the implementation limited to graphite only ? The problem description would seem a generic one and not only limited to those with graphite.\n\nThus, to what extent is the implementation graphite specific ?","commit_id":"139c80cd6da09a011309bc66fb416feb1e2d841c"},{"author":{"_account_id":7537,"name":"Matthew Macdonald-Wallace","email":"mmw@hp.com","username":"macdomat"},"change_message_id":"99e4eefceaa7f607099d33de548acc32dfaca14d","unresolved":false,"context_lines":[{"line_number":39,"context_line":""},{"line_number":40,"context_line":"This will allow all big cloud operators to still continue using the collection"},{"line_number":41,"context_line":"component of ceilometer but offload the metrics, aggregation, graphing part to"},{"line_number":42,"context_line":"graphite which is well suited for exactly this."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"Alternatives"},{"line_number":45,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"baada198_1cf00afd","line":42,"in_reply_to":"dab895d6_3c4bc7b1","updated":"2014-07-07 07:41:41.000000000","message":"I would personally keep this as \"graphite specific\".  The \"graphite\" part of the graphite monitoring system (i.e. the web frontend) is probably the weakest point however it is the name that the entire stack is known as.\n\nIf we send metrics to Carbon, then we can use carbon cache to redirect those metrics to multiple locations (see Etsy\u0027s \"Kale\" project at http://codeascraft.com/2013/06/11/introducing-kale/ for more) this allows us to write carbon-compatible plugins to various parts of the infrastructure in future should we decide we want the metrics to be analysed in multiple places.","commit_id":"139c80cd6da09a011309bc66fb416feb1e2d841c"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"3beb538a152951a7cda656f340ca1f6269a5bafa","unresolved":false,"context_lines":[{"line_number":44,"context_line":"Alternatives"},{"line_number":45,"context_line":"------------"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"None"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"Data model impact"},{"line_number":50,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"baada198_1ff92e80","line":47,"updated":"2014-07-03 09:44:07.000000000","message":"what is different/unique about this graphite publisher that it can\u0027t use the current udp publisher?","commit_id":"139c80cd6da09a011309bc66fb416feb1e2d841c"},{"author":{"_account_id":7537,"name":"Matthew Macdonald-Wallace","email":"mmw@hp.com","username":"macdomat"},"change_message_id":"99e4eefceaa7f607099d33de548acc32dfaca14d","unresolved":false,"context_lines":[{"line_number":44,"context_line":"Alternatives"},{"line_number":45,"context_line":"------------"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"None"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"Data model impact"},{"line_number":50,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"baada198_5c5b62f5","line":47,"in_reply_to":"baada198_1ff92e80","updated":"2014-07-07 07:41:41.000000000","message":"Carbon requires UDP messages to be in a specific format (http://graphite.readthedocs.org/en/latest/feeding-carbon.html) and whilst I have only read the code for the UDP publisher quickly, I cannot see how you format the message to be sent.\n\nThere is also the issue that the UDP publisher appears to be aimed at the monitoring segregation part of Ceilometer and therefore unless we can have multiple UDP publishers on a single system we will probably run into issues when people want to use UDP for alerts *and* send data to graphite at the same time.\n\nAn alternative to using Carbon could be to use StatsD, however this would probably need to then be configured to write to carbon anyway so it just adds one more thing to the chain.","commit_id":"139c80cd6da09a011309bc66fb416feb1e2d841c"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"b8b7e62d53e341af6c6f1e4d02ea8f2425a52b1e","unresolved":false,"context_lines":[{"line_number":44,"context_line":"Alternatives"},{"line_number":45,"context_line":"------------"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"None"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"Data model impact"},{"line_number":50,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"baada198_5bee858b","line":47,"in_reply_to":"baada198_5c5b62f5","updated":"2014-07-30 20:09:39.000000000","message":"yes, you can have mulitple publishers per sink.","commit_id":"139c80cd6da09a011309bc66fb416feb1e2d841c"}]}