新增Prometheus任务，无法连接/数据为空

[suzylili]

使用docker部署的hertzbeat，想要新增新增Prometheus任务（TDengine，安装在本机）。在powershell上发指令试了下，可以看到是有内容的。

但在新增监控的时候，就是连不上

log报错信息如下：
【ERROR】
2026-01-15 15:25:02.036 [1000000000-_prometheus_taoskeeper-auto-1834] ERROR org.apache.hertzbeat.collector.collect.prometheus.parser.OnlineParser Line:74 - prometheus parser failed because of wrong input format. null
2026-01-15 15:25:02.039 [1000000000-_prometheus_taoskeeper-auto-1834] ERROR org.apache.hertzbeat.collector.dispatch.MetricsCollect Line:480 - [Collect Failed] Response metrics data is null.
2026-01-15 15:25:10.061 [1000000000-_prometheus_taoskeeper-auto-9831] ERROR org.apache.hertzbeat.collector.collect.prometheus.parser.OnlineParser Line:74 - prometheus parser failed because of wrong input format. null
2026-01-15 15:25:10.062 [1000000000-_prometheus_taoskeeper-auto-9831] ERROR org.apache.hertzbeat.collector.dispatch.MetricsCollect Line:480 - [Collect Failed] Response metrics data is null.

【TOTAL】
2026-01-15 15:25:01.679 [http-nio-1157-exec-3] WARN org.apache.hertzbeat.common.util.AesUtil Line:159 - isCiphertext method error: Input length must be multiple of 16 when decrypting with padded cipher
2026-01-15 15:25:02.036 [1000000000-_prometheus_taoskeeper-auto-1834] ERROR org.apache.hertzbeat.collector.collect.prometheus.parser.OnlineParser Line:74 - prometheus parser failed because of wrong input format. null
2026-01-15 15:25:02.039 [1000000000-_prometheus_taoskeeper-auto-1834] ERROR org.apache.hertzbeat.collector.dispatch.MetricsCollect Line:480 - [Collect Failed] Response metrics data is null.
2026-01-15 15:25:09.662 [http-nio-1157-exec-9] WARN org.apache.hertzbeat.common.util.AesUtil Line:159 - isCiphertext method error: Input length must be multiple of 16 when decrypting with padded cipher
2026-01-15 15:25:10.061 [1000000000-_prometheus_taoskeeper-auto-9831] ERROR org.apache.hertzbeat.collector.collect.prometheus.parser.OnlineParser Line:74 - prometheus parser failed because of wrong input format. null
2026-01-15 15:25:10.062 [1000000000-_prometheus_taoskeeper-auto-9831] ERROR org.apache.hertzbeat.collector.dispatch.MetricsCollect Line:480 - [Collect Failed] Response metrics data is null.
2026-01-15 15:25:23.727 [jpa-metrics-cleaner-0] WARN org.apache.hertzbeat.warehouse.store.history.tsdb.jpa.JpaDatabaseDataStorage Line:89 - [jpa-metrics-store]-start running expired data cleaner.Please use time series db instead of jpa for better performance
2026-01-15 15:25:23.728 [jpa-metrics-cleaner-0] INFO org.apache.hertzbeat.warehouse.store.history.tsdb.jpa.JpaDatabaseDataStorage Line:109 - [jpa-metrics-store]-delete 0 rows.
2026-01-15 15:25:30.038 [597925861702144-ssl_cert-certificate-9831] INFO org.apache.hertzbeat.collector.dispatch.MetricsCollect Line:473 - [Collect Success, Run 207ms, All 207ms].
2026-01-15 15:25:53.726 [jpa-metrics-cleaner-0] WARN org.apache.hertzbeat.warehouse.store.history.tsdb.jpa.JpaDatabaseDataStorage Line:89 - [jpa-metrics-store]-start running expired data cleaner.Please use time series db instead of jpa for better performance
2026-01-15 15:25:53.728 [jpa-metrics-cleaner-0] INFO org.apache.hertzbeat.warehouse.store.history.tsdb.jpa.JpaDatabaseDataStorage Line:109 - [jpa-metrics-store]-delete 0 rows.
2026-01-15 15:26:23.724 [jpa-metrics-cleaner-0] WARN org.apache.hertzbeat.warehouse.store.history.tsdb.jpa.JpaDatabaseDataStorage Line:89 - [jpa-metrics-store]-start running expired data cleaner.Please use time series db instead of jpa for better performance
2026-01-15 15:26:23.725 [jpa-metrics-cleaner-0] INFO org.apache.hertzbeat.warehouse.store.history.tsdb.jpa.JpaDatabaseDataStorage Line:109 - [jpa-metrics-store]-delete 0 rows.
2026-01-15 15:26:31.037 [597925861702144-ssl_cert-certificate-0828] INFO org.apache.hertzbeat.collector.dispatch.MetricsCollect Line:473 - [Collect Success, Run 209ms, All 210ms].

[Duansg]

Is authentication enabled? Was authentication set up in the task?

[suzylili]

Is authentication enabled? Was authentication set up in the task?

YES, but it doesn't work

[suzylili]

您的邮件我已收到，祝好

[zqr10159]

This is a known issue that has been fixed. Please look forward to version 1.8.0.