gooddata-flight-server 1.53.0__tar.gz → 1.53.1.dev1__tar.gz

gooddata_flight_server-1.53.1.dev1/.gitignore

@@ -0,0 +1,69 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+env/
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+*.egg-info/
+.installed.cfg
+*.egg
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*,cover
+.hypothesis/
+venv/
+.venv/
+.python-version
+.pytest_cache
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+
+# Sphinx documentation
+docs/_build/
+docs/_autosummary/
+
+# PyBuilder
+target/
+
+#Ipython Notebook
+.ipynb_checkpoints
+
+test_data

gooddata_flight_server-1.53.1.dev1/.readthedocs.yaml

@@ -0,0 +1,19 @@
+# (C) 2024 GoodData Corporation
+# Read the Docs configuration file for Sphinx projects
+# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
+
+# Required
+version: 2
+
+# Set the OS, Python version and other tools you might need
+build:
+  os: ubuntu-22.04
+  tools:
+    python: "3.11"
+
+sphinx:
+  configuration: gooddata-flight-server/docs/conf.py
+
+python:
+  install:
+    - requirements: gooddata-flight-server/docs/requirements.txt

gooddata_flight_server-1.53.1.dev1/Makefile

@@ -0,0 +1,19 @@
+# (C) 2024 GoodData Corporation
+include ../../project_common.mk
+
+.PHONY: docs
+docs:
+	tox $(TOX_FLAGS) -e docs
+
+
+.PHONY: dev-certs
+dev-certs:
+	mkdir -p test_data
+	# create CA with self-signed certificate > generate keys + cert requests for server and client > sign
+	cd test_data && \
+		rm -f *.pem && \
+		openssl req -x509 -newkey rsa:4096 -days 3650 -nodes -keyout ca-key.pem -out ca-cert.pem -subj "/C=NA/ST=Unknown/L=Unknown/O=Unknown/OU=Unknown/CN=localhost/emailAddress=example@example.com" && \
+		openssl req -newkey rsa:4096 -nodes -keyout server-key.pem -out server-req.pem -subj "/C=NA/ST=Unknown/L=Unknown/O=Unknown/OU=Computer/CN=localhost/emailAddress=example@example.com" && \
+		openssl req -newkey rsa:4096 -nodes -keyout client-key.pem -out client-req.pem -subj "/C=NA/ST=Unknown/L=Unknown/O=Unknown/OU=Computer/CN=testClient1/emailAddress=example@example.com" && \
+		openssl x509 -req -in server-req.pem -days 3650 -CA ca-cert.pem -CAkey ca-key.pem -CAcreateserial -out server-cert.pem && \
+		openssl x509 -req -in client-req.pem -days 3650 -CA ca-cert.pem -CAkey ca-key.pem -CAcreateserial -out client-cert.pem

{gooddata_flight_server-1.53.0/gooddata_flight_server.egg-info → gooddata_flight_server-1.53.1.dev1}/PKG-INFO

@@ -1,13 +1,13 @@
 Metadata-Version: 2.4
 Name: gooddata-flight-server
-Version: 1.53.0
+Version: 1.53.1.dev1
 Summary: Flight RPC server to host custom functions
-Author: GoodData
-Author-email: support@gooddata.com
-License: MIT
-Project-URL: Documentation, https://gooddata-flight-server.readthedocs.io/en/v1.53.0
+Project-URL: Documentation, https://gooddata-flight-server.readthedocs.io/en/v1.53.1.dev1
 Project-URL: Source, https://github.com/gooddata/gooddata-python-sdk
-Keywords: gooddata,flight,rpc,flight rpc,custom functions,analytics,headless,business,intelligence,headless-bi,cloud,native,semantic,layer,sql,metrics
+Author-email: GoodData <support@gooddata.com>
+License: MIT
+License-File: LICENSE.txt
+Keywords: analytics,business,cloud,custom functions,flight,flight rpc,gooddata,headless,headless-bi,intelligence,layer,metrics,native,rpc,semantic,sql
 Classifier: Development Status :: 4 - Beta
 Classifier: Environment :: Console
 Classifier: License :: OSI Approved :: MIT License
