Detailed Status interface
The Detailed Status interface is useful for troubleshooting errors or other issues with Data Workbench server computers.
This includes any Transform profiles running on those computers, or Report computers that are clients of the Data Workbench server. You can access Master Server and Query Server Detailed Status interfaces through the Admin menu. To access the Detailed Status interface for other computers, in the Servers Manager, right-click the node of the server for which you want to view status and click Detailed Status . See The Servers Manager .
For more information about the Data Workbench server, see the Server Products Installation and Administration Guide .
To update the information in a Detailed Status interface, right-click the Detailed Status heading and click Refresh .
The following table lists the tasks that can be completed using the Detailed Status interface.
|To perform this task...||Do this...|
To display each computer component and its current status
Click Component Status .
To display how much memory on the computer is being used
Click Memory Status > Address Space Load .
For more information about monitoring address space load, see the Server Products Installation and Administration Guide .
To determine whether the computer is configured to use the /3GB Switch
Click Memory Status > Process Address Space .
If the Total field displays more that 3000000 KB, your computer is configured to use the /3GB Switch.
For more information about the /3GB Switch, see the Server Products Installation and Administration Guide .
To monitor the amount of disk space and memory used to store each dimension as well as that used to store the names of its elements
Click Performance > Dimensions > Disk Usage > < profile name > or Performance > Dimensions > Memory Usage > < profile name > .
The Disk Usage fields provide the name and amount of disk space (in MB) required to store each dimension. Large disk usage numbers can adversely affect query times because the Data Workbench server has to read through all the data to complete related queries. Lowering the disk usage for a dimension can reduce the time it takes to complete related queries.
The Memory Usage fields provide the number of elements in each dimension and the amount of memory required to store the list of element names. Large numbers of elements can adversely affect the amount of memory being used during a query because the Data Workbench server has to read through each element. Reducing the number of elements in a dimension can reduce the time it takes to complete related queries.
Example: + Performance - Dimensions - Disk Usage - ProfileName - DimensionName 1.386 MB . . . - Memory Usage - ProfileName - DimensionName 21 elements, 0.001 MB . . .
To monitor the CPU usage for the stages within Log Processing and Transformation
Click Performance > CPU Usage > Log Processing > < profile name > or Performance > CPU Usage > Transformation > < profile name >.
Each of these sets of fields provides you with the CPU Usage (in seconds) for each of the stages within Log Processing and Transformation.
Example: + Performance - CPU Usage - Log Processing - ProfileName 158.9 sec - Built-in 158.1 sec - StageName 13.0 sec . . . - Log Processing\ProfileName 0.8 sec - StageName 0.8 sec
The time that it takes to complete a query is usually proportional to the total size of all of your dimensions. After reviewing the size of each dimension, you can evaluate whether a particular dimension is useful enough and used often enough to justify the performance cost of the dimension. If it is not, you can delete the dimension in the Profile Manager . See The Profile Manager .
A dimension whose list of element names is excessively large (that is, more than 128 MB) may cause “Out of memory” errors even if the total address space usage is not near the limit.
Also, if you are using a Data Workbench server cluster but not using centralized normalization, a dimension whose list of element names is large has a significant impact on send memory budgets. For more information about centralized normalization, see the Dataset Configuration Guide . If the amount of memory required to store all of the lists of element names combined is more than 100 MB across all of the servers in the cluster, you might receive “Send memory budget exceeded” errors even when query activity is light. For example, if you have a four-server cluster with more than 25 MB on each server being used to store the lists of element names, you might receive errors.
To monitor the time spent in Log Processing and Transformation
Click Performance > CPU Usage > Log Processing > < profile name > or Performance > CPU Usage > Transformation > < profile name > .
Reviewing the fields in these sections enables you to identify filters and transformations that may be negatively affecting the amount of time needed for Log Processing and Transformation. You then can make design decisions regarding individual filters and transformations with long processing times.
To monitor disk space usage and increase query speed
Click Performance > Log Processing Fields > < profile name > .
Each line item in this section corresponds to a parameter in the Log Processing.cfg file. Reviewing these fields enables you to see how much memory each parameter is using. You then can make design decisions regarding individual items that are quite large.
To determine the elapsed time of previous reprocessing or transformation
Click Processing Status > < profile name > > Processing Mode History .
To diagnose “As-of time” issues
Click Processing Status > < profile name > > As Of Time > Sources as-of .
Reviewing the as-of times for each source can help you determine which source(s) may be negatively affecting the Overall As-of. You then can address the problems with those particular sources.
To estimate how long a running query takes to complete
Click Execution Engine .
Reviewing the Data Sweep Time field provides you with an estimate of how long it takes for a query to complete.
To list all profiles available on this computer and details about their status
Click Profiles .
To view Replication status
Click Component Status .
Check the status of the Replicate component. If Replication is running, OK displays. If the Replicate component has failed, an error message displays.
To view Report Server status for a Report computer that connects to the Data Workbench server
Click Report Server Status .
This section of the Detailed Status interface includes a copy of the Report Server.cfg file, information about the number of reports that are running (Current Slice), and information about the most recent error (Last Error).
For steps to edit the Report Server.cfg file, see the Data Workbench Report Guide .
Note: If the Report Server Status section does not appear in the Detailed Status interface, you may need to configure the Data Workbench server to display Report Server Status . For steps, see the Data Workbench Report Guide .
To view memory usage information for Transform
Click Processing Status > Transform .
For more information about Transform, see the Server Products Installation and Administration Guide and the Dataset Configuration Guide .
To save the Detailed Status interface as a *.cfg file that can be opened in a text editor such as Notepad or distributed to others
Right-click the Detailed Status heading and click Save Copy As .
Right-clicking the Detailed Status heading and clicking Save to server name /Status/ does not work in the Detailed Status interface. The following error message appears:
Unable to save /Status/. 403 Forbidden
To view Rows per Log Source metric
If Rows per Log Source metric needs to be reported in Detailed Status, then the Data Workbench Administrator should define the "Log Source ID" and provide a unique name in Custom Profile's Log Processing.cfg.