​Hi ISAM community,

We are on ISAM 9.0.4 soon moving to 9.0.5

We have a lot of customization in our mapping rule so I need to have a little knowledge of what happening in there. But at the same time, in production, I can't afford the lag from writing utra verbose tracing.

In the mapping rules, when I use the instruction "IDMappingExtUtils.traceString("test");" is there a way to control the level of tracing that this would apply to?

I would like to do some tracing in production that I could activate very specifically.

i.e. I would want absolutely only those tracing statement that I write to be written in the prod trace file and none of the other verbose stuff that normally comes with tracing activated.

When I activate the tracing there seems to be some mechanism to limit tracing as many choices are available:
ALL, FINEST, FINER, FINE, DETAIL, CONFIG, INFO, AUDIT, WARNING, SEVERE, FATAL, OFF

But all the example that I see always use ALL and the function signature as I understand it is:
static void traceString(java.lang.String str)
so no param to indicate which level this applies to.

Many thanks,
Louis

------------------------------
Louis Beaudry
Access Management
Intact Financial Corporation
------------------------------

Hi Louis,

The log level in 'IDMappingExtUtils.traceString()' is FINER which is mainly for capturing logs for debugging purposes, in production usually the tracespec is set at INFO level, hence  'IDMappingExtUtils.traceString()' won't produce any logs in trace logs.

If you need finer control on the trace logs generated during mapping rule execution, one way is we could include another utility method in IDMappingExtUtils with following function signautre:
IDMappingExtUtils.traceString(String message, Level level); 

There's a RFE process for tracking feature requests, do you mind to submit a RFE on this?

Best Regards

Chen Yongming

------------------------------
Yongming Chen
------------------------------

Original Message:
Sent: 09-27-2018 14:44
From: Louis Beaudry
Subject: Limited tracing in mapping rules

​Hi ISAM community,

We are on ISAM 9.0.4 soon moving to 9.0.5

We have a lot of customization in our mapping rule so I need to have a little knowledge of what happening in there. But at the same time, in production, I can't afford the lag from writing utra verbose tracing.

In the mapping rules, when I use the instruction "IDMappingExtUtils.traceString("test");" is there a way to control the level of tracing that this would apply to?

I would like to do some tracing in production that I could activate very specifically.

i.e. I would want absolutely only those tracing statement that I write to be written in the prod trace file and none of the other verbose stuff that normally comes with tracing activated.

When I activate the tracing there seems to be some mechanism to limit tracing as many choices are available:
ALL, FINEST, FINER, FINE, DETAIL, CONFIG, INFO, AUDIT, WARNING, SEVERE, FATAL, OFF

But all the example that I see always use ALL and the function signature as I understand it is:
static void traceString(java.lang.String str)
so no param to indicate which level this applies to.

Many thanks,
Louis

------------------------------
Louis Beaudry
Access Management
Intact Financial Corporation
------------------------------

Hi Louis,

Looking at the JavaDoc, it doesn't look like the traceString method has any way to specify a trace level.

Unless someone else knows something I don't, the best thing I can suggest right now would be to define your own trace method (in a JS mapping rule to be "included" in other rules) which would take a level parameter and compare to a static value.

To modify the current trace value you'd edit the custom trace JS and change the static level.

Having the ability to control the trace level directly - so you can take advantage of the tracing levels in the application monitoring screens - seems like a nice idea.  Maybe open an RFE for this?

Cheers... Jon.

------------------------------
Jon Harry
Consulting IT Security Specialist
IBM
------------------------------

Original Message:
Sent: 09-27-2018 14:44
From: Louis Beaudry
Subject: Limited tracing in mapping rules

​Hi ISAM community,

We are on ISAM 9.0.4 soon moving to 9.0.5

We have a lot of customization in our mapping rule so I need to have a little knowledge of what happening in there. But at the same time, in production, I can't afford the lag from writing utra verbose tracing.

In the mapping rules, when I use the instruction "IDMappingExtUtils.traceString("test");" is there a way to control the level of tracing that this would apply to?

I would like to do some tracing in production that I could activate very specifically.

i.e. I would want absolutely only those tracing statement that I write to be written in the prod trace file and none of the other verbose stuff that normally comes with tracing activated.

When I activate the tracing there seems to be some mechanism to limit tracing as many choices are available:
ALL, FINEST, FINER, FINE, DETAIL, CONFIG, INFO, AUDIT, WARNING, SEVERE, FATAL, OFF

But all the example that I see always use ALL and the function signature as I understand it is:
static void traceString(java.lang.String str)
so no param to indicate which level this applies to.

Many thanks,
Louis