@@ -21,8 +21,6 @@ Classifier: Topic :: Scientific/Engineering
 Classifier: Topic :: Software Development
 Classifier: Typing :: Typed
 Requires-Python: >=3.9.0
-Description-Content-Type: text/markdown
-License-File: LICENSE.txt
 Requires-Dist: dynaconf<4.0.0,>=3.1.11
 Requires-Dist: opentelemetry-api<=2.0.0,>=1.24.0
 Requires-Dist: opentelemetry-sdk<=2.0.0,>=1.24.0
@@ -31,18 +29,7 @@ Requires-Dist: prometheus-client~=0.20.0
 Requires-Dist: pyarrow>=16.1.0
 Requires-Dist: readerwriterlock~=1.0.9
 Requires-Dist: structlog<25.0.0,>=24.0.0
-Dynamic: author
-Dynamic: author-email
-Dynamic: classifier
-Dynamic: description
-Dynamic: description-content-type
-Dynamic: keywords
-Dynamic: license
-Dynamic: license-file
-Dynamic: project-url
-Dynamic: requires-dist
-Dynamic: requires-python
-Dynamic: summary
+Description-Content-Type: text/markdown
 
 # GoodData Flight Server
 

gooddata_flight_server-1.53.1.dev1/mypy.ini

@@ -0,0 +1,35 @@
+# (C) 2024 GoodData Corporation
+[mypy]
+plugins = pydantic.mypy
+disallow_untyped_defs = True
+warn_redundant_casts = True
+strict_equality = True
+no_implicit_optional = True
+python_version = 3.9
+
+[mypy-gooddata_api_client.*]
+ignore_missing_imports = True
+
+[mypy-gooddata_sdk.*]
+ignore_missing_imports = True
+
+[mypy-pyarrow.*]
+ignore_missing_imports = True
+
+[mypy-orjson.*]
+ignore_missing_imports = True
+
+[mypy-dynaconf.*]
+ignore_missing_imports = True
+
+[mypy-structlog.*]
+ignore_missing_imports = True
+
+[mypy-opentelemetry.*]
+ignore_missing_imports = True
+
+[mypy-prometheus_client.*]
+ignore_missing_imports = True
+
+[mypy-readerwriterlock.*]
+ignore_missing_imports = True

gooddata_flight_server-1.53.1.dev1/pyproject.toml

@@ -0,0 +1,77 @@
+# (C) 2025 GoodData Corporation
+[project]
+name = "gooddata-flight-server"
+version = "1.53.1.dev1"
+description = "Flight RPC server to host custom functions"
+readme = "README.md"
+license = {text = "MIT"}
+authors = [
+    {name = "GoodData", email = "support@gooddata.com"}
+]
+keywords = [
+    "gooddata",
+    "flight",
+    "rpc",
+    "flight rpc",
+    "custom functions",
+    "analytics",
+    "headless",
+    "business",
+    "intelligence",
+    "headless-bi",
+    "cloud",
+    "native",
+    "semantic",
+    "layer",
+    "sql",
+    "metrics",
+]
+requires-python = ">=3.9.0"
+dependencies = [
+    "dynaconf>=3.1.11,<4.0.0",
+    "opentelemetry-api>=1.24.0,<=2.0.0",
+    "opentelemetry-sdk>=1.24.0,<=2.0.0",
+    "orjson>=3.8.5,<4.0.0",
+    "prometheus-client~=0.20.0",
+    "pyarrow>=16.1.0",
+    "readerwriterlock~=1.0.9",
+    "structlog>=24.0.0,<25.0.0",
+]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Environment :: Console",
+    "License :: OSI Approved :: MIT License",
+    "Programming Language :: Python :: 3.9",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Database",
+    "Topic :: Scientific/Engineering",
+    "Topic :: Software Development",
+    "Typing :: Typed",
+]
+
+[project.urls]
+Documentation = "https://gooddata-flight-server.readthedocs.io/en/v1.53.1.dev1"
+Source = "https://github.com/gooddata/gooddata-python-sdk"
+
+[project.scripts]
+gooddata-flight-server = "gooddata_flight_server.cli:main"
+
+[dependency-groups]
+test = [
+    "pytest~=8.3.4",
+    "pytest-cov~=6.0.0",
+]
+type = [
+    "mypy~=1.11.2",
+    "pydantic~=2.9.2"
+]
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/gooddata_flight_server"]
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"

