Skip to content

Same agent Smaller bill. The tools and infrastructure to get more work from your AI. Fewer tokens. Less compute. Lower cost.

[Feat]: Add Section for Features in documentation (#249)

patcher9e05cf2ce0c2c
diff --git a/docs/images/multiple-db.png b/docs/images/multiple-db.png
new file mode 100644
index 00000000..8ecce46d
Binary files /dev/null and b/docs/images/multiple-db.png differ
diff --git a/docs/latest/features/metrics.mdx b/docs/latest/features/metrics.mdx
new file mode 100644
index 00000000..7679d184
--- /dev/null
+++ b/docs/latest/features/metrics.mdx
@@ -0,0 +1,72 @@
+---
+title: 'LLM Application Metrics'
+sidebarTitle: 'Metrics'
+---
+
+OpenLIT offers automatic instrumentation with OpenTelemetry for various LLM providers, frameworks, and VectorDBs, enabling you to gain valuable insights into the behavior and performance of your LLM applications through metrics.
+
+This documentation covers metrics settings, understanding semantic conventions, and interpreting metric attributes, empowering you to enhance the monitoring and observability of your LLM applications.
+
+<CardGroup cols={2}>
+<Card title="Quickstart" href="/latest/quickstart" icon='bolt'>
+Get Started with monitoring your LLM Applications in 2 simple steps
+</Card>
+<Card title="Connections" href="/latest/connections/intro" icon='link'>
+Connect to your existing Observablity Stack
+</Card>
+</CardGroup>
+
+## Disable Metrics
+You have the option to disable the collection of metrics if needed. By default, metrics collection is enabled.
+
+Example:
+
+```python
+# Disable metrics collection
+openlit.init(disable_metrics=True)
+```
+
+## Using an existing OTel Metrics instance
+
+You have the flexibility to integrate your existing OpenTelemetry (OTel) Metrics instance configuration with OpenLIT.
+If you already have an OTel Metrics instance instantiated in your application, you can pass it directly to `openlit.init(meter=meter)`.
+This integration ensures that OpenLIT utilizes your custom OTel metrics instance settings, allowing for a unified metrics setup across your application.
+
+Example:
+
+```python
+# Instantiate an OpenTelemetry Metrics meter
+meter = ...
+
+# Pass the meter to OpenLIT
+openlit.init(meter=meter)
+```
+
+## Semantic Convention
+
+This section outlines the OpenTelemetry metrics collected by **OpenLIT** from applications using LLMs and Vector Databases. These metrics offer a straightforward overview of application performance and resource usage. They serve as a supplement to the detailed data captured through [tracing](./tracing), aiding in the easy creation of dashboards for quick monitoring of system usage and performance.
+
+### GenAI/LLM Metrics
+
+| Metric Name | Description | Unit | Type | Attributes |
+|-----------------------------------|--------------------------------------------|-------|-------------|----------------------------------------------------------------------------------------------------|
+| `gen_ai.total.requests` | Number of requests to the LLM. | `1` | Counter | `telemetry.sdk.name`, `gen_ai.application_name`, `gen_ai.system`, `gen_ai.environment`, `gen_ai.type`, `gen_ai.request.model` |
+| `gen_ai.usage.prompt_tokens` | Number of prompt tokens processed. | `1` | Counter | `telemetry.sdk.name`, `gen_ai.application_name`, `gen_ai.system`, `gen_ai.environment`, `gen_ai.type`, `gen_ai.request.model` |
+| `gen_ai.usage.completion_tokens` | Number of completion tokens processed. | `1` | Counter | `telemetry.sdk.name`, `gen_ai.application_name`, `gen_ai.system`, `gen_ai.environment`, `gen_ai.type`, `gen_ai.request.model` |
+| `gen_ai.usage.total_tokens` | Total number of tokens processed. | `1` | Counter | `telemetry.sdk.name`, `gen_ai.application_name`, `gen_ai.system`, `gen_ai.environment`, `gen_ai.type`, `gen_ai.request.model` |
+| `gen_ai.usage.cost` | The cost distribution of LLM requests. | `USD` | Histogram | `telemetry.sdk.name`, `gen_ai.application_name`, `gen_ai.system`, `gen_ai.environment`, `gen_ai.type`, `gen_ai.request.model` |
+
+### VectorDB Metrics
+
+| Metric Name | Description | Unit | Type | Attributes |
+|-------------------------|--------------------------------------------|-------|-------------|--------------------------------------------------------------|
+| `db.total.requests` | Number of requests to VectorDBs. | `1` | Counter | `telemetry.sdk.name`, `gen_ai.application_name`, `gen_ai.environment` |
+
+<CardGroup cols={2}>
+<Card title="Integrations" href="/latest/integrations/introduction" icon='circle-nodes'>
+Integrate your LLM Stack with OpenLIT
+</Card>
+<Card title="Connections" href="/latest/connections/intro" icon='link'>
+Connect to your existing Observablity Stack
+</Card>
+</CardGroup>
\ No newline at end of file
diff --git a/docs/latest/features/multiple-db.mdx b/docs/latest/features/multiple-db.mdx
new file mode 100644
index 00000000..3011f841
--- /dev/null
+++ b/docs/latest/features/multiple-db.mdx
@@ -0,0 +1,29 @@
+---
+title: 'Connect Multiple Databases'
+description: 'Connect and switch between multiple ClickHouse databases in OpenLIT UI'
+sidebarTitle: 'Connect Multiple Databases'
+---
+
+In the OpenLIT UI, you can add and switch between multiple ClickHouse databases. This feature enables users to maintain separate databases for different environments while using the same OpenLIT UI to analyze LLM Observability data.
+
+<Frame>
+ <img src="/images/multiple-db.png" />
+</Frame>
+
+1. **Log in** to the OpenLIT UI.
+2. Go to the **database configuration** page.
+3. Click on the **Add new** option.
+4. Enter the ClickHouse database configuration details.
+5. Click **Save** to confirm.
+6. Simply **enable** the desired database to view its data. This selected database will power the dashboards and request page.
+
+---
+
+<CardGroup cols={2}>
+<Card title="Integrations" href="/latest/integrations/introduction" icon='circle-nodes'>
+Integrate your LLM Stack with OpenLIT
+</Card>
+<Card title="Connections" href="/latest/connections/intro" icon='link'>
+Connect to your existing Observablity Stack
+</Card>
+</CardGroup>
diff --git a/docs/latest/features/pricing.mdx b/docs/latest/features/pricing.mdx
new file mode 100644
index 00000000..b7b6fd9a
--- /dev/null
+++ b/docs/latest/features/pricing.mdx
@@ -0,0 +1,48 @@
+---
+title: 'Track Cost for Custom Models'
+description: 'Use your own Pricing File to calculate LLM usage costs'
+sidebarTitle: 'Track Cost for Custom Models'
+---
+
+OpenLIT provides built-in pricing information through a default pricing JSON file accessible from [this URL](https://raw.githubusercontent.com/openlit/openlit/main/assets/pricing.json). This default file, which is regularly updated to reflect the latest pricing from various LLM providers, covers a range of standard LLM usage scenarios and provides detailed pricing information.
+
+To support personalized pricing schemes for specialized needs, such as fine-tuned or custom models, OpenLIT allows users to specify their own pricing structure through a custom JSON file. This flexibility ensures that pricing calculations for LLM operations are accurately aligned with unique business models and specific application requirements.
+
+## Using the Default Pricing File
+
+The [default pricing file](https://raw.githubusercontent.com/openlit/openlit/main/assets/pricing.json) is recommended for general use as it is consistently updated to stay current with the pricing models of different LLM providers. Users should consider using a custom pricing file primarily when dealing with custom or fine-tuned models not covered by the default settings.
+
+## Using a Custom Pricing File
+
+Users can provide their own `pricing_json` variable, which can either be a file path or a URL pointing to a custom JSON file. This file should contain pricing details such as the model names and their associated costs in USD per 1000 tokens for chat-based models.
+
+**Example Usage:**
+
+- To load pricing details from an external URL:
+
+ ```python
+ openlit.init(pricing_json="https://example.com/path/to/your/pricing.json")
+ ```
+
+- To load pricing details from a local file path:
+
+ ```python
+ openlit.init(pricing_json="/path/to/your/local/pricing.json")
+ ```
+
+### Important Considerations
+
+1. **JSON Structure**: The custom pricing JSON must follow the same structure as the [default pricing file](https://raw.githubusercontent.com/openlit/openlit/main/assets/pricing.json) provided by OpenLIT. If the structure does not match, OpenLIT will not be able to accurately calculate costs based on the custom pricing file.
+
+2. **Initialization**: OpenLIT SDK initializes by pulling data from the provided or default JSON source. It's essential to ensure that the path or URL is accessible during initialization to fetch the necessary pricing data.
+
+3. **Updates**: If pricing details change, users need to update their custom JSON file accordingly. If using a URL, ensure that the file at the URL is updated; if using a local file, update the file directly on your system.
+
+<CardGroup cols={2}>
+<Card title="Integrations" href="/latest/integrations/introduction" icon='circle-nodes'>
+Integrate your LLM Stack with OpenLIT
+</Card>
+<Card title="Connections" href="/latest/connections/intro" icon='link'>
+Connect to your existing Observablity Stack
+</Card>
+</CardGroup>
\ No newline at end of file
diff --git a/docs/latest/features/tracing.mdx b/docs/latest/features/tracing.mdx
new file mode 100644
index 00000000..aed5e218
--- /dev/null
+++ b/docs/latest/features/tracing.mdx
@@ -0,0 +1,203 @@
+---
+title: 'LLM Application Traces'
+sidebarTitle: 'Tracing'
+---
+
+OpenLIT provides OpenTelemetry Auto instrumentation for various LLM providers, frameworks, and VectorDBs, providing you with insights into the behavior and performance of your LLM applications.
+
+This documentation covers tracing settings, understanding semantic conventions, and interpreting span attributes to enhance the monitoring and observability of your LLM applications.
+
+<CardGroup cols={2}>
+<Card title="Quickstart" href="/latest/quickstart" icon='bolt'>
+Get Started with monitoring your LLM Applications in 2 simple steps
+</Card>
+<Card title="Connections" href="/latest/connections/intro" icon='link'>
+Connect to your existing Observablity Stack
+</Card>
+</CardGroup>
+
+## Using an existing OTel Tracer
+
+You have the flexibility to integrate your existing OpenTelemetry (OTel) tracer configuration with OpenLIT.
+If you already have an OTel tracer instantiated in your application, you can pass it directly to `openlit.init(tracer=tracer)`.
+This integration ensures that OpenLIT utilizes your custom tracer settings, allowing for a unified tracing setup across your application.
+
+Example:
+
+```python
+# Instantiate an OpenTelemetry Tracer
+tracer = ...
+
+# Pass the tracer to OpenLIT
+openlit.init(tracer=tracer)
+```
+
+## Disable Tracing of Content
+
+By default, OpenLIT adds the prompts and completions to Trace span attributes.
+
+However, you may want to disable this logging for privacy reasons, as they may contain highly sensitive data from your users. You may also simply want to reduce the size of your traces.
+
+Example:
+
+```python
+openlit.init(trace_content=False)
+```
+
+## Disable Batch
+
+By default, the SDK batches spans using the OpenTelemetry batch span processor. When working locally, sometimes you may wish to disable this behavior. You can do that with this flag.
+
+Example:
+
+```python
+openlit.init(disable_batch=True)
+```
+
+## Disbale Instrumentations
+
+By default, OpenLIT automatically detects which models and frameworks you are using and instruments them for you. You can override this and disable instrumentation for specific frameworks and models.
+
+Example:
+
+```python
+openlit.init(disabled_instrumentors=["anthropic", "langchain"])
+```
+
+## Semantic Convention
+
+This section outlines the OpenTelemetry traces collected by **OpenLIT** from applications utilizing Large Language Models (LLMs) and Vector Databases. The span attributes adhere to the [GenAI Semantic Conventions](https://github.com/open-telemetry/semantic-conventions/tree/main/docs/gen-ai) established by the OpenTelemetry community, ensuring standardized data collection that enhances monitoring and debugging capabilities.
+
+### Span Definitions
+
+This section outlines fundamental definitions related to span types and names used within the OpenTelemetry traces to identify the nature and source of requests.
+
+| Attribute | Description | Examples |
+|-------------|-------------------------------------------------------------------------------------------------|---------------------------|
+| **Span kind** | Will always be `CLIENT` when the trace is generated successfully. | `CLIENT` |
+| **Span name** | Is set to the LLM endpoint which follows the convention `provider_name.operation_name`. | `openai.chat.completions` |
+
+### General Span Attributes
+
+General span attributes encapsulate the environmental and operational context of LLM applications, offering insights into where and how the spans are generated.
+
+| Attribute | Type | Description | Examples |
+|---------------------------------|----------|--------------------------------------------------|---------------------|
+| `gen_ai.endpoint` | string | The API endpoint used for the LLM request. | `cohere.chat` |
+| `gen_ai.system` | string | The Generative AI product as identified by the client instrumentation. | `openai`, `cohere`, `anthropic`, `groq`, `huggingface`, `azure_openai`, `mistral`, `bedrock`, `vertexai`, `ollama`, `langchain`, `llama_index`, `haystack` |
+| `gen_ai.environment` | string | Deployment environment of the LLM. | `production` |
+| `gen_ai.application_name` | string | The name of the application using the LLM. | `chatbot_app` |
+| `gen_ai.type` | string | The type of LLM operation performed. | `chat`, `embedding`, `audio`, `image`, `fine_tuning`, `vectordb`, `framework` |
+| `gen_ai.hub.owner` | string | The owner of the prompt hub where the prompt is hosted. | `openai` |
+| `gen_ai.hub.repo` | string | The repository within the hub from which the model is used. | `gpt-4` |
+| `gen_ai.retrieval.source` | string | Source from which the model was retrieved. | `slack` |
+| `telemetry.sdk.name` | string | Source of the generated traces | `openlit` |
+
+### GenAI/LLM Span Attributes
+
+#### Request Attributes
+
+These attributes detail the specifics of requests sent to LLMs, including configurations and parameters that define the behavior and responses of the LLM.
+
+| Attribute | Type | Description | Examples |
+|-----------------------------------------|------------|--------------------------------------------------------------------------|------------------------------------|
+| `gen_ai.request.model` | string | The name of the LLM a request is being made to. | `gpt-4` |
+| `gen_ai.request.temperature` | double | The temperature setting for the LLM request. | `0.0` |
+| `gen_ai.request.top_p` | double | The top_p sampling setting for the LLM request. | `1.0` |
+| `gen_ai.request.top_k` | double | The top_k sampling setting for the LLM request. | `1.0` |
+| `gen_ai.request.max_tokens` | int | The maximum number of tokens the LLM generates for a request. | `100` |
+| `gen_ai.request.is_stream` | boolean | Indicates if the request to LLM is a stream. | `true` |
+| `gen_ai.request.user` | string | Username or identifier for the user making the request. | `user123` |
+| `gen_ai.request.seed` | int | Seed used to generate deterministic results from the LLM. | `42` |
+| `gen_ai.request.frequency_penalty` | double | Frequency penalty parameter in the LLM request. | `0.5` |
+| `gen_ai.request.presence_penalty` | double | Presence penalty parameter in the LLM request. | `0.5` |
+| `gen_ai.request.embedding_format` | string | Format of embeddings requested from the LLM. | `json` |
+| `gen_ai.request.embedding_dimension` | int | Dimensionality of the generated embeddings. | `512` |
+| `gen_ai.request.tool_choice` | string | Tool or library chosen for processing the LLM request. | `PyTorch` |
+| `gen_ai.request.audio_voice` | string | Voice setting for audio generated by LLM. | `alto` |
+| `gen_ai.request.audio_response_format` | string | The format of the audio response from the LLM. | `mp3` |
+| `gen_ai.request.audio_speed` | double | Speed setting for audio responses generated by the LLM. | `1.0` |
+| `gen_ai.request.fine_tune_status` | string | Status or mode of finetuning the model. | `active` |
+| `gen_ai.request.fine_tune_model_suffix` | string | Suffix describing specifics of the finetuned model version. | `v2` |
+| `gen_ai.request.fine_tune_n_epochs` | int | Number of epochs used in training the finetuned model. | `4` |
+| `gen_ai.request.learning_rate_multiplier` | double | Learning rate multiplier used in finetuning. | `0.7` |
+| `gen_ai.request.fine_tune_batch_size` | int | Batch size used in the finetuning process. | `16` |
+| `gen_ai.request.validation_file` | string | Location or type of validation file used in the training process. | `val_data.json` |
+| `gen_ai.request.training_file` | string | Location or type of training file used for the LLM. | `train_data.json` |
+
+
+#### Response Attributes
+
+Attributes in this category help trace and understand responses from LLMs, encapsulating data relevant to outcomes and any content generated as a result.
+
+| Attribute | Type | Description | Examples |
+|-------------------------------------|-----------|---------------------------------------------------------------|-----------------------------------|
+| `gen_ai.response.id` | string | The unique identifier for the response. | `resp-456` |
+| `gen_ai.response.finish_reasons` | string | Reasons the model stopped generating tokens. | `stop` |
+| `gen_ai.response.image` | string | The image content generated by the LLM. | `<image URL or base64 string>` |
+| `gen_ai.response.image_size` | string | Size specifications for the generated image. | `1024x768` |
+| `gen_ai.response.image_quality` | int | Quality parameter for the generated image, usually a percentage. | `90` |
+| `gen_ai.response.image_style` | string | Style or theme of the generated image. | `van_gogh` |
+
+#### Usage Attributes
+
+These attributes track the consumption and costs associated with LLM requests, facilitating operational analysis and resource management.
+
+| Attribute | Type | Description | Examples |
+|-----------------------------------------|------------|-------------------------------------------------------------------------|-------------------|
+| `gen_ai.usage.prompt_tokens` | int | The number of tokens used in the LLM prompt. | `100` |
+| `gen_ai.usage.completion_tokens` | int | The number of tokens used in the LLM response (completion). | `180` |
+| `gen_ai.usage.total_tokens` | int | The total number of tokens used in both the prompt and completion. | `280` |
+| `gen_ai.usage.cost` | decimal | The cost (in USD) associated with the LLM request | `0.05` |
+
+#### Content Attributes
+
+Content attributes specifically relate to the data exchanged with LLMs during requests and responses, including initial prompts and resulting outputs.
+
+| Attribute | Type | Description | Example Value |
+|-------------------------------------|---------|----------------------------------------------------------------|-----------------------------------------------|
+| `gen_ai.content.prompt` | string | The full prompt sent to the LLM. | `"What is the capital of France?"` |
+| `gen_ai.content.completion` | string | The full response received from the LLM. | `"The capital of France is Paris."` |
+| `gen_ai.content.revised_prompt` | string | Revised or modified prompt, if applicable. | `"What's the capital city of France?"` |
+
+### VectorDB Span Attributes
+
+This section addresses attributes related to interactions with Vector Databases supporting the LLM operations, providing insights into database operations and related parameters.
+
+| Attribute | Type | Description | Example Value |
+|-----------------------------|----------|---------------------------------------------------------------------|-------------------------------------|
+| `db.system` | string | System type of the database. | `pinecone`, `chroma`, `qdrant`, `milvus` |
+| `db.collection.name` | string | Name of the collection within the database. | `user_profiles` |
+| `db.operation` | string | Type of database operation performed. | `query`, `delete`, `update`, `upsert`,`add`, `peek`, `create_index`, `create_collection`, `update_collection`, `delete_collection` |
+| `db.operation.status` | string | Status result of the operation (e.g., success, error). | `completed` |
+| `db.operation.cost` | decimal | Cost associated with the operation, if applicable. | `0.0` |
+| `db.ids_count` | int | Count of ids processed or retrieved in an operation. | `150` |
+| `db.vector_count` | int | Number of vectors involved in the operation. | `320` |
+| `db.metadatas_count` | int | Count of metadata entries retrieved or modified. | `120` |
+| `db.documents_count` | int | The number of documents involved in the database operation. | `85` |
+| `db.payload_count` | int | Payload count associated with the operation. | `45` |
+| `db.limit` | int | Limit number for query results. | `50` |
+| `db.offset` | int | The offset for the starting point of the query results. | `10` |
+| `db.where_document` | string | Filter document condition used in operations like query or update. | `"age > 30"` |
+| `db.filter` | string | Applied filters on database query. | `"{ 'status': 'active' }"` |
+| `db.statement` | string | Raw database query statement. | `[0.1, 0.3]` |
+| `db.n_results` | int | Number of results returned from a query operation. | `15` |
+| `db.delete_all` | boolean | Indicates if all records are to be deleted in the operation. | `false` |
+| `db.index.name` | string | Name of the index used or modified. | `user_index` |
+| `db.index.dimension` | int | Dimension of the index involved in the database operation. | `128` |
+| `db.collection.dimension` | int | Dimensionality configuration of the collection. | `128` |
+| `db.create_index.metric` | string | Metric type used for creating indexes. | `"euclidean"` |
+| `db.create_index.spec` | string | Specifications of the index created. | `"type: kd-tree; leaf_size: 40"` |
+| `db.query.namespace` | string | Namespace used for structuring database queries. | `"product_catalog"` |
+| `db.update.metadata` | string | Metadata being updated as part of the operation. | `"category: electronics"` |
+| `db.update.values` | string | Specifies the new values being applied in an update operation. | `"{ 'price': '99.99' }"` |
+| `db.update.id` | string | Unique identifier for the entry being updated. | `"product123"` |
+
+<CardGroup cols={2}>
+<Card title="Integrations" href="/latest/integrations/introduction" icon='circle-nodes'>
+Integrate your LLM Stack with OpenLIT
+</Card>
+<Card title="Connections" href="/latest/connections/intro" icon='link'>
+Connect to your existing Observablity Stack
+</Card>
+</CardGroup>
\ No newline at end of file
diff --git a/docs/latest/sdk-configuration.mdx b/docs/latest/sdk-configuration.mdx
new file mode 100644
index 00000000..061f25be
--- /dev/null
+++ b/docs/latest/sdk-configuration.mdx
@@ -0,0 +1,21 @@
+---
+title: 'SDK Configuration'
+description: 'Configuring Options for OpenLIT SDK'
+icon: 'file-code'
+---
+
+Below is a detailed overview of the configuration options available, allowing you to adjust OpenLIT's behavior and functionality to align with your specific observability needs:
+
+| Argument | Description | Default Value | Required |
+|-------------------------|-----------------------------------------------------------------------------------------------|----------------|----------|
+| `environment` | The deployment environment of the application. | `"default"` | Yes |
+| `application_name` | Identifies the name of your application. | `"default"` | Yes |
+| `tracer` | An instance of OpenTelemetry Tracer for tracing operations. | `None` | No |
+| `meter` | An OpenTelemetry Metrics instance for capturing metrics. | `None` | No |
+| `otlp_endpoint` | Specifies the OTLP endpoint for transmitting telemetry data. | `None` | No |
+| `otlp_headers` | Defines headers for the OTLP exporter, useful for backends requiring authentication. | `None` | No |
+| `disable_batch` | A flag to disable batch span processing, favoring immediate dispatch. | `False` | No |
+| `trace_content` | Enables tracing of content for deeper insights. | `True` | No |
+| `disabled_instrumentors`| List of instrumentors to disable. Choices: `["openai", "anthropic", "langchain", "cohere", "mistral", "transformers", "chroma", "pinecone"]`. | `None` | No |
+| `disable_metrics` | If set, disables the collection of metrics. | `False` | No |
+| `pricing_json` | URL or file path of the pricing JSON file. | `https://github.com/openlit/openlit/blob/main/assets/pricing.json` | No |
\ No newline at end of file
diff --git a/docs/latest/configuration.mdx b/docs/latest/ui-configuration.mdx
similarity index 95%
rename from docs/latest/configuration.mdx
rename to docs/latest/ui-configuration.mdx
index 16e465d4..3c43c556 100644
--- a/docs/latest/configuration.mdx
+++ b/docs/latest/ui-configuration.mdx
@@ -1,6 +1,6 @@
---
-title: 'Configuration'
-description: 'Configuring Options for OpenLIT'
+title: 'UI Configuration'
+description: 'Configuring Options for OpenLIT UI'
icon: 'sliders'
---
diff --git a/docs/mint.json b/docs/mint.json
index 58e44b07..4f6ea312 100644
--- a/docs/mint.json
+++ b/docs/mint.json
@@ -46,7 +46,8 @@
"pages": [
"latest/introduction",
"latest/quickstart",
- "latest/configuration"
+ "latest/sdk-configuration",
+ "latest/ui-configuration"
],
"version": "latest"
},
@@ -93,6 +94,16 @@
}
]
},
+ {
+ "group": "Features",
+ "pages": [
+ "latest/features/tracing",
+ "latest/features/metrics",
+ "latest/features/pricing",
+ "latest/features/multiple-db"
+ ],
+ "version": "latest"
+ },
{
"group": "Connections",
"pages": [