> For the complete documentation index, see [llms.txt](https://docs.apica.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apica.io/autonomous-insights/log-pattern-signature/config-ps.md).
# Config PS
## Configuring Pattern-Signature
Pattern-Signature feature is activated and controlled via the configuration steps below,
1. Go to the “Ingest Configuration” menu item to display the PS configuration fillers.
2. Four rows are used to manage PS features: “PS\_Configure”, “PS\_STREAM\_ENABLE”, “PS\_STEAM\_MAX\_SIZE”, “PS\_TOTAL\_STREAM\_MAX\_SIZE”.
#### PS\_STREAM\_MAX\_SIZE
Maximum number of Pattern-Signatures (PS) that each namespace-application log stream can create. The ingestion turns off the Pattern-Signature engine and assigns default null PS id \*6 to that log stream. The default max count is set to 8,000.
#### PS\_TOTAL\_STREAM\_MAX\_SIZE
A maximum number of total Pattern-Signatures (PS) the cluster can create. Once the total maximum count is reached, subsequent log event PS will be set to default PS id \*6. The default max count is set to 20,000.
#### PS\_STREAM\_ENAB
**\[ ( \ \,)\*]**
\ is the namespace string, a valid namespace specifier.
\ is the application name string, a valid application specifier.
#### PS\_CONFIG
Reserved for internal use.
#### PS Id Default Code
* \*3 : Disable PS generation at the top level.
* \*4 : PS feature is turned off from log stream configuration or FlashOps level.
* \*6 : Exceed PS count at either total PS count or per log stream PS count max.
---
# 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.apica.io/autonomous-insights/log-pattern-signature/config-ps.md?ask=&goal=
```
`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.