# Group by service name

Inspector segments metrics by hostnames. So as the number of underlying hosts increase it could create a bit of clutter in the charts.

It may be more clear to use a human friendly **service name** to represent all your servers inside the same logical group.

<figure><img src="/files/MTlewxkYjZda4qXZ7eYE" alt=""><figcaption></figcaption></figure>

We can use the Inspector library to programmatically change the hostname just before the transaction is sent out of your server and set the same for related instances. It will make your dashboard more clear and understandable.

<figure><img src="/files/Lpy7bRa6i7nkupnz58TA" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Read the step by step guide on our blog: <https://inspector.dev/how-to-monitor-your-laravel-application-by-services-not-by-hostnames/>
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.inspector.dev/guides/laravel/group-by-service-name.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.