Log messages

Documentation / C/C++ Edition / User Guide / Appendix / Log messages

Log messages

Log message No. 1: CONFIG PROPERTY

Brief
Log message which reports used configuration properties.
Level
config
Message
Property: <Property>='<Value>' read from config
Arguments
Property
Name of the configuration property
Value
Configured value for the property.
Description

For each configuration property this message is issued with its used value. Therefore the complete MyARM configuration is logged to the configured logging destination. Only the log messages until the logging configuration is read will not be logged.

Log message No. 2: CONFIG DEFAULT PROPERTY

Brief
Log message which reports used default configuration properties.
Level
config
Message
Property: "<Property>" not found using default: '<DefValue>'
Arguments
Property
Name of the configuration property
DefValue
Default value used.
Description

For each configuration property which can not be found in the current configuration the used default value is reported with the log message.

Log message No. 3: CONFIG PROPERTY ERROR

Brief
Log message which reports an error for a configuration property.
Level
error
Message
Property: <Property>='<Value>' not valid. Using default: '<DefValue>'
Arguments
Property
Name of the configuration property.
Value
Configured value for the property.
DefValue
Default value used.
Description

Some configuration properties allows only a set of defined values. If another value was specified in the configuration this error message is issued.

Log message No. 4: CONFIG PROPERTY FILE

Brief
Reports which configuration property file was used.
Level
config
Message
Property file '<File>' used
Arguments
File
Name of the configuration property file used.
Description

MyARM can be configured using configuration property files. This log message reports which file is used to read the configuration. Therefore it allows you to check your MyARM environment.

Log message No. 5: CONFIG VAR ERROR

Brief
An environment variable expansion failed for the report property key and value.
Level
error
Message
Environment variable expansion failed for <Key>='<Value>': Variable <Variable> <Reason>
Arguments
Key
Property key which caused the error.
Value
Property value which caused the error.
Variable
Variable which caused the error.
Reason
Reason of the error.
Description

The value of the reported property key contains a reference to an environment variable and the expansion of this reference failed for the reported reason.

Log message No. 6: CONFIG URL ERROR

Brief
The configuration URL has an error.
Level
error
Message
Configuration URL '<URL>': <Reason>
Arguments
URL
The URL which caused the error.
Reason
Reason of the error.
Description

MyARM uses configuration property files to read user defined configuration properties. A configuration property file is passed to MyARM via the MYARM_CONFIG_URL environment variable. The value of this variable is erroneous.

Log message No. 7: CONFIG NOT FOUND

Brief
The configuration could not be found.
Level
error
Message
Configuration not found: <Reason>
Arguments
Reason
Reason of the error.
Description

The MyARM configuration property file could not be found.

Log message No. 8: CONFIG OUT OF RANGE

Brief
The value of the configuration property is out of the given range. MyARM adjusted the used value.
Level
error
Message
Property <Key>='<Value>' out of range [<Min>,<Max>] using <Used>
Arguments
Key
Property key which caused the error.
Value
Property value which is out of range.
Min
Minimum allowed value.
Max
Maximum allowed value.
Used
Used value.
Description

The value of the reported property key is out of range and is adjusted by MyARM.

Action

Please configure the configuration property to an allowed value.

Log message No. 9: EVENTLOG CREATE FAILED

Brief
The creation of the MyARM event log channel under Windows failed.
Level
error
Message
Can not create event log logger reason='<Reason>'
Arguments
Reason
Reason code of failure. A call to the registry failed.
Description

To create an event log channel under Windows various variables have to be set in the Windows registry. The Reason code describes which registry call failed.

Action

Consult the MyARM support.

Log message No. 10: DYNAMIC OBJECT FAILED

Brief
A dynamic object (e.g. datasink or datasource) could not be loaded.
Level
error
Message
Loading of dynamic object '<Object>' failed: '<Reason>'
Arguments
Object
The dynamic object which should be loaded.
Reason
Reason code of failure.
Description

MyARM uses a modular plugin concept for its datasink and datasources. These plugins are written as dynamic objects which are loaded during runtime of the application. The reported dynamic object failed to load into memory for the reported reason.

Action

Make sure you have not mixed different MyARM versions otherwise consult the MyARM support.

Log message No. 11: OUT OF MEMORY

Brief
During an operation not enough memory could be allocated to finish the operation.
Level
error
Message
Out of memory: <Operation>.
Arguments
Operation
The operation which was canceled due to an out of memory problem.
Description

During low memory siutations MyARM tries to allocate memory but this failed. The operation is canceled.

Action

Please check you configuration (transaction and ARM data buffer pools) to avoid low memory situation support.

Log message No. 12: API ERROR

Brief
Reports an API error of the C, Java or C# API bindings.
Level
error
Message
< Method>(): (rc='<Code>') '<Description>'. <Details>
Arguments
Method
Method or function name the API error occured.
Code
Return code of the API method or function.
Description
Brief description of the error.
Details
More details if available.
Description

