Supported OS

Versión de la integración1.1.0

Información general

Recopila métricas de tu sistema Vespa en tiempo real para:

  • Visualizar y monitorizar el estado y el rendimiento de Vespa
  • Alertas sobre estado y disponibilidad

Configuración

El check de Vespa no está incluido en el paquete del Datadog Agent, por lo que es necesario instalarlo.

Instalación

Para el Agent v7.21/v6.21 o posteriores, sigue las instrucciones a continuación para instalar el check de Vespa en tu host. Para instalarlo con el Agent Docker o versiones anteriores del Agent, consulta Uso de integraciones de la comunidad.

  1. Ejecuta el siguiente comando para instalar la integración del Agent:

    datadog-agent integration install -t datadog-vespa==<INTEGRATION_VERSION>
    
  2. Configura tu integración como si fuese una integración de base.

Configuración

Para configurar el check de Vespa:

  1. Crea una carpeta vespa.d/ en la carpeta conf.d/ en la raíz del directorio de configuración de tu Agent.
  2. Crea un archivo conf.yaml en la carpeta vespa.d/ creada anteriormente.
  3. Consulta el archivo vespa.d/conf.yaml de ejemplo y copia su contenido en el archivo conf.yaml.
  4. Edita el archivo conf.yaml para configurar el consumer, que decide sobre el conjunto de métricas reenviadas por el check:
    • consumer: El consumidor para el que se van a recopilar métricas, ya sea default o un consumidor personalizado de services.xml de tu aplicación Vespa.
  5. Reinicia el Agent.

Validación

Ejecuta el subcomando de estado del Agent y busca vespa en la sección Checks.

Datos recopilados

Métricas

vespa.http.status.1xx.rate
(gauge)
Number of responses with a 1xx status
Shown as response
vespa.http.status.2xx.rate
(gauge)
Number of responses with a 2xx status
Shown as response
vespa.http.status.3xx.rate
(gauge)
Number of responses with a 3xx status
Shown as response
vespa.http.status.4xx.rate
(gauge)
Number of responses with a 4xx status
Shown as response
vespa.http.status.5xx.rate
(gauge)
Number of responses with a 5xx status
Shown as response
vespa.jdisc.gc.ms.average
(gauge)
Time spent in GC
Shown as millisecond
vespa.mem.heap.free.average
(gauge)
Free heap size
Shown as byte
vespa.queries.rate
(gauge)
Number of search queries
Shown as query
vespa.feed.operations.rate
(gauge)
Number of feed operations
Shown as operation
vespa.query_latency.average
(gauge)
Total query processing time
Shown as millisecond
vespa.query_latency.95percentile
(gauge)
95 percentile total query processing time
Shown as millisecond
vespa.query_latency.99percentile
(gauge)
99 percentile total query processing time
Shown as millisecond
vespa.hits_per_query.average
(gauge)
Hits in the returned result, per query
Shown as hit
vespa.totalhits_per_query.average
(gauge)
Estimated total number of hits per query
Shown as hit
vespa.degraded_queries.rate
(gauge)
Queries with degraded results due to timeout
Shown as query
vespa.failed_queries.rate
(gauge)
Failed queries
Shown as query
vespa.serverActiveThreads.average
(gauge)
Threads that are active processing requests
Shown as thread
vespa.content.proton.search_protocol.docsum.requested_documents.rate
(gauge)
Requested document summaries
Shown as document
vespa.content.proton.search_protocol.docsum.latency.average
(gauge)
Docsum request latency on content node
Shown as second
vespa.content.proton.search_protocol.query.latency.average
(gauge)
Query request latency on content node
Shown as second
vespa.content.proton.documentdb.documents.total.last
(gauge)
Total documents in this document db (ready + not-ready)
Shown as document
vespa.content.proton.documentdb.documents.ready.last
(gauge)
Ready documents in this document db
Shown as document
vespa.content.proton.documentdb.documents.active.last
(gauge)
Active/searchable documents in this document db
Shown as document
vespa.content.proton.documentdb.disk_usage.last
(gauge)
Total disk usage for this document db
Shown as byte
vespa.content.proton.documentdb.memory_usage.allocated_bytes.last
(gauge)
Total memory usage for this document db
Shown as byte
vespa.content.proton.resource_usage.disk.average
(gauge)
Relative amount of disk space used by this process
Shown as fraction
vespa.content.proton.resource_usage.memory.average
(gauge)
Relative amount of memory used by this process
Shown as fraction
vespa.content.proton.resource_usage.feeding_blocked.last
(gauge)
Whether feeding is blocked due to resource limitations (value is 0 or 1)
vespa.content.proton.documentdb.matching.docs_matched.rate
(gauge)
Number of documents matched
Shown as document
vespa.content.proton.documentdb.matching.docs_reranked.rate
(gauge)
Number of documents re-ranked (second phase)
Shown as document
vespa.content.proton.documentdb.matching.rank_profile.query_latency.average
(gauge)
Total latency when matching and ranking a query
Shown as second
vespa.content.proton.documentdb.matching.rank_profile.query_setup_time.average
(gauge)
Average time spent setting up and tearing down queries
Shown as second
vespa.content.proton.documentdb.matching.rank_profile.rerank_time.average
(gauge)
Time spent on 2nd phase ranking
Shown as second
vespa.content.proton.transactionlog.disk_usage.last
(gauge)
Disk usage of the transaction log
Shown as byte

Eventos

La integración Vespa no incluye eventos.

Checks de servicio

vespa.metrics_health
Returns CRITICAL if there is no response from the Vespa Node metrics API. Returns WARNING if there is a response from the Vespa Node metrics API but there was an error in processing, otherwise returns OK.
Statuses: ok, warning, critical

vespa.process_health
For each Vespa process, returns CRITICAL if the process seems to be down. Returns WARNING if the process status is unknown, otherwise returns OK.
Statuses: ok, warning, critical

Solucionar problemas

¿Necesitas ayuda? Ponte en contacto con el servicio de asistencia de Datadog.