Skip to content

Conversation

ricoberger
Copy link
Member

@ricoberger ricoberger commented Sep 3, 2021

Some days ago we change the Elasticsearch plugin to support multiple
queries in the panel. In the same way we are chaning the options for the
Jaeger plugin now. So that a user can specify multiple queries within a
Jaeger panel. In the UI the user can then select the query he wants to
see via the select box.

This is a breaking change for the Jaeger panel, this means that old
specification wont work anymore with the current version of kobs.

Some days ago we change the Elasticsearch plugin to support multiple
queries in the panel. In the same way we are chaning the options for the
Jaeger plugin now. So that a user can specify multiple queries within a
Jaeger panel. In the UI the user can then select the query he wants to
see via the select box.

This is a breaking change for the Jaeger panel, this means that old
specification wont work anymore with the current version of kobs.
@ricoberger ricoberger merged commit 3dc0c53 into main Sep 3, 2021
@ricoberger ricoberger deleted the support-multiple-queries-for-jaeger-plugin branch September 3, 2021 13:45
ricoberger added a commit that referenced this pull request Sep 9, 2021
In #130 we changed the options for the Jaeger plugin to allow multiple
queries. For that we set the initial selected query to the first query
from the "queries" property. This caused a bug, were the results were
not refreshed after a user changed the service, operation, etc. on the
Jaeger page, because we didn't updated the selected query. The selected
query is now always updated when the queries property is changed and
when it only contains one query, which is always the case for the page
implementation of the Jaeger plugin.

Fixes #142.
ricoberger added a commit that referenced this pull request Sep 9, 2021
In #130 we changed the options for the Jaeger plugin to allow multiple
queries. For that we set the initial selected query to the first query
from the "queries" property. This caused a bug, were the results were
not refreshed after a user changed the service, operation, etc. on the
Jaeger page, because we didn't updated the selected query. The selected
query is now always updated when the queries property is changed and
when it only contains one query, which is always the case for the page
implementation of the Jaeger plugin.

Fixes #142.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant