Influx does not store values of a certain data source

I am pushing data to influxdb via Apache Camel. The data comes from an ActiveMq message broker and is processed through the camel framework. I have six data sources pushing to ActiveMq, all are processed properly and end up as exprected on InfluxDB. However, one of the data sources does not show up in InfluxDB, while the data send to Influux does not show any obvious error.

An example of data whic works fine looks like this:

BatchPoints [database=cryring_db, retentionPolicy=autogen, consistency=ONE, tags={}, precision=NANOSECONDS, points=[Point [name=YRT1IN1M, time=1574254025973119224, tags={}, precision=NANOSECONDS, fields={acquisitionstamp=1574254025973119224, chainindex=1, chainstartstamp=0, current=1.498764000366222, current_max=10.0, current_min=0.0, current_units=A, currentset=1.500595110934782, currentset_units=A, devicename=YRT1IN1M, eventnumber=273, eventstamp=1574254025973730624, power=129.14609759068637, processindex=2, processstartstamp=1574254025872519224, resistance=57.49297495418449, sequenceindex=1, sequencestartstamp=1574254025742519224, timinggroupid=200, voltage=86.16840113528855, voltage_max=360.0, voltage_min=0.0, voltage_units=V, voltageset=90.00, voltageset_units=V}]]]

The data sets that DO NOT work look like this:

BatchPoints [database=cryring_db, retentionPolicy=autogen, consistency=ONE, tags={}, precision=NANOSECONDS, points=[Point [name=YRT1DT1F, time=1573577803667626752, tags={}, precision=NANOSECONDS, fields={acqstatus=0, acquisitionstamp=1573577803667626752, blintercept=2.6568981024042055, blslope=9.273853016251246E-9, caldata_units=A, chainindex=1, chainstartstamp=0, devicename=YRT1DT1F, eventnumber=280, eventstamp=1574254167493819224, frequency=1.0E7, gainset=2, maxcurrent=1.4560321795898501E-5, maxcurrent_status=0, maxcurrent_units=A, meancurrent=7.982097275649405E-6, meancurrent_status=0, meancurrent_units=A, meancurrentstddev=1.3439169461502865E-6, meancurrentstddev_units=A, particles=2.391241449485833E10, particles_status=0, processindex=2, processstartstamp=1574254167373269224, range=1.0E-4, roicharge=3.831247050366202E-9, roicharge_status=0, roicharge_units=C, roifromevents=false, roimaxcurrent=1.4560321795898501E-5, roimaxcurrent_status=0, roimaxcurrent_units=A, roimeancurrent=7.982097275649405E-6, roimeancurrent_status=0, roimeancurrent_units=A, roimeancurrentstddev=1.3439169461502865E-6, roimeancurrentstddev_units=A, roiparticles=2.391241449485833E10, roiparticles_status=0, sequenceindex=1, sequencestartstamp=1574254167243269224, starttime=-676363705642472, timinggroupid=200, totalcharge=3.831247050366202E-9, totalcharge_status=0, totalcharge_units=C}]]]

Any advice appreciated

Hello @wgeithner,
Thanks for your question. How are you ingesting this metrics in influxdb? What version are you using?

Hi @Aniasg,

this issue is fixed. The “error” was not a real error, but a problem with our timestamps for the specific data set, which was 7 day in the past, and hence invisible in the timeframe I expected it. With the correct timestamp everything works as expected.

kind regards
wgeithner

1 Like