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

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

Open
dhooper6430 opened this issue Sep 17, 2024 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@dhooper6430
Copy link

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
Copy link

brevius commented Sep 30, 2024

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
Copy link
Owner

Hello,

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

@door7302 door7302 self-assigned this Sep 30, 2024
@door7302 door7302 added the bug Something isn't working label Sep 30, 2024
@kmisak
Copy link

kmisak commented Dec 8, 2024

Same issue for me, MX routers

@nguyenduchoa37
Copy link

Hi.

This issue is resolved or not ? I also face this. Other profiles show the data normally except traffic profile.

I test with MX 960 Junos 21 and vMX Junos 23

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants