Hi,

I have a similar usecase but without the old influxdb migration part.
The short usecase is I want to query data related to a specific host and move 
it to a new database, I had the same problem as the ResultSet is not something 
you can easily write back.

The long story is we need a way to be able to compare datapoints from different 
hosts from different time (2 hosts or more) in grafana. My idea was to get 
these data from the main influx server, probably change the timestamps and put 
them into a temporal one what will serve grafana. 

Thanks for your help

Cheers

2016. augusztus 31., szerda 17:44:08 UTC+2 időpontban Sean Beckett a következőt 
írta:
> Telegraf is in no way compatible with InfluxDB 0.8. It requires InfluxDB 0.9+
> 
> 
> Please see the Export tool for InfluxDB 0.8.9, which was explicitly created 
> to migrate data from InfluxDB 0.8 to InfluxDB 0.9+
> 
> 
> https://github.com/influxdata/influxdb/blob/master/importer/README.md
> 
> 
> 
> We also have white papers and migration webinars to help you understand the 
> export/import process.
> 
> 
> On Wed, Aug 31, 2016 at 8:24 AM,  <ajac...@wework.com> wrote:
> Have you looked at using Telegraf? It supports Influxdb as an input and 
> output so you could pipe data from the source db to the sink db. Does the 
> functionality of Telegraf not meet your needs?
> 
> 
> 
> Alan
> 
> 
> 
> On Wednesday, August 31, 2016 at 9:11:19 AM UTC-4, Bart Verleye wrote:
> 
> > Hi,
> 
> >
> 
> > I have two serves with an influxdb, a source version 0.8 and a sink version 
> > 0.13. Now I'm looking for a convenient approach to copy points from the 
> > source to the sink (preferably in python).
> 
> >
> 
> > What I tried so far:
> 
> > - a query on a InfluxDBClient results in a ResultSet which can't be easily 
> > written back. 
> 
> > - a query on a DataFrameClient results in a dict of dataframes. These 
> > dataframes can be written to the sink with write_points, however, it seems 
> > to be a hassle to get/set the tags. Do I miss something here?
> 
> >
> 
> > What would be the best approach to solve this problem?
> 
> >
> 
> > Thanks,
> 
> > Bart
> 
> 
> 
> --
> 
> Remember to include the InfluxDB version number with all issue reports
> 
> ---
> 
> You received this message because you are subscribed to the Google Groups 
> "InfluxDB" group.
> 
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to influxdb+u...@googlegroups.com.
> 
> To post to this group, send email to infl...@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/8caddf52-b243-4eea-8b6e-44aa3b37ddad%40googlegroups.com.
> 
> 
> 
> 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/16990902-c1fb-4787-a380-0a1bfbbb2a3d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to