> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/~/changes/Sh4xqs4GDClkDKT9Hvux/user-guide/using-finder-classic/monitoring-it-services-classic/analyzing-service-quality-classic.md).

# Analyzing service quality (classic)

{% hint style="info" %}
Nexthink Finder is a Windows-only desktop application whose functionality is now available within the Nexthink web interface. Nexthink can now be used directly from a browser and most functions no longer require an additional desktop application.
{% endhint %}

## Overview <a href="#analyzingservicequality-classic-overview" id="analyzingservicequality-classic-overview"></a>

Companies strongly depend on a set of IT Services to carry out their daily work. Although the particular set of deployed IT services may vary from one company to another, the correct functioning of services is vital for the day-to-day business of every organization.

With Nexthink, define the IT services you want to survey by specifying their characteristic resources and see how well those IT services perform inside your corporate network. Thanks to Nexthink’s user-centered approach, you can get a sense of the quality of service through the eyes of employees. See the status of a service in real-time and detect which users are being impacted when the service degrades. In the event of service degradation, Nexthink may help you determine where the problem lies. For long term analysis, follow the evolution of the service throughout extended time intervals.

Nexthink divides IT services into two types:

### Connection-based services <a href="#analyzingservicequality-classic-connection-basedservices" id="analyzingservicequality-classic-connection-basedservices"></a>

Services that rely on TCP connections to provide their solutions to the users. Both Windows and Mac devices report information on connection-based services.

### Web-based services <a href="#analyzingservicequality-classic-web-basedservices" id="analyzingservicequality-classic-web-basedservices"></a>

Websites or web applications that use the HTTP protocol or its encrypted variant with TLS (HTTPS) provide a service to their users. Web-based services also rely on TCP for transport, but defining the service at the HTTP level allows you to filter the service by the accessed web domains or URLs. For the moment, only Windows devices report information specific to web-based services.

## Service metrics <a href="#analyzingservicequality-classic-servicemetrics" id="analyzingservicequality-classic-servicemetrics"></a>

The type of service determines the exact metrics that are used to measure its performance. The set of metrics is nevertheless very similar for both connection-based and web-based services. Most metrics are shared or serve a similar purpose in both types of services. All metrics where the shared metrics are emphasized are listed below:

| Connection-based service metrics                                                                                                                                                                                                                             | Web-based service metrics                                                                                                                                                                                           |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <ul><li>Devices with issues</li><li>Devices using service</li><li>Failed connections</li><li>Application crashes</li><li>Average response time</li><li>Incoming traffic</li><li>Outgoing traffic</li><li>Incoming bitrate</li><li>Outgoing bitrate</li></ul> | <ul><li>Devices with issues</li><li>Devices using service</li><li>Failed web requests</li><li>Application crashes</li><li>Average response time</li><li>Incoming web traffic</li><li>Outgoing web traffic</li></ul> |

## Analyzing services in Finder and the Nexthink web interface <a href="#analyzingservicequality-classic-analyzingservicesinfinderandthenexthinkwebinterface" id="analyzingservicequality-classic-analyzingservicesinfinderandthenexthinkwebinterface"></a>

To analyze service quality, Nexthink offers two options:

The [Service View](/platform/~/changes/Sh4xqs4GDClkDKT9Hvux/user-guide/using-finder-classic/visualizing-system-activity-with-finder-classic/observing-service-performance-with-finder-classic.md) in Finder

The Service View provides you with a real-time view of the service, including the values of the service metrics for the last 60 minutes and the last 24 hours. Break down results according to entities and, if Cross-Engine features are enabled in Finder, according to the nodes in your hierarchies. Drill down to individual connections or devices and quickly switch to the Network or Web views directly from the Service View.

The [service dashboards](/platform/~/changes/Sh4xqs4GDClkDKT9Hvux/user-guide/using-finder-classic/monitoring-it-services-classic/following-the-evolution-of-a-service-classic.md) in the Nexhink web interface

Service modules summarize the status of your services in a special overview dashboard. Moreover, for each individual service in the module, a detailed service dashboard provides you with a full view of the service key metrics through a comprehensive set of widgets. In addition to a real-time view for the last 60 minutes and 24 hours, the Nexthink web interface lets you select longer periods to see historical values and trends in your service-related data.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nexthink.com/platform/~/changes/Sh4xqs4GDClkDKT9Hvux/user-guide/using-finder-classic/monitoring-it-services-classic/analyzing-service-quality-classic.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.