If you are using the "Out of the box alerts" you won't be able to. The alerts that get installed with SolarWinds cannot be modified.
If you are using a custom alert, that that one really depends on how you have your alert configured. There are a couple different approaches to accomplish this, and it all depends on how you want to manage it. Something like this should appear in the Scope section of the alert. You could duplicate the alert, then modify the scope section on the cloned alert.
Method 1: Custom Property drop down listHave a custom property for CPU alerts. Build out a drop down list with your alert options (Email, Console, etc...), basically what types of communication you send out for alerts. Once again, very contingent on company and processes. I guess at a minimum, you would do a true/false or Alert/No Alert for your options. Then in the alert scope, look for that specific option you created.
Method 2: Custom property text listHave a custom property for resource alerts, and set it up as a text box. I would then update your existing nodes with "CPU" or "CPU, Memory" depending on the alerts you want to toggle. Then clone your alert, and in the scope setup "Resource Alerts contains CPU"
Method 3: hard code the nodeI do not recommend this approach at all, and it really becomes unmanageable for larger environments. In the scope action, and an "Or" block. Then set it where Node caption or DNS name is equal to X, where X is your node name. Then repeat the Node Caption/DNS line for each node you want to alert on. This list could get really complicated really fast. So this would be more for a one off test in my opinion.
Depending on the size of your environment, Method 1 or 2 would both work really well. We use Method 1 in ours and have it as a required field. I do have a "No" option in my list for devices that the teams do not want to receive CPU based alerts on (like network equipment). It also pairs really well if you use a custom property to populate the email address for the node alerts as well. Email Alert Action: Send to Custom Property - Forum - Hybrid Cloud Observability - THWACK (solarwinds.com). This way you do not need to build custom alerts for each team.
It depends on how you have configured your alerts for CPU. There are several ways to do it based on your alert.
Use of Custom properties - if you can effectively use this then you can play around with alerting and reporting.
using out of the box alerts. can we use this method go to edit properties and override the threshold and uncheck the box for warning and critical. Is it right way?
I always avoid using the out of box alerts since you can not modify them. You could copy the alert though and make modifications to that.
Technically speaking you could set the thresholds to be high enough that they would realistically never trip, but I wouldn't recommend that route. I would setup a custom property to be able to toggle off the alert for the node.
When I look at the OOB Alert it's hard coded CPU Load is greater then 80%.
What I've done in my environment is having a Node based alert with the condition
Node - Criritcal Value Reached (CPU Load) - is equal to - Yes
When doing it this way you can use the checkmarks and overrides on the edit node page itself.
In that case you can check the override but disable the checkmarks for warnings and criticals. This will make sure that you don't have defined values for the Warning/Critical threshold and that will not trigger the alert.
Custom properties are another way, but I'd rather keep it simple within the UI with the least amount of custom properties.
