iSharkFly-Docs/opensearch-docs-cn
1
0
Fork 0
mirror of https://github.com/iSharkFly-Docs/opensearch-docs-cn synced 2025-02-21 23:16:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

redirect updates (#4061)

Browse Source 
* redirect updates

Signed-off-by: Heather Halter <hdhalter@amazon.com>

* Update _search-plugins/sql/ppl/syntax.md

Co-authored-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com>
Signed-off-by: Heather Halter <HDHALTER@AMAZON.COM>

---------

Signed-off-by: Heather Halter <hdhalter@amazon.com>
Signed-off-by: Heather Halter <HDHALTER@AMAZON.COM>
Co-authored-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com>
This commit is contained in:
Heather Halter 2023-05-11 15:48:29 -07:00 committed by GitHub
parent cb29ffb862
commit e9db68d327
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 13 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
_observing-your-data/operational-panels.md
View File

@ -4,6 +4,7 @@ title: Operational panels
nav_order: 60
redirect_from:
- /observing-your-data/operational-panels/
- /observability-plugin/operational-panels/
---
# Operational panels

2
_search-plugins/sql/ppl/functions.md
View File

@ -4,6 +4,8 @@ title: Commands
parent: PPL &ndash; Piped Processing Language
grand_parent: SQL and PPL
nav_order: 2
redirect_from:
- /search-plugins/ppl/commands/
---
# Commands

7
_search-plugins/sql/ppl/index.md
View File

@ -6,9 +6,10 @@ nav_order: 5
has_children: true
has_toc: false
redirect_from:
- /search-plugins/sql/ppl
- /search-plugins/ppl
- /observability-plugin/ppl
- /search-plugins/sql/ppl/
- /search-plugins/ppl/
- /observability-plugin/ppl/
- /search-plugins/ppl/index/
---
# PPL &ndash; Piped Processing Language

2
_security/configuration/disable.md
View File

@ -3,6 +3,8 @@ layout: default
title: Disabling security
parent: Configuration
nav_order: 40
redirect_from:
- /security-plugin/configuration/disable/
---
# Disabling security

8
_tools/logstash/advanced-config.md
View File

@ -197,7 +197,7 @@ The user agent is the last part of a log entry that consists of the name of the
Users might be using a wide range of browsers, devices, and OS's. Doing this manually is hard.
You can't use `grok` patterns because the `grok` pattern only matches the usage in the string as whole and doesn't figure out which browser the visitor used for instance.
You can't use `grok` patterns because the `grok` pattern only matches the usage in the string as whole and doesn't figure out which browser the visitor used, for instance.
Logstash ships with a file containing regular expressions for this purpose. This makes it really easy to extract user agent information, which you could send to OpenSearch and run aggregations on.
@ -216,7 +216,7 @@ Start Logstash and send an HTTP request.
You can see a field named `ua` with a number of keys including the browser name and version, the OS, and the device.
You could OpenSearch Dashboards to create a pie chart that shows how many visitors are from mobile devices and how many are desktop users. Or, you could get statistics on which browser versions are popular.
You can use OpenSearch Dashboards to create a pie chart that shows how many visitors are using mobile devices and how many are desktop users. Or, you could get statistics on which browser versions are popular.
## Enriching geographical data
@ -235,11 +235,11 @@ geoip {
Start Logstash and send an HTTP request.
Within the terminal, you see a new field named `geoip` that contains information such as the timezone, country, continent, city, postal code, and the latitude / longitude pair.
Within the terminal, you see a new field named `geoip` that contains information such as the time zone, country, continent, city, postal code, and the latitude / longitude pair.
If you only need the country name for instance, include an option named `fields` with an array of the field names that you want the `geoip` plugin to return.
Some of the fields are not always available such as city name and region because translating IP addresses into geographical locations is generally not that accurate. If the `geoip` plugin fails to look up the geographical location, it adds a tag named `geoip_lookup_failure`.
Some of the fields, such as city name and region, are not always available because translating IP addresses into geographical locations is generally not that accurate. If the `geoip` plugin fails to look up the geographical location, it adds a tag named `geoip_lookup_failure`.
You can use the `geoip` plugin with the OpenSearch output because `location` object within the `geoip` object, is a standard format for representing geospatial data in JSON. This is the same format as OpenSearch uses for its `geo_point` data type.