What do you want to see in a new Dashboard resource?

[mbazhlekova]

Hi all,

We're thinking of creating a new Dashboard resource for a future TF provider release that is more user friendly and can support newer dashboard features. Please use this space to share any ideas you have for improving the Dashboard resource.

We're excited to hear from you!

[rdhar]

At the base level, supporting dashboard-specific metadata would be useful, such as: "tv-mode: show the dashboard name" and "tv-mode: cycle to the next page every 20 seconds". That should get rid of the current workaround of having to manually configure every single dashboard generated (which isn't feasible after a certain point).

Beyond that, I'm curious about the scope of this discussion. Particularly with regards to current existence of both one_dashboard and one_dashboard_raw. Do you mean something to replace both of these resources, or adding on top of them?

For example, the biggest drawback of dashboards for me is the difficulty of setting widgets to filter on their page. Current workarounds are far from ideal. Recent releases include a cryptic filter_current_dashboard boolean attribute but it doesn't seem applicable as of yet.

[kidk]

Great feedback @rdhar

In general we would like to combine one_dashboard and one_dashboard_raw, or at least introduce a widget_raw to one_dashboard, but there are technical limitations with that.

[rdhar]

I wonder if it's worth considering support for raw JSON in the same format as you would get from any dashboard's "Copy JSON by clipboard" button?

This puts the configuration onus on the user while maintaining full compatibility with the rest of New Relic and its "Import dashboard" button via the UI. This also reduces development management of the dashboard resource since you're dealing with the JSON directly. Similar implementation to webhook alert_channel resource with JSON payload.

Though it does add abstraction to the code, it's very flexible as well.

[rdhar]

Happy to confirm that v2.38.0 has resolved the main filter_current_dashboard = true issue observed with newrelic_one_dashboard. Many thanks for shipping!

[cdobbyn]

Right now managing dashboards as a single resource works, but is difficult to manage for more complicated usages. I would like to see the ability to define pages as a separate resource, maybe even the widgets themselves.

Additionally being able to place some of the more unique widgets (like kubernetes nodes) would be nice.

[kidk]

Thanks for feedback @cdobbyn! Once we have a draft of a new resource we will post it here. Splitting up the resources is going to require API changes, so we will need to work with the dashboard team to make that happen. But we're hopeful :D