[for analysis] Not working airmail

distribution/docker/ubuntu/Dockerfile

@@ -0,0 +1,30 @@
+FROM ubuntu:noble AS builder
+
+RUN apt-get update && apt-get install -y curl
+RUN curl -L https://install.quickwit.io | sh
+
+
+FROM ubuntu:noble AS quickwit
+
+LABEL org.opencontainers.image.title="Quickwit"
+LABEL maintainer="Quickwit, Inc. <[email protected]>"
+LABEL org.opencontainers.image.vendor="Quickwit, Inc."
+LABEL org.opencontainers.image.licenses="AGPL-3.0"
+
+RUN apt-get -y update \
+    && apt-get -y install ca-certificates \
+                          libssl3 \
+    && rm -rf /var/lib/apt/lists/*
+
+WORKDIR /quickwit
+RUN mkdir config qwdata
+COPY --from=builder /quickwit-v*/quickwit /usr/local/bin/quickwit
+COPY --from=builder /quickwit-v*/config/quickwit.yaml /quickwit/config/quickwit.yaml
+
+ENV QW_CONFIG=/quickwit/config/quickwit.yaml
+ENV QW_DATA_DIR=/quickwit/qwdata
+ENV QW_LISTEN_ADDRESS=0.0.0.0
+
+RUN quickwit --version
+
+ENTRYPOINT ["quickwit"]

docs/configuration/storage-config.md

@@ -5,17 +5,19 @@ sidebar_position: 2
 
 ## Supported Storage Providers
 
-Quickwit currently supports three types of storage providers:
+Quickwit currently supports four types of storage providers:
 - Amazon S3 and S3-compatible (Garage, MinIO, ...)
 - Azure Blob Storage
 - Local file storage*
+- Google Cloud Storage (native API)
 
 ## Storage URIs
 
 Storage URIs refer to different storage providers identified by a URI "protocol" or "scheme". Quickwit supports the following storage URI protocols:
 - `s3://` for Amazon S3 and S3-compatible
 - `azure://` for Azure Blob Storage
 - `file://` for local file systems
+- `gs://` for Google Cloud Storage
 
 In general, you can use a storage URI or a file path anywhere you would intuitively expect a file path. For instance:
 - when setting the `index_uri` of an index to specify the storage provider and location;

docs/deployment/cluster-sizing.md

@@ -1,6 +1,6 @@
 ---
 title: Cluster sizing
-sidebar_position: 2
+sidebar_position: 3
 ---
 
 In this guide, we discuss how to size your Quickwit cluster and nodes. As shown

docs/deployment/kubernetes/_category_.yaml

@@ -0,0 +1,3 @@
+label: 'Kubernetes'
+position: 2
+collapsed: true

docs/deployment/kubernetes/gke.md

@@ -1,5 +1,6 @@
 ---
-title: Google GKE
+title: Install Quickwit on Google GKE
+sidebar_label: Google GKE
 sidebar_position: 2
 ---
 

docs/deployment/kubernetes/glasskube.md

