Coldfusion 7.x server
Coldfusion 7.x server
Log Track Supported: Yes
Config Track Supported: No
Custom Properties Supported:
| Name | Description |
|---|---|
| version | Coldfusion Version |
Supported Control Actions: None
Supported Metrics:
| Name | Alias | Units | Category | Default On | Default Interval |
|---|---|---|---|---|---|
| Availability | Availability | percentage | AVAILABILITY | true | 5 min |
| Threads Listening For A New Connection | listenTh | none | THROUGHPUT | false | 5 min |
| Threads Waiting For A New Request | idleTh | none | THROUGHPUT | false | 5 min |
| Threads Waiting To Run | delayTh | none | THROUGHPUT | false | 5 min |
| Threads Currently Running | busyTh | none | THROUGHPUT | true | 5 min |
| Total Worker Threads | totalTh | none | THROUGHPUT | false | 5 min |
| Requests Delayed Due To High Concurrency | delayRq | none | THROUGHPUT | true | 5 min |
| Requests Dropped | droppedRq | none | THROUGHPUT | true | 5 min |
| Requests Handled | handledRq | none | THROUGHPUT | false | 5 min |
| Time Servicing Requests Not Including Any Delay Time | handledMs | ms | THROUGHPUT | true | 5 min |
| Time Spent In Delay State | delayMs | ms | THROUGHPUT | true | 5 min |
| Data Read From Request | bytesIn | B | THROUGHPUT | false | 5 min |
| Data Written To Response | bytesOut | B | THROUGHPUT | false | 5 min |
| Free Heap Memory | freeMemory | KB | THROUGHPUT | false | 5 min |
| Total Memory In The Heap (In Use And Free) | totalMemory | KB | THROUGHPUT | false | 5 min |
| Active J2EE Sessions | sessions | none | THROUGHPUT | false | 5 min |
| J2EE Sessions In Memory | sessionsInMem | none | THROUGHPUT | false | 5 min |
Configuration help:
Configure HQ for monitoring Coldfusion
To enable Coldfusion metric logging follow these instructions:
http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_19120&sliceId=2
Here is sample of what the log file should look like (all the important
attributes are listed).
For HQ metric collection to work properly, the name/value pair must be specified
as follows (may span multiple lines or not).
Look for:
<!-- ================================================================== -->
<!-- This Service represents JRun's logging facility -->
<!-- ================================================================== -->
Then change:
<attribute name="metricsEnabled">true</attribute>
<attribute name="metricsLogFrequency">300</attribute>
<attribute name="metricsFormat">
listenTh={listenTh}
idleTh={idleTh}
delayTh={delayTh}
busyTh={busyTh}
totalTh={totalTh}
delayRq={delayTh}
droppedRq={droppedRq}
handledRq={handledRq}
handledMs={handledMs}
delayMs={delayMs}
bytesIn={bytesIn}
bytesOut={bytesOut}
freeMemory={freeMemory}
totalMemory={totalMemory}
sessions={sessions}
</attribute>
General Log and Config Track Properties
- Enable Log Tracking - Check to enable log tracking.
- Track event log level - Only track events of level greater than or equal to this level. Order is: [Error, Warn, Info, Debug]
Mapping:- Fatal,Error -> Error
- Warning -> Warn
- Information -> Info
- Debug -> Debug
- Log Pattern Match - Include messages that match the given regular expression. The given pattern can be a substring to look for in log messages or a regular expression. See: java.util.regex.Pattern.
- Log Pattern Exclude - Exclude messages that match the given regular expression.
- Log Files - Comma delimited list of log files to track. Relative files are resolved to ${installpath}.