Netowork Monitoring Extension Enablement(Zabbix)

kmns requirement as a dp and service delivery analyst i want to view network performance monitoring dashboards in bridge aiops, so that i can understand the health of my customer's network as a customer, i want to view network performance monitoring dashboards in bridge, so that i can understand the health of my network solution develop and deploy shared extension to pull network devices metrics from source zabbix instance for multiple customers assumptions zabbix host tags are defined zabbix item keys used are a defined for lab devices \<font color="#eef0f3"> ado feature \</font> \<font color="#eef0f3"> description \</font> \<font color="#eef0f3"> status \</font> 2476651 develop shared zabbix instance extension for performance monitoring dashboards development complete & prod deployment process in progress architecture tests performed onboarded devices on npm dashboard devices with multiple gsma code are pulled from zabbix pull network devices based on tag definition 'class\ network' extension check for zabbix instance availability & gsma code extension polling and payload from log support existing l1/l2/l3 support model appendix o\&a naming conventions create hosts groups naming convention the naming convention is mostly optional, but recommended naming host naming the name must be unique in the zabbix instance, therefore there can be conflict between different accounts it is recommended to add prefix with customer code the recommended naming for hosts is {customer code} {short hostname} example m12 eu1d63lpm1eslap1 a single agent can have multiple host names, this can be used to identify monitoring for susbsystems and instances then follow naming as {customer code} {short hostname} {subsystem name} {subsystem instance} examples m12 eu1d63lpm1eslap1 mysql production proxies and proxy groups the name of the proxy and especially proxy group should allow the account admin to clearly identify which proxy group (or proxy) should be used for which devices it should usually contain customer code and specific scope in form of location or type of devices, for which is the proxy group dedicated recommended {customer code} proxy {scope} considering that many admins may manage multiple accounts in single environment (optionally adding a number as {id}, as result {customer code} proxy {id} {scope}) host groups the host groups are used to assign access to user groups the zabbix organize groups and subgroups as “nested” groups for example, the group named “/europe/belgium” is a subgroup of group named “/europe” this is usually used to grant access to group and all its subgroups the account hosts will be assigned to a group with following naming standard accounts/{customer code} where \ customercode customer tricode the following additional separation is optional accounts/{customer code}/{type}/{group}/{environmnet} where \ type type of server belong to ('os', 'db', 'middleware', 'app', 'service', 'web', etc ) \ group group of types ('linux', 'windows', 'mysql', 'mssql', 'was', etc ) \ environment depend of customer (usual 'prod', 'dev', 'preprod', etc ) examples accounts/hmc/os/linux/prod customers/ib1/os/aix/dev template groups template group for accounts should follow below naming standard (schema) templates/{customer code} or templates {customer code}/ depending on your agreement with o\&aaas the following additional separation is optional templates/{customer code}/{type}/{group} templates {customer code}/{type}/{group} examples templates/tbe/os/linux templates/tbe/os/linux/modules templates tbe/os/aix