All work
- Convert Alarm Table Panel to ReactOPG-314Alberto
- Convert Query Editors to ReactOPG-313Scott Theleman
- Port Helm to ReactOPG-312Jeff Gehlbach
- Top N Devices option in OpenNMS HELM and GrafanaOPG-153
- nodeResources query not working properlyOPG-475Scott Theleman
- Unable to set node in Perf DS QueryOPG-424Scott Theleman
- Parameter values are being sent for the wrong parameters in flow datasource queriesOPG-423Scott Theleman
- Alarm datasource query not keeping proper equalityOPG-411Alberto
- Dashboard Conversion Tool Not Finding Legacy PluginsOPG-408Scott Theleman
- Adding a perf filter query to a dashboard elicits "TypeError: l is undefined"OPG-406Alberto
- Rename Helm in the Helm docsOPG-388Bonnie Robinson
- Convert Perf Datasource to ReactOPG-331Scott Theleman
- Expose interface label in Flow DS like in performance DSOPG-280
- Flow deep dive dashboard shows error start cannot be after endOPG-234fooker
- Dealing with flows without sampling intervalOPG-226
- Alarm Color Themes not supported in histogramsOPG-225
- Alarm Histogram x axis labels are incorrectOPG-224
- Migrate Helm from Bamboo to CircleCIOPG-215
- Alerting SupportOPG-200
- Disable clear/ack & ticket related actions on historical alarmsOPG-198
- Query historical alarmsOPG-197
- entity query is wrongOPG-194
- Template variables from many OpenNMS instancesOPG-177
- IPLIKE support in Filter PanelOPG-169
- Alarm table column headings don't centerOPG-168
- Seamless scrolling in alarm table panelOPG-158
- Create filter for Interface name on basis of SNMP ifAlias under SNMP InterfaceOPG-157
- Data for Null values affecting the dashboard. Need an option to bypass the null metricsOPG-141
- Is In Situation Column not available for Alarm TableOPG-114
- Add a sticky note to multiple alarmsOPG-113
- Repeating panels and rows (scoped vars) broken in fault-dsOPG-112Markus von Rüden
- Template variable for "All" not handled correctly in fault-dsOPG-111Markus von Rüden
- Situation Feedback should accept additional AlarmsOPG-108
- Flow Deep Dive dashboard shows NaN.nfinity values in Errors/DiscardsOPG-107
- Flow DS: Support multiple targetsOPG-85
- Severity colors are not consistent with those in the OpenNMS Web UIOPG-83
- Alarm table panel does not work with snapshotsOPG-81
- Implement a flexible SSO framework that encompasses Helm and OpenNMS and can work with identity providers including OktaOPG-80Jeff Gehlbach
- Alarm table is text is hard to readOPG-59
- Link to the alarm details broken when using proxied datasourceOPG-57
- Add support for relative date handlingOPG-47Markus von Rüden
- Add troubleshooting datasources to the documentationOPG-44
- Highlighting of template variables does not work properlyOPG-34
- Expose other tables as Grafana panelsOPG-9
- Helm DocumentationOPG-5
- Performance datasource returns incomplete data when multiple resources are queriedOPG-482
- upgrade helm to latest grafana 9.x APIsOPG-445Scott Theleman
- React Flow Panel and Datasource improvementsOPG-369Scott Theleman
- Add the ability to filter conversations based on a host in the conversationOPG-366
- Multiple Values for String Property does not work for OpenNMS Performance DatasourceOPG-365Alberto
50 of 214
Convert Alarm Table Panel to React
Unresolved
Description
Lucidchart Diagrams
Details
Assignee
AlbertoAlbertoReporter
Benjamin ReedBenjamin ReedSprint
NoneFix versions
Priority
Critical
Details
Details
Assignee
Alberto
AlbertoReporter
Benjamin Reed
Benjamin ReedSprint
None
Fix versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created March 30, 2022 at 1:52 PM
Updated May 10, 2023 at 7:27 PM
Activity
Show:
Scott ThompsonDecember 15, 2022 at 5:39 PM
PR #1 for this is up here: https://github.com/OpenNMS/opennms-helm/pull/580
This is more of a PR to get the repo synced up before my PTO. It’s in a really good place though, so it’s ready if someone wants to test it, or take over development to get it 100% of the way there. I suspect it’s about 90% of the way so far, testing being a good chunk of that remaining 10%.
The Helm Alarm Table Panel was originally based on Grafana's
table
panel.Even Grafana decided trying to port it to React would be too much trouble, and instead they implemented a new React-based table called
table2
. 🙂(Suggestion: look into whether it's possible to subclass or extend their table as much as possible, rather than copying it wholesale like we did for the first implementation.)