MyARM detected an error during a API method or function call. This can be caused by passing some invalid parameters or some sort of ARM standard specification violation.

Action

Please read the MyARM users guide return code reference section for details on a specific error.

Log message No. 13: API WARNING

Brief
Reports an API warning of the C, Java or C# API bindings.
Level
warning
Message
< Method>(): (rc='<Code>') '<Description>'. <Details>
Arguments
Method
Method or function name the API warning occured.
Code
Return code of the API method or function.
Description
Brief description of the warning.
Details
More details if available.
Description

MyARM detected a situation which is not standard compliant during a API method or function call.

Action

Please read the MyARM users guide return code reference section for details on a specific warning.

Log message No. 14: ERROR

Level
error
Message
< Message>
Arguments
Message
Error message.
Description

General purpose error message. This error message is issued whenever MyARM detects an exception within its analysis tools.

Log message No. 15: CANNOT OPEN FILE

Level
error
Message
Cannot open file '<File>'. Reason: '<Reason>'
Arguments
File
The name of the file which could not be opened.
Reason
Reason of the failure.
Description

The reported file could not be opened due to the reported reason.

Log message No. 16: ARM DATA DROPPED

Brief
Log message which reports dropped ARM data.
Level
error
Message
Could not process ARM data (defs='<Defs>', apps='<Apps>', trans='<Trans>', metrics='<Metrics>', logs='<Logs>') <reason>. ARM data is dropped!
Arguments
Defs
Number of definitions dropped (application-, transaction- or metric-definition)
Apps
Number of application instances dropped.
Trans
Number of transaction instances dropped.
Metrics
Number of metric instances dropped.
Logs
Number of dropped log messages.
reason
Description of the reason.
Description

This message is issued when the ARM data cannot be passed to its datasink and the temporary file storage for storing ARM data has reached its limit.

Action

To resolve this problem check why the datasink is not available (database, network)

Log message No. 17: ARM DATA DROPPED TOTAL

Brief
Log message which reports the total number of dropped ARM data.
Level
error
Message
Total number of dropped ARM data: defs='<Defs>', apps='<Apps>', trans='<Trans>', metrics='<Metrics>', logs='<Logs>').
Arguments
Defs
Number of definitions dropped (application-, transaction- or metric-definition)
Apps
Number of application instances dropped.
Trans
Number of transaction instances dropped.
Metrics
Number of metric instances dropped.
Logs
Number of dropped log messages.
Description

This message is issued when the MyARM agent is closed from the instrumented application and reports the total number of dropped ARM data (definitions, application- and transaction instances, metrics and log messages). This log message reports the sum of all dropped ARM data.

Log message No. 18: NO LICENSE

Level
error
Message
No license for <Name> available!
Arguments
Name
Name of the component the license check failed
Description

This message indicates that the named component is not licensed to you. It is possible that you mixed components of different MyARM editions.

Action

Please verify your MyARM installation.

Log message No. 19: ARM TRAN CALLS STAT

Level
info
Message
Transaction function calls: start=<StartCalls>, stop=<StopCalls>, update=<UpdateCalls>, discard=<DiscardCalls>, active=<ActiveTrans>
Arguments
StartCalls
Number of calls to the arm_start_transaction() function call.
StopCalls
Number of calls to the arm_stop_transaction() function call.
UpdateCalls
Number of calls to the arm_update_transaction() function call.
DiscardCalls
Number of calls to the arm_discard_transaction() function call.
ActivteTrans
Number of currently active transaction measurements.
Description

This message reports the number of calls to the appropriate ARM 4.0 C functions. It is usefull to monitor start and stop calls as well number of currently active transaction measurements during development and test phase of the ARM instrumentation. Also this information gives a hint if MyARM C ARM 4.0 transaction functions are called at all (start and stop calls increases).

Log message No. 20: FILTER TOKENIZE FAILED

Level
error
Message
< Step> string '<Filter>' failed: '<ErrorCode>'
Arguments
Step
The tokenize step either 'Tokenizing' or 'Parsing'
Filter
The filter string to tokenize and parse
ErrorCode
Internal error code
Description

This message reports an error within the Filter string.

Action

Please check the filter string and update your configuration.

Log message No. 21: FILTER CANNOT FIND METRIC

Level
error
Message
cannot find metric '<Metric>'
Arguments
Metric
The name of the metric which could not be found during filtering
Description

A filter references a metric with the name Metric but the metric was not attached to a transaction measurement.

Action

Please check if the appropriate transaction definition has such a metric.

Log message No. 22: APP NOT STOPPED

Level
warning
Message
application instance app_handle='<AppHandle>' not stopped
Arguments
AppHandle
The handle as returned by the arm_start_application() function
Description

Within the C language binding a previously started application was not stopped before the instrumented application terminated or the libarm4.so was unloaded.

Action

Please verify your ARM instrumentation of the appropriate application or notify the vendor of the instrumented application that there is an ARM instrumentation issue.

Log message No. 23: TRAN NOT STOPPED

