influxdata / influxdata/docs-v2
How to orchestrate tasks and workflows using InfluxDB v3
- Dominant language
- JavaScript
- Stars
- 82
- Forks
- 326
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 82
Description
Provide strategies and examples for orchestrating tasks using InfluxDB v3.
Describe cases for different tools (K8s, Prefect, Fargate/Python (check with Tech Support for examples))
How to migrate v2 tasks (conceptually or procedurally) to other tools and workflows while taking advantage of InfluxDB v3 performance, storage, and existing clients.
See thread https://influxdata.slack.com/archives/CDBJ35NBV/p1692036000828809
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the issue and the linked Slack thread, then confirm Fargate/Python examples with Tech Support. Document orchestration strategies for Kubernetes, Prefect, and Fargate/Python, and explain conceptual or procedural migration from InfluxDB v2 tasks to workflows using InfluxDB v3.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, python
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100