------------------------------
Louis Beaudry
Access Management
Intact Financial Corporation
------------------------------

​RFE opened:
Case ID : 125378

http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=125378


Thanks!
Louis

------------------------------
Louis Beaudry
Access Management
Intact Financial Corporation
------------------------------

Original Message:
Sent: 09-27-2018 14:44
From: Louis Beaudry
Subject: Limited tracing in mapping rules

​Hi ISAM community,

We are on ISAM 9.0.4 soon moving to 9.0.5

We have a lot of customization in our mapping rule so I need to have a little knowledge of what happening in there. But at the same time, in production, I can't afford the lag from writing utra verbose tracing.

In the mapping rules, when I use the instruction "IDMappingExtUtils.traceString("test");" is there a way to control the level of tracing that this would apply to?

I would like to do some tracing in production that I could activate very specifically.

i.e. I would want absolutely only those tracing statement that I write to be written in the prod trace file and none of the other verbose stuff that normally comes with tracing activated.

When I activate the tracing there seems to be some mechanism to limit tracing as many choices are available:
ALL, FINEST, FINER, FINE, DETAIL, CONFIG, INFO, AUDIT, WARNING, SEVERE, FATAL, OFF

But all the example that I see always use ALL and the function signature as I understand it is:
static void traceString(java.lang.String str)
so no param to indicate which level this applies to.

Many thanks,
Louis

------------------------------
Louis Beaudry
Access Management
Intact Financial Corporation
------------------------------

Submitted RFE from our end.

http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=125567

------------------------------
Vishnu Vamsi Bathula
------------------------------

Original Message:
Sent: 09-28-2018 09:37
From: Louis Beaudry
Subject: Limited tracing in mapping rules

​RFE opened:
Case ID : 125378

http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=125378


Thanks!
Louis

------------------------------
Louis Beaudry
Access Management
Intact Financial Corporation

Original Message:
Sent: 09-27-2018 14:44
From: Louis Beaudry
Subject: Limited tracing in mapping rules

​Hi ISAM community,

We are on ISAM 9.0.4 soon moving to 9.0.5

We have a lot of customization in our mapping rule so I need to have a little knowledge of what happening in there. But at the same time, in production, I can't afford the lag from writing utra verbose tracing.

In the mapping rules, when I use the instruction "IDMappingExtUtils.traceString("test");" is there a way to control the level of tracing that this would apply to?

I would like to do some tracing in production that I could activate very specifically.

i.e. I would want absolutely only those tracing statement that I write to be written in the prod trace file and none of the other verbose stuff that normally comes with tracing activated.

When I activate the tracing there seems to be some mechanism to limit tracing as many choices are available:
ALL, FINEST, FINER, FINE, DETAIL, CONFIG, INFO, AUDIT, WARNING, SEVERE, FATAL, OFF

But all the example that I see always use ALL and the function signature as I understand it is:
static void traceString(java.lang.String str)
so no param to indicate which level this applies to.

Many thanks,
Louis

------------------------------
Louis Beaudry
Access Management
Intact Financial Corporation
------------------------------

Hi Louis

Long time ago you posted this question. Would like to answer for others that search on the same subject.

1: Import logging.Level

importClass(java.util.logging.Level);

2: Add a second parameter to traceString

defining the level of logging. Eg:

IDMappingExtUtils.traceString("test", Level.INFO);

------------------------------
Kim Petersen
Specialist
ATP
------------------------------

Original Message:
Sent: Thu September 27, 2018 02:44 PM
From: Louis Beaudry
Subject: Limited tracing in mapping rules

​Hi ISAM community,

We are on ISAM 9.0.4 soon moving to 9.0.5

We have a lot of customization in our mapping rule so I need to have a little knowledge of what happening in there. But at the same time, in production, I can't afford the lag from writing utra verbose tracing.

In the mapping rules, when I use the instruction "IDMappingExtUtils.traceString("test");" is there a way to control the level of tracing that this would apply to?

I would like to do some tracing in production that I could activate very specifically.

i.e. I would want absolutely only those tracing statement that I write to be written in the prod trace file and none of the other verbose stuff that normally comes with tracing activated.

When I activate the tracing there seems to be some mechanism to limit tracing as many choices are available:
ALL, FINEST, FINER, FINE, DETAIL, CONFIG, INFO, AUDIT, WARNING, SEVERE, FATAL, OFF

But all the example that I see always use ALL and the function signature as I understand it is:
static void traceString(java.lang.String str)
so no param to indicate which level this applies to.

Many thanks,
Louis

------------------------------
Louis Beaudry
Access Management
Intact Financial Corporation
------------------------------