SolarWinds Observability-Self-Hosted-Fundamentals Exam Dumps

Custom Properties are one of the most versatile features of the SolarWinds Platform, providing a way to extend the metadata associated with monitored objects. The SolarWinds Platform Administrator Guide defines them as 'user-defined fields that allow you to add custom information to nodes, interfaces, volumes, or other monitored entities'.

Unlike built-in attributes like 'IP Address' or 'Vendor,' which are discovered automatically, custom properties are created by the administrator to suit specific business needs. Common examples include 'Site Location,' 'Emergency Contact,' 'Department,' or 'Service Level Agreement (SLA) Tier'. These fields are critical for organization and automation because they allow for:

Filtering and Grouping: You can create groups that automatically include any node where the 'Department' custom property is set to 'Finance'.

Alerting: You can configure alerts to only trigger for nodes marked as 'Mission Critical' in a custom property field.

Reporting: Reports can be generated to show the uptime of all nodes belonging to a specific 'Owner' or 'Cost Center'.

Because they are user-defined, they provide the necessary flexibility to map technical monitoring data to real-world business structures.

In the SolarWinds Platform, data visibility is controlled at the account level through a security feature known as Account Limitations. According to the SolarWinds Platform User Account Management documentation, when a single user has restricted visibility while others do not, it points to a specific Account Limitation applied to that user's profile.

Account limitations act as a persistent filter on the database queries performed by the Web Console during that user's session. If an administrator has configured a limitation based on a custom property like 'Location' or 'Region,' the user will only see entities that match that specific criteria. For example, if the user's account is limited to Location = New York, they will be unable to see nodes, alerts, or reports associated with Location = London, even if those nodes are active and being monitored by the system.

This is a fundamental tool for multi-tenant environments or large enterprises where different teams are responsible for different geographic or logical segments of the network. It is more effective than 'View Limitations' (Option D) because an account limitation follows the user across the entire platform, including search results, alerts, and reports, whereas a view limitation only affects a specific dashboard page. Options B and C are unlikely because they would typically affect multiple users or indicate a major monitoring gap rather than a user-specific visibility issue.

SolarWinds Hybrid Cloud Observability provides robust reporting capabilities designed for both technical analysis and executive presentation. The SolarWinds Platform Reporting Guide specifies that reports generated through the Web Console can be delivered or manually exported in several standardized formats.

Excel (.xls/.xlsx): This format is primarily used for data-heavy reports where administrators need to perform further calculations, sorting, or external data manipulation. It allows the raw table data from the report to be easily ingested into other business intelligence tools.

PDF: This is the standard format for automated delivery and 'executive-ready' documentation. It preserves the visual layout, including charts, logos, and specific formatting defined in the report builder.

While the platform uses JSON (Option B) for internal API communications and some dashboard configurations, and txt (Option D) might be used for certain log exports, they are not standard selectable 'export formats' within the primary Web-Based Report builder for end-user consumption. The primary focus of the reporting engine is providing human-readable (PDF) and spreadsheet-compatible (Excel) outputs.

Visibility of the reporting module is a configurable security setting within each SolarWinds user account. According to the SolarWinds Platform User Account Management guide, if a user logs into the Web Console and finds the Reports section empty or inaccessible, it is likely due to an Account Limitation.

Specifically, the 'Report Limitation' field in the user's profile can be set to 'No Reports'. This setting acts as a total block, preventing the user from viewing any report definitions, whether they are predefined (out-of-the-box) or custom-made. This is a common configuration for restricted user roles, such as basic operators or external contractors, who need to see real-time status in dashboards but should not have access to the historical, inventory, or security data contained in the platform's reporting engine. While a user could also be restricted from seeing specific entities (Option B), this would typically just result in empty data inside a report rather than the total inability to view the reports module itself. Setting the account to 'No Reports' ensures the user is prevented from viewing all reports globally across the platform.

Alert escalation in the SolarWinds Platform allows for a tiered response to critical issues (e.g., emailing a technician immediately, then emailing a manager if the issue persists for 30 minutes). According to the SolarWinds HCO Alerting Engine documentation, the primary mechanism for a human operator to pause this automated progression is acknowledgement.

When an active alert is acknowledged via the Web Console, several things happen:

The alert is moved to the 'Acknowledged' category, signaling to other team members that the issue is being addressed.

The 'Acknowledge' timestamp and the user's name are recorded.

The escalation chain is halted. Any further actions defined in the 'Escalation' tab of the alert configuration---which were scheduled to fire after a certain duration---are cancelled.

It is important to note that acknowledging an alert does not clear the alert or stop the 'Reset Conditions' from being monitored. If the node stays down, the alert remains active, but no further new escalation emails will be sent. The alert will only truly disappear once the environment returns to a healthy state and the reset conditions are met.