[Bug] JSON Data - error while performing the infinity query. unexpected EOF

[Severus157]

Describe the bug

When querying an JSON Endpoint, which does not have a Newline at the end. The JSON is not displayed correctly, but showing the following Error Message:
error while performing the infinity query. unexpected EOF

If I curl the endpoint manually via Terminal it works and give the correct data:
$ curl -X 'GET' -H 'Accept: application/json;q=0.9,text/plain' 'http://endpoint:8109/subdomain/v1/core_usage' {"data": [{"hotcores": 3, "id": "ID-1", "misccores": 1}, {"hotcores": 9, "id": "ID-2", "misccores": 3}, {"hotcores": 2, "id": "ID-3", "misccores": 1}, {"hotcores": 15, "id": "ID-4", "misccores": 3}, {"hotcores": 3, "id": "ID-5", "misccores": 1}, {"hotcores": 10, "id": "ID-6", "misccores": 3}, {"hotcores": 2, "id": "ID-7", "misccores": 1}, {"hotcores": 2, "id": "ID-8", "misccores": 1}, {"hotcores": 8, "id": "ID-9", "misccores": 3}], "success": true, "error": ""}NAME@DOMAIN @ HOST

Just querying with Infinity does not work. The provided JSON is still valid and should be able to show. Even when missing the \n for a Newline at the end. Showing as the next line of Terminal just follows the Command.

If I query a different Endpoint, which includes the \n at the end. The data is correctly shown by Infinity. Unfortunately I have multiple endpoints I need to query, where some of them are missing the \n and some include it.

Steps to reproduce

Query a JSON Endpoint, which is missing the \n for a newline at the end.

Note: bugs will be fixed only if enough information provided to reproduce the issue

Sample Data

• Unfortunately the endpoints are all internal and not reachable externally.

Screenshots

Version Details:

• Grafana version : 12.0.1
• Plugin version : 3.2.1

Additional context

Add any other context about the problem here.

[yesoreyeram]

I don't think this is an issue with new line.. ( i tried and couldn't reproduce ).

https://play.grafana.org/goto/4mqyqpBNR?orgId=1

https://play.grafana.org/goto/RM88qpfHR?orgId=1

Are you sure the query returns JSON? ( just change the type to CSV with the same url and see what you are getting.. set the delimiter to something random ;;;;;

[Severus157]

I do get the same issue, unfortunately.

But it should be valid JSON.
So far, we always have used curl with jq to check manually. But as we are querying about 30-40 Servers with this, we wanted to transfer to Grafana. Currently about 60% not working and 40% percent working.

If I run a diff on these data, I receive via curl, I find that the only difference seems to be the /n.

[yesoreyeram]

Currently about 60% not working and 40% percent working

Sorry that is bit suspicious on the downstream API configuration. My guts says, If infinity able to parse similar 60%, then it should be able to handle remaining 40% if they are same setup. Can you provide us a clear reproduction steps with sample URL ( as I couln't reproduce this with my sample URLs )

[yesoreyeram]

Converting this into dicussion to get more clarification and reproduction steps.

[Severus157]

Unfortunately you won't be able to query the URLs, as the URL's are all only reachable from internal company network. I'm not sure how I can set up a sample URL right now. It's not as easy, as the non working JSON query comes from the old SL6 Servers with an older version of an internal Software.
While we are working on getting everything migrated, but it looks to take some years to get everything done.

One weird thing I just found with the Query inspector is, that it seems to append 'Accept-Encoding: gzip' in the new version? I've just updated Grafana and the Plugin from 2.12.x yesterday:

Not working Endpoint:

NAME@DOMAIN @ HOST in ~ |12:41:46  
$ curl -X 'GET' -H 'Accept: application/json;q=0.9,text/plain' -H 'Accept-Encoding: gzip' 'http://ENDPOINT/v1/core_usage'
Warning: Binary output can mess up your terminal. Use "--output -" to tell curl to output it to your terminal anyway, or consider "--output <FILE>" to save to a file.
NAME@DOMAIN @ HOST in ~ |12:41:49  
$ curl -X 'GET' -H 'Accept: application/json;q=0.9,text/plain' 'http://ENDPOINT/v1/core_usage'
{"data": [{"hotcores": 3, "id": "ID-1", "misccores": 1}, {"hotcores": 9, "id": "ID-2", "misccores": 3}, {"hotcores": 2, "id": "ID-3", "misccores": 1}, {"hotcores": 15, "id": "ID-4", "misccores": 3}, {"hotcores": 3, "id": "ID-5", "misccores": 1}, {"hotcores": 10, "id": "ID-6", "misccores": 3}, {"hotcores": 2, "id": "ID-7", "misccores": 1}, {"hotcores": 2, "id": "ID-8", "misccores": 1}, {"hotcores": 8, "id": ID-9", "misccores": 3}], "success": true, "error": ""}NAME@DOMAIN @ HOST

Working Endpoint:

NAME@DOMAIN @ HOST in ~ |12:48:40  
$ curl -X 'GET' -H 'Accept: application/json;q=0.9,text/plain' -H 'Accept-Encoding: gzip' 'http://ENDPOINT/v1/core_usage'
{"data":[{"hotcores":2,"id":"ID-1","misccores":1},{"hotcores":5,"id":"ID-2","misccores":1},{"hotcores":3,"id":"ID-3","misccores":1},{"hotcores":22,"id":"ID-4","misccores":3},{"hotcores":17,"id":"ID-5","misccores":3},{"hotcores":2,"id":"ID-6","misccores":1}],"error":"","success":true}
NAME@DOMAIN @ HOST in ~ |12:48:41  
$ curl -X 'GET' -H 'Accept: application/json;q=0.9,text/plain' 'http://ENDPOINT/v1/core_usage'
{"data":[{"hotcores":2,"id":"ID-1","misccores":1},{"hotcores":5,"id":"ID-2","misccores":1},{"hotcores":3,"id":"ID-3","misccores":1},{"hotcores":22,"id":"ID-4","misccores":3},{"hotcores":17,"id":"ID-5","misccores":3},{"hotcores":2,"id":"ID-6","misccores":1}],"error":"","success":true}

[Severus157]

@yesoreyeram
I might have found a hint.
If I add "Accept-Encoding: identity" as an HTTP Header the Query from infinity seems to work. It looks like there is any issue with a compression, that causes it to fail.

[yesoreyeram]

Yeah. Feel free to go for it. I don't see any fix required in infinity as this is purely depends on your setup.

Good luck.