Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
63 changes: 26 additions & 37 deletions source/monitoring.txt
Original file line number Diff line number Diff line change
Expand Up @@ -327,41 +327,31 @@

.. step:: Connect to the {+kafka-connect+} JMX server.

.. procedure::
:style: connected
a. Enter your JMX Server URI ``localhost:{+jmx-port-mapping+}``
into the
:guilabel:`Remote Process` text input box in the {+jconsole+}
interface.

.. step:: Enter your JMX Server URI.
#. Click :guilabel:`Connect`.

Enter the URI ``localhost:{+jmx-port-mapping+}`` into the :guilabel:`Remote Process`
text input box in the {+jconsole+} interface.

.. step:: Click :guilabel:`Connect`.

.. step:: In the dialog box, click :guilabel:`Insecure Connection`.
#. In the dialog box, click :guilabel:`Insecure Connection`.

.. step:: Explore your connectors' metrics.

.. procedure::
:style: connected

.. step:: Navigate to the :guilabel:`MBeans` tab in {+jconsole+}.

.. step:: Inspect connector metrics.
a. Navigate to the :guilabel:`MBeans` tab in {+jconsole+}.

Notice that the ``{+metrics-path+}.sink-task-metrics.sink-task-0.records``
attribute has a value of ``0``. This value indicates that
your sink task has not received any records from {+kafka+}.
#. Inspect connector metrics. Notice that the
``{+metrics-path+}.sink-task-metrics.sink-task-0.records``
attribute has a value of ``0``. This
value indicates that your sink task has not received any
records from {+kafka+}.

.. step:: Continue the Quick Start.
#. Continue the Quick Start until, but not through, the
:ref:`<kafka-quickstart-remove-the-sandbox>` step.

Continue the Quick Start until, but not through, the
:ref:`<kafka-quickstart-remove-the-sandbox>` step.

.. step:: Return to {+jconsole+}.

Navigate back to the :guilabel:`MBeans` tab in {+jconsole+}.
The ``{+metrics-path+}.sink-task-metrics.sink-task-0.records``
attribute should now have a value of ``1``.
#. Navigate back to the :guilabel:`MBeans` tab in {+jconsole+}.
The ``{+metrics-path+}.sink-task-metrics.sink-task-0.records``
attribute should now have a value of ``1``.

Check failure on line 354 in source/monitoring.txt

View workflow job for this annotation

GitHub Actions / TDBX Vale rules

[vale] reported by reviewdog 🐶 [MongoDB.AvoidSubjunctive] Avoid the subjunctive 'should'. Raw Output: {"message": "[MongoDB.AvoidSubjunctive] Avoid the subjunctive 'should'.", "location": {"path": "source/monitoring.txt", "range": {"start": {"line": 354, "column": 20}}}, "severity": "ERROR"}

.. step:: Stop and remove the Quick Start environment.

Expand Down Expand Up @@ -614,17 +604,16 @@

.. _kafka-monitoring-averge-record-size-span:

.. tip:: Average Record Size Over a Span of Time

To calculate the average size of the records your sink connector
processed over a span of time, perform the following actions:
To calculate the average size of the records your sink connector
processed over a span of time, perform the following actions:

#. Determine the change in the value of the ``mongodb-bytes-read``
attribute for a span of time.
#. Determine the change in the value of the ``records`` attribute
for the same span of time you used for the preceding step.
#. Divide the change in the value of the ``mongodb-bytes-read`` attribute
by the change in the value of the ``records`` attribute.
#. Determine the change in the value of the
``mongodb-bytes-read`` attribute for a span of time.
#. Determine the change in the value of the ``records`` attribute
for the same span of time you used for the preceding step.
#. Divide the change in the value of the ``mongodb-bytes-read``
attribute by the change in the value of the ``records``
attribute.

* - **latest-mongodb-time-difference-secs**
- The number of seconds of the most recent time difference recorded between
Expand Down
Loading