gooddata_flight_server-1.53.1.dev1/sample-config.toml

@@ -0,0 +1,345 @@
+# (C) 2024 GoodData Corporation
+[server]
+
+#######################################################################
+# Flight RPC Setup
+#######################################################################
+
+# host to bind Flight RPC server to. Default is 127.0.0.1 - listening on
+# localhost only.
+#
+# use:
+#
+# - 0.0.0.0 - to bind to all addressed = reachable via network
+# - 127.0.0.1 - to bind to localhost only (unreachable via outside network)
+# - custom address to bind to
+#
+# env: GOODDATA_FLIGHT_SERVER__LISTEN_HOST
+listen_host = "127.0.0.1"
+
+# port on which the Flight RPC server should listen
+#
+# env: GOODDATA_FLIGHT_SERVER__LISTEN_PORT
+listen_port = 17001
+
+# host name to use when sending this server's Flight RPC location to clients.
+# Defaults to current hostname.
+#
+# Advertising different host from the one that the server is bound to is
+# often needed in Dockerized environments.
+#
+# ---
+#
+# Example: you run the server inside Docker on localhost and have port forwarding
+# setup. You want to access the server from your workstation. In this setup,
+# the 'listen_host' is set to "0.0.0.0" (server listens on all interfaces within
+# the container) and the 'advertise_host' is set to "localhost".
+#
+# When you make a GetFlightInfo call to the server (running inside docker), it will
+# generate a Flight accordingly and the returned Locations will again point at
+# "localhost" so the subsequent DoGet call goes again to the Dockerized server.
+#
+# Without the 'advertise_host', the GetFlightInfo would return Location referencing
+# some internal / randomly assigned hostname that is unreachable from your workstation.
+#
+# env: GOODDATA_FLIGHT_SERVER__ADVERTISE_HOST
+advertise_host = "127.0.0.1"
+
+# port number to use when sending this server's Flight RPC location to clients.
+# Defaults to value of 'listen_port'.
+#
+# Advertising different port from the one that the server is listening is often
+# needed in environments where port forwarding is in effect.
+#
+# ---
+#
+# Example: you run multiple servers inside Docker on localhost and have port
+# forwarding setup. Each server goes to different port.
+#
+# Analogous to the host example (see above), the Dockerized server needs to send
+# location with port number that can be reached from your workstation.
+#
+# env: GOODDATA_FLIGHT_SERVER__ADVERTISE_PORT
+advertise_port = 17001
+
+#######################################################################
+# TLS Setup
+#######################################################################
+
+# optionally specify to use TLS; default when not specified is False
+#
+# IMPORTANT: when you turn on TLS, you must also specify at minimum
+# the TLS certificate and TLS private key for the server to use.
+# Additionally, if you use self-signed certificates, you need to
+# also specify the tls_root_certificate.
+#
+# env: GOODDATA_FLIGHT_SERVER__USE_TLS
+# use_tls = false
+
+# if you want to use TLS (see 'use_tls' above), then you must specify
+# server's certificate.
+#
+# This is supposed to be a PEM encoded X.509 certificate identifying
+# your server.
+#
+# You can inline the certificate value into this setting, or you can
+# specify file where the certificate resides.
+#
+# To specify certificate file, code the value of this setting as
+# `@/absolute/path/to/cert`
+#
+# env: GOODDATA_FLIGHT_SERVER__TLS_CERTIFICATE
+# tls_certificate = '''...'''
+
+# if you want to use TLS (see 'use_tls' above), then you must specify
+# the server's private key.
+#
+# This is supposed to be PEM encoded X.509 private key. Similar to
+# the certificate, you can also use the `@/absolute/path/to/cert`
+# notation to make server load the certificate from some file.
+#
+# IMPORTANT: never commit config files containing inlined secrets
+# such as the private key into VCS. You can leverage the server's
+# ability to combine config from multiple files: have one file
+# without secrets and commit that to VCS if you so desire. The other
+# config file with secrets should be outside of VCS.
+#
+# env: GOODDATA_FLIGHT_SERVER__TLS_PRIVATE_KEY
+# tls_private_key = '''...'''
+
+# if you use mTLS and have self-signed certificates, then you must
+# also include the X.509 certificate of your CA that signed them.
+#
+# Again, you can inline the certificate in PEM encoding right here
+# into this setting, or you can use the '@/absolute/path/to/ca-cert'
+# notation.
+#
+# env: GOODDATA_FLIGHT_SERVER__TLS_ROOT_CERTIFICATE
+# tls_root_certificate = '''...'''
+
+#######################################################################
+#
+#######################################################################
+
+# specify authentication method to use. can be one of 'none' or 'token'.
+#
+# if you do not include this option, then the server will not do
+# any authentication. This is dangerous if your server is listening
+# on interfaces that are reachable from the public network.
+#
+# if you specify the 'token' method, then the default strategy
+# for verifying tokens is the 'EnumeratedTokenVerification'. For this
+# to work, you need to specify one or more valid tokens that the
+# client is expected to send. See the end of this file on how to
+# do this.
+#
+# Alternatively, you can implement your own strategy for verifying
+# tokens. See the option below.
+#
+# env: GOODDATA_FLIGHT_SERVER__AUTHENTICATION_METHOD
+authentication_method = "none"
+
+# Specify strategy to use for verifying tokens.
+#
+# The default strategy is 'EnumeratedTokenVerification' which expects
+# that client sends a token that is included in a list of allowed
+# tokens. See the end of this file for example how to define those
+# tokens.
+#
+# To implement your own token verification strategy, you need to
+# implement your own subclass of 'TokenVerificationStrategy' and
+# then modify this setting to provide module name that contains
+# that implementation.
+#
+# For example if the full path to class implementing your strategy
+# is my_server.auth.custom.MyCustomStrategy, then the value
+# of the 'token_verification' should be 'my_server.auth.custom'.
+#
+# Upon startup, the server will try to dynamically import and
+# load your implementation of TokenVerificationStrategy from the
+# specified module.
+#
+# env: GOODDATA_FLIGHT_SERVER__TOKEN_VERIFICATION
+# token_verification = "EnumeratedTokenVerification"
+
+# Optionally specify header name that is expected to carry the
+# token.
+#
+# If not specified, the token is expected to come in a HTTP-like
+# convention: the 'authorization' header (must be lower-case) and
+# the value of 'Bearer <token>' where <token> is the value token
+# itself.
+#
+# env: GOODDATA_FLIGHT_SERVER__TOKEN_HEADER_NAME
+# token_header_name = "x-custom-header-with-token"
+
+#######################################################################
+# Task Handling
+#######################################################################
+
+# Number of threads available for tasks which generate flights or
+# flight listing. Default is 32.
+#
+# Each GetFlightInfo request that generates a flight delegates this
+# to a task. The task executes in a thread pool of this size.
+#
+# Default is 32.
+#
+# env: GOODDATA_FLIGHT_SERVER__TASK_THREADS
+# task_threads = 32
+
+# Number of threads that will be used when closing used / unneeded
+# task results.
+#
+# Default is 2.
+#
+# env: GOODDATA_FLIGHT_SERVER__TASK_CLOSE_THREADS
+# task_close_threads = 2
+
+# Number of seconds a task result will be retained by the server.
+#
+# In other words, when GetFlightInfo uses task to generate the
+# flight, the result will be kept by the server for this number
+# of seconds - the client must come within this timeframe to pick
+# the data using DoGet.
+#
+# env: GOODDATA_FLIGHT_SERVER__TASK_RESULT_TTL_SEC
+# task_result_ttl_sec = 60
+
+#######################################################################
+# Server Infrastructure & Maintenance
+#######################################################################
+
+# host to bind prometheus metrics endpoint; disabled by default
+#
+# use:
+#
+# - 0.0.0.0 - to bind to all addressed
+# - 127.0.0.1 - to bind to localhost only (unreachable via outside network)
+# - custom address to bind to
+#
+# if not specified, the prometheus metrics endpoint will not be started
+#
+# env: GOODDATA_FLIGHT_SERVER__METRICS_HOST
+# metrics_host = "0.0.0.0"
+
+# port for prometheus metrics endpoint; default is 17101
+#
+# will only be used if `metrics_host` is specified
+#
+# env: GOODDATA_FLIGHT_SERVER__METRICS_PORT
+# metrics_port = 17101
+
+# host to bind health check endpoint; disabled by default
+#
+# use:
+#
+# - 0.0.0.0 - to bind to all addressed
+# - 127.0.0.1 - to bind to localhost only (unreachable via outside network)
+# - custom address to bind to
+#
+# if not specified, the health check endpoint will not be started
+#
+# env: GOODDATA_FLIGHT_SERVER__HEALTH_CHECK_HOST
+# health_check_host = "0.0.0.0"
+
+# port for health check endpoint; default is 8877
+#
+# will only be used if `health_check_host` is specified
+#
+# env: GOODDATA_FLIGHT_SERVER__HEALTH_CHECK_PORT
+# health_check_port = 8877
+
+# optionally specify interval, in seconds, of calls to malloc_trim - this
+# helps to release unused memory back to the system. Default is 30 seconds.
+#
+# especially useful in memory constrained and memory-limited environments.
+#
+# env: GOODDATA_FLIGHT_SERVER__MALLOC_TRIM_INTERVAL_SEC
+# malloc_trim_interval_sec = 30
+
+# optionally specify key name under which the log event name should appear
+# in the structured logs. Default is 'event'
+#
+# you may want to override this in case you want to align the event's key
+# name with the rest of your environment
+#
+# env: GOODDATA_FLIGHT_SERVER__LOG_EVENT_KEY_NAME
+# log_event_key_name = "event"
+
+# optionally specify mapping for telemetry (tracing) key names that will appear
+# in structured logs. by default, server writes trace information into 'trace_id',
+# 'span_id' and 'parent_span_id'
+#
+# you may want to override these in case you want to align those logs key names
+# with the rest of your enviornment
+#
+# env: GOODDATA_FLIGHT_SERVER__LOG_TRACE_KEYS
+# log_trace_keys = { "trace_id" = "trace_id", "span_id" = "trace_id", "parent_span_id" = "parent_span_id" }
+
+# optionally enable exports of OpenTelemetry tracing. Default is no exports
+# which also means most of the tracing code and instrumentation will be noop.
+#
+# Allowed values are: zipkin, otlp-grpc, otlp-http or console (for debug)
+#
+# IMPORTANT: If you want to enable the trace exports, you must install one
+# the appropriate OpenTelemetry exporter package yourself and then configure
+# the exporter using the appropriate environment variables (these are typically
+# documented by the exporter)
+#
+# env: GOODDATA_FLIGHT_SERVER__OTEL_EXPORTER_TYPE
+otel_exporter_type = "none"
+
+# optionally specify OpenTelemetry service name to associate with the server's
+# resource.
+#
+# If you do not specify the service name, then the tracing infrastructure and
+# instrumentation will be no-op.
+#
+# IMPORTANT: if you want to enable and export OpenTelemetry tracing, then you
+# must specify both the `otel_exporter_type` and this option.
+#
+# env: GOODDATA_FLIGHT_SERVER__OTEL_SERVICE_NAME
+# otel_service_name = "your-service-name"
+
+# optionally specify OpenTelemetry namespace to associate with this server's resource.
+#
+# Default is no namespace.
+#
+# env: GOODDATA_FLIGHT_SERVER__OTEL_SERVICE_NAMESPACE
+# otel_service_namespace = "your-namespace"
+
+# optionally specify OpenTelemetry service instance id to associate with this server's
+# resource.
+#
+# Usually, this is a unique identifier of the running server instance. In environments
+# such as k8s, you typically want to associate the instance id to pod name. In other
+# environments, it may be the hostname.
+#
+# Default is to use current hostname.
+#
+# env: GOODDATA_FLIGHT_SERVER__OTEL_SERVICE_INSTANCE_ID
+# otel_service_instance_id = "your-service-instance-id"
+
+# optionally specify whether OpenTelemetry integration within the server should look
+# for, extract and use an OpenTelemetry context coming through the Flight RPC
+# request headers.
+#
+# When this option is enabled, the code will use OpenTelemetry's context
+# propagation `extract` method to obtain the context from Flight RPC request headers. This
+# context will then be used when creating OpenTelemetry span representing the Flight
+# RPC call.
+#
+# In simple words:
+#
+# - IF your server is configured to export traces to same backend where your server's clients
+#   also export their traces AND the clients inject the trace context into the Flight RPC headers AND
+#   you turn this option on, THEN you will be able to correlate all calls under one trace ID.
+#
+# - ELSE, you should keep this turned off; each Flight RPC request to your server will create
+#   a new trace ID.
+#
+# Default is false.
+#
+# env: GOODDATA_FLIGHT_SERVER__OTEL_EXTRACT_CONTEXT
+# otel_extract_context = false

