> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/install/10.2-install/multidimensional-data-modeling-in-pentaho/olap-log-output/enabling-segment-cache-logging.md).

# Enabling segment cache logging

The Pentaho Server allows you to view engine segment cache logs by opening the log window from within Analyzer.

If you are using Analyzer with a standalone Mondrian engine, cache log information is available through `log4j`. Edit your `log4j` configuration as explained in [Analysis SQL output logging](broken://pages/7fTHhKjGdByrZqStT82g), and set the value of `com.pentaho.analysis.segmentcache` to `DEBUG`. The table below lists other `log4j` categories that can help you diagnose configuration and performance problems.

| Class Name                                            | Cache System                                                                            |
| ----------------------------------------------------- | --------------------------------------------------------------------------------------- |
| `com.pentaho.​analysis.segmentcache.​impl.infinispan` | Outputs information related to the Infinispan implementation of the segment cache.      |
| `com.pentaho.​analysis.segmentcache.​impl.memcached`  | Outputs information related to the Memcached implementation of the segment cache.       |
| `com.pentaho.​analysis.segmentcache.​impl.pentaho`    | Outputs information related to the Pentaho BI Platform Delegating Cache implementation. |


---

# 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.pentaho.com/install/10.2-install/multidimensional-data-modeling-in-pentaho/olap-log-output/enabling-segment-cache-logging.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.