HI @mehdi can you try: https://docs.centreon.com/docs/22.10/monitoring/passive-monitoring/create-snmp-traps-definitions/#custom-code

Regards

Hi, i open a ticket (83786) to support.

I have the same problem, every time a trap arrives with an accented character (for me: éèùçà and all the variants with ^), the trap arrives in hexa.

This is due to the behavior of snmptrap at the source. Doing a tcpdump on the destination shows that the trap is already in hex.

I have a workaround by changing the original language of the trap sender. It's not a fix but it's better than nothing.