ESC KPI metric for vm overload and underload error missing actionresults (NFVO)

[neetimit]

I have been trying to setup vnf scaling using KPI metrics in esc device template using NFVO. Looks like my metric gets created under that deployment in ESC which I can see in the ESC portal. However, the "last polled" always remain as N/A. Even though I have set polling frequency as 3 seconds. Attaching the screenshot of the ESC portal as well. When I checked the mona.log file I see below error:

2020-02-28 04:52:07.104 [QuartzScheduler_Worker-35] rule-VM_UNDERLOADED-austx-lab-dev-esc-01-vnf-info-csrscale51__afed529d-a728-4d77-84b8-5230e2084db2__0 Error missing actionResults, MonitorThreshold will not be triggered

Can someone please help what might be wrong??

Here goes my ESC device template I am applying.

<devices xmlns="http://tail-f.com/ns/ncs">

<template tags="merge">

<name>CSR_LOAD_TEMPLATE</name>

<ned-id>

<id xmlns:esc-id="http://tail-f.com/ned/esc-id">esc-id:esc</id>

                 <config>

                   <esc_datamodel xmlns="http://www.cisco.com/esc/esc">

                     <tenants>

                       <tenant>

                         <name>ciscoesc</name>

                         <deployments>

                           <deployment>

                             <name>{$VM_NAME}</name>

                             <vm_group>

                               <name>{$SERVICE}-CSR</name>

                               <kpi_data>

                                 <kpi>

                                   <event_name>VM_OVERLOADED</event_name>

                                   <metric_value>10</metric_value>

                                   <metric_cond>GT</metric_cond>

                                   <metric_type>UINT32</metric_type>

                                   <metric_occurrences_true>1</metric_occurrences_true>

                                   <metric_occurrences_false>2</metric_occurrences_false>

                                   <metric_collector>

                                     <type>CPU</type>

                                     <nicid>0</nicid>

                                     <poll_frequency>3</poll_frequency>

                                     <polling_unit>seconds</polling_unit>

                                     <continuous_alarm>false</continuous_alarm>

                                   </metric_collector>

                                 </kpi>

                                 <kpi>

                                   <event_name>VM_UNDERLOADED</event_name>

                                   <metric_value>5</metric_value>

                                   <metric_cond>LT</metric_cond>

                                   <metric_type>UINT32</metric_type>

                                   <metric_occurrences_true>1</metric_occurrences_true>

                                   <metric_occurrences_false>2</metric_occurrences_false>

                                   <metric_collector>

                                     <type>CPU</type>

                                     <nicid>0</nicid>

                                     <poll_frequency>3</poll_frequency>

                                     <polling_unit>seconds</polling_unit>

                                     <continuous_alarm>false</continuous_alarm>

                                   </metric_collector>

                                 </kpi>

                               </kpi_data>

                               <rules>

                                 <admin_rules>

                                   <rule>

                                     <event_name>VM_OVERLOADED</event_name>

                                     <action>ALWAYS log</action>

                                     <action>TRUE servicescaleup.sh</action>

                                   </rule>

                                   <rule>

                                     <event_name>VM_UNDERLOADED</event_name>

                                     <action>ALWAYS log</action>

                                     <action>TRUE servicescaledown.sh</action>

                                   </rule>

                                 </admin_rules>

                               </rules>

                             </vm_group>

                           </deployment>

                         </deployments>

                       </tenant>

                     </tenants>

                   </esc_datamodel>

                 </config>

</ned-id>

</template>

</devices>

Thank you

[ydorego]

Given the provided object model (ESC Device Template) it seems that the action identified by <action>TRUE servicescaleup.sh</action> are not returning any results.

The action tag is a unique identifier for the actions that needs to be defined through the dynamic mappings API. See the following wiki for more information: https://confluence-eng-sjc1.cisco.com/conf/display/ESCWIKI/Dynamic+Mapping+API

Validation steps:

1. Perform a GET request to validate that the actions are defined in the list of actions.
2. If the actions are defined, then validate that the expected operation (custom-script, SNMP) is actually supported by your VNF.

In your specific case you will want to see that the two actions identified by <action>TRUE servicescaleup.sh</action> and TRUE servicescaledown.sh

are defined…

The missing actionResults is an indication that the operations is present may have failed to return any results, the default behavior is to not trigger anything in that scenario.

Best Regards,