Skip to content

docs: add GreptimeDB performance and health-check skills#2591

Draft
evenyag wants to merge 3 commits into
mainfrom
docs/add-performance-skills
Draft

docs: add GreptimeDB performance and health-check skills#2591
evenyag wants to merge 3 commits into
mainfrom
docs/add-performance-skills

Conversation

@evenyag

@evenyag evenyag commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

What's Changed in this PR

Adds GreptimeDB AI-agent skills for performance diagnosis, performance tuning, table design, and cluster health checks.

Also updates skills/README.md with descriptions and install commands for the new skills.

Checklist

  • Please confirm that all corresponding versions of the documents have been revised.
  • Please ensure that the content in sidebars.ts matches the current document structure when you changed the document structure.
  • This change requires follow-up update in localized docs.

evenyag added 3 commits June 29, 2026 17:03
Add four new agent skills: performance diagnosis, performance tuning,
table design, and cluster health check. Register them in skills/README.md.

Signed-off-by: evenyag <realevenyag@gmail.com>
Use distinct hosts in the cluster-health-check smoke test so the
deduplicating table keeps both rows. Point the grafana links in the
diagnosis and health-check skills to the dashboards directory, the
canonical source for the referenced metric names.

Signed-off-by: evenyag <realevenyag@gmail.com>
Signed-off-by: evenyag <realevenyag@gmail.com>
@evenyag

evenyag commented Jul 2, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c65685cfad

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +125 to +126
- CPU: `rate(process_cpu_seconds_total[$__rate_interval])` vs
`greptime_cpu_limit_in_millicores`

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Scale CPU usage before comparing to millicore limits

When agents use this health check to decide whether a pod is near its CPU limit, rate(process_cpu_seconds_total[$__rate_interval]) is reported in CPU cores/seconds, but greptime_cpu_limit_in_millicores is in millicores. The existing key-metrics docs multiply the process CPU rate by 1000 before displaying it in millicores, so this comparison makes CPU usage look 1000x smaller than the limit and can incorrectly mark saturated pods as healthy.

Useful? React with 👍 / 👎.

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.

1 participant