You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In v8.3.0, if you incremented a counter of a name, then in graphite-web or grafana, you were still able to browse it hierarchically.
In our case, we also have datadog environment variables. In v9.1.0, those DD_* env variables are automatically added as tags, which is fine, but then it also means that the counter name is added as a tag:name instead, which means the counter name cannot be browsed hierarchically anymore.
I'm fine with having tags, but in the cases where I don't care about the tags while browsing, I'd prefer to be able explore that tag hierarchically in the frontends. Am I missing something basic about how this is intended to work? Can the ability to browse these metric names be hierarchically be restored, even if they were sent with tags?
The text was updated successfully, but these errors were encountered:
In v8.3.0, if you incremented a counter of a name, then in graphite-web or grafana, you were still able to browse it hierarchically.
In our case, we also have datadog environment variables. In v9.1.0, those DD_* env variables are automatically added as tags, which is fine, but then it also means that the counter name is added as a tag:name instead, which means the counter name cannot be browsed hierarchically anymore.
I'm fine with having tags, but in the cases where I don't care about the tags while browsing, I'd prefer to be able explore that tag hierarchically in the frontends. Am I missing something basic about how this is intended to work? Can the ability to browse these metric names be hierarchically be restored, even if they were sent with tags?
The text was updated successfully, but these errors were encountered: