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

Metrics: RTT

XMLWordPrintable

    • BU Product Work
    • 3
    • False
    • None
    • False
    • OCPSTRAT-964 - Metrics and dashboard enhancements for Lokiless usage
    • NetObserv - Sprint 241, NetObserv - Sprint 242, NetObserv - Sprint 243, NetObserv - Sprint 244

      Allow RTT to be reported in prometheus:

      • by src/dst namespace (default)
      • by src/dst node
      • by src/dst workload

      If users need more metrics (such as by pod) they would be encouraged to use the Custom Metrics API instead (coming soon: NETOBSERV-1341 )

      That will give the user the ability to set an alert on a specific value (100ms ?) and see the ribbon on network traffic page 

      Also it will make RTT available without Loki install

       

      These metrics will be available in prometheus, but at the moment without a dedicated chart in our dashboard (it would require more changes because our dashboard doesn't support histogram metrics at the moment)

       

       

      Metric names are:

      • netobserv_node_rtt_seconds
      • netobserv_namespace_rtt_seconds
      • netobserv_workload_rtt_seconds

            [NETOBSERV-1231] Metrics: RTT

            GitLab CEE Bot added a comment -

            CPaaS Service Account mentioned this issue in a merge request of netobserv-midstream / Network Observability Operator Midstream on branch network-observability-1.5.0-rhel-9_upstream_c19857fca9f60bf9210ddfb35112c5c5:

            Updated 2 upstream sources

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in a merge request of netobserv-midstream / Network Observability Operator Midstream on branch network-observability-1.5.0-rhel-9_ upstream _c19857fca9f60bf9210ddfb35112c5c5 : Updated 2 upstream sources

            Amogh Rameshappa Devapura added a comment - - edited

            Could observe the RTT metrics. Works as expected!

            Cluster details:

            • OCP: 4.13.0-0.nightly-2023-11-09-031200
            • NetObserv operator: v0.0.0-6bbedc2
            • eBPF-agent: main
            • FLP: main
            • ConsolePlugin: main

            Amogh Rameshappa Devapura added a comment - - edited Could observe the RTT metrics. Works as expected! Cluster details: OCP: 4.13.0-0.nightly-2023-11-09-031200 NetObserv operator: v0.0.0-6bbedc2 eBPF-agent: main FLP: main ConsolePlugin: main

            Joel Takvorian added a comment -

            rhn-support-aramesha this is ready for review along with NETOBSERV-1326, in the same PR https://github.com/netobserv/network-observability-operator/pull/453

            I updated the description of both tasks to include the names of the metrics added

            Joel Takvorian added a comment - rhn-support-aramesha this is ready for review along with NETOBSERV-1326 , in the same PR https://github.com/netobserv/network-observability-operator/pull/453 I updated the description of both tasks to include the names of the metrics added

            GitLab CEE Bot added a comment -

            CPaaS Service Account mentioned this issue in a merge request of netobserv-midstream / Network Observability Operator Midstream on branch network-observability-1.5.0-rhel-9_upstream_226e34127a8c915a51021aca787a2711:

            Updated 2 upstream sources

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in a merge request of netobserv-midstream / Network Observability Operator Midstream on branch network-observability-1.5.0-rhel-9_ upstream _226e34127a8c915a51021aca787a2711 : Updated 2 upstream sources

            Julien Pinsonneau added a comment -

            rhn-support-aramesha yes the goal was to merge that for 1.4 as dev preview, without QE checks but it was not code reviewed in time so I'm falling back to 1.5 with QE validation  

            Thanks for the reminder !

            Julien Pinsonneau added a comment - rhn-support-aramesha yes the goal was to merge that for 1.4 as dev preview, without QE checks but it was not code reviewed in time so I'm falling back to 1.5 with QE validation   Thanks for the reminder !

            Amogh Rameshappa Devapura added a comment -

            jpinsonn@redhat.com The operator PR has mentioned no-qe in the PR template but does not have no-qe label. Does the FLP PR require no-qe as well? If so, please no-qe to the Jira as well. If QE testing is required please let me know

            Amogh Rameshappa Devapura added a comment - jpinsonn@redhat.com The operator PR has mentioned no-qe in the PR template but does not have no-qe label. Does the FLP PR require no-qe as well? If so, please no-qe to the Jira as well. If QE testing is required please let me know

              jtakvori Joel Takvorian
              jpinsonn@redhat.com Julien Pinsonneau
              Amogh Rameshappa Devapura Amogh Rameshappa Devapura
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: