Jedr Blaszyk

Hey @khushbu-elastic , those errors are an obfuscated way that your request body is empty. We should add better error messages when the request body for connector creation is empty...

Also, you can refer to the postman collection with all API endpoints here: https://github.com/elastic/connectors/tree/main/resources/connectors_api

Hey @khushbu-elastic we have update index name endpoint that attached the index name to the connector: https://www.elastic.co/guide/en/elasticsearch/reference/master/update-connector-index-name-api.html All the available endpoints are listed in: https://www.elastic.co/guide/en/elasticsearch/reference/master/connector-apis.html

@khushbu-elastic there might be a gap in Kibana that causes this issue when index doesn't exist yet. You should be able to get around it when: - configuring your connector...

Linking relevant issue from aiohttp https://github.com/aio-libs/aiohttp/issues/4581 - maybe this will give us more insight into handling this edge case better for SPO. People also report that the connection being broken...

@navarone-feekery it was discussed that while such matrix can work well for stack, it will likely be problematic with serverless. If we can enforce in just for stack it should...

in `api_call` the `ServerDisconnectedError` should be probably logged as well (as we are closing the session and re-raising)

@moxarth-elastic could you share updated example DEBUG output, before we hit ✅

Hey @jfreden thank you for reviewing. Answering your questions: > The purpose is to switch everything that reads from the connector indices to use new actions in the ent-search plugin...

Hi @jfreden thank you for bringing this topic up in the Elasticsearch security team meeting > Sounds like there is a use case for Kibana where they need only read...