Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-17717

FIWARE.Question.Tech.Best practices/Expected way to retrieve yearly KPI.

    Details

    • Type: Monitor
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:

      Description

      Created question in FIWARE Q/A platform on 11-05-2021 at 07:05
      Please, ANSWER this question AT https://stackoverflow.com/questions/67482486/best-practices-expected-way-to-retrieve-yearly-kpi

      Question:
      Best practices/Expected way to retrieve yearly KPI

      Description:
      Moving forward from here, I don't know What's the expected way/best practice to handle yearly KPIs to/from Orion?.
      Consider the following scenario:
      1-Consumers requests per-year city inhabitants KPI (city census in 2020, 2021, and so on).
      Sometimes it requests current year, or even a few (ie:drawing population graph) making multiple requests.
      2-Orion should forward the request to Context Provider
      3-Context Provider returns keyPerformanceIndicator for a valid year

      As doing one registration for each year population seems odd to me, perhaps, when registering the provider, I could use:
      isPattern: 'true',
      id: 'city.inhabitants:'

      And then, provider application parsing year from 'city.inhabitants:2020'
      Maybe I'm completely wrong, and Fiware is not expected to handle KPIs but entities, and each year is an attribute for population entity
      Please, don't hesitate to correct anything you may find wrong. Any link/documentation would be great also.

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        1d 1 Backlog Manager 13/May/21 7:31 AM
        In Progress In Progress Closed Closed
        1d 1 Backlog Manager 14/May/21 7:31 AM

          People

          • Assignee:
            Unassigned
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: