The Monitors tab allows users to configure Kubernetes monitoring by selecting monitors from different categories and setting how they should run. When a category is expanded, it displays its monitors, and selecting any monitor shows options such as Frequency and Other Arguments for configuration. Users can choose whether the monitors apply to all clusters or a specific cluster and then add them to the table for management using edit, delete, filter, and column customization options.

Common Kubernetes Monitor Deployment Options

When a user clicks on any monitoring group such as Kubernetes Cluster Monitors, Kubernetes Cluster Configuration Monitors, Kubernetes Node Monitors (With Agent Installation) or Kubernetes Container Monitors (With Agent Installation)

Kubernetes Cluster Monitors, the selected section expands and displays all available metrics that will be ingested under that group. Users can select it using the checkbox, and clicking on the settings icon, after which the Frequency and Other Arguments fields appear for configuration. Since all categories follow the same structure and behavior, the monitor selection and configuration process remains consistent across every monitor type.

• Frequency: The Frequency field defines how often the selected monitor collects data. The dropdown includes options such as Same as progress interval, 10 Secs, 1 Min, 10 Mins, 1 Hour, 4 Hours, and 1 Day. Users can choose an interval based on how frequently they want the monitor to run.
• Other Arguments: The Other Arguments field allows entering additional parameters required by some monitors. If the selected monitor needs extra input, it can be provided here; otherwise, this field can be left empty.

Configuration for Kubernetes Container Monitors (With Agent Installation)

• Protocol:Specifies the protocol used to communicate with the ContainerD service, typically http or https.
• ContainerD Port: Specifies the port on which the ContainerD metrics or API endpoint is exposed. This value is required to establish the connection.
• Cluster: This field allows selecting the mode in which Kubernetes monitors will be applied. The dropdown provides options to choose whether monitors should run for all clusters or only for a specific cluster, and whether the monitoring method is agent-based or agentless. Users can choose from options such as All (Agent), Specified (Agent), All (Agentless), and Specified (Agentless) depending on how the monitoring is configured in their environment.
• Specified Cluster: When the user selects any “Specified” option from the Cluster dropdown, this field becomes active and displays the list of all configured Kubernetes clusters. The user can then choose the exact cluster on which the monitors should run. If “All” is selected in the previous field, this dropdown remains disabled.

Monitors Table

• Tier-Server Information: Displays the tier and server details where the selected Kubernetes monitors will run. This helps identify which server or tier is mapped to a particular monitoring configuration.
• Monitors: Shows the name of the monitor added to the list. Each entry represents a specific Kubernetes monitor selected from the expandable categories.
• Arguments: Displays any additional parameters or arguments provided during monitor configuration. If no extra input was required, this field remains empty.
• Action: Provides options to edit, delete, or run the monitor entry from the list.
  • Edit: Allows modifying the existing monitor configuration.
  • Delete: Removes monitors that are no longer required.
  • Run: Executes the selected monitor immediately to collect data on demand.

Global Action Icons

• Delete: Allows removing one or more selected monitor entries from the table. Users must first select the checkbox next to the entries they want to delete.
• Column Filter: Allows filtering table data based on specific column values. This helps users quickly locate particular monitor entries by applying filters on fields like Tier-Server Information, Monitors, or Arguments.
• Manage Column: Allows showing or hiding selected table columns to customize the view. Users can enable only the columns they want to see in the table.