- 2 minutes to read

JMX, FAQ, Troubleshooting, Common Questions JMX, FAQ, troubleshooting, common questions 11. How do I set different heap thresholds for dev/QA vs production?

11. How do I set different heap thresholds for dev/QA vs production?

11. How do I set different heap thresholds for dev/QA vs production?

Use Monitor Views + Resource Groups for environment-specific thresholds:

Approach 1: Separate resources per environment

  • Create resource "Boomi Atom Prod-1 Heap" → Threshold Warning >85%, Error >95% (strict production monitoring)
  • Create resource "Boomi Atom Dev-1 Heap" → Threshold Warning >90%, Error >98% (relaxed dev/QA monitoring, less critical)
  • Assign to different Resource Groups: "Production JVMs", "Dev/QA JVMs"

Approach 2: Environment tagging + Monitor Views

  • Tag all resources with environment (Prod, QA, Dev)
  • Create Monitor View "Production JVM Health" → Filter by Environment=Prod → RBAC: operations team, high-priority alerts (PagerDuty)
  • Create Monitor View "Dev/QA JVM Health" → Filter by Environment!=Prod → RBAC: developers, low-priority alerts (email only, no pages)

Rationale for different thresholds:

  • Production: Strict thresholds (>85% Warning), proactive alerts, zero tolerance for OutOfMemoryError, 24/7 monitoring
  • Dev/QA: Relaxed thresholds (>90% Warning), less critical (dev/QA outages acceptable), reduce alert noise (devs testing heap limits intentionally)

Example: Dev team load-testing Spring Boot service, intentionally pushing heap to 95% to validate behavior under stress. Production threshold >85% would fire 20+ alerts during load test (alert fatigue). Dev/QA threshold >90% fires 3 alerts only (actionable: heap exceeded safe limit even in test).

See all FAQs: [Troubleshooting Overview][]