Level
warning
Message
transaction instance tran_handle='<TranHandle>' not stopped
Arguments
TranHandle
The handle as returned by the arm_start_transaction() function
Description

Within the C language binding a previously started transaction was not stopped before the instrumented application terminated or the libarm4.so was unloaded.

Action

Please verify your ARM instrumentation of the appropriate application or notify the vendor of the instrumented application that there is an ARM instrumentation issue.

Log message No. 24: POOL INFO

Brief
Reports resource allocation and usage information
Level
info
Message
< Name> pool info: min=<Min>, max=<Max>, allocated=<Alloc>, current=<Current>, total=<Total>
Arguments
Name
Name of the resource pool
Min
Configured minimal number of allocated instances
Max
Configured maximal number of allocated instances
Alloc
Maximal allocated instances at one time
Current
Currently used instances at report time
Total
Total number of used instances
Description

MyARM manages various resources in so-called resource pools. The following named resource pools are currently used:

  • Transaction for storing transaction measurement information
  • Metric for storing ARM metric information
  • ARMData for storing serialized ARM data

Log message No. 26: FILESTORAGE STATE

Level
status
Message
State changed from [<old>] to [<new>]
Arguments
old
Old file storage state
new
New file storage state
Description

The file storage module has changed its state from the old to the new state. A state change indicates that the processing of ARM data within the file storage stopped (e.g. the new state is INACTIVE) or is started again (e.g. the new state is SCANDIR or READNEXT).

Log message No. 42: FILESINK CHECK DIR

Level
error
Message
Directory check for '<Dir>' failed: <Reason>
Arguments
Dir
Path to the directory which was checked
Reason
The description why the check failed.
Description

The filesink checked the existance and permission of the configured directory where ARM data files should be written to. The directory must exist and the user on behalf the filesink was executed needs write permission for that directory.

Action
  • Please create the directory if it does not exist.
  • Please set the correct write permissions.

Log message No. 43: FILESINK ARMDATA INFO

Brief
Reports about a processed ARM data file.
Level
info
Message
ARM data file: '<File>' contains defs='<Defs>', apps='<Apps>', trans='<Trans>', logs='<Logs>'
Arguments
File
Name of the processed file.
Defs
Number of ARM definitions.
Apps
Number of ARM application instances.
Trans
Number of ARM transaction instances.
Logs
Number of log messages.
Description

This message reports the successful processing of an ARM data file by the filesink. The number of contained entites are reported.

Log message No. 44: LICENSED INSTALLS EXCEEDED

Brief
Number of licensed installations was exceeded.
Level
error
Message
Number of licensed installations (<Number>) exceeded
Arguments
Number
Licensed installations.
Description

The number of licensed installations (system addresses) was exceeded and measurements were dropped.

Action
  • Please contact MyARM to increase the number of licensed installations.

Log message No. 69: FILESINK CANNOT MOVE FILE

Level
error
Message
Cannot move file '<File>' to '<Dir>': Reason '<Reason>', dropped ARM data: defs='<Defs>', apps='<Apps>', trans='<Trans>', logs='<Logs>'
Arguments
File
Name of the file which was not moved.
File
Directory name where the file should be moved to.
Defs
Dropped number of ARM definitions.
Apps
Dropped number of ARM application instances.
Trans
Dropped number of ARM transaction instances.
Logs
Dropped number of log messages.
Description

This message is issued when an ARM data file could not be moved to its destination directory.

Action
  • Please check the existance and write permissions of the destination directory.

Log message No. 75: FILESINK MIN FREE

Level
error
Message
Minimum free disk space reached '<Free><=<Min>', dropped ARM data: defs='<Defs>', apps='<Apps>', trans='<Trans>', logs='<Logs>'
Arguments
Free
Current free disk space
Min
Configured minimum disk space.
Defs
Dropped number of ARM definitions.
Apps
Dropped number of ARM application instances.
Trans
Dropped number of ARM transaction instances.
Logs
Dropped number of log messages.
Description

This message is issued when the disk space gets low and drops below the configured minimum disk space of the file datasink. Please check if the myarmfiled is running and processes stored files. Also check other system resources which may waste disk space.

Log message No. 76: FILESINK MAX USED

Level
error
Message
Maximum used disk space reached '<Used>>=<Max>', dropped ARM data: defs='<Defs>', apps='<Apps>', trans='<Trans>', logs='<Logs>'
Arguments
Used
Currently used ARM data disk space
Max
Configured maximum of used disk space.
Defs
Dropped number of ARM definitions.
Apps
Dropped number of ARM application instances.
Trans
Dropped number of ARM transaction instances.
Logs
Dropped number of log messages.
Description

This message is issued when the used disk space of ARM data gets its configured maximum limit. Please check if the myarmfiled is running and processes stored files. Also check the destination datasink (e.g. the database or myarmtcpd) is up and running.

Log message No. 98: STATUS

Level
status
Message
< Message>
Arguments
Message
The status message.
Description

General purpose status message. This status message is issued within the Web-Analysis server part.