graphite

Hi,

first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.

First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there

If I set all the prefixes (globalPrefix, prfixTimer, etc.) to "", what kind of ramifications will that have on the server side if any? Will all the timers, gauges, counters be calculated as normal or will see if any side effects?

This one...

https://github.com/Icinga/icinga2/blob/826f999c47270f344b93ac6f30bed2abf5fbd8e2/lib/icingadb/redisconnection.hpp#L167-L168

... orders its items by priority (std::map<QueryPriority,) and then by insertion order (std::queue<WriteQueueItem>).

Replace it with a std::priority_queue<WriteQueueItem>. Adjust WriteQueueItem and the usages of Writes as needed.

If we can't open port, then lets do something like:

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Addr

Breakout from #80:

• Provide examples using regex not just glob in the documentation
• Provide an example using a catch-all regex for metrics not matching an existing regex.
• Explain the difference between using the configuration for dropping all non match metrics versus using a catch all regex to provide an indication that metrics are not matching and would have been dropped.

The mapping