# Config JSON PS

### JSON Log PS Configuration

JSON PS setting is shown at the ingestion general setting menu below,

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

#### COMPUTE\_JSON\_PS, COMPUTE\_PS

<table><thead><tr><th width="167">CMP_JSON_PS</th><th width="102">CMP_PS</th><th width="325">Description</th></tr></thead><tbody><tr><td>Off</td><td>Off</td><td>No PS generated (Everything is PS3)</td></tr><tr><td>Off</td><td>On</td><td><p>(default behavior)</p><p>Generic PS generation method for all incoming logs</p></td></tr><tr><td>On</td><td>Off</td><td>JSON pattern only and none JSON logs get PS3</td></tr><tr><td>On</td><td>On</td><td>JSON logs goes to JSON ps and non-JSON goes to generic PS</td></tr></tbody></table>

#### **PS\_JSON\_DEPTH**

The maximum depth limitation the JSON log clustering method looks into for each JSON log.  &#x20;

Zero(0) is set for no maximum depth limitation. &#x20;

The default maximum matching depth is set to three(3).


---

# 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.apica.io/autonomous-insights/log-pattern-signature/config-ps/config-json-ps.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.