Skip to content
This repository has been archived by the owner on Sep 26, 2022. It is now read-only.

Add option to keep InfluxDB instance alive after attack cluster teardown #94

Open
rpappalax opened this issue Feb 8, 2017 · 1 comment
Assignees

Comments

@rpappalax
Copy link

rpappalax commented Feb 8, 2017

We'll need this in order to review data post test run. An InfluxDB node is created together with the attack cluster, but entire cluster is destroyed at end of run. In order to review the data after the run, we'll need to keep this instance around to query the data.
Long-term goal would be instead to forward (dump) the data to a collective data store like S3 or a permanent InfluxDB instance (as indicated in Issue #70)

@rpappalax
Copy link
Author

See: Issue #70

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants