Skip to content

Monitor Attributes

Monitor Attributes is tag strategy to append short term to describe Monitor Tools with more details. In daily deployment, we need to understand the plugin logic details to decrease false alerts. In the process of troubleshooting, we should understand the plugin dependencies to fastly locate root cause. So we put forward such solution to represent plugin deeply.

All attributes are split to core parts. The first one is general level describing common characteristics, e.g., operation system in deployed station. The second part is business level describing specific logic in Webex, e.g., Webex group and monitor tool dependencies.

Attribute List

General Level

Operating System

Operating System represents station where monitor tool are deployed.

  • os:windows2016
  • os:windows2019
  • os:centos76
  • os:alma8

Develop Language

  • language:golang
  • language:java
  • language:cpp
  • language:python
  • language:shell
  • language:javascript

Network Protocol

  • protocol:http(s)
  • protocol:sip
  • protocol:tcp
  • protocol:udp
  • protocol:icmp

Business Level

App Group

  • app_group:mas - description: mas is short term of Monitoring and Status service.

Applications

  • application:mct
  • application:eureka
  • application:mmp
  • application:nbr

Server Type

  • server_type:top_collaboration_bridge - description: more details about Top CB Server
  • server_type:sub_meetig_zone_management - description: more details about Sub MZM Server
  • server_type:email_server

MCT Setting

  • mct_setting:conference_id - description: conference id setting item is split conference id range and assign to different MCT Agent Groups to ensure that conference id in each monitor test case is unique. In some cases, conference id reuse always causes target server starting meeting failure. MCT Conference Id Group in Production
  • mct_setting:url_template - description: url template setting item is a collection of urls which could be rendering with specific http protocols, ip and port, and then monitor tools access rendered url. MCT URL Template in Production

Middleware Dependency

  • middleware_dependency:j2ee - description: J2EE play a role of provider of meeting security key for MCT. MCT server alway builds two connection to fetching key with J2EE. Firstly MCT stations runs as a server and then access J2EE URL with MCT server information, e.g. ip and port. Eventually J2EE accesses MCT server to send key.
  • middleware_dependency:tahoe_server_vip - description: Tahoe Server, shortly ts, is a server as a role of start telephony meeting. Lots of test cases in MCT are based on telephony meeting, so monitor tools have to start a such meeting as test preparation.
  • middleware_dependency:eureka_sdk - description: eureka sdk is a tool of simulating Webex Client supporting meeting processes, e,g, start meeting, join meeting and terminate meeting. Eureka sdk details
  • middleware_dependency:telephony_sdk - description: telephony sdk is a tool of simulating client to start and terminate telephony meeting.