[FEATURE] Add GreptimeDB datasource Plugin#629
Conversation
Signed-off-by: sun <sunchang_long@163.com>
|
The CI workflow failure seems unrelated to the changes in this PR. |
Signed-off-by: sun <sunchang_long@163.com>
Signed-off-by: sun <sunchang_long@163.com>
Signed-off-by: sun <sunchang_long@163.com>
Fixgeneration
|
Added |
|
Hi team, @jgbernalp we have addressed most review issues could you please check again. |
Signed-off-by: sun <sunchang_long@163.com>
Signed-off-by: sun <sunchang_long@163.com>
Signed-off-by: sun <sunchang_long@163.com>
Signed-off-by: sun <sunchang_long@163.com>
Signed-off-by: sun <sunchang_long@163.com>
Signed-off-by: sun <sunchang_long@163.com>
Signed-off-by: sun <sunchang_long@163.com>
Signed-off-by: sun <sunchang_long@163.com>
Signed-off-by: sun <sunchang_long@163.com>
Signed-off-by: sun <sunchang_long@163.com>
chore: plugin version
|
the CI error was caused by perses-dev peerDependencies upgration, should be fixed |
Code reviewFound 1 issue:
plugins/greptimedb/package.json Lines 44 to 85 in 21a1d26 The component exists but is dead code without proper wiring: plugins/greptimedb/src/explore/GreptimeDBTraceExplorer.tsx Lines 1 to 5 in 21a1d26 Reference: Tempo plugin's correct pattern: Lines 14 to 18 in 21a1d26 Lines 78 to 87 in 21a1d26 🤖 Generated with Claude Code |
yes, it is a knowned issue. |
|
@sunchanglong in that case, please remove the dead code and create an GitHub issue for later implementation |
Signed-off-by: sun <sunchang_long@163.com>
feat: remove explorer
|
the dead code has been removed. |
Signed-off-by: sun <sunchang_long@163.com>
Signed-off-by: sun <sunchang_long@163.com>
Signed-off-by: sun <sunchang_long@163.com>
Signed-off-by: sun <sunchang_long@163.com>
Signed-off-by: sun <sunchang_long@163.com>
Signed-off-by: sun <sunchang_long@163.com>
Description
This pull request adds a new GreptimeDB plugin to the plugins repository so Perses can query and visualize metrics & logs data from GreptimeDB.
The implementation covers the main GreptimeDB query workflows used in Perses dashboards:
querying time series data from GreptimeDB based on panel time range
converting GreptimeDB responses into the data format expected by Perses panels, so charts and related visual components can consume results without additional handling
A few points worth calling out for review:
GreptimeDB response data is normalized and mapped into Perses-compatible series/frames, including timestamps, values, and label dimensions
plugin schemas, SDK integration helpers, datasource configuration, query editor support, and tests are included in the same change
only files required for the GreptimeDB plugin and workspace/plugin registration were touched
This change is intended to address GreptimeDB datasource support discussed in the linked issue and related follow-up conversations.
Screenshots
Checklist
[<catalog_entry>] <commit message>naming convention using one of thefollowing
catalog_entryvalues:FEATURE,ENHANCEMENT,BUGFIX,BREAKINGCHANGE,DOC,IGNORE.UI Changes