* Update dashboard app to use app SDK v0.35.0
What
This change updates dashboard app to use app SDK v0.35.0 and adds new
Makefile target for running codegen for all apps, in opt-in manner.
Currently only dashboards app is opted in.
Additionally, this changes dashboard app Makefile to properly install
and update app SDK versions when generating code, with app SDK version
pinned in the Makefile itself.
Why
The upgrade addresses issues with `DeepCopy` methods, while the Makefile
targets ensure that codegen is easy to run and uses reproducible
environments.
Signed-off-by: Igor Suleymanov <igor.suleymanov@grafana.com>
* Run make update-workspace
Signed-off-by: Igor Suleymanov <igor.suleymanov@grafana.com>
* Fix deepcopy methods
Signed-off-by: Igor Suleymanov <igor.suleymanov@grafana.com>
* Re-run CUE codegen to satisfy the CI
Signed-off-by: Igor Suleymanov <igor.suleymanov@grafana.com>
* Run make update-workspace
Signed-off-by: Igor Suleymanov <igor.suleymanov@grafana.com>
* Update to v0.35.1
Signed-off-by: Igor Suleymanov <igor.suleymanov@grafana.com>
---------
Signed-off-by: Igor Suleymanov <igor.suleymanov@grafana.com>
* feat: align frontend more with designs
* feat: remove unnecessary fields
* chore: remove imports
* chore: move imports
* fix: make label not spit out undefined
* feat: update title of nav item
* chore: make update-workspace
* fix: don't wrap text with span unless required
---------
Co-authored-by: Roberto Jimenez Sanchez <roberto.jimenez@grafana.com>
* refactor(frontend): rename all @grafana/data/src imports to @grafana/data
* feat(grafana-data): introduce internal entrypoint for sharing code only with grafana
* feat(grafana-data): add test entrypoint for data test utils usage in core
* refactor(frontend): update import paths to use grafana/data exports entrypoints
* docs(grafana-data): update comment in internal/index.ts
* refactor(frontend): prefer public namespaced exports over re-exporting via internal
* chore(frontend): fix a couple more weird paths that typescript complains about
* Remove aggregate by
* Update betterer
* Run toggles test
* Add back group by in schema so it can be checked for
* Show error if group by
* Update error message
* Allow user to remove the group by from the query
* Fix assertion
---------
Co-authored-by: Piotr Jamróz <pm.jamroz@gmail.com>
* Dashboard: Add object to selected object
* Try not to nest rows
* Update
* Update
* rows in rows, tabs in tabs
* Update schema to allow nested rows and nested tabs
* fix lint issue
* reset v2alpha1 types from main
* reset dashboard_object_gen.go to main
---------
Co-authored-by: oscarkilhed <oscar.kilhed@grafana.com>
* remove range from class
* remove range from language provider
* use range parameters in MetricsLabelsSection
* use range parameters in metric_find_query
* pass range parameter in monaco-query-field
* typo
* use range in prometheus metrics browser languageProvider calls
* fix unit tests
* fix unit tests
* update unit tests
* lint
* Live: allow publishing over Centrifuge subscription
Currently when publishing over a Grafana Live channel,
the data is sent over the HTTP API. This works fine when
there is only a single Grafana instance running, but
when there are multiple instances, the data will only hit
one instance, which is often not desired: sometimes you need
to guarantee that the data appears on the same instance that
the frontend is connected to.
An example of this is in the Grafana LLM app when running the
MCP server. The MCP protocol is stateful; users subscribe to
a channel to get a long-lived stream of server-sent events,
then send subsequent requests to the server to get further
results. If there are multiple Grafana instances running then
the requests are likely to land on an instance other than the
one that the user is connected to.
This commit adds a new option to the `GrafanaLiveSrv` interface
that allows the user to publish data over the Centrifuge
subscription instead of the HTTP API. This is not the default and
should rarely be used, but is required to fulfil certain use cases.
* Address nits from code review
Co-authored-by: kay delaney <45561153+kaydelaney@users.noreply.github.com>
---------
Co-authored-by: kay delaney <45561153+kaydelaney@users.noreply.github.com>
Developers using Grafana Live need to know whether a message is too
big to be sent over the Grafana Live websocket. Since this limit
is configurable, it is useful to expose it to the frontend.
This commit adds a new field to the frontend settings,
`liveMessageSizeLimit`, which the frontend can use to access the
limit configured in the backend.
Relates to #99770.
* Draft: Move css grid stuff to main
* Scenes: Implement drag and drop support for SceneCSSGridLayout
* Fix some nits
* WIP Refactor
* Added a comment
* Add orchestrator to v2schema and fix error (#100964)
* Add orchestrator to v2schema and fix error
* Display placeholder directly when starting to drag
---------
Co-authored-by: kay delaney <kay@grafana.com>
* Fix merge issue
* Fix panel drag offset and remove console.logs
* Fix small nit
* Fix issue where layout options weren't refreshed on changing layout
* Return empty array from useEditPaneOptions if dashboard body isn't LayoutOrchestrator
* Expect layoutOrchestrator when serializing scene
* Fix tests to expect orchestrator instead of layoutManager
* Fix tests in transformSaveModelSchemaV2ToScene.test.ts
* Fix tests in transformSceneToSaveModelSchemaV2.test.ts
* More test fixes
* fix lint issues
* Small fixes
* default to adding layout orchestrator?
* Empty commit
* delete artifactspage.go
* remove artifactspage.tmpl.html
* betterer
* WIP refactor, not ready for review
* Slightly fix placeholder behavior. still broken though
* Fixed some visual glitches. Still very buggy
* Fix layout bugginess when initiating dragging
* more WIP
* Fix some broken logic
* clean up
* Move LayoutOrchestrator to dashboard state
* More cleanup
* Fix misaligned placeholders after changing layout options or resizing browser
* Fix issue with dragging vs selection
* Fix scroll position jumping when dragging in vertically-oriented grid
* Fix import order errors
* Remove '!' from layoutOrchestrator references
* Add LazyLoader support
* Dynamic Dashboards: Responsive Grid drag and drop minor fixes (#102430)
Changes
---------
Co-authored-by: Oscar Kilhed <oscar.kilhed@grafana.com>
Co-authored-by: Bogdan Matei <bogdan.matei@grafana.com>
* Allow html in tooltips
* Display multiple warnings/infos properly with html
* Revert "Allow html in tooltips"
This reverts commit 5c7e965d2d554b693d4897e52cf6865e0c9b8374.
* Display multiple warnings/infos properly with html in ReactNode
* Fix lint
* Revise according to code review
* Revise according to code review part 2
* Revise according to code review part 3
* feat: component extension point for adaptive telemetry query actions
- only render the first non-null added-component, and provide utility in the added component infrastructure to support this
---------
Co-authored-by: Levente Balogh <balogh.levente.hu@gmail.com>