Forest, that's an interesting find. Please open an issue <https://github.com/influxdata/kapacitor/issues/new> on the Kapacitor repo so the developers can take a look.
On Tue, Oct 25, 2016 at 12:09 PM, <[email protected]> wrote: > Actually, I have discovered a workaround. when creating the task, I can > use the following JSON: > > "dbrps": [ > { > "db": "my_db", > "rp": "" > } > ], > > instead of > > "dbrps": [ > { > "db": "my_db", > "rp": "autogen" > } > ], > > which I was using before. > > But I still think this inconsistency should be fixed. > > On Tuesday, October 25, 2016 at 12:51:48 PM UTC-5, > [email protected] wrote: > > We are using the TICK stack with the InfluxDb relay according to the > diagram at https://github.com/influxdata/influxdb-relay#description > > > > We decided the cleanest way to configure kapacitor would be to have the > relays forward data to it directly, rather than having kapacitor subscribe > to one of the replicas or subscribe to a load balancer representing the > replicas. > > > > We were able to configure that, but we hit a snag. When data is ingested > by influxdb, if no retention policy is specified, influxdb will > automatically put it in the "autogen" retention policy. However, it appears > that when data is forwarded to Kapacitor, it won't show up in a StreamNode > unless it has a retention policy specified. This really threw me for a > loop and I had no idea what was going on until I stumbled across the > following thread on this mailing list: > > > > https://groups.google.com/forum/#!searchin/influxdb/ > kapacitor$20write$20|sort:relevance/influxdb/mnomTKVUK98/fYnMoP3sCgAJ > > > > In my opinion either InfluxDb should require a retention policy to be > specified like Kapacitor does, or Kapacitor should automatically shovel > metrics with null retention policies into one called autogen just like > InfluxDb. > > > > For now we will probably have to configure Kapacitor to listen to one of > the InfluxDb replicas since we can't update every single one of our > Telegraf instances just to get around this inconsistency. > > > > Forest > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > 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/8671deb5-fceb-4c17-b620-628bc5bb1631%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 [email protected]. To post to this group, send email to [email protected]. 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/CALGqCvN%2B57G5vVu-EqPk0WHknzHgoAk%3DmCh%2B_wCoMzjw1NB1GQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
