From 4389dd3f91bb7d1025f11cf14f6b3a9b8e4a8387 Mon Sep 17 00:00:00 2001 From: Qian Min Chen Date: Thu, 16 Aug 2018 13:09:37 +0800 Subject: [PATCH] Add the missing markup for the hyperlink title Change-Id: If3e13534573ca691a736d8804efe2d8c17447e72 --- doc/source/code-and-documentation/elastic-recheck.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/source/code-and-documentation/elastic-recheck.rst b/doc/source/code-and-documentation/elastic-recheck.rst index 5b02bb3..4875b72 100644 --- a/doc/source/code-and-documentation/elastic-recheck.rst +++ b/doc/source/code-and-documentation/elastic-recheck.rst @@ -85,16 +85,17 @@ This guide won't go into the details of tracing through the logs of a run and finding a good fingerprint, since that's quite involved, dependent on the job you're looking at, and already documented in a few places including: - * https://www.openstack.org/videos/vancouver-2015/tales-from-the-gate-how-debugging-the-gate-helps-your-enterprise - * https://docs.openstack.org/infra/elastic-recheck/readme.html#queries + * `Tales From the Gate: How Debugging the Gate Helps Your Enterprise + `_ + * `elastic-recheck queries `_ Once you've identified a message in the logs that can be used for fingerprinting you need to turn that into an elastic-search query. You can use any of the existing fingerprints as an example: -https://git.openstack.org/cgit/openstack-infra/elastic-recheck/tree/queries +`openstack-infra/elastic-recheck `_ You should also check any elastic search queries using kibana at: -http://logstash.openstack.org/ +`Logstash Search `_ Once you've constructed a query and checked in on elastic-search you should create a yaml file in the queries directory of the elastic-recheck git repo.