High Watermark Report
The High Watermark Report provides information to help manage Sterling Connect:Direct® node usage or meet other reporting needs.
The High Watermark Report can also be used to see how many times sessions would be queued if the number of concurrent sessions allowed were reduced. To do this, set the report session limit to a value lower than the license limit.
You can use the report to determine what would happen if the limit on simultaneous sessions were raised or reduced. The # Times sessions exceeded limit column tells how many processes would have been queued to run later if the session limit were enforced.
The start time of the longest period over limit, in conjunction with the Last time max reached, can serve as an indicator of when the most Sterling Connect:Direct processing is occurring on your systems.
Max Concurrent Sessions indicates the maximum number of processes that ran at the same time. The # Times max reached column can indicate whether or not the maximum number of processes running at one time was an aberration or whether it happens frequently. By reducing the report limit, you can determine the typical number of processes running simultaneously by watching for an increase in the # Times max reached value.You can restrict High Watermark Report output to a range of dates and times, to specific servers or server groups, and to a session limit. Default filter criteria preset for this report include Limit, Max Process Duration, Data/Time, and Servers. You can change the presets at the time of creation. Servers is the only one required.
After you confirm your choices and run the report, a status window displays the time elapsed since the report was initiated, along with start date/time and end date/time criteria. A progress bar depicts report generation progress and shows the date of the last statistics record processed.
The report includes detailed statistics for each selected server or server group as well as summary statistics across all selected servers.
The following table describes the columns of the High Watermark Report.
|*||An asterisk next to a server ID indicates that a process on this server has exceeded the maximum duration.|
|Server Name||The server ID.|
|Max Concurrent Sessions||The peak number of sessions reached during the selected period.|
|# Times Max Reached||The number of occurrences within the selected period that Max Concurrent Sessions was reached.|
|Last Time Max Reached||The date and time of the last point when Max Concurrent Sessions was reached.|
|# Times Above Limit||The number of times the specified session limit was exceeded.|
|# Times Sessions Exceeded Limit||The number of sessions initiated while the session concurrency count was at or above the session limit.|
|Last Time Limit Exceeded||The date and time of the point when the limit was last exceeded (not the point when concurrent sessions returned below the threshold).|
|Start Time of Longest Period Over Limit||The date and time when the longest over limit period began.|
|Longest Period Over Limit||The amount of time in the longest over limit period.|
|% Time Over Limit||The percent of the total date/time range that the server or servers spent over the limit.|
|# Processes Exceeding Max Duration||How many processes have exceeded the maximum process duration.|
|Longest Process Exceeding Max Duration||The running time for the process that has furthest exceeded the maximum process duration.|