Pinecone

Supported OS Linux Windows Mac OS

Pinecone Pod-Based Dashboard Overview
Pinecone Serverless Dashboard Overview
이 페이지는 아직 한국어로 제공되지 않으며 번역 작업 중입니다. 번역에 관한 질문이나 의견이 있으시면 언제든지 저희에게 연락해 주십시오.

Overview

  • Optimize performance and control usage: Observe and track specific actions (e.g. request count) within Pinecone to identify application requests with high latency or usage. Monitor trends and gain actionable insights to improve resource utilization and reduce spend.

  • Automatically alert on metrics: Get alerted when index fullness reaches a certain threshold. You can also create your own customized monitors to alert on specific metrics and thresholds.

  • Locate and triage unexpected spikes in usage or latency: Quickly visualize anomalies in usage or latency in Pinecone’s Datadog dashboard. View metrics over time to better understand trends and determine the severity of a spike.

Requirements

Monitoring Pinecone with Datadog requires:

  • An Enterprise or Enterprise Dedicated Pinecone plan.
  • Pod-based or Serverless indexes: Datadog supports both pod-based and serverless metric capturing.

Setup

Installation

  1. Login to your Pinecone account.
  2. Navigate to API Keys tab.
  3. Create an API key.
  4. Copy the created API Key to your clipboard.

Configuration

  1. Navigate to the configuration tab inside Datadog Pinecone integration tile.
  2. Enter your Pinecone Project ID which can be found in the project list in the Pinecone console.
  3. For pod-based environments only: Select your environment. Projects in serverless environments can leave this blank.
  4. Paste your copied API key.

Data Collected

Metrics

pinecone.vector.count
(gauge)		Number of records per pod in the index.
Shown as record
pinecone.request.count.total
(count)		Number of data plane calls made by clients.
Shown as request
pinecone.request.error.count.total
(count)		Number of data plane calls made by clients that resulted in errors.
Shown as request
pinecone.request.latency.seconds.min
(gauge)		Minimum of the distribution of server-side processing latency for Pinecone data plane calls.
Shown as second
pinecone.request.latency.seconds.max
(gauge)		Maximum of the distribution of server-side processing latency for Pinecone data plane calls.
Shown as second
pinecone.request.latency.seconds.avg
(gauge)		Average of the distribution of server-side processing latency for Pinecone data plane calls.
Shown as second
pinecone.request.latency.seconds.50percentile
(gauge)		p50 of the distribution of server-side processing latency for Pinecone data plane calls.
Shown as second
pinecone.request.latency.seconds.90percentile
(gauge)		p90 of the distribution of server-side processing latency for Pinecone data plane calls.
Shown as second
pinecone.request.latency.seconds.95percentile
(gauge)		p95 of the distribution of server-side processing latency for Pinecone data plane calls.
Shown as second
pinecone.request.latency.seconds.99percentile
(gauge)		p99 of the distribution of server-side processing latency for Pinecone data plane calls.
Shown as second
pinecone.request.latency.seconds.99.9percentile
(gauge)		p99.9 of the distribution of server-side processing latency for Pinecone data plane calls.
Shown as second
pinecone.request.latency.seconds.count
(count)		Count of the distribution of server-side processing latency for Pinecone data plane calls.
Shown as request
pinecone.index.fullness
(gauge)		Fullness of the index on a scale of 0 to 1.
Shown as unit
pinecone.db.op.query.total
(count)		The number of Query Request made to an Index (Serverless)
Shown as request
pinecone.db.op.fetch.total
(count)		The number of Fetch Request made to an Index (Serverless)
Shown as request
pinecone.db.op.update.total
(count)		The number of Update Request made to an Index (Serverless)
Shown as request
pinecone.db.op.delete.total
(count)		The number of Delete Request made to an Index (Serverless)
Shown as request
pinecone.db.op.upsert.total
(count)		The number of Upsert Request made to an Index (Serverless)
Shown as request
pinecone.db.op.query.duration.total
(count)		Total time taken processing Query Request for an Index (Serverless)
Shown as millisecond
pinecone.db.op.fetch.duration.total
(count)		Total time taken processing Fetch Request for an Index (Serverless)
Shown as millisecond
pinecone.db.op.update.duration.total
(count)		Total time taken processing Update Request for an Index (Serverless)
Shown as millisecond
pinecone.db.op.delete.duration.total
(count)		Total time taken processing Delete Request for an Index (Serverless)
Shown as millisecond
pinecone.db.op.upsert.duration.total
(count)		Total time taken processing Upsert Request for an Index (Serverless)
Shown as millisecond
pinecone.db.op.write.unit.total
(count)		Total number of write units consumed (Serverless)
Shown as request
pinecone.db.op.read.unit.total
(count)		Total number of read units consumed (Serverless)
Shown as request
pinecone.db.storage.size.bytes
(gauge)		Total size of the index in bytes (Serverless)
Shown as byte
pinecone.db.record.total
(gauge)		Total number of records (Serverless)
Shown as record

Logs

Pinecone does not include collectings logs.

Service Checks

Pinecone does not include any service checks.

Events

Pinecone does not include any events.

Troubleshooting

Need help? Contact Datadog support.

PREVIEWING: mervebolat/span-id-preprocessing