Closed dyrnq closed 4 months ago
@medcl Thanks for reporting this, can you also attach your configurations, i just did a test with this config:
env:
LR_GATEWAY_HOST: 127.0.0.1:8001
LR_GATEWAY_API_HOST: 127.0.0.1:9000
ELASTICSEARCH_ENDPOINT: ['https://127.0.0.1:9200']
path.data: data
path.logs: log
stats:
enabled: false
entry:
- name: my_es_entry
enabled: true
router: my_router
max_concurrency: 10000
network:
binding: $[[env.LR_GATEWAY_HOST]]
flow:
- name: es-flow
filter:
- elasticsearch:
elasticsearch: es-server
refresh:
enabled: true
interval: 10s
fixed_client: true
client_mode: host
timeout: -1
skip_cleanup_hop_headers: true
skip_keep_original_uri: true
skip_metadata_enrich: true
router:
- name: my_router
default_flow: es-flow
elasticsearch:
- name: es-server
enabled: true
endpoints: $[[env.ELASTICSEARCH_ENDPOINT]]
basic_auth:
username: admin
password: xxx
discovery:
enabled: true
refresh:
enabled: true
interval: 60s
Seems all good:
fell free to reopen or provide more details.
Description
ref https://www.elastic.co/guide/en/elasticsearch/reference/8.12/api-conventions.html#api-date-math-index-names
Steps to reproduce
curl call put index API
Actual behavior
A description of what you expected to happen.
Expected behavior
Environment
Build:
[GATEWAY] A light-weight, powerful and high-performance search gateway. [GATEWAY] 1.21.0#1229, 2023-12-28 08:22:36, 2024-12-31 10:10:10, 5ca75b9539303a3ceb62e37e72811b580e7e004f gateway 1.21.0 1229 2023-12-28 08:22:36 +0000 UTC 2024-12-31 10:10:10 +0000 UTC 5ca75b9539303a3ceb62e37e72811b580e7e004f