I’m writing line protocol like this,
ModemCHA,PACKET=BiasLevels,ITEM=RTG4_1_3.3 value=-0.2567891829 1724660922323914528
ModemCHA,PACKET=BiasLevels,ITEM=RTG4_1_NEG3.3 value=0.4968618744 1724660922323914528
ModemCHA,PACKET=BiasLevels,ITEM=MED_I_1.1 value=0.2320251371 1724660922323914528
I’m not able to get all the columns to show up in Chronograph. I need to get Measurement, two tags and one field. (I only have one field.) I get checkboxes for Measurement, Packet and Item, but not for _field = value. Or I can get Measurement and Field and Packet, but not Item. I always get no results. Please see attached. I’m goin to try the CLI and see what’s in there. thanks. -cc
Today all the data is there. Is there some latency between when the data is written and when it shows up?
I am running
X-Influxdb-Build: OSS
X-Influxdb-Version: v2.7.4
in a container from Github on Fedora 38 on a VMWare Fusion VM (2 cores, 6 GB Mem) on MacOS 14.5 i9.
Writing data using the API api/v2/write
I also see see that Chronograph says “No … found in the current time range.” I am currently writing data at 50 channels per second with no batching (lots of small writes) and I chose past 1h and past 24 hours. I am saving at UTC time and I am MDT. Do I need to choose past 12h to capture the UTC delta?
I’m ok for now, but I have a presentation soon about InfluxDB. Any guidance would be helpful. Thank you.
Hello @downow,
yes there can be some latency issues. You should be able to select between UTC and local time zone in the top right next to the save as button.
Does that help? Have you tried using that?
Thank you for your response! Ok I did click around with the UTC button, but I’ll be more systematic about it now.
This is repeatable. On day 2 I wrote 50 - 100 channels of data for a few hours, all points at a frequency of 1 write/s using api/v2/write. I stop writing and wait 20-30 minutes and can’t see any data in chronograph. Then I leave everything on and the next day I look and the data is all there.
Next steps,
I’m going to create a new Fedora 40 VM in Fusion and install InfluxDB 2.7.x straight, no container. Do the data write again.
Second experiment I’ll use Telegraph instead of HTTP Post for writing
Thoughts, ideas always appreciated.
Hi,
SOLVED. I was incorrectly converting my timestamps and my data was being written 6 hours in the future. Therefore it was not visible in Chronograf at the time of writing and it would be visible after I waited six hours, doh. I thought I should convert to UTC in addition to converting to the Linux Epoch, but I only needed the Linux Epoch operation. Thanks again for your reply. You were very close to the solution. -cc
