small documentation update concerning feeding in Data with AMQP
Don't error on GET requests to /browser/search/
Added link to the tools list from the feeding-carbon documentation because that is another great way to get metrics into Carbon. Added entry for txCarbonClient to the tools list.
fix data-cache invalidation

This fixes and issue with adding data to the data-cache. The previous
implementation used 'set' instead of 'add'. As discussed in
https://docs.djangoproject.com/en/dev/topics/cache/ 'set' will add the value
again, even if it exists already. This has the side-effect of also updating the
cache expiry time.

This means, that when you use 'set' on values that have been retrieved from the
cache, you keep bumping the cache expiry time and thereby extending the
life-time of the data in the cache.

This behaviour can lead to problems if you select a time in the future as your
value for the 'until' parameter in your query and then keep sending that query
at intervals smaller than the DEFAULT_CACHE_DURATION. The result is that you
will, until you cease requesting at that interval, receive the same values,
even if new values have become available in the meantime.

To reproduce select an existing metric and fix the 'from' and 'until' times to
fixed values selecting the 'until' time to be in the future:

current time is 12:0520131106:

curl "http://grphite/render/?target=METRIC&format=json&from=12:0020131106&until=12:2020131106&local=0"

Then execute the above curl statement in a while loop for about 15 minutes.
Observe how the same set of values is returned over the course of these 15
minutes.  Then, wait one minute (or whatever you set DEFAULT_CACHE_DURATION to)
and execute the curl query once again. Observe how several additional values
have appeared.

The fix is to use 'add' instead of 'set'. 'add' will only add new values if
they do not exist already.

If you apply this patch and try the same while loop again, observe how any new
values are fetched correctly one minute after they actually become available
from carbon.

Of course this depends on how often the metric is written to carbon. In my
example above my metric was written every 5 minutes.
improve data-cache invalidation

The further improves the previous commit by only even communication with the
cache, if the data has not been retrieved from the cache. The 'add' instead of
'set' is still used to make sure that concurrent WSGI workers who are accessing
a distributed cache, e.g. memcached, don't interfer with each other.
Merge pull request #459 from BobClaerhout/patch-1

small documentation update concerning feeding in Data with AMQP
Merge pull request #460 from draco2003/patch-1

Don't error on GET requests to /browser/search/
Add an isNotNull to count/determine whether a metric had any values.

In a pool where I have a flexible number of nodes, I need to be able to
determine how many nodes were alive at a particular time. (Well technically
the closest I can get is how many nodes were reporting metrics at a
particular time.)

This is a function that just returns whether a metric is non-null for each
measurement. You can create a 'nodes alive' graph with something like:

sumSeries(isNonNull(server*.cpu-1.cpu-idle))
Merge pull request #365 from burr86/master

add an isNonNull function
Merge pull request #487 from ImmobilienScout24/fix_data_cache

Fix data cache
Add mapSeries and reduceSeries render functions

Currently, graphite has no way to map-reduce disparate series together
which is desirable for series that come from collectd and others
where calculations need to be performed on two or more related series.

This commit adds two new render functions: mapSeries and reduceSeries.
This is a generic way of mapping several related series together and
reducing them with another function.

- Add mapSeries function which takes a seriesList and maps it to a
  list of sub-seriesList. Each sub-seriesList has the given mapNode
  in common.
- Add reduceSeries function which takes a list of seriesLists and
  reduces it to a list of series by means of the reduceFunction.
- Add mock module to .travis.yml
- Add tests for mapSeries and reduceSeries
Revert "Added link to the tools list from the feeding-carbon documentation because that is another great way to get metrics into Carbon. Added entry for txCarbonClient to the tools list."

This reverts commit 05f925a1dca1e39251cb8db5917526b1c500beaf.
Merge remote-tracking branch 'parent/master'
Split up the documentation for the tools and the APIs into separate pages and link to them from the feeding carbon page. Add a link to txCarbonClient on the APIs page.
Merge pull request #578 from justenwalker/map-reduce-functions

Add mapSeries and reduceSeries render functions
Merge branch 'pr/469'

Closes #469
Update whisper.rst

Fixed inaccuracy and mentioned carbon-aggregator
Update config-carbon.rst

Mentioned usage of carbon-aggregator with the same input and output metric
Update config-carbon.rst

Typo fix and rephrasing
Remove reference to bundled pytz