Great, thanks for the update. Documentation is now updated.

Just to note - PollerTrace line is optional - it just produces debug output when configuration poll is executed manually.

It's just display issue, should get fixed in next patch release

Thanks for the info

It's a bug introduced in 4.2. It affects syslog and windows event log processing in fields "source" and "tag". Bug is fixed, will be in next patch release.  Meanwhile you can put * character in syslog tag field, it should work that way.

Ups, i missed that line Yes, it's correct

Last line return $1; is there so transformation script returns DCI's value. Currently your DCI return "true" all the time.

@filipp-sudanov said in Windows event parser stopped working: Meanwhile you can put * character in source, it should work that way. Yes, it did work. Thank you.

Yes, there is some encoding issue (also with µ). Should be fixed in next patch release.

And it works like a charm.  Thank you for solving this so quickly!

I've updated Juniper driver to use this MIB if available. Changes will be included into next patch release. Best regards, Victor

This did the trick, thank you! Great support as always. Will also look into this background mode as well.

Ah, ok.  Thank you very much!

Yes, we are moving toward term "metric" in the UI (and also in NXSL at some point)

Yes, normally previous functions should have remained as deprecated for some time, but this time it did not happen. We've updated documentation on the current situation.

MIB file as such will not add VLAN information, we have to make changes to device driver so it read non-standard MIB. If you can provide SNMP access to test device we can implement necessary changes in D-Link driver for reading VLAN information. Best regards, Victor

Right thanks, forgot netxms db is very human eye friendly, used to obfuscated dbs with guids everywhere

@jbriseno said in Telegram channel Issue: Hi, Filipp. First I appreciate a lot your time to help me to fix my Telegram channel issue. Second, today, I found the technical reason for that Telegram channel configuration change its status in unxpected way. Because, I added an event with the Telegram bot in the Actions Configuration menu. I updated it. Then my problem is solved. Finally, according with my participation in other Open Source Projects, NetXMS project offers to its members an excellent support. Kudos. Problem solved Thanks my best Jose I have this issue too. What did you change in the actions configuration to fix this?

Thanks a lot I can confirm this is working. In agent config add: ExternalCommandTimeout = 30000 Timeout is in milliseconds..

this was exactly it. thank you. so much!