Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature_request] Templates: multiple tag matching #1272

Closed
kostasb opened this issue May 25, 2016 · 0 comments · Fixed by #1273
Closed

[feature_request] Templates: multiple tag matching #1272

kostasb opened this issue May 25, 2016 · 0 comments · Fixed by #1273

Comments

@kostasb
Copy link

kostasb commented May 25, 2016

Multiple tag matching for templates does not work.

Multiple measurement matching does work.

Documentation for InfluxDB states that multiple tag matching should work:
https:/influxdata/influxdb/tree/master/services/graphite#multiple-measurement--tags-matching

however such functionality is not referenced under Telegraf's Graphite data input:
https:/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md#graphite

Telegraf version tested: 0.13.1

Steps to reproduce:

Setup a udp input with graphite format
templates= [".host.host.measurement.cpu.measurement"]

actual input:
services.host123.sfo.performance.1.percent-active 5

results in InfluxDB:
measurement crated: performance.percent-active (multiple measurement matching works)

> select * from "performance.percent-active"
name: performance.percent-active
--------------------------------
time            cpu host    value
1464182865000000000 1   sfo 5

Tag key host has value "sfo" , only holding the latest value matching the "host" templates.
With multiple tag matching enabled this should be host123.sfo

sparrc added a commit that referenced this issue May 25, 2016
sparrc added a commit that referenced this issue May 25, 2016
sparrc added a commit that referenced this issue May 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant