sematext · fulyauluturk · May 20, 2025 · May 5, 2025 · May 5, 2025 · May 5, 2025
diff --git a/docs/app/logs.md b/docs/app/logs.md
@@ -1,7 +1,7 @@
 title: Sematext App - Logs
 description: Sematext App is a modern monitoring, log management, transaction tracing, and real user monitoring system that aggregates and structures your logs across various languages and platforms. It is a suite of products that combine high-quality logging experience with other monitoring and alerting devops tools helping fix production issues
 
-[Sematext logging platform](https://sematext.com/logsene/) provides both ability to create your own queries through its [Elasticsearch API](/docs/logs/search-through-the-elasticsearch-api/) as well as rich, yet simple query syntax very much like the [query syntax](/docs/logs/search-syntax/) used by Google. 
+[Sematext logging platform](https://sematext.com/logsene/) provides both ability to create your own queries through its [Sematext API](/docs/logs/search-through-the-sematext-api/) which is compatible with both Elasticsearch and OpenSearch. It offers rich, yet simple query syntax very much like the [query syntax](/docs/logs/search-syntax/) used by Google. 
 
 We also have a [command line tool](https://sematext.com/blog/logsene-cli/) used for viewing, searching, filtering, and analyzing of log entries across all your logs from all your apps. 
 
@@ -10,4 +10,4 @@ Logs are aggregated by time and shown in the logging management web application,
 Also check related [Field Types](/docs/logs/field-types/), [Supported Date Formats](/docs/logs/supported-date-formats/), special fields,
 and [FAQ](/docs/logs/faq/) about our log management platform features.
 
-Upload your logs from all your servers to our centralized log management solution with Elasticsearch API, and experience the first true Hosted ELK Stack.
+Upload logs from all your servers to our centralized log management solution using the Sematext API, compatible with both Elasticsearch and OpenSearch.
diff --git a/docs/events/event-api.md b/docs/events/event-api.md
@@ -12,8 +12,7 @@ See [here](adding.md#adding-events-via-api).
 
 ### Event Search API
 
-Sematext exposes the Events Search HTTP API - as [Elasticsearch search API](https://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl.html) - so
-events can be searched and retrieved programmatically via HTTP(S), using curl or any other Elasticsearch client.  The API endpoint is:
+Sematext exposes the Events Search HTTP API, which is compatible with both [Elasticsearch](https://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl.html) and [OpenSearch](https://docs.opensearch.org/docs/latest/query-dsl/) query DSLs. This allows you to search and retrieve events programmatically over HTTP(S), using curl or any standard Elasticsearch/OpenSearch client. The API endpoint is:
 
 `https://event-receiver.sematext.com/APP_TOKEN`
 
@@ -25,7 +24,7 @@ events will be limited to the type specified in the URI:
 https://event-receiver.sematext.com/APP_TOKEN/event
 ```
 
-The simplest way to run a query is using [URI search](https://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-uri-request.html),
+The simplest way to run a query is using [URI search](https://docs.opensearch.org/docs/latest/api-reference/search/),
 like this:
 
 ```bash
@@ -34,9 +33,9 @@ https://event-receiver.sematext.com/1111111-2222-3333-4444-555555555555/_search?
 -H 'Authorization: apiKey 1111111-2222-3333-4444-555555555555'
 ```
 
-For more info about ```apiKey``` [see](/docs/logs/search-through-the-elasticsearch-api) .
+For more info about ```apiKey``` [see](/docs/logs/search-through-the-sematext-api) .
 
-More complex queries are available when using [request body search](https://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-request-body.html),
+More complex queries are available when using [request body search](https://docs.opensearch.org/docs/latest/api-reference/search),
 e.g.:
 
 ```json
@@ -52,4 +51,4 @@ curl -XGET "https://event-receiver.sematext.com/1111111-2222-3333-4444-555555555
 ```
 
 This example shows how to use one of the simplest query types: `query_string`. To see which other query types are available, please
-check [Elasticsearch docs](https://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl.html).
+check [OpenSearch docs](https://docs.opensearch.org/docs/latest/query-dsl/).
diff --git a/docs/guide/app-guide.md b/docs/guide/app-guide.md
@@ -4,7 +4,7 @@ description: Sematext Cloud Apps Guide. Using Apps to control access to metrics,
 Apps act as containers for your data. You can store performance
 metrics or logs about servers, containers, software, programming
 languages and databases. Our Apps have dozens of monitoring
-integrations with software like Docker, AWS, Solr, Elasticsearch, [and
+integrations with software like Docker, AWS, Solr, Elasticsearch, OpenSearch, [and
 many more](/docs/integration/), while our log
 integration works with several different [log
 shippers](/docs/integration/#log-shippers). Every

diff --git a/docs/images/logs/kibana-integration.gif b/docs/images/logs/kibana-integration.gif
diff --git a/docs/index.md b/docs/index.md
@@ -119,7 +119,7 @@ Stay informed about the most recent developments in our product and agent releas
 
 Sematext integrations let you collect metrics, logs and events across your whole stack from frontend to backend. Our solution goes beyond collecting metrics and detects anomalies, uncovers your slowest transactions, communication between servers and applications, etc.
 
-We expose an Elasticsearch API. Sematext works with all standard log shippers and agents you're already used to, such as syslog, Logstash, Fluentd, Filebeat, Vector, NXLog, log4j and many others, and integrates in minutes.
+We expose [Sematext API](docs/logs/index-events-via-elasticsearch-api) that works with all standard log shippers and agents you're already used to, such as syslog, Logstash, Fluentd, Filebeat, Vector, NXLog, log4j and many others, and integrates in minutes.
 
 With Experience you can monitor your frontend or website performance and receive alerts when end-user experience is affected by performance. Sematext Experience provides invaluable insights that keep your business in control of how happy your customers are when interacting with your website or webapp.
 

diff --git a/docs/integration/index.md b/docs/integration/index.md
@@ -1,5 +1,5 @@
 title: Integrations
-descriptions: Sematext integrations with ready to use monitoring agents and log shippers for infrastructure and container monitoring, log management and analytics, alerting, chatops, and more. Our Cloud and on-premises platform exposes the Elasticsearch API and syslog receivers with built in anomaly detection, data analysis and visualization tools and services
+descriptions: Sematext integrations with ready to use monitoring agents and log shippers for infrastructure and container monitoring, log management and analytics, alerting, chatops, and more. Our Cloud exposes the Sematext API -compatible with Elasticsearch and OpenSearch- and syslog receivers with built in anomaly detection, data analysis and visualization tools and services
 
 Sematext supports over **100 different integrations** that automatically collect thousands of metrics and logs from your systems and applications. These integrations simplify monitoring and logging processes, offering fine-tuned **pre-built reports and alert rules** that are readily available and require no additional configuration.
 

diff --git a/docs/integration/opensearch-integration.md b/docs/integration/opensearch-integration.md
@@ -1,16 +1,16 @@
-title: Opensearch
+title: OpenSearch
 description: Covers critical metrics—Cluster States, Pending Tasks, shard memory, search latency, request and cache stats—with anomaly detection and diverse alerting options. Correlate events, logs, filter metrics, and visualize cluster health using standard graphs and custom dashboards. Additionally, the OpenSearch Logs integration offers insights into query distribution, error analysis, deprecations, and cluster manager logs for troubleshooting and analysis.
 
-OpenSearch is a powerful, open-source search and analytics engine built for scalability, flexibility, and advanced data exploration capabilities. The [Sematext Agent](/docs/agents/sematext-agent/) collects Opensearch metrics and logs, transmits them to Sematext Cloud; installing the agent takes less than 5 minutes.
+OpenSearch is a powerful, open-source search and analytics engine built for scalability, flexibility, and advanced data exploration capabilities. The [Sematext Agent](/docs/agents/sematext-agent/) collects OpenSearch metrics and logs, transmits them to Sematext Cloud; installing the agent takes less than 5 minutes.
 
 ## Install Sematext Agent
 
-1. Create an Opensearch Logs or Monitoring [App](/docs/guide/app-guide/). This will let you install the agent and control access to your monitoring and logs data.
+1. Create an OpenSearch Logs or Monitoring [App](/docs/guide/app-guide/). This will let you install the agent and control access to your monitoring and logs data.
 3. Install the Sematext Agent according to the [https://apps.sematext.com/ui/howto/Opensearch/overview](https://apps.sematext.com/ui/howto/Opensearch/overview) displayed in the UI.
-4. After installing the agent, the Discovery tab shows all the Opensearch services identified on the host and you will start receiving metrics or logs from Opensearch services.
-5. If you've created an Opensearch Monitoring App and want to collect Opensearch logs as well, or vice versa, click on the **Create Logs App** button from the left menu panel. This will navigate you to the 'Create Logs App' (or Monitoring App) page, where you'll find all the discovered log sources from Opensearch services and manage log and metric shipping effortlessly.
+4. After installing the agent, the Discovery tab shows all the OpenSearch services identified on the host and you will start receiving metrics or logs from OpenSearch services.
+5. If you've created an OpenSearch Monitoring App and want to collect OpenSearch logs as well, or vice versa, click on the **Create Logs App** button from the left menu panel. This will navigate you to the 'Create Logs App' (or Monitoring App) page, where you'll find all the discovered log sources from OpenSearch services and manage log and metric shipping effortlessly.
 
-Having both Opensearch Logs and Monitoring Apps lets you correlate performance metrics and logs, and accelerate troubleshooting using [Split Screen](/docs/guide/split-screen/) for faster resolution. For example, if you see logs of a node restarting, metrics let you see the impact on the rest of the cluster in terms of CPU, GC, and other metrics. Including query time metrics, even if you don't collect slowlogs from [all] queries.
+Having both OpenSearch Logs and Monitoring Apps lets you correlate performance metrics and logs, and accelerate troubleshooting using [Split Screen](/docs/guide/split-screen/) for faster resolution. For example, if you see logs of a node restarting, metrics let you see the impact on the rest of the cluster in terms of CPU, GC, and other metrics. Including query time metrics, even if you don't collect slowlogs from [all] queries.
 
 
 To [explore logs and services](/docs/monitoring/autodiscovery/) across multiple hosts, navigate to [Fleet & Discovery > Discovery > Services](https://apps.sematext.com/ui/fleet-and-discovery/discovery/services) (or  [Sematext Cloud Europe](https://apps.eu.sematext.com/ui/fleet-and-discovery/discovery/services)). From there, you can create additional [Apps](/docs/guide/app-guide/) or stream data to existing ones without requiring any additional installations. 

diff --git a/docs/logagent/cli-parameters.md b/docs/logagent/cli-parameters.md
@@ -1,8 +1,8 @@
 title: Logagent Command-line Parameters
-description: Command Line Parameters for Logagent, light-weight log shipper with out of the box and extensible log parsing, on-disk buffering, secure transport, bulk indexing to Elasticsearch and Sematext logs management platform. Low memory footprint and low CPU overhead make it suitable for deploying on edge nodes and devices, while its ability to parse and structure logs makes it a great Logstash alternative.
+description: Command Line Parameters for Logagent, light-weight log shipper with out of the box and extensible log parsing, on-disk buffering, secure transport, bulk indexing to Elasticsearch/OpenSearch and Sematext logs management platform. Low memory footprint and low CPU overhead make it suitable for deploying on edge nodes and devices, while its ability to parse and structure logs makes it a great Logstash alternative.
 
 ```bash
-# Parse all logs and stream them to Sematext Logs 1-Click managed Elasticsearch 
+# Parse all logs and stream them to Sematext Logs
 $ logagent -i LOGSENE_TOKEN /var/log/*.log 
 
 # stream logs to local Elasticsearch
@@ -74,9 +74,9 @@ $ logagent [options] [file list]
 | `-y, --yaml` | prints parsed messages in YAML format to stdout|
 | `-p, --pretty` | prints parsed messages in pretty JSON format to stdout|
 | `-j, --ldjson` | print parsed messages in line-delimited JSON format to stdout |
-| __Elasticsearch or Sematext Cloud__| Log storage |
+| __Elasticsearch/OpenSearch or Sematext Cloud__| Log storage |
 | `-e, --elasticsearchUrl <url>` | Elasticsearch URL e.g. https://localhost:9200, default `htpps://logsene-receiver.sematext.com`|
-| `-i, --index <index>` | [Logs App token](https://sematext.com/logsene) to ship data to Sematext Cloud Apps or Elasticsearch index (see `--elasticsearchUrl`) |
+| `-i, --index <index>` | [Logs App token](https://sematext.com/logsene) to ship data to Sematext Cloud Apps or Elasticsearch/OpenSearch index (see `--elasticsearchUrl`) |
 | `--httpProxy <url>` | HTTP proxy url |
 | `--httpsProxy <url>` | HTTPS proxy url |
 
@@ -91,9 +91,9 @@ The default output is line-delimited JSON for parsed log lines, as long as no fo
 |LOGS_TMP_DIR | Directory to store failed bulk requests for later retransmission.|
 |LOG_INTERVAL | Time to batch logs before a bulk request is done. Default is 10000 ms (10 seconds)|
 |LOGS_BULK_SIZE | Maximum size of a bulk request. Default is 1000.|
-|LOGS_RECEIVER_URL | URL for the Logsene receiver. For a local Elasticsearch server or for Sematext Enterprise version of Logsene. Defaults to Sematext Logsene SaaS receiver https://logsene-receiver.sematext.com/_bulk. Example for Elasticsearch: ```LOGSENE_URL=https://localhost:9200/_bulk```|
+|LOGS_RECEIVER_URL | URL for the Logsene receiver. For a local Elasticsearch/OpenSearch server. Defaults to Sematext Logs receiver https://logsene-receiver.sematext.com/_bulk. Example for Elasticsearch: ```LOGSENE_URL=https://localhost:9200/_bulk```|
 |HTTPS_PROXY| Proxy URL for HTTPS endpoints, like Logsene receiver. ```export HTTPS_PROXY=https://my-proxy.example```|
-|HTTP_PROXY| Proxy URL for HTTP endpoints (e.g. On-Premises or local Elasticsearch). ```export HTTP_PROXY=https://my-proxy.example```|
+|HTTP_PROXY| Proxy URL for HTTP endpoints (e.g. On-Premises or local Elasticsearch/OpenSearch). ```export HTTP_PROXY=https://my-proxy.example```|
 |LOGAGENT_CONFIG | Filename to read Logagent CLI parameters from a file, defaults to ```/etc/sematext/logagent.conf`` |
 |PATTERN_MATCHING_ENABLED | Default is 'true'. The value 'false' disables parsing of logs. |
 |SCAN_ALL_PATTERNS | Default is 'false'. For performance reasons, patterns are matched by source name. Setting the value to 'true' enables pattern search regardless of source name |

diff --git a/docs/logagent/filter-output-sql.md b/docs/logagent/filter-output-sql.md
@@ -3,7 +3,7 @@ Filter and aggregate parsed logs with SQL.
 
 This filter function applies SQL queries on parsed log events. The result of the query is emitted as new event, while the original events are omitted. 
 
-Using SQL it is very easy to aggregate values, e.g. group HTTP requests by status codes. The SQL WHERE statement is used to filter events before they get shipped to Elasticsearch or [Logsene](https://sematext.com/logsene). 
+Using SQL it is very easy to aggregate values, e.g. group HTTP requests by status codes. The SQL WHERE statement is used to filter events before they get shipped to Elasticsearch/OpenSearch or [Sematext Logs](https://sematext.com/logsene). 
 
 The supported SQL syntax for SELECT statements is described in the [alasql documentation](https://github.com/agershun/alasql/wiki/Select).  
 
@@ -43,4 +43,4 @@ output:
 Run logagent with your config: 
 ```
 logagent --config logagent-example-config.yml 
-```
+```
diff --git a/docs/logagent/filters.md b/docs/logagent/filters.md
@@ -20,7 +20,7 @@ Example:
 2. Input Filter: Grep URLs of interest 'login|register|upgrade'   
 3. Parser: Parse Log and generate fields like URL, status code, size, referrer, country etc.
 4. Output Filter: Drop irelevant log events like redirects (status=302)
-5. Output Plugin: Store filtered log-events in Elasticsearch
+5. Output Plugin: Store filtered log-events in Elasticsearch/OpenSearch
 ```
 
 Filters can be declared inline as JavaScript in function or as a reference to npm modules in a Logagent config file. 

diff --git a/docs/logagent/how-to-gdpr_web_logs.md b/docs/logagent/how-to-gdpr_web_logs.md
@@ -1,5 +1,5 @@
 Title: GDPR and personal data in web server logs 
-Description: Log anonymizer, logs and data fields masking needed for GDPR data protection regulation with Logagent, light-weight log shipper, filebeat, fluentd or rsyslog alternative with out of the box and extensible log parsing, on-disk buffering, secure transport, bulk indexing to Elasticsearch and Sematext logs management platform
+Description: Log anonymizer, logs and data fields masking needed for GDPR data protection regulation with Logagent, light-weight log shipper, filebeat, fluentd or rsyslog alternative with out of the box and extensible log parsing, on-disk buffering, secure transport, bulk indexing to Elasticsearch/OpenSearch and Sematext logs management platform
 
 
 Masking data in logs got really important due to meet the requirements of GDPR a European data protection regulation. In the GDPR role "data controller" for your logs, you should minimize the risk of exposing sensitive data to 3rd parties. In some cases, even IP-Addresses are considered as personal data, but your logs might more sensitive data like username, phone numbers etc. 

diff --git a/docs/logagent/index.md b/docs/logagent/index.md
@@ -1,10 +1,10 @@
 Title: Sematext Logagent Log Shipper
-Description: Logagent is lightweight log shipper, filebeat, fluentd or rsyslog alternative with out of the box and extensible log parsing, on-disk buffering, secure transport, bulk indexing to Elasticsearch, Kafka, and Sematext
+Description: Logagent is lightweight log shipper, filebeat, fluentd or rsyslog alternative with out of the box and extensible log parsing, on-disk buffering, secure transport, bulk indexing to Elasticsearch, OpenSearch, Kafka, and Sematext
 
 ## What is Logagent?
 [Logagent](https://sematext.com/logagent) is a modern, open-source, lightweight **log shipper** with a low memory footprint and low CPU overhead!
 
-It comes with out of the box and extensible **log parsing**, **on-disk buffering**, **secure transport**, and **log shipping** with **bulk indexing** to any **Elasticsearch endpoint**, including [Sematext Logs](https://sematext.com/logsene), Kafka, etc.
+It comes with out of the box and extensible **log parsing**, **on-disk buffering**, **secure transport**, and **log shipping** with **bulk indexing** to any **Elasticsearch/OpenSearch endpoint**, including [Sematext Logs](https://sematext.com/logsene), Kafka, etc.
 
 If you're eager to get started, here's how you start shipping logs.
 
@@ -38,7 +38,7 @@ Logagent contains an installer when you want to use it as a [log shipper](/docs/
 - Plugins:
     - Inputs (files, streams, sockets, databases)
     - Input filters (grep/grok filters)
-    - Outputs (Elasticsearch, Sematext Cloud, Kafka, etc.)
+    - Outputs (Elasticsearch, OpenSearch, Sematext Cloud, Kafka, etc.)
     - Output filters (SQL aggregation of parsed data, enrichment of data)
 - Node.js API
 
@@ -72,7 +72,7 @@ input:
     - '/var/log/**/*.log'
 
 output:
-  # index logs in Elasticsearch or Sematext Logs
+  # index logs in Sematext Logs
   sematext: # output a name, e.g., elasticsearch, sematext, etc.
     module: elasticsearch
     url: https://logsene-receiver.sematext.com