en en eu en en eu en en en en en en eu eu en en en en en en en en en en en en en en en en en en en en en ne en en en en en es en en en en en en en en en en en en en en en en fi en en cv it en en tr es en eo eu pl en pt en ca ja ca en en en en en en es en en en en en en en en en en en en en en en en en en en en en fi en en en en en en en en en fa fi en en en en en en en fi en en en fi en pt en fi en pt ru fi en pt en en en en en en en en en en en en en en en en pt en en en en en en en en en fa fi en en en fi en en en en en pt en en en en en en en en en en en en en en en en en en en en en en mk en en en en en eo en en en en en en en en en en en en en en en en fi en en en en en en en en
The Elasticsearch plugin can be used to retrieve logs from a configured Elasticsearch instance. You can specify a query, which is used to retireve all documents from Elasticsearch. You can also select a list of fields, to display the results in a table. From this table you can also select a single document to view the complete json representation of this document.
To use the Elasticsearch plugin the following configuration is needed in the satellites configuration file:
The name of the Elasticsearch plugin instance.
The type for the Elasticsearch plugin.
Address of the Elasticsearch instance.
Username to access an Elasticsearch instance via basic authentication.
Token to access an Elasticsearch instance via token based authentication.
plugins: - name: elasticsearch type: elasticsearch options: address: username: password: token:
The Elasticsearch plugin can not be used within the insights section of an application.
The Elasticsearch plugin can not be used to get a list of variable values.
The following options can be used for a panel with the Elasticsearch plugin:
If this is true the chart with the distribution of the Documents over the selected time range will be shown
A list of Elasticsearch queries, which can be selected by the user.
A name for the Elasticsearch query, which is displayed in the select box.
The Elasticsearch query. We are using the Query String Syntax for Elasticsearch.
A list of fields to display in the results table. If this field is omitted, the whole document is displayed in the results table.
The Elasticsearch plugin can not be used to get a list of notifications.
The Elasticsearch plugins uses the query string syntax for filtering log lines.
You can specify fields to search in the query syntax:
where the status field contains active
where the title field contains quick or brown
where the author field contains the exact phrase "john smith"
where the first name field contains Alice (note how we need to escape the space with a backslash)
where any of the fields book.title, book.content or book.date contains quick or brown (note how we need to escape the * with a backslash):
where the field title has any non-null value:
Wildcard searches can be run on individual terms, using ? to replace a single character, and * to replace zero or more characters:
Regular expression patterns can be embedded in the query string by wrapping them in forward-slashes ("/"):
We can search for terms that are similar to, but not exactly like our search terms, using the "fuzzy" operator:
Ranges can be specified for date, numeric or string fields. Inclusive ranges are specified with square brackets [min TO max] and exclusive ranges with curly brackets {min TO max}.
All days in 2012:
Tags between alpha and omega, excluding alpha and omega:
Numbers from 10 upwards
By default, all terms are optional, as long as one term matches. A search for foo bar baz will find any document that contains one or more of foo or bar or baz. We have already discussed the default_operator above which allows you to force all terms to be required, but there are also boolean operators which can be used in the query string itself to provide more control.
The preferred operators are + (this term must be present) and - (this term must not be present). All other terms are optional. For example, this query:
quick brown +fox -news
Multiple terms or clauses can be grouped together with parentheses, to form sub-queries:
(quick OR brown) AND fox
--- apiVersion: kobs.io/v1 kind: Dashboard spec: placeholders: - name: namespace description: The workload namespace - name: app description: The workloads app label rows: - size: -1 panels: - title: Istio Logs colSpan: 12 plugin: name: elasticsearch type: elasticsearch options: showChart: true queries: - name: Istio Logs query: "kubernetes.namespace: {% .namespace %} AND kubernetes.labels.app: {% .app %} AND kubernetes.container.name: istio-proxy AND _exists_: content.method" fields: - "kubernetes.pod.name" - "content.authority" - "content.route_name" - "content.protocol" - "content.method" - "content.path" - "content.response_code" - "content.upstream_service_time" - "content.bytes_received" - "content.bytes_sent"