Publish additional events

[zbud-msft]

Why I did it

Add event_publish code or regex for rsyslog plugin for additional events

How I did it

How to verify it

Which release branch to backport (provide reason below if selected)

• 201811
• 201911
• 202006
• 202012
• 202106
• 202111
• 202205

Description for the changelog

Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

[lgtm-com]

This pull request introduces 1 alert when merging 1c69b25 into 2626573 - view on LGTM.com

new alerts:

• 1 for Unreachable code

[qiluo-msft]

del

__del__ is hacky. Suggest follow https://stackoverflow.com/a/6104568/2514803 for unmanaged resource. #Closed

[zbud-msft]

No longer use del, moved deinit to the end of check() method which is the main driver of the script, used by manager.py

[zbud-msft]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[dgsudharsan]

@zbud-msft I am getting the following traceback. Can you please investigate?

Program 'container_memory_telemetry'
status Status ok
monitoring status Monitored
monitoring mode active
on reboot start
last exit value 1
last output Traceback (most recent call last):
File "/usr/bin/memory_checker", line 173, in
main()
File "/usr/bin/memory_checker", line 165, in main
check_memory_usage(events_handle, args.container_name, args.threshold_value)
File "/usr/bin/memory_checker", line 103, in check_memory_usage
publish_events(events_handle, container_name, mem_usage_bytes, threshold_value)
File "/usr/bin/memory_checker", line 64, in publish_events
params["mem_usage"] = mem_usage_bytes
File "/usr/lib/python3/dist-packages/swsscommon/swsscommon.py", line 419, in setitem
return swsscommon.FieldValueMap___setitem_(self, *args)
TypeError: Wrong number or type of arguments for overloaded function 'FieldValueMap___setitem__'.
Possible C/C++ prototype[telemetry]: Memory usage (864131481.6 Bytes) is larger than the threshold (4
19430400 Bytes)!
data collected Tue, 22 Nov 2022 02:44:14

Here is a full trace
/usr/bin/memory_checker telemetry 400000
[telemetry]: Memory usage (760951603.2 Bytes) is larger than the threshold (400000 Bytes)!
Traceback (most recent call last):
File "/usr/bin/memory_checker", line 173, in
main()
File "/usr/bin/memory_checker", line 165, in main
check_memory_usage(events_handle, args.container_name, args.threshold_value)
File "/usr/bin/memory_checker", line 103, in check_memory_usage
publish_events(events_handle, container_name, mem_usage_bytes, threshold_value)
File "/usr/bin/memory_checker", line 64, in publish_events
params["mem_usage"] = mem_usage_bytes
File "/usr/lib/python3/dist-packages/swsscommon/swsscommon.py", line 419, in setitem
return swsscommon.FieldValueMap___setitem_(self, *args)
TypeError: Wrong number or type of arguments for overloaded function 'FieldValueMap___setitem__'.
Possible C/C++ prototypes are:
std::map< std::string,std::string >::setitem(std::map< std::string,std::string >::key_type const &)
std::map< std::string,std::string >::setitem(std::map< std::string,std::string >::key_type const &,std::map< std::string,std::string >::mapped_type const &)

[zbud-msft]

@zbud-msft I am getting the following traceback. Can you please investigate?

Program 'container_memory_telemetry' status Status ok monitoring status Monitored monitoring mode active on reboot start last exit value 1 last output Traceback (most recent call last): File "/usr/bin/memory_checker", line 173, in main() File "/usr/bin/memory_checker", line 165, in main check_memory_usage(events_handle, args.container_name, args.threshold_value) File "/usr/bin/memory_checker", line 103, in check_memory_usage publish_events(events_handle, container_name, mem_usage_bytes, threshold_value) File "/usr/bin/memory_checker", line 64, in publish_events params["mem_usage"] = mem_usage_bytes File "/usr/lib/python3/dist-packages/swsscommon/swsscommon.py", line 419, in setitem return swsscommon.FieldValueMap___setitem_(self, *args) TypeError: Wrong number or type of arguments for overloaded function 'FieldValueMap___setitem__'. Possible C/C++ prototype[telemetry]: Memory usage (864131481.6 Bytes) is larger than the threshold (4 19430400 Bytes)! data collected Tue, 22 Nov 2022 02:44:14

Here is a full trace /usr/bin/memory_checker telemetry 400000 [telemetry]: Memory usage (760951603.2 Bytes) is larger than the threshold (400000 Bytes)! Traceback (most recent call last): File "/usr/bin/memory_checker", line 173, in main() File "/usr/bin/memory_checker", line 165, in main check_memory_usage(events_handle, args.container_name, args.threshold_value) File "/usr/bin/memory_checker", line 103, in check_memory_usage publish_events(events_handle, container_name, mem_usage_bytes, threshold_value) File "/usr/bin/memory_checker", line 64, in publish_events params["mem_usage"] = mem_usage_bytes File "/usr/lib/python3/dist-packages/swsscommon/swsscommon.py", line 419, in setitem return swsscommon.FieldValueMap___setitem_(self, *args) TypeError: Wrong number or type of arguments for overloaded function 'FieldValueMap___setitem__'. Possible C/C++ prototypes are: std::map< std::string,std::string >::setitem(std::map< std::string,std::string >::key_type const &) std::map< std::string,std::string >::setitem(std::map< std::string,std::string >::key_type const &,std::map< std::string,std::string >::mapped_type const &)

Fixed as part of #12797