Azure / Azure/iotedge

[monitor-workbook] Routing tree looses route by diving into shorter time-range.

Open
#6,021 1 comment 0 reactions 1 assignee Assigned to @veyalla View on GitHub
customer-reported iotedge no-issue-activity
Dominant language
C#
Stars
1.5k
Forks
473
Avg merge
2d 17h
Merged PRs (30d)
7

Description

Created from https://github.com/Azure/iotedge/issues/5662, thanks @micahl so far!

Please take a look at this gif/video. First the messages send by `visu-poc-rabbitmq-gateway::unide_process` are shown. But after diving into a a specific time span, the complete route is missing.

![](https://user-images.githubusercontent.com/969523/150096952-aefd2469-5def-407b-b9c9-07731bb18a01.gif)

The slightly modified query provided by @micahl exposes the underlying problem - from my understanding.

The result:
![grafik](https://user-images.githubusercontent.com/969523/150336493-3fb57604-68e7-43c6-8296-c4e401fb6379.png)

So the route seems to be only visible if the selected time range includes the range that already exposes result for the upper query. But this seems to swallow some data as the gif indicates.

Please let me know if further information is needed or I could contribute in any manner.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.