Creating a report for the SOW environment

[sapir]

I need to create two separate reports that show the average time it took for the home page to load.
The reports will display information from the "transactions all users" table.
One report should examine the SOW environment, and the second report the environment of the end users who use the portal.
I am having trouble separating the environments.
Thanks in advance for any help.

[Community Alums]

Hi @sapir ,\

o create two separate reports to show the average time for the home page to load for different environments (SOW and end users) using the "Transactions All Users" table, you can achieve this by leveraging filters and conditions in ServiceNow reporting.

Steps to Create the Reports:

1. Understand the Environment Identifier
   First, determine how the environments are distinguished in the "Transactions All Users" table. This could be based on fields like Session Source, Instance Name, User Role, or any other relevant field. For example:

   • SOW Environment: Might have specific Session Source or Instance Name.
   • End Users: May have a different identifier or belong to a specific role or group.

2. Create the SOW Environment Report

   • Navigate to Reports > Create New.
   • Set the name (e.g., "Average Load Time - SOW Environment").
   • Choose the data source as Transactions All Users.
   • In the conditions section, filter the data specific to the SOW environment. For example:
     • Session Source is SOW.
     • Instance Name matches your SOW instance.
   • Select the visualization type (e.g., Line, Bar, etc.).
   • Use the Average aggregation for the load time field (e.g., Duration or equivalent).
   • Save the report.

3. Create the End Users Report

   • Repeat the steps above, but change the filter to match the end-user environment. For example:
     • Session Source is End Users.
     • User Role is Portal User.
   • Save this report with a distinct name (e.g., "Average Load Time - End Users").

4. Verify and Test the Reports

   • Run the reports to ensure that the data is being filtered correctly.
   • Validate that the average load time calculations reflect the respective environments.

Troubleshooting Tips:

• Missing Environment Identifiers: If you don’t have clear fields to differentiate the environments, you may need to add custom attributes or tags to transactions during data collection.
• Dynamic Filters: Use dynamic filters in case the environments might change over time.
• Data Validation: Ensure the "Transactions All Users" table captures accurate data for both environments.