> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/support-center-framework/support-center-framework-data-tables.md).

# Support Center Framework Data Tables

The Support Center Framework stores statistics in the data tables named *observations* and *causes* in the project folder. However, you can store this data in external databases instead, and LogicNets supports Oracle, MS SQL, and MySQL.

Use the following field names for selecting observations and causes:

* *selection\_key* – This is the unique id of the troubleshooting logicnet. You can select all observations and causes for a certain troubleshooting logicnet using the selection\_key.
* *session\_id* – This is the unique id of the session. Hence, you can select all observations and causes selected within the same session using the session\_id.
* *package* – This is the name of the package. You can select all observations and causes made with a certain package using the package.
* *category* – This is the name of the project. All observations and causes made by all of the packages of the same project can be selected using the category.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-761aee2b2151f91984fcf42ffe3994c069b734ef%2Fc34faf5b-3961-4afb-878d-b3d851a5e717.png?alt=media)


---

# 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://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/support-center-framework/support-center-framework-data-tables.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.