Michel, Thanks for the response! It seems that the problem is my data. I didn't mention it, and didn't want to post the full data set, but the json, while at the root level, does have other data. I added just the latency data to my instance and the line chart worked perfectly. Do you happen to know what to do if there's other data in the json message? If possible, I can just do a field extraction and parse that data, though I haven't been able to find examples of doing that. Here's a sample of the other information that isn't needed in the chart: {
"rate_limit": {
"default": {
"reject": "false",
"shared": "true",
"count": "94",
"limit": "100",
"period": "1",
"unit": "hour",
"interval": "1"
}
},
"@version": "1",
"request_method": "GET",
"datetime": "2021-07-12T14:24:41.162Z",
"time_to_serve_request": "2",
"bytes_sent": "0",
"request_http_headers": [],
"headers": {
"content_length": "1939",
"http_accept": null,
"http_version": "HTTP/1.0",
"connection": "close",
"http_user_agent": null
},
"response_http_headers": [],
"latency_info": [{
"started": "0",
"task": "Start"
}, {
"started": "0",
"task": "api-routing"
}, {
"started": "1",
"task": "api-cors"
}, {
"started": "1",
"task": "api-client-identification"
}, {
"started": "1",
"task": "api-rate-limit"
}, {
"started": "1",
"task": "api-security"
}, {
"started": "1",
"task": "api-execute"
}, {
"started": "1",
"task": "assembly-invoke"
}, {
"started": "2",
"task": "api-result"
}
],
"response_body": "",
"status_code": "200 OK",
"transaction_id": "123456789",
"request_protocol": "https",
"request_body": ""
}
... View more
