このコンテンツは選択した言語では利用できません。

Chapter 4. Troubleshooting


The following sections explain how to resolve issues that may occur in Metrics Store.

4.1. Information Is Missing from Kibana

If Kibana is not displaying metric or log information as expected, use journalctl to investigate the collectd and rsyslog log files as follows:

  • If only metrics information is missing, check the collectd log files.
  • If only log information is missing, check the rsyslog log files.
  • If both metrics and logs information are missing, check both log files.

    1. To investigate collectd log files, log in as root and run the following command:

      # journalctl -u collectd
      Copy to Clipboard Toggle word wrap
    2. To investigate rsyslog log files, run the following command:

      # journalctl -u rsyslog
      Copy to Clipboard Toggle word wrap

To learn about additional journalctl options, see journalctl in Linux man pages .

4.2. Extracting Elasticsearch logs

To extract Elasticsearch logs

  1. Log in to the Metrics Store virtual machine as root, and run the following command. Where openshift-logging is the namespace for the Elasticsearch pod:

    for espod in $(oc -n openshift-logging get pods -l component=es -o jsonpath='{.items[*].metadata.name}') ; do
        oc -n openshift-logging exec -c elasticsearch $espod -- logs > $espod.log 2>&1
    done
    Copy to Clipboard Toggle word wrap
  2. Optionally, you can use the use the OpenShift logging-dump tool located at logging dump tool script

4.3. Searching Elasticsearch Logs

  1. To search for all RHV/oVirt logs, ordered by timestamp from newest to oldest.Log in to the Metrics Store virtual machine as root, and run the following command, where openshift-logging is the namespace for the Elasticsearch pod:

    oc -n opesnshift-logging exec -c elasticsearch $(oc -n openshift-logging get pods -l component=es -o jsonpath='{.items[0].metadata.name}') -- es_util --query=project.ovirt-logs*/_search?sort=@timestamp:desc​\&pretty | more
    Copy to Clipboard Toggle word wrap
  2. The output is presented in the human readable JSON format.

4.4. Searching log record results

To search the log report results, you can use the get last rec from host search tool.

The search tool shows how long it has been since the Metrics Store virtual machine received a record from each host that it knows about during a given time interval (last 3 hours by default).

For each host that the Metrics Store virtual machine receives logs from over the defined duration (default 3h) duration, it prints out "green", "yellow", or "red", depending on whether the Metrics Store virtual machine received a record from that host recently or not.

This is followed by the number of seconds it has been since the last record was received from that host, and the number of records received.

  1. Log in to the Metrics Store virtual machine as root, and clone the script repository:

    # git clone https://github.com/jcantrill/cluster-logging-tools -b release-3.11
    Copy to Clipboard Toggle word wrap
  2. Run the script:

    # cd cluster-logging-tools/scripts
    [OLDEST=3h] ./get-last-rec-from-host
    Copy to Clipboard Toggle word wrap
  3. To change the interval, change the OLDEST value to a longer or shorter interval in hours.

    For example, to go back 1 day (24 hours), use:

    OLDEST=24h ./get-last-rec-from-host
    Copy to Clipboard Toggle word wrap
Note

Some hosts may not be listed, if no records were received from that host during the given time interval.

トップに戻る
Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

Theme

© 2025 Red Hat