In support of being able to more easily do things such as build Grafana dashboard directly from Elastic/Opensearch, it would be nice if the PWA generated JSON had more metadata. ESnet currently does this with its static file using the pscheduler reference fields. After talking with Shawn McKee, it seems like there is potentially some low hanging fruit to always add Mesh Names (thing MaDDash "dashboard" concept) and test names (think MaDDash "grid" concept") to the reference section by default. This doesn;t even require a UI change, just a backend change to add these fields.
In support of being able to more easily do things such as build Grafana dashboard directly from Elastic/Opensearch, it would be nice if the PWA generated JSON had more metadata. ESnet currently does this with its static file using the pscheduler reference fields. After talking with Shawn McKee, it seems like there is potentially some low hanging fruit to always add Mesh Names (thing MaDDash "dashboard" concept) and test names (think MaDDash "grid" concept") to the reference section by default. This doesn;t even require a UI change, just a backend change to add these fields.