Sanitize key when globalKeySanitize is true

[ljestrada]

The existing code prevents tagged metrics from being posted even though the keyNameSanitize key in the configuration file is set to true.

Made a minor modification to have the if statement match the configuration option.

[BlueHatbRit]

Hmm, not sure how this ever slipped through. It seems quite simple, I'm wondering if we've misunderstood the relation between globalKeySanitize and keyNameSanitize. I'll take a deeper look at the docs and if this is all good then I'll merge it in.

PS: Sorry for the delay, this project's been dead for a while and is now being reivived.

[DanCech]

The problem with this fix is that the intent of the function is to sanitize the key name to make it graphite-safe if it wasn't already sanitized due to global key sanitize being enabled.

If globalKeySanitize is true then the key has already been sanitized and we don't need to process it again.

If globalKeySanitize is false then the key may contain unsafe characters and we need to sanitize it before sending to graphite.

The minimal patch to support tagged series is to add ; and = as allowed characters in the sanitize regular expressions, so they don't get stripped when sanitizing. I'll open a PR for that, and also for a larger patch that properly handles tags.

[BlueHatbRit]

Hey @DanCech thanks for this and the PR submissions, I'll give them a review asap. As you can imagine things are quite busy right now with covid-19 but this is on my list and it hasn't been forgotten. I'll look to check them over and integrate them as soon as I can.