Uploaded image for project: 'GPII - Global Public Inclusive Infrastructure'
  1. GPII - Global Public Inclusive Infrastructure
  2. GPII-2390

Match the GPII logging messages with the metrics needed.

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: Pilot Stage 2
    • Labels:
      None
    • Environment:
      Windows clients:
       * GPII installed
       * Filebeat ELK client installed
       * Internet connection

      Cloud:
       * ElasticSearch engine
       * Kibana
    • Sprint:
      DevOps Sprint 2 - Pilots 1&2
    • Story Points:
      5

      Description

      The Metrics team requires a collection of logs which report the use of GPII. The metrics that need to be collected are described in the following document:

      https://docs.google.com/document/d/1MEBTL3wpFUUk5B-g9ZbpfKMXt_Q7mk-GUQnKTygs16o/edit

      In order to collect those metrics a cloud instance of ElasticSearch + Kibana has been deployed. At the Windows client side the service called Filebeat will send the logs reported by GPII to the ElasticSearch cluster.

      Actually the structure of the GPII logs and the contents of them don't allow the matching to get the metrics needed.

      Some research about how to set a schema for the logs to be understandable by ELK, and how to report the events that the GPII generates, are mandatory to build the automatic metrics needed by the Metrics team.

      Also, additional lines of code in the GPII will be needed in some cases.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              amatas Alfredo Matas
              Reporter:
              amatas Alfredo Matas
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: