Alert suppression rules

Manage Coralogix alert suppression rules directly from your AI agent. The Model Context Protocol (MCP) server provides a unified tool to create, retrieve, update, and delete suppression rules, and to generate infrastructure-as-code definitions from suppression rule configurations.

Tool

Use manage_alerts_scheduler for all alert suppression rule operations.

Action value	Description
create	Create a new suppression rule.
get	Retrieve a specific suppression rule by ID.
list	List suppression rules with an optional case-insensitive name filter.
update	Update an existing suppression rule. The agent retrieves the current configuration first, then applies your changes.
delete	Delete a suppression rule by ID.
generate_openapi	Generate the OpenAPI JSON payload for use with the Coralogix REST API.
generate_kubernetes	Generate a Kubernetes Operator YAML manifest for the Coralogix Operator.
generate_terraform	Generate Terraform configuration for the Coralogix Terraform Provider.

Supported scheduling

The tool supports single-use schedules, recurring always-active schedules, and recurring dynamic daily, weekly, and monthly schedules. Suppression rule filters must use exactly 1 alert selector: alert IDs or meta labels.

Example prompts

List suppression rules

List Coralogix alert suppression rules whose name contains "maintenance".

Create a temporary mute

Create an enabled alert suppression rule named weekend-maintenance.
Filter alerts by meta label env=production and use whatExpression
"source logs | filter true". Mute alerts from 2026-06-06T01:00:00Z
to 2026-06-06T03:00:00Z.

Generate Terraform configuration

Generate Terraform configuration for an enabled alert suppression rule named
daily-maintenance-preview. Filter alerts by meta label env=staging,
use operation mute, and repeat every day for a 2-hour dynamic time frame.
Do not create it.

Generate Kubernetes YAML output

Generate Kubernetes Operator YAML for an alert suppression rule that filters
alert ID 1234567890abcdef with whatExpression "source logs | filter true".
Do not create or apply it.

Important behaviors

• All-alert filters are not supported. Use either alert IDs or meta labels.
• Use 1 filter type. The tool rejects requests that mix alert IDs and meta labels.
• Update requires retrieval first. Retrieve the current suppression rule, modify it, then update with the complete suppression rule definition.
• Alert ID filters in Kubernetes output use placeholder alert resource references. Review the generated manifest before applying it.