Skip to content

Conversation

@fredjoonpark
Copy link

Adds a new Kiro Power for Timestream for InfluxDB. See POWER.md for an overview.

Next steps

  1. Review current PR (see placeholder steering guides)
  2. Decide if we want to keep or change current POWER.md structure/format
  3. Decide which steering guides we want as part of v1 launch
  4. Decide if we want to keep track of WIP steering guides in the POWER.md or remove it

The below can be used as a guideline for which topics we want to cover in our corresponding development guides.

Topics for Development Guide in InfluxDB 2 & 3

Some important topics to cover are:

  • Onboarding

    • Deploy v2/v3 instances, create org/bucket (v2) or database/table (v3)
    • Generate operator/admin tokens with least privilege
    • Produce ready-to-run client snippets
  • Data Ingestion & Writing

    • Batch writing - Optimize batch sizes for performance
    • Line protocol formatting
      • "Here are sample metrics: . Convert them to line protocol with good tags/fields and write it to my InfluxDB 3 instance."
  • Querying & Analysis

    • Common examples for Flux, SQL queries
      • Time-range queries - Filter data by time windows
      • Aggregations - Calculate means, sums, percentiles over time periods
    • Provide “query cookbook” patterns; generate queries from English + explain/optimize them; text-to-SQL examples
    • Query language migration examples (Flux → SQL)
    • Query troubleshooting - “This query is slow—rewrite it and suggest indexes/structure changes (or schema changes) to fix it.”
  • Schema Design & Data Modelling

    • Tag vs Field optimization - Guide on storing metadata in tags (indexed) vs numeric values in fields (not indexed)
    • Series cardinality management - Identify and reduce high cardinality issues that slow writes/reads, random IDs as tags, mixed field types
      • "Audit my bucket/table: which tags are blowing up series count, and how do I redesign?"
    • Naming conventions - Avoid reserved keywords and special characters in tag/field keys

Nice-to-haves once we have the above:

  • Dashboards & Visualization

    • Integrate with Grafana MCP and create end-to-end Grafana dashboards from schema
    • Guide for updating dashboard queries on schema changes
  • Migration & Version Management

    • Handle migrations
    • Navigate differences between InfluxDB 2 and 3
    • Backup or moving data across instances/orgs/dbs/tables
      • "Export the last 7 days of tenant=acme data for incident analysis."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants