Skip to content

Commit

Permalink
Document how series counts are logged
Browse files Browse the repository at this point in the history
  • Loading branch information
trevorbonas committed May 6, 2024
1 parent 6e06ba9 commit 8ec1d2f
Showing 1 changed file with 14 additions and 0 deletions.
14 changes: 14 additions & 0 deletions tools/python/influx-migration/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -651,3 +651,17 @@ Possible reasons for a restore failing include:
- Invalid InfluxDB destination token.
- A bucket existing in the destination instance with the same name as in the source instance. For individual bucket migrations use the `--dest-bucket` option to set a unique name for the migrated bucket.
- Connectivity failure, either with the source or destination hosts or with an optional S3 bucket.

### Determining Amount of Data Migrated

By default, the number of shards migrated, as reported by the Influx CLI, and the
number of rows migrated when `--csv` is used, are logged.
When the log level is set to `debug`, with the option `--log-level debug`, the
number of [series](https://docs.influxdata.com/influxdb/v2/reference/key-concepts/data-elements/#series) as reported by
the [InfluxDB `/metrics` endpoint](https://docs.influxdata.com/influxdb/v2/api/#operation/GetMetrics), under [bucket series number](https://docs.influxdata.com/influxdb/v2/reference/internals/metrics/#bucket-series-number),
will be logged.

If a bucket is empty or has not been migrated, it will not be listed under bucket series number and an error indicating as such will be logged.
This can help determine whether data is successfully being migrated.

To manually verify migrated records, see the recommended queries listed in the [Migration Overview](#migration-overview) section, step 3.

0 comments on commit 8ec1d2f

Please sign in to comment.