Dimensions in the Data Workbench Profile Status profile

IMPORTANT

Read more about Data Workbench’s End-of-life announcement.

The following dimensions are available for use in the data workbench Profile Status profile.

Block This is the only countable in this configuration and exists as the root for all dimensions. A block can be considered a server. It is using the x-trackingid field. The block ID is a hash of the server name plus host name, so there will be approximately one block per server per profile.
As of Delay Minutes cs-uri-query(bi) is placed into the x-as-of-delay-minutes field and rounded to the nearest minute. As of Delay Minutes is a numeric dimension that takes the Last Row from x-as-of-delay-minutes for a block.
Environment The cs-uri-query(c) value is used for the Environment ID. The Last Row for a Block is used as the value for the dimension. This Simple Dimension will display the Environment in which your Servers are running (provided it is configured properly).

This can be set in the insight_monitor_agent.cfg file

Fast Input MegaBytes per Minute The cs-uri-query(bj) value is used for this dimension. The Last Row for a block is used as the value for the dimension. If the dataset is in Fast Input this Numeric Dimension's value will display the MB per minute at which the system is inputting data.

Note: This dimension is hidden because it is only useful when averaged into a metric.

Fast Merge MegaBytes per Minute The cs-uri-query(bk) value is used for this dimension. The Last Row for a Block is used as the value for the dimension. If the dataset is in Fast Merge This Numeric Dimension's value will display the MB per minute at which the system is merging.

Note: This dimension is hidden because it is only useful when averaged into a metric.

Field GigaBytes The cs-uri-query(bg) value is used for this dimension. The value is divided by 1000 and rounded to the nearest whole number. This Numeric Dimension's value will display the amount of space the Fields in the dataset are using.

Note: This dimension is hidden because it is only useful when averaged into a metric.

Host The cs-uri-query(b) value is used for this dimension. The Simple dimension's value is the Last Row for a Block.
Last Ping x-last-ping is x-unixtime divide by 10 (to accommodate Numeric dimensions size constraints). Last Ping is the Last Row for a given Block, and it represents the last time the monitoring agent logged the system health.

Note: This dimension is hidden because it is only useful when averaged into a metric.

Log Reading Percentage the cs-uri-query(be) value is used for this numeric dimension. It is the Last Row for a given Block. This dimension is used to calculate the percentage of logs being read.

Note: This dimension is hidden because it is only useful when averaged into a metric.

Processing Mode ID The cs-uri-query(bb) value is used for this Simple Dimension. It the Last Row for a given Block. Processing Mode ID allows one to see what mode of processing the system is in (Fast Input, Fast Merge, Real Time).

Note: This dimension is hidden then re-exposed with friendly values in the client-side dimension Processing Mode.

Processing Stalled The x-processing-stalled field is created through various conditions to indicate whether the profile is currently running or not. It is a simple dimension.

Note: This dimension works best when there are a large number of input logs to fairly distribute amongst the DPUs. If there is, for example, only one large file loaded per day, then data workbench can appear to "stall" for an hour or more resulting in a false positive reading from this dimension.

Profile The cs-uri-query(ba) value is used for this Simple Dimension. This dimension displays the name(s) of the profiles currently being monitored.
Source Furthest Behind The last row of cs-uri-query(bl) is copied into the x-source-furthest-behind field. The Simple Dimension uses the Last Row for a given Block. This dimension displays the when the last contact with a data source occurred.
Transformation Percentage the cs-uri-query(bf) value is used for this numeric dimension. It is the Last Row for a given Block. This dimension is used to calculate the percentage of complete data transformation.

Note: This dimension is hidden because it is only useful when averaged into a metric.

Time Dimensions Hour, Day, Week, Month, Hour of Day, and Day of Week are all derived from the x-timestamp field.
Group Grouping word that gives you another way to filter the resulting dataset. Set in the insight_monitor_agent.cfg file.
Metrics The following lists the metrics included in the data workbench Profile Monitoring Profile and how they are derived.
As Of Delay Minutes This metric is the sum of the As Of Delay Minutes for each Block, then divided by the Blocks metric.
As Of Delay Seconds This metric is the sum of the As Of Delay Seconds for each Block, and divided by the total number of Blocks. (As of Delay Seconds Dimension not configured out of the box)
Blocks Sum one for each Block.
Fast Input MB per Minute The sum of Fast Input MegaBytes per Minute for each Block divided by the number of Blocks when Fast Input MegaBytes per Minute is greater than zero.
Fast Merge MB per Minute The sum of Fast Merge MegaBytes per Minute for each Block divided by the number of Blocks when Fast Merge MegaBytes per Minute is greater than zero.
Field GigaBytes The sum of Field Gigabytes for each Block divided by Blocks metric.
Last Ping Age The As Of Time minus Last Ping Time.
Last Ping Time The sum of Last Ping for each Block divided by Blocks, then multiplied by 10.
Log Reading Where Log Reading Percentage is greater than zero, Log Reading is the sum of Log Reading Percentage for each Block, divided by Blocks metric, all of which is divided by 10.
Processing Stalled The sum of the Processing Stalled Dimension for each Block, divided by the Blocks metric.
Transformation The sum of Transformation Percentage for each Block divided by the Blocks metric, when Transformation Percentage is greater than zero, all divided by 10.

Business.Adobe.com resources

Docs links
Audio Analytics Flow Analysis Data Explorer Mobile Analytics Mobile Marketing Marketing Analytics

On this page