new Cisco Webex plugin

[rmorandell-pgum]

Community contributors

Description

The new plugin allows you to monitor Cisco Webex Workspace and devices via the Webex REST API.

The plugin requires a client ID, a client secret, and a refresh token. The token is then generated automatically and stored in a state file for 14 days before being renewed with the refresh token.
Since the Cisco Webex API has a limit on the number of calls, the devices can be stored in a cache file so that all devices can be retrieved with a single call (paging).
Unfortunately, the cache does not work for workspace metrics, as these can only be queried per individual WorkspaceID.
However, the Workspace Health mode includes an --add-metrics option. The metrics are only queried if the option is set

modes:

• cache
• device-status
• discovery
• list-devices
• workspace-health

custom mode => REST Api

Type of change

• Patch fixing an issue (non-breaking change)
• New functionality (non-breaking change)
• Functionality enhancement or optimization (non-breaking change)
• Breaking change (patch or feature) that might cause side effects breaking part of the Software

How this pull request can be tested ?

Here are all the requests with curl examples and response examples

requests.txt

Checklist

• I have followed the coding style guidelines provided by Centreon
• I have commented my code, especially hard-to-understand areas of the PR.
• I have rebased my development branch on the base branch (develop).
• I have provide data or shown output displaying the result of this code in the plugin area concerned.

---

Centreon team (internal PR)

Description

PLEASE MAKE SURE THAT THE BRANCH PR INCLUDES JIRA TICKET ID

Please include a short resume of the changes and what is the purpose of this pull request.
Any relevant information should be added to help reviewers to understand what are the stakes
of the pull request.

Fixes # (issue)
If you are fixing a github Issue already existing, mention it here.
If you are fixing one or more JIRA ticket, mention it here too.

Type of change

• Patch fixing an issue (non-breaking change)
• New functionality (non-breaking change)
• Functionality enhancement or optimization (non-breaking change)
• Breaking change (patch or feature) that might cause side effects breaking part of the Software

How this pull request can be tested ?

Please describe the procedure to verify that the goal of the PR is matched.
Provide clear instructions so that it can be correctly tested.
Mention the automated tests included in this FOR (what they test like mode/option combinations).

Checklist

• I have followed the coding style guidelines provided by Centreon
• I have commented my code, especially hard-to-understand areas of the PR.
• I have rebased my development branch on the base branch (develop).
• In case of a new plugin, I have created the new packaging directory accordingly.
• I have implemented automated tests related to my commits.
  • Data used for automated tests are anonymized.
• I have reviewed all the help messages in all the .pm files I have modified.
  • All sentences begin with a capital letter.
  • All sentences end with a period.
  • I am able to understand all the help messages, if not, exchange with the PO or TW to rewrite them.
• After having created the PR, I will make sure that all the tests provided in this PR have run and passed.

Summary by Aikido

Security Issues: 0	Quality Issues: 0	Resolved Issues: 0

🚀 New Features

• Introduced a new Cisco Webex monitoring plugin and modes.
• Added custom API module that managed tokens and HTTP requests.

⚡ Enhancements

• Implemented cache mode and optional cache usage to reduce calls.
• Added workspace health metrics collection with aggregation and add-metrics option.
• Provided device listing, discovery, and status modes with validations.

^{More info}