gooddata_flight_server-1.53.1.dev1/tests/__init__.py

@@ -0,0 +1 @@
+# (C) 2024 GoodData Corporation

gooddata_flight_server-1.53.1.dev1/tests/assert_error_info.py

@@ -0,0 +1,12 @@
+#  (C) 2024 GoodData Corporation
+import pyarrow.flight
+from gooddata_flight_server.errors.error_code import ErrorCode
+from gooddata_flight_server.errors.error_info import ErrorInfo
+
+
+def assert_error_code(code: int, err: pyarrow.flight.FlightError):
+    info = ErrorInfo.maybe_from_pyarrow_error(err)
+    assert info is not None, "The error does not contain the ErrorInfo."
+
+    if code != info.code:
+        raise AssertionError(f"Expected error code '{ErrorCode.name(code)}'. Got: '{ErrorCode.name(info.code)}'")

gooddata_flight_server-1.53.1.dev1/tests/config/__init__.py

@@ -0,0 +1 @@
+#  (C) 2024 GoodData Corporation

gooddata_flight_server-1.53.1.dev1/tests/config/auth-config.toml

@@ -0,0 +1,6 @@
+# (C) 2024 GoodData Corporation
+[server]
+
+authentication_method = "token"
+token_header_name = "x-my-header"
+token_verification = "EnumeratedTokenVerification"

