# Servers View
A server provides several options for client access to Connectware data, such as through OPC UA or RESTful interaction. Alternatively, you can access the data of the MQTT broker through the MQTT API. The data of the server resource is structured by node resources that define the available data structure.
See also: [Cybus::Server resource](https://docs.cybus.io/2-0-6/documentation/services/service-commissioning-files/resources/cybus-server)
## Overview
The **Servers View** displays all active and inactive servers. Click a server for further information about its configuration and the associated nodes.
* To open the **Servers** view, click **Services** on the navigation panel and click **Service Resources**. In the **Service Resources** view, click the **Servers** tab.
Servers View
In the list, all servers are displayed with the following information:
**Service ID**
* The unique identifier of the service that contains this server.
**Name**
* The name of the server.
**Protocol**
* The communication protocol used for the server (e.g., Modbus, HTTPS, OPC UA).
**Status**
* The current state of the server.
## Server Details View
* To open the **Server View** for a specific service, click **Services** > **Service Overview** and select a service. In the **Service Details View** of the selected service, click the **Servers** tab.
The following information is displayed:
### Server Logs
Shows the server logs of the selected server.
**Download CSV**
* Export the visible log entries as a CSV file.
{% hint style="info" %}
The log entries in the CSV file are limited to the most recent 500 lines in the current view. To download the raw logs that contain the full logs, see [Logs of All Services](https://docs.cybus.io/2-0-6/documentation/services/service-logs/service-logs-of-all-services).
{% endhint %}
**Refresh Logs**
* Refresh the log messages to show the most recent entries.
**Filter**
* Use these filters to focus on specific service log message types based on your troubleshooting or monitoring needs. You can filter for **Debug**, **Error**, **Fatal**, **Info**, **Trace**, and **Warn** messages.
**Start Time/End Time**
* Select a specific start date/time and end date/time to define the period for which you want to view log messages.
**Search**
The search allows you to filter the list.
* Minimum search length is 3 characters.
* Search services by service ID or name.
* Search resources by name, ID, protocol, parent resource ID, agent name, or service ID.
* Search is case-insensitive.
**Level**
* The type of message. For example, info or warning.
**Time**
* Shows the exact date and time when each log message was generated.
**Message**
* Displays the message of the log (e.g., **Started HTTP Server A23 on port: 8080**).
### Nodes
Shows the associated nodes of the selected server.
**Service ID**
* The unique identifier of the service that contains this server.
**Name**
* The name of the server.
**Parent**
* The parent server of the active server.
**Protocol**
* The communication protocol used for the server (e.g., Modbus, HTTPS, OPC UA).
**Operation**
* The operation of the server.
**Status**
* The current state of the server.
**Search**
* Find specific nodes by keyword. The search filters the displayed service log messages, showing only matching results.
* Minimum search length is 3 characters.
* Search services by service ID or name.
* Search resources by name, ID, protocol, parent resource ID, agent name, or service ID.
* Search is case-insensitive.
