[LoadRunner Professional] Dashboard and pipeline fixes (DataDog#2410)

Co-authored-by: Owen Moreau <[email protected]>

loadrunner_professional/README.md

@@ -11,7 +11,7 @@ With this integration, Controller pushes real-time metrics and data from scenari
 |   |   |
 |---|---|
 |__Send scenario information__| Send information about the scenario run, such as the start and stop time, duration and included scripts in the form of logs.
-|__Send run information__| Send metrics from the scenario run, such as Vuser status and transaction response times. |
+|__Send run metrics__| Send metrics from the scenario run, such as Vuser status and transaction response times. |
 
 ## Setup
 
@@ -20,11 +20,11 @@ Configure LoadRunner Controller to push data to Datadog. You can choose whether
 1.  Open Controller.
 2.	In the Controller toolbar, select __Tools > Datadog Configuration__.
 3.	In the __Site__ field, select your [Datadog site][6].
-4.	In the __API Key__ field, enter the [API key][7] generated by Datadog.
+4.	In the __API key__ field, enter the [API key][7] generated by Datadog.
 5.	Click __Test Connection__.
-6.	Once the connection is successful, choose whether to send scenario information, run information, or both to Datadog.
+6.	Once the connection is successful, choose whether to send scenario information, run metrics, or both to Datadog.
 7.	If you enable Controller to send scenario information, the included log pipeline with this integration automatically processes your logs and adds relevant tags. For more specifics on the pipeline, navigate to Logs > Pipelines in Datadog.
-8.	In Datadog, the __LoadRunner Stats__ dashboard will automatically be installed with the integration. The dashboard includes widgets that display run information and scenario information (depending on the data that Controller is configured to send).
+8.	In Datadog, the __LoadRunner Professional Dashboard__ will automatically be installed with the integration. The dashboard includes widgets that display run metrics and scenario information (depending on the data that Controller is configured to send).
 
 Once Controller has been configured to push data to Datadog, the data is pushed each time you run a scenario in Controller. To disable Controller from pushing data to Datadog, select __Tools > Datadog Configuration__ and clear the fields in the Datadog Configuration dialog box.
 

loadrunner_professional/assets/dashboards/loadrunner_professional_overview.json

@@ -213,7 +213,7 @@
                         "response_format": "event_list",
                         "query": {
                             "data_source": "logs_stream",
-                            "query_string": "service:loadrunner_professional source:loadrunner",
+                            "query_string": "service:loadrunner_professional source:loadrunner_professional",
                             "indexes": [],
                             "storage": "hot"
                         },

loadrunner_professional/assets/logs/loadrunner_professional.yaml

@@ -1,7 +1,22 @@
 id: loadrunner_professional
 metric_id: loadrunner-professional
 backend_only: false
-facets: []
+facets: 
+  - groups: 
+      - LoadRunner Professional
+    name: Scenario Mode
+    path: scenario_started.summary.mode
+    source: log
+  - groups: 
+      - LoadRunner Professional
+    name: Scenario Type
+    path: scenario_started.summary.scenario_type
+    source: log
+  - groups: 
+      - LoadRunner Professional
+    name: Load Behavior
+    path: scenario_started.summary.load_behavior
+    source: log
 pipeline:
   type: pipeline
   name: LoadRunner Scenario Information Pipeline
@@ -20,33 +35,3 @@ pipeline:
       targetType: tag
       preserveSource: true
       overrideOnConflict: false
-    - type: attribute-remapper
-      name: Map `scenario_started.summary.mode` to `loadrunner.scenario.mode`
-      enabled: true
-      sources:
-        - scenario_started.summary.mode
-      sourceType: attribute
-      target: loadrunner.scenario.mode
-      targetType: attribute
-      preserveSource: true
-      overrideOnConflict: false
-    - type: attribute-remapper
-      name: Map `scenario_started.summary.scenario_type` to `loadrunner.scenario.type`
-      enabled: true
-      sources:
-        - scenario_started.summary.scenario_type
-      sourceType: attribute
-      target: loadrunner.scenario.type
-      targetType: attribute
-      preserveSource: true
-      overrideOnConflict: false
-    - type: attribute-remapper
-      name: Map `scenario_started.summary.load_behavior` to `loadrunner.scenario.load_behavior`
-      enabled: true
-      sources:
-        - scenario_started.summary.load_behavior
-      sourceType: attribute
-      target: loadrunner.scenario.load_behavior
-      targetType: attribute
-      preserveSource: true
-      overrideOnConflict: false

loadrunner_professional/assets/logs/loadrunner_professional_tests.yaml

@@ -4,11 +4,6 @@ tests:
         {"scenario_started":{"general":{"product": "LoadRunner Controller","version": "2024.1.0.0","path": "Scenario1","resultname": "","result_file": "C:\\Users\\user1\\AppData\\Local\\Temp\\2\\res\\res.lrr","start_time": 1707817084.000000,"daylight_bias": "0 minutes","time_zone": "0 seconds"},"scripts":[{"name": "webhttphtml1","type": "Multi+QTWeb","path": "C:\\Users\\user1\\Desktop\\WebHttpHtml1"}],"summary":{"scenario_type": "Manual Scenario","goal_profile_name": "Schedule 1","mode": "Scenario Scheduling","scenario_duration": "Start 25 Vusers: 5 every 00:00:05 (HH:MM:SS); Run for 00:01:00 (HH:MM:SS); Stop all Vusers: 5 every 00:00:05 (HH:MM:SS)","load_behavior": "Initialize each Vuser just before it runs"}}}
     result: 
       custom:
-        loadrunner:
-          scenario:
-            load_behavior: "Initialize each Vuser just before it runs"
-            mode: "Scenario Scheduling"
-            type: "Manual Scenario"
         scenario_started:
           general:
             daylight_bias: "0 minutes"