Log messages

Online section / Guides / User Guide / Appendix / Log messages contact | download | sitemap

Log messages

Message No. 1: CONFIG PROPERTY

Brief

Log message which reports used configuration properties.

Level

config

LogMsg

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.

Message No. 2: CONFIG DEFAULT PROPERTY

Brief

Log message which reports used default configuration properties.

Level

config

LogMsg

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.

Message No. 3: CONFIG PROPERTY ERROR

Brief

Log message which reports an error for a configuration property.

Level

error

LogMsg

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.

Message No. 4: CONFIG PROPERTY FILE

Brief

Reports which configuration property file was used.

Level

config

LogMsg

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.

Message No. 5: CONFIG VAR ERROR

Brief

An environment variable expansion failed for the report property key and value.

Level

error

LogMsg

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.

Message No. 6: CONFIG URL ERROR

Brief

The configuration URL has an error.

Level

error

LogMsg

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.

Message No. 7: CONFIG NOT FOUND

Brief

The configuration could not be found.

Level

error

LogMsg

Configuration not found: <Reason>

Arguments

Reason: Reason of the error.

Description

The MyARM configuration property file could not be found.

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

LogMsg

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.

Message No. 9: EVENTLOG CREATE FAILED

Brief

The creation of the MyARM event log channel under Windows failed.

Level

error

LogMsg

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.

Message No. 10: DYNAMIC OBJECT FAILED

Brief

A dynamic object (e.g. datasink or datasource) could not be loaded.

Level

error

LogMsg

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.

Message No. 11: OUT OF MEMORY

Brief

During an operation not enough memory could be allocated to finish the operation.

Level

error

LogMsg

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.

Message No. 12: API ERROR

Brief

Reports an API error of the C, Java or CSharp API bindings.

Level

error

LogMsg

< 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.

Message No. 13: API WARNING

Brief

Reports an API warning of the C, Java or CSharp API bindings.

Level

warning

LogMsg

< 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.

Message No. 14: ERROR

Level

error

LogMsg

< Message>

Arguments

Message: Error message.

Description

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

Message No. 15: CANNOT OPEN FILE

Level

error

LogMsg

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.

Message No. 16: ARM DATA DROPPED

Brief

Log message which reports dropped ARM data.

Level

error

LogMsg

Could not process ARM data (Defs=<Defs>, Apps=<Apps>, Trans=<Trans>) <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.
reason: Description of the reason.

Description

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

Action

To resolve this problem there exists the following options:

Solve the problem why the datasink is not available (database, network)
Increase the size of the temporary ARM data file using the MyARM property basic.sink.thread.tmpfile.size

Message No. 17: ARM DATA DROPPED TOTAL

Brief

Log message which reports the total number of dropped ARM data.

Level

error

LogMsg

Total number of dropped ARM data: Defs=<Defs>, Apps=<Apps>, Trans=<Trans>).

Arguments

Defs: Number of definitions dropped (application-, transaction- or metric-definition)
Apps: Number of application instances dropped.
Trans: Number of transaction instances dropped.

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). This log message reports the sum of all dropped ARM data.

Message No. 18: NO LICENSE

Level

error

LogMsg

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.

Message No. 19: ARM TRAN CALLS STAT

Level

info

LogMsg

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).