> For the complete documentation index, see [llms.txt](https://docs.inspector.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inspector.dev/guides/raw-php.md).

# PHP

### Introduction

The Inspector PHP package sends performance metrics and errors to your Inspector account. It has  a simple API which allows you to instrument any application or PHP script.

### How does the package works?

The package can be used to wrap your application execution cycles to measure their duration and metadata (like the DB statements), as well as HTTP related information (like the URL, parameters, headers, etc).

These events, called Transactions and Segments, are sent to our ingestion API. Our data ingestion system  converts and store them to provides you with insights into latency issues and error culprits within your application.

{% hint style="info" %}
This package can be used as dependency to develop frameworks' specific integration as we did for [Symfony](/guides/symfony.md) and [Laravel](/guides/laravel.md).
{% endhint %}

### Useful Links

* Website: <https://www.inspector.dev>
* Blog: <https://www.inspector.dev/blog>
* GitHub repository: <https://github.com/inspector-apm/inspector-php>


---

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

```
GET https://docs.inspector.dev/guides/raw-php.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.