@@ -0,0 +1,69 @@
+---
+title: Install Quickwit with Glasskube
+sidebar_label: Glasskube
+sidebar_position: 3
+---
+
+[Glasskube](https://glasskube.dev) is a package manager for Kubernetes that empowers you to effortlessly install, upgrade, configure, and manage your Kubernetes cluster packages, all while streamlining repetitive and cumbersome maintenance tasks.
+
+## Requirements
+
+To deploy Quickwit on Kubernetes, you will need:
+
+- kubectl, compatible with your cluster (+/- 1 minor release from your cluster) (`kubectl version`)
+- A Kubernetes cluster
+
+1. Install `kubectl` and `glasskube` cli.
+
+To install `kubectl` locally, you can refere to [this documentation](https://kubernetes.io/docs/tasks/tools/#install-kubectl).
+
+To install `glasskube` cli locally, you can refer to [this documentation](https://glasskube.dev/docs/getting-started/install) and choose the right installation options according to your operating system.
+
+For example, let's assume that you're on MacOS using homebrew and kind, this is what you'll have to do:
+
+```shell
+brew install glasskube/tap/glasskube # install the glasskube cli
+kind create cluster # create a kind Kubernetes cluster
+```
+
+2. Install glasskube in your Kubernetes cluster:
+
+```shell
+glasskube bootstrap
+```
+
+3. Start and access to the Glasskube's GUI:
+
+```shell
+glasskube serve
+```
+
+You'll be able to access to the GUI of Glasskube here: http://localhost:8580
+
+## Install Quickwit using Glasskube
+
+`glasskube` will install Quickwit in the `quickwit` namespace. You can perform the Quickwit installation directly with the GUI:
+
+![screenshot-glasskube-ui.png](../../assets/images/screenshot-glasskube-ui.png)
+
+Or use the CLI instead:
+
+```shell
+glasskube install quickwit
+```
+
+In both, you'll have to set the value of thoses parameters:
+
+* `defaultIndexRootUri`: the default index URI is a S3 compliant bucket which usually looks like this: `s3://<bucket-name>/<optional-base-path>`
+* `metastoreUri`: if you're not using PostgreSQL and object storage, you can pick the same bucket and value you used for the `defaultIndexRootUri` parameter
+* `s3Endpoint`: the http(s) URL of your object storage service which should looks like `https://s3.{region}.{your object storage domain}`
+* `s3Flavor`: which can be one of the following: `do`, `garage`, `gcp`, `minio`. You can leave it empty if your object storage is compliant with AWS S3
+* `s3Region`
+* `s3AccessKeyId`
+* `s3SecretAccessKey`
+
+## Uninstall quickwit
+
+```shell
+glasskube uninstall quickwit
+```

docs/deployment/kubernetes/helm.md

@@ -1,13 +1,12 @@
 ---
-title: Kubernetes
+title: Install Quickwit with Helm
+sidebar_label: Helm
 sidebar_position: 1
 ---
 
 [Helm](https://helm.sh) is a package manager for Kubernetes that allows you to configure, install, and upgrade containerized applications in a Kubernetes cluster in a version-controlled and reproducible way.
 
-## Install Quickwit using Helm
-
-Install Quickwit on Kubernetes with the official Quickwit Helm chart. If you encounter any problem with the chart, please, open an issue in our [GitHub repository](https://github.com/quickwit-oss/helm-charts).
+You can install Quickwit on Kubernetes with the official Quickwit Helm chart. If you encounter any problem with the chart, please, open an issue in our [GitHub repository](https://github.com/quickwit-oss/helm-charts).
 
 ## Requirements
 

docs/get-started/installation.md

@@ -18,6 +18,7 @@ Quickwit compiles to a single binary and we provide different methods to install
 - Linux/MacOS binaries that you can [download manually](#download) or with the [install script](#install-script)
 - [Docker image](#use-the-docker-image)
 - [Helm chart](../deployment/kubernetes/helm.md)
+- [Glasskube](../deployment/kubernetes/glasskube.md)
 
 ## Prerequisites
 

docs/log-management/send-logs/using-vector.md

@@ -43,83 +43,9 @@ docker run --rm -v $(pwd)/qwdata:/quickwit/qwdata -p 7280:7280 quickwit/quickwit
 
 ## Taking advantage of Quickwit's native support for logs
 
-Let's embrace the OpenTelemetry standard and take advantage of Quickwit features. With the native support for OpenTelemetry standards, Quickwit already comes with an index called `otel-logs_v0_6` that is compatible with the OpenTelemetry [logs data model](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/data-model.md). This means we can start pushing log data without any prior usual index setup. 
-
-Here is the OpenTelemetry index configuration for reference.
-
-```yaml title="otel-logs_v0_6"
-version: 0.7
-
-index_id: otel-logs-v0_6
-
-doc_mapping:
-  mode: strict
-  field_mappings:
-    - name: timestamp_nanos
-      type: datetime
-      input_formats: [unix_timestamp]
-      output_format: unix_timestamp_nanos
-      indexed: false
-      fast: true
-      fast_precision: milliseconds
-    - name: observed_timestamp_nanos
-      type: datetime
-      input_formats: [unix_timestamp]
-      output_format: unix_timestamp_nanos
-    - name: service_name
-      type: text
-      tokenizer: raw
-    - name: severity_text
-      type: text
-      tokenizer: raw
-      fast: true
-    - name: severity_number
-      type: u64
-      fast: true
-    - name: body
-      type: json
-    - name: attributes
-      type: json
-      tokenizer: raw
-      fast: true
-    - name: dropped_attributes_count
-      type: u64
-      indexed: false
-    - name: trace_id
-      type: bytes
-    - name: span_id
-      type: bytes
-    - name: trace_flags
-      type: u64
-      indexed: false
-    - name: resource_attributes
-      type: json
-      tokenizer: raw
-      fast: true
-    - name: resource_dropped_attributes_count
-      type: u64
-      indexed: false
-    - name: scope_name
-      type: text
-      indexed: false
-    - name: scope_version
-      type: text
-      indexed: false
-    - name: scope_attributes
-      type: json
-      indexed: false
-    - name: scope_dropped_attributes_count
-      type: u64
-      indexed: false
-
-  timestamp_field: timestamp_nanos
-
-indexing_settings:
-  commit_timeout_secs: 10
-
-search_settings:
-  default_search_fields: [body.message]
-```
+Let's embrace the OpenTelemetry standard and take advantage of Quickwit features. With the native support for OpenTelemetry standards, Quickwit already comes with an index called `otel-logs_v0_7` that is compatible with the OpenTelemetry [logs data model](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/data-model.md). This means we can start pushing log data without any prior usual index setup.
+
+The OpenTelemetry index configuration can be found in the [quickwit-opentelemetry/src/otlp/logs.rs](https://github.com/quickwit-oss/quickwit/blob/main/quickwit/quickwit-opentelemetry/src/otlp/logs.rs) source file.
 
 ## Setup Vector
 
@@ -140,7 +66,7 @@ inputs = [ "generate_syslog"]
 type = "remap"
 source = '''
   structured = parse_syslog!(.message)
-  .timestamp_nanos, err = to_unix_timestamp(structured.timestamp, unit: "nanoseconds")
+  .timestamp_nanos = to_unix_timestamp!(structured.timestamp, unit: "nanoseconds")
   .body = structured
   .service_name = structured.appname
   .resource_attributes.source_type = .source_type
@@ -163,6 +89,7 @@ source = '''
   .scope_name = structured.msgid
   del(.message)
   del(.timestamp)
+  del(.service)
   del(.source_type)
 '''