Engine metrics support for: CPU use, network use, end to end processor latency

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Atlas Streams
    • Fully Compatible
    • Sprint 55, Sprint 56, Sprint 57, Sprint 58, Sprint 59
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This is the top level improvement ticket for engine work to support customer facing metrics.

      The required engine work in Q3 is exposing the below, likely in the stats command:

      • End to End Processor Latency
      • Worker level-- CPU Use (this might be better implemented outside of the engine, we can consider using FTDC for it if we want to use the engine)
      • Network use

      See the priority metrics in this spreadsheet: https://docs.google.com/spreadsheets/d/1xMkpOokwbV7dcmsfsIpWUbcY2N9NIQU9lk02itb_ij0/edit#gid=0... And this table in the product description: https://docs.google.com/document/d/1AkCzgbd3z0gyWgLp46ptubV44zC-naUpi-_poHxKCyE/edit

              Assignee:
              Jagadish Nallapaneni
              Reporter:
              Matthew Normyle
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 4 weeks
                  4w
                  Remaining:
                  Remaining Estimate - 4 weeks
                  4w
                  Logged:
                  Time Spent - Not Specified
                  Not Specified