Comment 3 for bug 1420836

I'd like to add that this is not related to the comma issue, described by the reporter.

The comma is a legal character in metric names, but the comma has specific meaning when building graphite-web graph targets, and there is no meaningful way to quote the commas when building graph targets. This is why commas were added to the list of characters that will be replaced by underscores when metric names are generated by NAV.

The *actual* name of a sensor still contains commas - only the corresponding metric files created by Carbon/Graphite will have them replaced by underscores. Also, NAV doesn't open whisper files; they are entirely handled by Graphite. NAV only asks the graphite webapp to retrieve the data it needs, either as raw numbers or rendered graphs.