This documentation and the Cisco Observability Platform functionalities it describes are subject to change. Data saved on the platform may disappear and APIs may change without notice.
Modules
Modules are additional features or functionalities built to enrich a standalone application. An application can support multiple modules, and compatibility is essential to ensure that multiple modules coexist without compromising the overall functionality of the application.
In the following sections, you will gain a better understanding of what modules are, how they differ from applications, and when to create them.
A Closer Look at Modules
To gain a better understanding of modules and their relationship with applications, consider the following characteristics:
- Modules contain knowledge objects, including module details, screenshots, and module category (application, database, network, etc.).
- Modules can be dependent on multiple components.
- Modules can be subscribed to by a tenant.
- An application can support multiple modules, each serving a unique purpose.
- Compatibility is critical, so multiple modules must coexist without compromising the application's overall functionality.
- One module should not interfere with another one built on the same application.
Module Types and Their Capabilities
Modules are categorized into the following three types but can be combined together.
- Data Modules
- UI Modules
- Configuration Modules
The following table describes the capabilities, the Cisco Observability Platform components used, and examples of each module type.
Module Type | Capabilities | Cisco Observability Platform Components | Module Examples |
---|---|---|---|
Data Modules |
Adds:
|
|
|
UI Modules |
Modifies:
|
|
|
Configuration Modules |
Adds:
|
|
|