Comments
-
looks very promising. Can someone please tell when is tentative release date for 2022.3 ? I see the RC but when will be the Go-live for it
-
You need to do 3 things: 1. create an application monitor (or template) and add all the application services and components into it. 2. Create alert rule for SAM component down (service down or service NOT equals UP) 3. Create alert rule for Application monitor down (this will give more coverage)
-
Use custom table, and select object as "application or component" It all depends on what fields you select during the report columns. It will be directly available
-
We are using a Query for SNMP/WMI failure on nodes which i created as an Alert rule as well as a Report and scheduled to owners to fix them. Let me know if you are still looking for it, ll share
-
One more scenario, IF the alert condition is changed or sometimes IF the object is modified once alert is triggered, the alert will NOT auto clear. (like lets say you changed IP or custom property, often since alert is already triggered, now object is changed- it will not reset, and consider the object as a new one).
-
Go to Manage windows credentials, update the new password there. It will handle everything.
-
we now have 2024.2.1
-
Had the exact same error. When we do changes to DB's its better to elevate access to DBOAdmin role and run the config. wizard. It will avoid this error. and then it can be reduced to standard user
-
simpler way to reduce your burden to check manually is to run a discovery of the IPs, & schedule it weekly/monthly/etc, the job will take care of adding any/all new drives that were not selected in past. You would also need to use a query to check WMI failures separately, so you need to fix those first & wait for next…
-
Exact feeling. I support 7 different global clients - unique Customer ID. Mostly i try to fix myself, but when i raise a ticket, i regret until its resolved. (mostly by the hint or directive i figured out during the process)
-
Had exact same issue. Only fix i felt most practical without Overkill of efforts is to "Split down the NCM jobs into smaller groups, based on region or device type or custom prop.etc & have few NCM jobs running. Each of its start time with at least 30min gap. it will surely avoid the bottle neck and hung. It worked for us.
-
ANSWER: The Screenshot KMSigma gave in reply here is different from your screenshot. In show variables, try Hardware Sensor(Node) , not Hardware Category".. It will work. these parameters also depends on Source (I want alert on) in your trigger condition "Trigger condition" page. Use Node, but select the hardware sensor…
-
We had run into frequent issues with the database in AWS due to a lot of RWs. Be aware of the DB server to be on a good hardware and spend a better plan on databases to avoid outages.
-
3 options.Go to manage nodes page>> click on "Maintenance Mode". 1.Either Unmanage them to save Polling load. 2. Or use Mute alerts option- so status will be recorded but alerts wont be seen. 3. If you have hugelist of Nodes, use network discovery, add everything. Later you can go to "Manages nodes">>Group by Vendor- We…
-
You can use "Import custom property values" option in manage nodes page. it will ask you to upload a simple excel. Get your data sorted properly in excel, import it, It will automatically map the columns & ask you to match with respective custom property.
-
Use the trigger condition as below, it worksperfectly: ( i want alert on "custom node pollert", condition- Unique name = pansessionactive, & value> Your threshold. (Please mark as helpful if this works, so that everyone can know)
