Comments
-
Thanks for your reply
-
This was very helpful. When you create the rules is there a way to set the severity of the rule you are creating?
-
it can be view limited using the "where" clause in the report so what do you set your limitations by I.E location, device type?
-
what restricted view issue are you dealing with?
-
SELECT ---Nodes.Site AS Site, Nodes.Caption AS ServerName, --nodes.DeviceRole As DeviceRole, Nodes.Vendor AS Vendor, Nodes.MachineType AS OSModel, --Nodes.Description AS Hardware, --Nodes.IOSVersion AS OSVersion, --Nodes.CPULoad AS CPUUtil, --Nodes.PercentMemoryUsed AS PercentMemory, --Nodes.TotalMemory AS TotalMemory,…
-
SELECT ---Nodes.Site AS Site, Nodes.Caption AS ServerName, nodes.DeviceRole As DeviceRole, Nodes.Vendor AS Vendor, Nodes.MachineType AS OSModel, --Nodes.Description AS Hardware, --Nodes.IOSVersion AS OSVersion, --Nodes.CPULoad AS CPUUtil, --Nodes.PercentMemoryUsed AS PercentMemory, --Nodes.TotalMemory AS TotalMemory,…
-
Typically what I do to group the volumes is to use a pivot table in Excel.
-
check the vcenter node and make sure it is polling correctly.
-
you have yours to trigger when the application status is up. you have to change it to "is not equal to" and that should fix it.
-
So you have no fail over to bring up Orion up in a critical failure?
-
Yes, that is exactly what I am trying to do. The problem is that the network discovery put to much load on the network. I only manage a very specific amount of nodes. Is it possible to make the network discovery only run on my specific nodes using their DeviceRole?
-
how would you like it grouped? I can help. Also if this is done you can mark it as completed.
-
then you will have to change the alert trigger from "down" to not found.
-
I Fixed it
-
yeah. it will help. some times it has a bit more information the screen you can black out what ever is critical to your environment.
-
I posted a little bit of the code. I will take a little bit to add everything you need.
-
Opps I dont think you DeviceRole try this also are you using SQL Studio? select --VM.Name, --VM.PowerState as PowerState, node.Caption, node.MachineType, Hardware.AgentVersion, hardware.Manufacturer, hardware.Model, procs.NumberOfCores, --procs.NumberOfThreads, procs.Manufacturer, procs.Name, procs.Stepping, procs.Caption,…
-
npm ncm nta qoe ivim vnqm
-
Would I would like is to have a report that shows the down applications and shows what part of the application is down. That way I can send the report to the sys admins and they can fix the issues
-
Do you know what the function would be to create the report from within the Orion Report Writer?
-
Bump
-
Also where are you showing the departments of your nodes?
-
Select Nodez.Caption as Servername, Nodez.DeviceRole as DeviceRole, IPAddr.IPAddress as 'IP Addresses' FROM dbo.Nodes AS Nodez join dbo.NodeIPAddresses as IPAddr on Nodez.NodeID = IPAddr.NodeID
-
bump
-
This is not mine I grabbed it along time and do not know who it came from. But this will give you the physical / virtual information you are looking for
-
Thanks I will try to publish more information on HP servers in Orion.
-
select nodez.NodeID as id, Nodez.Caption as Servername, HDD.CapacityB as HDDsize, hdd.Model, hdd2.VolumeName, hdd2.CapacityB, Nodez.DeviceRole as DeviceRole, IPAddr.IPAddress as 'IP Addresses' FROM dbo.Nodes AS Nodez join dbo.NodeIPAddresses as IPAddr on Nodez.NodeID = IPAddr.NodeID join dbo.AssetInventory_HardDrive as HDD…
-
set the reset condition to recommended and try the alert on only one of the servers and see if that works.