bigcyy opened a new issue, #3268:
URL: https://github.com/apache/hertzbeat/issues/3268
### Is there an existing issue for this?
- [x] I have searched the existing issues
### Current Behavior
When deploying HertzBeat with VictoriaMetrics in **cluster mode**,
historical charts fail to display.
> ❗Although `VictoriaMetricsClusterProperties` and
`VictoriaMetricsClusterDataStorage` exist in the codebase to support cluster
mode, they are currently ineffective due to:
- `VictoriaMetricsClusterProperties` is missing the `enabled` field, so
`@ConditionalOnProperty` fails to activate the configuration.
- The API paths used (e.g., `/api/v1/import`) are for single-node mode, but
the cluster mode requires prefixed paths like
`/select/<accountID>/prometheus/<suffix>`.
As a result, the application does not connect to the VM cluster correctly,
and historical data retrieval fails silently.
### Expected Behavior
HertzBeat should correctly detect and activate
`VictoriaMetricsClusterDataStorage` when cluster mode is enabled via
`application.yml`, and send read/write requests to valid cluster-mode API paths
such as:
- Read: `/select/<accountID>/prometheus/<suffix>`
- Write: `/insert/<accountID>/prometheus/<suffix>`
Historical charts should be displayed successfully using data retrieved from
VM cluster.
### Steps To Reproduce
1. Deploy VictoriaMetrics in cluster mode (vminsert + vmselect + vmstorage).
2. Configure HertzBeat `application.yml` with:
```yaml
warehouse:
store:
victoria-metrics:
cluster:
enabled: true
insert:
url: http://vm-insert:8480
select:
url: http://vm-select:8481
```
3. Start HertzBeat and add a monitored device.
4. Open a historical chart — an error is shown:
> "Unable to provide historical chart, please configure time series database
Service not available!"
### Environment
```markdown
HertzBeat version(s):
```
### Debug logs
_No response_
### Anything else?
#3261 #3249
--
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]
