We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The approach to Data Stream naming in the connector is too restrictive. Right now the only option we have is to pattern the data stream name like so:
<data.stream.type>-<data.stream.dataset>-<topic>
This pattern doesn't even really allow us to match the common data steam naming scheme which, in kafka terms, would look a bit more like:
<type>-<topic>-<namespace>
And further, the data.stream.type can only be "metrics" or "logs".
None of these restrictions exist in elasticsearch itself; they are only imposed by the connector.
We should really be able to specify the entire data stream name, using some basic substitution variables (for topic name, etc.) in the string.
The text was updated successfully, but these errors were encountered:
+1
Sorry, something went wrong.
Was this problem ever tackled ? @sduff @mcb
The method is using data.stream.namespace property to change the output datastream name
No branches or pull requests
Uh oh!
There was an error while loading. Please reload this page.
The approach to Data Stream naming in the connector is too restrictive. Right now the only option we have is to pattern the data stream name like so:
This pattern doesn't even really allow us to match the common data steam naming scheme which, in kafka terms, would look a bit more like:
And further, the data.stream.type can only be "metrics" or "logs".
None of these restrictions exist in elasticsearch itself; they are only imposed by the connector.
We should really be able to specify the entire data stream name, using some basic substitution variables (for topic name, etc.) in the string.
The text was updated successfully, but these errors were encountered: