-
Notifications
You must be signed in to change notification settings - Fork 59
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
Doubt how to get Dashboard data #190
Comments
An additional detail, I am able to get the data using the API directly with this endpoint |
Not all of the endpoints have been implemented in mstrio-py. Many times you may need to dig through the .py files to see if an endpoint is used then go back to the API-docs page to look at the schema of the result so you know how to deal with the response. Though, even those schema are not fully documented, so then you've got to step through a debugger. Like list_dashboards() ultimately calls return connection.post(endpoint='/api/metadataSearches/results', ... But you can access the REST endpoints from the same Connection class you've already instantiated. That makes it a bit simpler to hop back and forth. One of mine for example:
|
Thanks for the answer @hustontrevor. |
Hi @axnsantana , @hustontrevor If you feel that the workaround you found should be resolved directly via mstrio-py functionalities, please request an Enhancement Request via our MSTR TechSupport and provide a CS id here, for reference. With it, we will be able to properly plan and estimate for required changes. |
Hi,
first thanks a lot for the tool, really appreciate.
I am looking at the Dashboard snippets and I do not understand what are the steps to get the same data (time series) I see in the Micro UI.
I can retrieve the Dashboard, its properties, cubes, etc...
I was able to extract the data from Reports (launching instances and so on), but had no success with the Dashboard.
Probably I am missing how Micro works.
Would really appreciate if someone could help me with that.
Thanks a lot.
The text was updated successfully, but these errors were encountered: