Uploaded image for project: 'Network Observability'
  1. Network Observability
  2. NETOBSERV-1721

Lokiless topology: "step into" bypasses forbidden scopes

XMLWordPrintable

    • False
    • None
    • False
    • Hide
      Previously, when Loki was disabled, in the Topology view of the console plugin with the Scope set to Owner, clicking on the "step into" icon next to any graph node would bring the Scope to Resource, which isn't available without Loki, hence showing an error message. Now the "step into" icon is hidden in the Owner scope when Loki is disabled, so that this scenario is not possible.
      Show
      Previously, when Loki was disabled, in the Topology view of the console plugin with the Scope set to Owner, clicking on the "step into" icon next to any graph node would bring the Scope to Resource, which isn't available without Loki, hence showing an error message. Now the "step into" icon is hidden in the Owner scope when Loki is disabled, so that this scenario is not possible.
    • Bug Fix
    • NetObserv - Sprint 255

      Description of problem:

      When using the lokiless mode, the topology "step into" actions still allow to enter in "resource" scope even though this should only be possible with Loki.

      Steps to Reproduce:

      1. Install & deploy NetObserv in lokiless mode
2. Open topology, switch to Owner scope
3. Click on "step into" from any graph node

      Actual results:

      Error is displayed mentioning that this query cannot be run

      Expected results:

      The "step into" icon should not even be displayed when coming from Owner, same as the "Resource" scope that isn't displayed.

              jtakvori Joel Takvorian
              jtakvori Joel Takvorian
              Mehul Modi Mehul Modi
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: