Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-20827

API Path missing in Velocloud template

    XMLWordPrintable

Details

    • Incident report
    • Status: Closed
    • Trivial
    • Resolution: Fixed
    • None
    • None
    • Templates (T)
    • None
    • Team INT

    Description

      API path /linkQualityEvent/getLinkQualityEvents in the Zabbix template

      Fetch per-link and overall Quality of Experience scores for the specified Edge over the specified time interval. For each link, this method reports an aggregate totalScore, a score breakdown by traffic type, a timeseries composed of samples for which pre- and post-enhancement link states are recorded by traffic type, and quality state distributions by traffic type. It also summarizes effective overall link quality scores across all links in the same format on the overallLinkQuality property.

      QoE scores are computed based on a sample of events stored on the Orchestrator. Clients may optionally parameterize the number of events sampled (see the maxSamples parameter) or the duration of samples (see minutesPerSample), but the default parameter values should be sufficient for most, if not all, use cases.

      The response schema for this method is unique in that several of the constituent objects use integer keys that inform how values should be interpreted.

      Where breakdowns are presented by traffic type, as they are in the distribution and score summary objects, they should be interpreted as follows:

      0: Voice
      1: Video
      2: Transactional
      Where breakdowns are presented by state, as they are in the traffic-type-specific distribution summaries, they should be interpreted as follows:

      0: Offline
      1: Unknown
      2: Red
      3: Yellow
      4: Green
      Where actions are referenced in timeseries samples, they should be interpreted as follows:

      0: None
      1: Avoid
      2: Jitter Buffer
      3: Error Correction
      4: Forward Error Correction
      Where metrics are referenced in timeseries samples, they should be interpreted as follows:

      0: Latency Rx
      1: Latency Tx
      2: Jitter Rx
      3: Jitter Tx
      4: Loss Rx
      5: Loss Tx ”

      Attachments

        Activity

          People

            abiba Andrew Biba
            asebiskveradze Aleksandre Sebiskveradze
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: