Closed henriklb closed 6 years ago
Hi, Fluentd UDP sensor plugin retrieve key information embedded in proto files and create data with these information. In case you want to (re-)define those keys you have to specifically define it into the fluent.conf
i.e (In that case it will take keys from .proto files + defined manually)
<match juniperNetworks.cpu_memory_util_ext>
[.....]
tag_keys ["device","utilization.application_utilization.name","utilization.name"]
tag_keys_field key_fields
[.....]
</match>
or (in that case it will take key values only from the proto file)
<match juniperNetworks.**>
{% if OUTPUT_INFLUXDB == 'true' %}
tag_keys ["device"]
tag_keys_field key_fields
{% endif %}
For example if you take a look at .proto file of jnpr_interface_ext , you will see a couple of key fields:
//
// Interface information
//
message InterfaceInfos {
// Interface name, e.g., xe-0/0/0
required string if_name = 1 [(telemetry_options).is_key = true];
//
// Interface queue statistics
//
message QueueStats {
// Queue number
optional uint32 queue_number = 1 [(telemetry_options).is_key = true];
Regards
Thanks very much for the quick and informative reply.
I solved the issue. I figured I cloned the wrong branch of the fluentd-plugin repo. I had to specify the "with_keys" branch.
Hi,
I'm running latest open-nti with JTI. Issuing a
show tag keys
in InfluxDB outputs a lot of tags, more than expected by looking at input-jti's fluent.conf file (see below).However, I cannot find/understand the code that turn certain "fields" into indexed tags. According to the the fluent.conf file only a few of these fields should be turned into tags.
For instance, where is the code (in fluent.conf?) that specifies that
interface_stats.if_name
should be a tag? What am I missing?Thank you very much