update readme after removing jobs

Author: ceelias

samples/alerts/README.md

@@ -75,21 +75,18 @@ The following elements may need to be adjusted to match your specific environmen
 
 #### 4. Alert Thresholds
 Adjust thresholds based on your environment size and requirements:
-- `cas/cas-thread-count-high.yaml`: > 400 threads
 - `cas/cas-memory-usage-high.yaml`: > 300 GB
-- `database/postgresql-connection-utilization-high.yaml`: > 85%
 - `platform/rabbitmq-ready-queue-backlog.yaml`: > 10,000 messages
 - `platform/rabbitmq-unacked-queue-backlog.yaml`: > 5,000 messages
 - `platform/viya-pod-restart-count-high.yaml`: > 20 restarts
 - `other/nfs-share-high-usage.yaml`: > 85% full
-- `platform/high-viya-api-latency.yaml`: > 1 second (95th percentile)
 - `database/crunchy-pgdata-usage-high.yaml` and `database/crunchy-backrest-repo.yaml`: > 50% full
 
 #### 5. Verify Metric Availability
 Ensure the following metrics are available in your Prometheus instance:
 - CAS metrics: `cas_thread_count`, `cas_grid_uptime_seconds_total`
 - Database metrics: `sas_db_pool_connections`, `pg_stat_activity_count`, `pg_settings_max_connections`
-- RabbitMQ metrics: `rabbitmq_queue_messages_ready`, `rabbitmq_queue_messages_unacknowledged`
+- RabbitMQ metrics: `rabbitmq_queue_messages_ready`, `rabbitmq_queue_messages_unacked`
 - Kubernetes metrics: `kube_pod_container_status_restarts_total`, `kube_pod_container_status_ready`
 - HTTP metrics: `http_server_requests_duration_seconds_bucket`
 - SAS Job Launcher: `:sas_launcher_pod_status:` (recording rule)