SNMP trap definitions are managed across multiple scopes in OpsRamp. Scopes allow you to customize trap behavior for specific environments without affecting other tenants.
Each scope can define its own version of a trap. When the same trap exists in multiple scopes, the system applies the definition based on scope precedence.
Scope levels
Trap definitions are available at the following scope levels:
- Global – Default trap definitions available to all environments
- Service Provider – Configurations applied at provider level
- Partner – Configurations for partner environments
- Client – Configurations specific to a client
Info
When the same trap (same OID) exists in multiple scopes, the system uses the definition based on the following priority:For example, if a global trap is configured with severity Critical and a client updates it to Warning, the client-level configuration is applied when the trap is received.
Inheritance
Trap definitions defined at higher scopes are inherited by lower scopes.
For example, traps defined at the Global level are available at Service Provider, Partner, and Client levels unless overridden.
Note
- Changes in lower scopes override higher scopes
- Multiple users modifying the same trap can overwrite changes
- Copying traps is required before editing global definitions
Customization
Global trap definitions are read-only and cannot be modified directly.
To customize a trap:
- Copy the trap from a higher scope (for example, Global) into your current scope
- Modify the copied trap definition as required
The copied trap becomes independent of the original definition. Changes made to it do not affect other scopes. This allows you to tailor trap behavior for specific environments while maintaining a consistent baseline.