> For the complete documentation index, see [llms.txt](https://docs.pyck.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pyck.cloud/graphql-api/queries/service-status.md).

# Service Status

Service health and status monitoring queries

Audience: System Administrator

pyck provides dedicated queries for monitoring the health and status of each microservice in the system. These queries are essential for:

* Health checks and monitoring
* Deployment verification
* Version tracking
* Service availability monitoring

## Available Service Status Queries

Each pyck service exposes a status query that returns `ServiceInfo` with version and deployment information:

* **inventory** - Inventory service status
* **main\_data** - Main data service status
* **management** - Management service status
* **picking** - Picking service status
* **receiving** - Receiving service status
* **file** - File service status
* **workflow** - Workflow service status

## Return Type

All service status queries return the `ServiceInfo` type containing:

* `version` - Service version string
* `date` - Build/deployment date

## Usage Example

```graphql
query {
  inventory {
    version
    date
  }
  picking {
    version
    date
  }
}
```

## Monitoring Best Practices

1. **Regular Health Checks**: Set up automated queries to monitor service availability
2. **Version Tracking**: Track version numbers across deployments
3. **Alert Configuration**: Configure alerts when services become unavailable
4. **Dashboard Integration**: Integrate status queries into monitoring dashboards

## See Also

* [ServiceInfo Type](/graphql-api/types/serviceinfo.md) - Details about the ServiceInfo return type


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pyck.cloud/graphql-api/queries/service-status.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.