gooddata_flight_server-1.53.1.dev1/tests/config/empty-config.toml

@@ -0,0 +1,5 @@
+# (C) 2024 GoodData Corporation
+[server]
+
+# nothing here
+# let's see how the defaults work out

gooddata_flight_server-1.53.1.dev1/tests/config/private_key.pem

@@ -0,0 +1 @@
+The matrix has you :D

gooddata_flight_server-1.53.1.dev1/tests/config/sample-config.toml

@@ -0,0 +1,34 @@
+# (C) 2024 GoodData Corporation
+[server]
+
+#######################################################################
+# Flight RPC Setup
+#######################################################################
+
+listen_host = "127.0.0.1"
+listen_port = 17001
+advertise_host = "127.0.0.1"
+advertise_port = 17001
+
+#######################################################################
+# Task Handling
+#######################################################################
+
+task_threads = 32
+
+#######################################################################
+# Server Infrastructure & Maintenance
+#######################################################################
+
+metrics_host = "0.0.0.0"
+metrics_port = 17101
+health_check_host = "0.0.0.0"
+health_check_port = 8877
+malloc_trim_interval_sec = 30
+log_event_key_name = "event"
+log_trace_keys = { "trace_id" = "trace_id", "span_id" = "trace_id", "parent_span_id" = "parent_span_id" }
+otel_exporter_type = "otlp-grpc"
+otel_service_name = "your-service-name"
+otel_service_namespace = "your-namespace"
+otel_service_instance_id = "your-service-instance-id"
+otel_extract_context = true