Use the fill() clause to substitute whatever value you like for missing data.
On Mon, Nov 7, 2016 at 2:43 AM, Schmurfy <schmu...@gmail.com> wrote: > I am really puzzled on this, I would really like to have some input on > this. > By definition when you have monitoring in place you want the real data, I > don't see how anyone can be okay with no way to represent missing points, > unless I missed something I just don't get it... > > On 18 October 2016 at 11:59, Julien Ammous <schmu...@gmail.com> wrote: > >> Hello eveyone, >> I started my discussion here: https://github.com/influxdata/ >> influxdb/pull/2429 but the mailing list might be a better platform for >> it. >> >> I am still using 0.8 and I am evaluating 1.0, before this particular >> issue I was pretty happy with the changes but I don't know how to handle >> the absence of NULL. >> What we are currently doing is inserting a NULL value when the stream of >> data is broken so that a clear cut will appear on the graph, the issue is >> how to do that with 1.0, if a server goes dark for two minutes I want the >> resulting graphs to show an empty section, not interpolate the line from >> the last point, how are 1.0.x users handling this ? I don't want to show >> false data in our monitoring graphs... >> >> After a quick look at grafana issues on this it looks like some users >> don't even know why their line graphs are connected instead of showing the >> expected void. >> The "solution" mentioned in the issue linked above is to have a separate >> field to signal null but it needs support from the frontend aside from >> being a hack instead of a real solution, inserting 0 is also not an option >> as 0 is a real value. >> >> >> -- >> Remember to include the version number! >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "InfluxData" group. >> To unsubscribe from this topic, visit https://groups.google.com/d/to >> pic/influxdb/aVDKk3Ny5J4/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> influxdb+unsubscr...@googlegroups.com. >> To post to this group, send email to influxdb@googlegroups.com. >> Visit this group at https://groups.google.com/group/influxdb. >> To view this discussion on the web visit https://groups.google.com/d/ms >> gid/influxdb/8cd8c32f-d0f2-4cd8-97e1-855e2aff2551%40googlegroups.com >> <https://groups.google.com/d/msgid/influxdb/8cd8c32f-d0f2-4cd8-97e1-855e2aff2551%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- > Remember to include the version number! > --- > You received this message because you are subscribed to the Google Groups > "InfluxData" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to influxdb+unsubscr...@googlegroups.com. > To post to this group, send email to influxdb@googlegroups.com. > Visit this group at https://groups.google.com/group/influxdb. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/influxdb/CAA0q%3Dt%2BYGAnTMyBh3BN9HZ7vuvbkud8V% > 3DcvZKCka7V59hMHPrw%40mail.gmail.com > <https://groups.google.com/d/msgid/influxdb/CAA0q%3Dt%2BYGAnTMyBh3BN9HZ7vuvbkud8V%3DcvZKCka7V59hMHPrw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Sean Beckett Director of Support and Professional Services InfluxDB -- Remember to include the version number! --- You received this message because you are subscribed to the Google Groups "InfluxData" group. To unsubscribe from this group and stop receiving emails from it, send an email to influxdb+unsubscr...@googlegroups.com. To post to this group, send email to influxdb@googlegroups.com. Visit this group at https://groups.google.com/group/influxdb. To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/CALGqCvOszwvmFvtHOh_E6_2ummXx1kyxOU%2BzZZEVgopT%2Bn%2B%2BFA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
