Conventions used

There are a number of text conventions used throughout this book.

Code in text: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: “The or and and operators yield results that are too broad or too strict; you can use the minimum_should_match parameter to filter less relevant results.”

A block of code is set as follows:

GET /movies/_search
{
  "query": {
    "multi_match": {
      "query": "come home",
      "fields": ["title", "plot"]
    }
  }
}

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

GET movies-dense-vector/_search
{
  "knn": {
    "field": "plot_vector",
    "k": 5,
    "num_candidates": 50,
    "query_vector_builder": {
      "text_embedding": {
        "model_id": ".multilingual-e5-small_linux-x86_64",
        "model_text": "romantic moment"
      }
    }
  },
  "fields": [ "title", "plot" ]
}

Any command-line input or output is written as follows:

$ kubectl apply -f elastic-agent-managed-kubernetes.yml
$ sudo metricbeat modules enable tomcat

Bold: Indicates a new term, an important word, or words that you see onscreen. For example, words in menus or dialog boxes appear in the text like this. Here is an example: “In Kibana, go to Observability | APM | Services, to check whether the different microservices have been correctly instrumented.”

Tips or important notes

Appear like this.