Duansg opened a new pull request, #4369:
URL: https://github.com/apache/hertzbeat/pull/4369

   ## What's changed?
   
   **New `update-1.9.0.md` (en + zh-cn)**: a step-by-step 1.8.x → 1.9.0 guide 
covering runtime, `application.yml`, `sureness.yml`, GreptimeDB, collectors, 
monitors, alerting, API consumers, Docker Compose, Helm, AI/SOP schedules, 
removed features, dependency changes, a post-upgrade checklist and the 
export/import fallback. 
   
   **Corrections to `upgrade.md`**
   
   - Dropped the `/api/traces/**` and `/api/ingestion/otlp/metrics/*` rows from 
the path mapping table; neither path exists in 1.8.0, so they are not 
migrations.
   - Rewrote the GreptimeDB signal table section: 1.8.0 has no trace ingestion, 
query API or traces page, so `hzb_traces` holds only HertzBeat's own spans and 
the documented `service_name` split had nothing to act on.
   - Replaced "`hertzbeat_logs` is not renamed, no action needed" with the 
`body` column type change, which is what actually breaks ingestion.
   
   ## Verification
   
   `markdownlint-cli2` over all 569 files: 0 errors. Full `pnpm run build`: 
`[SUCCESS]` for en, zh-cn and ko with `onBrokenLinks: 'throw'`. Anchors checked 
with `github-slugger`.
   
   ## Checklist
   
   - [x]  I have read the [Contributing 
Guide](https://hertzbeat.apache.org/docs/community/code_style_and_quality_guide)
   - [x]  I have written the necessary doc or comment.
   - [ ]  I have added the necessary unit tests and all cases have passed.
   
   ## Add or update API
   
   - [ ] I have added the necessary [e2e 
tests](https://github.com/apache/hertzbeat/tree/master/e2e) and all cases have 
passed.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to