<![CDATA[Use logwatch parameter in data collection]]>Hello,

I have configured logwatch to parse the content of my windows server application event log.
I can now collect over DCI Number of records processed and Number of records matched.
And i can fire an alarm over my event policy rule where i can see the parsed parameter content (it is a float value).
Is it possible to configure a DCI that will collect this value?

Thanks for any help.

Regards

Transform.png

Situation.png

EventProcessing.png

EventLog.png

]]>https://forum.netxms.org/topic/3170/use-logwatch-parameter-in-data-collectionRSS for NodeFri, 13 Nov 2026 11:18:11 GMTFri, 23 May 2014 10:07:17 GMT60<![CDATA[Reply to Use logwatch parameter in data collection on Sat, 24 May 2014 17:28:48 GMT]]>Hello Victor,

return real(res)

Doesn't work also.

Have you any other suggestions.

Thanks and Regards

José

]]>https://forum.netxms.org/post/13980https://forum.netxms.org/post/13980Sat, 24 May 2014 17:28:48 GMT<![CDATA[Reply to Use logwatch parameter in data collection on Sat, 24 May 2014 17:04:28 GMT]]>Hi!

Actually that means that server did not recognize string value as floating point number. You can try to set data type to float and use explicit cast with real(), like

return real(res)

It is also possible that your locale expects floating point numbers to have , instead of .

Best regards,
Victor

]]>https://forum.netxms.org/post/13976https://forum.netxms.org/post/13976Sat, 24 May 2014 17:04:28 GMT<![CDATA[Reply to Use logwatch parameter in data collection on Sat, 24 May 2014 16:39:23 GMT]]>Yesss it shows....
I was thinking it recognize the datatype itself.
Can i make a strong type convert in transformation script?

Thanks again.

Regards

José

]]>https://forum.netxms.org/post/13974https://forum.netxms.org/post/13974Sat, 24 May 2014 16:39:23 GMT<![CDATA[Reply to Use logwatch parameter in data collection on Sat, 24 May 2014 16:34:05 GMT]]>Hi!

Try to change DCI data type to string - will it show correct history then?

Best regards,
Victor

]]>https://forum.netxms.org/post/13973https://forum.netxms.org/post/13973Sat, 24 May 2014 16:34:05 GMT<![CDATA[Reply to Use logwatch parameter in data collection on Sat, 24 May 2014 15:10:27 GMT]]>Hello Victor,

It seems i have still something going wrong.
My DCI History is still 0.0.

I have the Event that works well an reads the Application Event Log.
To check it i have an action that writes the value as an Event in Netxms and the values are correct.
I have also the action that updates the situation, an the value is also updated correctly.
If i test my transformation in the DCI it shows also the right value, so it can access the situation correctly.
But the DCI itselfs stores all the time 0.0.

Is this a Bug or are i missing something?

Thanks for your feedback.

Regards

José

]]>https://forum.netxms.org/post/13972https://forum.netxms.org/post/13972Sat, 24 May 2014 15:10:27 GMT<![CDATA[Reply to Use logwatch parameter in data collection on Sat, 24 May 2014 06:46:57 GMT]]>Create Victor

Thanks it works.

]]>https://forum.netxms.org/post/13970https://forum.netxms.org/post/13970Sat, 24 May 2014 06:46:57 GMT<![CDATA[Reply to Use logwatch parameter in data collection on Fri, 23 May 2014 15:52:41 GMT]]>Hi!

Yes, it's possible. You can create "situation" object and in event processing policy set situation's attribute. Then you can create DCI with source "Internal" and parameter "Dummy" and in transformation script read value from situation's attribute. Sample script to access situation can be found here: https://www.netxms.org/documentation/adminguide/event-processing.html#situations.

Best regards,
Victor

]]>https://forum.netxms.org/post/13966https://forum.netxms.org/post/13966Fri, 23 May 2014 15:52:41 GMT