SOL002_56: filters implemented in Alarms GET

          in: header

          required: true

          type: string

        - name: filter

          description: >

            Attribute-based filtering expression according to clause 4.3.2.

            The VNFM shall support receiving this parameter as part of the URI query string.

            The EM may supply this parameter. The VNF may supply its instance Id as an attribute filter.

            The following attribute names shall be supported in the filter expression: id, managedObjectId,

            vnfcInstanceIds, rootCauseFaultyResource.faultyResourceType, eventType, perceivedSeverity, probableCause.

            If the vnfcInstanceIds parameter is provided, exactly one value for the managedObjectId attribute

            shall be provided.

            EXAMPLE

            objects

            obj1: {"id":123, "weight":100, "parts":[{"id":1, "color":"red"}, {"id":2, "color":"green"}]}

            obj2: {"id":456, "weight":500, "parts":[{"id":3, "color":"green"}, {"id":4, "color":"blue"}]}

            Request 1:

            GET …/container

            Response 1:

            [

                {"id":123, "weight":100, "parts":[{"id":1, "color":"red"}, {"id":2, "color":"green"}]},

                {"id":456, "weight":500, "parts":[{"id":3, "color":"green"}, {"id":4, "color":"blue"}]}

            ]

            Request 2:

            GET …/container?filter=(eq.weight,100)

            Response 2:

            [

                {"id":123, "weight":100, "parts":[{"id":1, "color":"red"}, {"id":2, "color":"green"}]}

            ]

          #Request 2 in EXAMPLE from clause 4.3.2 probably wrong, since "," should be used after opOne (eq), "." is used

          in: query

          required: false

          type: string

        - name: nextpage_opaque_marker

          description: >

            Marker to obtain the next page of a paged response.

            Shall be supported by the VNFM if the VNFM supports alternative 2

            (paging) according to clause 4.7.2.1 for this resource.

          in: query

          required: false

          type: string

      responses:

        200:

          description: >