Uploaded image for project: 'Couchbase Documentation'
  1. Couchbase Documentation
  2. DOC-9685

Elasticsearch Connector Metrics - add corrective action or next step based on the metric

    XMLWordPrintable

Details

    • 1

    Description

      Customer is reviewing this page about metrics for Elasticsearch connector.
      https://docs.couchbase.com/elasticsearch-connector/current/monitoring.html

      They are asking
      1. What are most important metrics to keep an eye on
      2. What should I do based on the outputs.

      The ask for the documentation is to add context and suggested next steps/corrective action. They see the info, now how do we know its good/bad/don't care and how do I fix it.

      For example,

      • cbes.retryDelay Time spent waiting after a temporary indexing failure before the request is retried. --> What is good or bad range? What should I be looking for to indicate good or bad? If it is bad, what next steps should I take to research and resolve it so it's good again?
      • cbes.docRejected Recorded when there is a permanent indexing failure. These failures usually result in an entry being added to the rejection log Elasticsearch index. --> What are corrective actions? How do I recover? What are next steps to get back in sync, etc.?
      • etc for other items as well.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            david.nault David Nault
            david.elliott David Elliott
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty