search

door7302 / openjts

The Open Juniper Telemetry Stack Project
BSD 3-Clause "New" or "Revised" License
45 stars 9 forks source link

InfluxDB returned error: error parsing query on LOGICAL IF. TRAFFIC MONITORING PROFILE #57

Open dhooper6430 opened 2 months ago

dhooper6430 commented 2 months ago

Device being polled is MX204, Junos - 22.4R3.25.

Physical interface graphs don't contain any data, all other graphs being used appear to work correctly (firewall filtering, BGP monitoring, Optics).

Influx_Error

Drilling into an individual port on the logical port dashboard, this error is shown in the query:

InfluxDB returned error: error parsing query: found \/, expected identifier, string, number, bool at line 1, char 119

Influx Port Errors

OpenJTS Version: 1.0.11 - JTSO Version: 1.0.5 - JTS Telegraf Version: 1.0.6

brevius commented 1 month ago

Similar case for interfaces with multiple units (like ae4.100, ae4.111) Status: 500. Message: InfluxDB returned error: error parsing query: found \(, expected identifier, string, number, bool at line 1, char 135 However there are results for interfaces with single unit (ae0.0) It seems there is no unit data for TRAFFIC measurement, but there is TRAFFIC_UNIT. For aggregated interfaces (aeX) there are data for unit 0. For LAG memeber(s) the measurement contains numbers close to unit number like:

          null,
          108.20453825505594,
          null,

or

          null,
          111.7034780401117,
          null,

In my case 108 and 111 are unit numbers. OpenJTS Version: 1.0.11 - JTSO Version: 1.0.5 - JTS Telegraf Version: 1.0.6

door7302 commented 1 month ago

Hello,

Thank you for your feedback; Let me replicate the issue in may lab for fixing it.