SolarWinds SCP-NPM Exam With Confidence Using Practice Dumps

 By default, Orion NPM retains Syslog messages in the database for seven days before discarding them. This means that any Syslog messages older than seven days are deleted from the database and cannot be viewed or searched in the web console. To change the default Syslog retention period, you need to modify the Database Settings on the Orion Polling Settings page in the web console. You can also use the Database Manager tool to manually delete or archive Syslog messages from the database. References: SolarWinds SCP Study Aid - NPM, page 19; NPM Administrator Guide, page 111.

An alert limitation is a filter that restricts the scope of an alert to a specific set of objects, such as nodes, interfaces, applications, or groups. You can use an alert limitation to create an alert that only applies to a select set of nodes in your network, and exclude the rest. To set an alert limitation for the nodes to be included in the alert, follow these steps1:

• Click Alerts & Activity > Alerts > Manage Alerts.
• Find the alert that you want to edit or create a new alert.
• On the Trigger Condition tab, define the condition that triggers the alert, such as Percent Loss is greater than or equal to 50.
• On the Scope of Alert tab, select Limit the scope of this alert to a specific subset of objects.
• Choose the method to define the subset of objects, such as Select objects manually, Use a custom SWQL query, or Use a custom SQL query.
• Select or enter the criteria to filter the objects, such as the node name, IP address, group, custom property, or any other attribute.
• Click Add Selected Objects to add the objects to the alert limitation.
• Click Next and complete the rest of the alert configuration.

You can now save and enable the alert, and it will only notify you when packet loss meets or exceeds 50% for the nodes that you have selected in the alert limitation. References: 1: Limit the objects an alert applies to

Response time is the amount of time it takes for a service request to return a response. It is a critical SLA performance metric for a hosted data center service, as it directly affects the user experience and satisfaction. High response time can indicate network congestion, server overload, or other performance issues that can degrade the quality of the service. By tracking response time, you can monitor the availability and reliability of the service, identify and troubleshoot potential problems, and ensure that the service meets the SLA expectations and standards. References: How to measure your SLA: 5 Metrics you should be Monitoring and Reporting, Data Center SLA Frequently Offer a 100% Uptime Guarantee, How To Measure SLA Performance in 4 Steps (With Tips).