Comments (8)
... and for OnPremise Clusters it requires additional configs on the external loadbalancers
seems very counter intuitive for something that works very easy in all other regards..
from logstash-output-opensearch.
@erSitzt Thanks for creating an issue. Do you have a proposal that introduce this change without affecting existing configurations?
from logstash-output-opensearch.
Hi @VijayanB ,
maybe an additional parameter that, when set, overrides appending the port.
as it would mostly benefit users who want to use the host header only, it could be a true/false flag defaulting to false
use_http_host_header_only => true
something like this ? i'm bad at naming stuff, but you should get the intention ;)
from logstash-output-opensearch.
Hi @erSitzt , Thanks for suggestion. What do you think of creating new config called "port" with default value as 9200 and behavior as follows
- use defaults.
The below configuration will have host as "hostname:9200"
opensearch { hosts => ["hostname"] user => "admin" password => "admin" index => "logstash-logs-%{+YYYY.MM.dd}" }
- override default port
The below configuration will have host as "hostname:1234"
opensearch {
hosts => ["hostname"]
port => "1234"
user => "admin"
password => "admin"
index => "logstash-logs-%{+YYYY.MM.dd}"
}
- Don't append port using above apporach
The below configuration will have host as "hostname"
opensearch {
hosts => ["hostname"]
port => ""
user => "admin"
password => "admin"
index => "logstash-logs-%{+YYYY.MM.dd}"
}
from logstash-output-opensearch.
It would be ok for my situation, but wouldnt it confuse people switching from ES to OpenSearch version ?
Because it's "Hosts" and not "Host" ?
the original examples were like this, so how would you handle different ports for different hosts ?
"127.0.0.1"
["127.0.0.1:9200","127.0.0.2:9200"]
["http://127.0.0.1"]
["https://127.0.0.1:9200"]
["https://127.0.0.1:9200/mypath"]
(If using a proxy on a subpath)
My approach would only take affect when NO port is defined for any of the hosts and then NOT to default to 9200 to allow named based routing in a load-balancer
I think this would have less impact and cause less confusion for people familiar with logstash from Elastic
from logstash-output-opensearch.
I would prefer just to be able to opt out of this default here
from logstash-output-opensearch.
hey @VijayanB is there any progress on this ?
from logstash-output-opensearch.
Sorry @erSitzt, the team has not had a chance to prioritize this work. We will review work across clients again in the Jul-Aug timeframe. This would be a good candidate for help wanted though so I'm adding the proper label.
from logstash-output-opensearch.
Related Issues (20)
- 403 errors when delivering logs to AWS OpenSearch Serverless after a successful period HOT 27
- Include an offline logstash zip in the release
- Release a new docker image for logstash-oss-with-opensearch-output-plugin HOT 17
- Could not connect to a compatible version of Elasticsearch - Opensearch 2.9.0-1 - Logstash OutputPlugin 8.9.0 HOT 2
- [BUG] Getting code 400 in logstash with http_compression enabled HOT 1
- [v2.12.0] Ensure CI/documentation reflect changes to default admin credentials
- Build using logstash >=8.10 HOT 5
- [BUG] Unexpected behaviour if remote Opensearch response is not "common" HOT 2
- [BUG] 503 Error encountered during the upgrade of Logstash from version 8.10.4 to 8.12.1 HOT 3
- [QUESTION] logstash appending 9200 to opensearch endpoint in k8s HOT 1
- [QUESTION] Clarification on Data Processing Order During Outages HOT 2
- Lower the number of required approvers for CRs to 1 HOT 4
- upload of logstash-oss-with-opensearch-plugin docker container version 8.12 HOT 2
- [BUG] In case of multiple end-points defined in opensearch.hosts - the events are being distributed using a round-robin mechanism instead of being sent to all endpoints HOT 2
- [BUG] Enabling this plugin affect the elasticsearch output (Only Opensearch output works) HOT 1
- Ingest data to opensearch data stream from logstatsh. HOT 1
- Unable to create template on open search 1.3 getting 400 error HOT 13
- Document building and debugging logstash-output-opensearch
- Add detail reported with 400 errors
- Release v. Next HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from logstash-output-opensearch.