kubernete dashboard not full work.Latest Kubernetes Warning Events have error info
first I opened json feature,I don't know whether there is an effect
error info
First argument for function 'arrayElement' must be array, got 'JSON' instead: In scope SELECT Timestamp AS Timestamp, JSONExtractString(LogAttributes['object'], 'type') AS Severity, JSONExtractString(LogAttributes['object'], 'regarding', 'kind') AS Kind, JSONExtractString(LogAttributes['object'], 'regarding', 'name') AS Name, JSONExtractString(LogAttributes['object'], 'note') AS Message, Timestamp, ServiceName FROM default.otel_logs WHERE ((Timestamp >= fromUnixTimestamp64Milli(_CAST(1762343814887, 'Int64'))) AND (Timestamp <= fromUnixTimestamp64Milli(_CAST(1762347414887, 'Int64')))) AND ((toString(LogAttributes.k8s.resource.name) = 'events') AND (Severity != 'Normal')) ORDER BY Timestamp DESC LIMIT _CAST(0, 'Int32'), _CAST(200, 'Int32').
SELECT
Timestamp AS "Timestamp",
JSONExtractString (LogAttributes['object'], 'type') AS "Severity",
JSONExtractString (LogAttributes['object'], 'regarding', 'kind') AS "Kind",
JSONExtractString (LogAttributes['object'], 'regarding', 'name') AS "Name",
JSONExtractString (LogAttributes['object'], 'note') AS "Message",
Timestamp,
ServiceName
FROM
default.otel_logs
WHERE
(
Timestamp >= fromUnixTimestamp64Milli (1762343814887)
AND Timestamp <= fromUnixTimestamp64Milli (1762347414887)
)
AND (
(
(
(
toString (`LogAttributes`.`k8s`.`resource`.`name`) = 'events'
)
AND (Severity != 'Normal')
)
)
)
ORDER BY
Timestamp DESC
LIMIT
200
OFFSET
0
Hey @SamPeng87 thanks for reporting this! This error is caused by a bug in our beta support for the JSON schema. We will fix it. In the meantime, the Kubernetes dashboard should work with the older Map schema.
嘿,谢谢你反馈这个问题!这个错误是由我们对 JSON schema 的 beta 支持中的一个 bug 引起的。我们会修复它。与此同时,Kubernetes dashboard 可以使用较旧的 Map schema 正常工作。
thanks your reply,but,where is older Map schema?
thanks your reply,but,where is older Map schema?
The older map schema should be available by default. The JSON schema is enabled when you set the BETA_CH_OTEL_JSON_SCHEMA_ENABLED and OTEL_AGENT_FEATURE_GATE_ARG environment variables as described here.
If you have already created the JSON schema, to revert to the Map schema you would have to disable those settings ^ and drop the existing otel_logs and otel_traces tables in your ClickHouse instance (either by connecting to the ClickHouse instance and running DROP TABLE ... or by deleting any volumes that exist for the ClickHouse container. You'd also probably want to delete the volumes associated with the HyperDX container, to reset to the default (non-JSON) source configurations.
Note: These steps will result in data and settings being cleared from ClickHouse and HyperDX's MongoDB instance.