KIALI-2456,2459,2466,2465, 2450 and 2507 . Improve toolbar for Jaeger Integration and refactor#1025
Conversation
| key: persistKey, | ||
| storage: storage, | ||
| whitelist: ['authentication', 'namespaces', 'serverConfig'], | ||
| whitelist: ['authentication', 'namespaces', 'serverConfig', 'jaegerState'], |
There was a problem hiding this comment.
Should we store all the jaegerState? I'm worried about storing information that might not be accurate the next time we use Kiali such as: toolbar.isFetchingService and jaegerURL.
Please, if needed, consider to only store a subset of this, see: https://github.com/kiali/kiali-ui/blob/master/src/store/ConfigStore.ts#L30-L41
There was a problem hiding this comment.
Totally agree , I am still testing why the state of redux take time in get updated before the rendering of the component, We'll only persist the jaegerUrl.
|
@hhovsepy I fixed the problem here, now traces tab is hide until load. But I see another problems like the missing sidecar icon (See the gif) Maybe we should create some loading view while we fetch the backend what do you think @lucasponce @jotak @xeviknal ? |
|
Removed visual options (Enable by default) to avoid the user get confuse and make the search button more visual. What do you think @pilhuhn ? I think that this is clearer now |
f1df8f2 to
798d333
Compare
|
@aljesusg Much better. I personally (but I don't speak for UxD) would even put the search button next to the input boxes and not "far away" in the corner. |
| whitelist: ['authentication', 'namespaces', 'serverConfig'], | ||
| transforms: [namespacePersistFilter] | ||
| transforms: [namespacePersistFilter, ...persitingJaegerReducers] | ||
| }; |
There was a problem hiding this comment.
Now I persist only the data required @josejulio
|
Fixed !!! Thanks !!! |
8205c41 to
2053cd4
Compare
|
Waw that's a title! :-) Maybe you could set a more meaningful title to better identify this PR in our notifications? |
So Jiras in the same PR ^^ I'll change to another title with more sense, In the description you can see the JIRAs related. Sorry @jotak ^^ |
|
One thing I see, that can be addressed in a different PR, is that traces tab is not linkable. |
lucasponce
left a comment
There was a problem hiding this comment.
Commented with @aljesusg that there is a pending bug
#1025 (comment)
that probably is good to fix on this PR.
Other comments probably can be in separate tasks.
|
Pr rdy for review @lucasponce @xeviknal @hhovsepy |
59d111f to
21909a9
Compare
|
Ok I found the problem, I had persistStore and I didn't see that. Thanks @hhovsepy |
22a3368 to
f745ffe
Compare
|
Fixed @hhovsepy and I did the JIRA https://issues.jboss.org/browse/KIALI-2515 too, it was related with the status too. Thanks !!! |
d17eb8d to
2871fd6
Compare
|
All verified now. |
KIALI-2459 Fix traces tab if value is -1 KIALI-2466 Remove visual options in jaeger toolbar (Hide graph, hide summary) and make the search button bigger KIALI-2465 Get Services in jaegerToolbar is not working after Openshift oauth changes KIALI-2450 Change the namespace Selector in Jaeger Distributed tracing view to be like other views KIALI-2507 Distributed tracing link disappear in a new tab KIALI-2515 UI About - Components not persist when the user open a new tab
lucasponce
left a comment
There was a problem hiding this comment.
Testing locally and tested both with https + http to validate that links are external and https + https, where after accepting the certificate, everything seems to work as expected.












KIALI-2456 Error Traces shows kiali home when refreshing the page
KIALI-2459 Fix traces tab if value is -1
KIALI-2466 Remove visual options in jaeger toolbar (Hide graph, hide summary) and make the search button bigger
KIALI-2465 Get Services in jaegerToolbar is not working after Openshift oauth changes
KIALI-2450 Change the namespace Selector in Jaeger Distributed tracing view to be like other views
KIALI-2507 Distributed tracing link disappear in a new tab
KIALI-2515 UI About - Components not persist when the user open a new tab
All removed from redux to improve performance
Now when you click lookback custom by default is set the dates from 1 hour
Now we support query params in the jaeger integration

