prometheus/retrieval
beorn7 0f191629c6 Next try to deal with backed-up ingestion.
This is now not even trying to throttle in a benign way, but creates a
fully-fledged error. Advantage: It shows up very visible on the status
page. Disadvantage: The server does not really adjusts to a lower
scraping rate. However, if your ingestion backs up, you are in a very
irregulare state, I'd say it _should_ be considered an error and not
dealt with in a more graceful way.

In different news: I'll work on optimizing ingestion so that we will
not as easily run into that situation in the first place.
2015-02-09 17:32:47 +01:00
..
helpers_test.go Clean up license issues. 2015-01-21 20:07:45 +01:00
ingester.go Next try to deal with backed-up ingestion. 2015-02-09 17:32:47 +01:00
interface_test.go Clean up license issues. 2015-01-21 20:07:45 +01:00
target.go Next try to deal with backed-up ingestion. 2015-02-09 17:32:47 +01:00
target_provider.go Clean up license issues. 2015-01-21 20:07:45 +01:00
target_test.go Next try to deal with backed-up ingestion. 2015-02-09 17:32:47 +01:00
targetmanager.go Clean up license issues. 2015-01-21 20:07:45 +01:00
targetmanager_test.go Clean up license issues. 2015-01-21 20:07:45 +01:00
targetpool.go Clean up license issues. 2015-01-21 20:07:45 +01:00
targetpool_test.go Clean up license issues. 2015-01-21 20:07:45 +01:00