New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Undocumented dashboards/import API Call #44383
Comments
Hi, regarding the missing documentation we plan to change the way we document the API. Therefore it's hard to prioritise it unless we get some help. example request for importing dashboard with library panels
|
If Grafana is re-working how the imports are being done that's fine. I understand that this isn't a big priority though I did want to point out the discrepancy. I am trying to understand the recommended REST API to use though. Is it fair to say that /api/dashboards/import is likely the recommended end approach to use to import dashboards over /api/dashboard/db/ ? I'd like to at least confirm I'm going down the right path as the documentation on said endpoint is missing. |
sorry, I think my comment got misinterpreted. I was replying to Also what issues do you have with the Post dashboard with library panels example request
I don't think that there is a recommended endpoint to use. The |
@papagian I believe this ticket has more context: #44003. It's my understanding that the dashboard/db does not support importing third party panels. Last comment was:
This was initialed from a user opening up a ticket in the dashboard management tool I wrote for grafana. My understanding from the user feedback is that:
My concern was using the /import over /dashboard/db was related to the fact that it seems like an undocumented API. My request / questions: A. Can you confirm that the 3 assertions above are correct? |
@papagian Here would be the fix/feature for |
If you want to share dashboards among different grafana instances then the endpoint to use is the |
Exactly, and that is how we came to this issue and request to document that |
Closing this issue because it's over a year old, in an unresourced area, and not likely to be worked on in the next year. |
I'm not sure if this qualifies as a bug or feature request but...
The API used by the frontend to import a dashboard is /api/dashboards/import which seems to be the only one that supports importing library panels. The documented API for doing so /api/dashboard/db/ does not support library panels.
It would be nice if we could get either the dashboard/db to support the library panels OR document /import as a valid endpoint to use.
Either approach is fine as long as it's documented accordingly.
The text was updated successfully, but these errors were encountered: