Case # 374095 Created: Bug found / feature request?
The Event log is not subject to "Limitations" as some of the other views in NPM are.
Example: I can create an account for one of our customers to monitor their own equipment in Orion. I can enforce limitations on their views based on their customer ID defined in our system. This limits what devices they are able to look at based on the customer ID tag associated to Nodes and Interfaces.
When I create a link for the customer to view the Event log for their Node or Interface, the default page that pops up properly displays information based on the filter defined in the link.
Example:
*** Links ***
Click Here to View Down Interface Events on this Node - Last 30 days:
/Orion/NetPerfMon/Events.aspx?NetObject=N:${NodeID}&Period=Last+30+Days&EventType=10
Click Here to View Triggered Alerts on this Node - Last 30 days:
/Orion/NetPerfMon/Events.aspx?NetObject=N:${NodeID}&Period=Last+30+Days&EventType=5000
The event log window that pops up however, has a selectable field for "Filter Devices" that does not impose the same limitation that is defined on the Account... While I can limit the customer views to Nodes and Interfaces based on the customer ID, I am unable to do this in the Event Log.
Because there is no limit defined on the Filter Devices, the customer could select ANY Node or Interface on our network using the filter drop downs. This imposes serious security and confidentiality risks to both our internal network as well as other customers defined in Orion.
Being able to properly present triggered events/alerts associated to customer equipment is a very important feature, but poses some serious business ethics issues by not enforcing the Limitations defined on the account.
The only current options we have available are to allow the customer to view the Event Log and hope that they do not snoop around the other devices in our network, or to remove the Event Log feature from being viewed by accounts with limitations imposed.
This problem could easily be corrected by development if the Event Log could be popped up with the default of "HIDE" set and the ability to remove the "HIDE" and "SHOW" buttons from being displayed on the Event Log.... Even if this change was just another SWSQL tag that was added to the URL. This would securely lock down the display by not allowing the customer account to modify the filters.
