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

Wrong metrics when conversation tracking is used

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • netobserv-1.9
    • netobserv-1.7
    • None
    • None
    • False
    • None
    • False
    • NetObserv - Sprint 264, NetObserv - Sprint 265, NetObserv - Sprint 266

      When Conversation Tracking is enabled with logTypes=All or logTypes=Conversations, metrics generated (such as bytes and packet rates) show much bigger numbers as expected. This doesn't happen with logTypes=EndedConversations.

      cf https://issues.redhat.com/browse/NETOBSERV-1922?focusedId=25741876&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-25741876

      > "Moreover there seems to be a bug in metrics generation, which probably counts all flows regardless of their log types, ending up in duplicated counts."

       

              jtakvori Joel Takvorian
              jtakvori Joel Takvorian
              Amogh Rameshappa Devapura Amogh Rameshappa Devapura
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: