Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

All work

Select view

Select search mode

 
5 of 5

Ensure that template variables are allowed in query editor fields

Unresolved

Description

Ensure that users can use template variables in query editor fields, for example using $node in an Entity or Performance Datasource query editor.

Validation is done to restrict these values to actual property values (e.g. existing node IDs or labels), but need to accept template variables as well, and perhaps include them in the ‘select’ lists.

Attachments

2

Details

Assignee

Reporter

Story Points

Parent

Sprint

Affects versions

Fix versions

Priority

PagerDuty

Created November 30, 2023 at 2:54 PM
Updated May 28, 2024 at 3:49 PM

Activity

Show:

Scott ThelemanJanuary 9, 2024 at 10:50 PM
Edited

This seems to mostly be working for example when using the Performance datasource, Attribute query, selecting a node or resource.

However, in some cases there are issues with dropdowns not allowing a user to input a template variable. Added a new Performance datasource configuration option, allowManualOverrideExtensions, which when enabled, will result in Performance query editor displaying a switch and an input text box next to the Node dropdown, where a static value or template variable can be entered.

Wanted to get this pattern in the code, we can add it as needed to any other fields where there are issues with inputting a template variable.

Performance data source configuration options panel:

 

Performance query editor, using the manual override option to enter a $node template variable: