tFlowMeter result not writing to log file

[LFR1665328374]

Hi all,

I have an issue with a job containing a tFlowMeter. The component does not write the volume in my log file. The file is empty. ("meter_file.log")

This behavior is only seen on the production environment. It is working fine on my personal laptop (dev) and the pre-production environmment.

An idea ?

Thanks for your feedback.

An extract from my job

The log configuration for my job

The tFlowMeter configuration

[Anonymous]

Hello,

As the tFlowMeterCatcher component catches the processing volumetric from the tFlowMeter component and passes them onto the output component, actually tFlowMeterCatcher will count the no. of records pass by the specify flow.

You did add tFlowMeterCatcher -> tDbOutput( log file) components in the workflow or check out the option "Use volumetrics(tFlowMeterCatcher)"?

Best regards

Sabrina

[LFR1665328374]

Hello Sabrina,

Thanks for your feedback.

I checkout the option "Use volumetrics" option from Stats & logs Job 's tab.

Laurent

[Anonymous]

Hello,

Is the result not writing to log file even checkout the option "Use volumetrics" option from Stats & logs Job 's tab?

Could you please take a try to add tFlowMeterCatcher ->tlogrow component in the workflow to see if this result can be printed on console?

Best regards

Sabrina

[Anonymous]

Hi

What is the OS type of dev machine and prod machine? I see you use the context variable in the directory path field.

Do you change the value of context.log_base_dir when the job is executed on prod macine?

Regards

Shong

[LFR1665328374]

Hello,

Thanks Sabrina and Shong.

OS on my laptop is Ubuntu and Debian for the production.

The context.log_base_dir is correct and it is the same path on each environment.

I have 15 jobs with the same configuration without issue.

Only 1 job is concerned, the job can create the meter file but it is always empty. No problem for stats file located in the same directory.

OS permissions are correct.

I'm going to test the tFlowMeterCatcher proposed by Sabrina.

I'm going also to test to delete the tFlowMeter and checkout the "monitor this connection" in advanced settings from the link.

Laurent