-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
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
Ingest API #5199
Comments
+1 for this feature |
+1 👍 |
+1 |
1 similar comment
+1 |
Hi, Is this endpoint now available for Kibana? |
Hi @trekr5 This feature is still in progress and hasn't been merged yet. |
+1 |
Hey @Bargs - we super-duper want this feature. How far through implementation are you? Would love to roll up our sleeves and help if your bandwidth is split across other duties. |
+1 |
+1 thanks! |
on which release will this make it ? |
It's been merged into master, so 5.0. |
@Bargs oh i see...shame as i believe is long way till will be released. I was hopping will get into current minor 4.x release |
+1 for minor 4.x. release |
+1 |
Very cool indeed if this would be possible for 4.x.minors! |
+1 for minor 4.x. release |
Great ! We'll be very excited once it is available! |
hey, is this feature available in Kibana 5.x ? You added the label but i found no further documentation about that API call. Thanks |
Hi @schmandforke, this feature was removed from 5.0. It does not currently have a target release because it will most likely require some changes. |
Hey @Bargs, found a solution to realize this:
I actually not know, how long this route will exists, but by now - it works like a charm ;-) Thanks |
@schmandforke that's just a proxy for ES requests that we have in the Kibana backend. It's no different than sending the same request to elasticsearch directly. We'd like to get rid of the proxy eventually, but I don't think it will go away any time soon. |
+1 for this feature - very badly needed. Realizing that this has been put aside for the moment, a good substitute might be an unofficial gist showing curl commands to do things like add an index pattern or create a scripted field, etc. |
Here's a very simple example for creating index patterns and setting a default by (ab)using the Kibana "Api": |
If you would prefer a method for loading dashboards and indexpatterns from the file-system (for use with Chef, Puppet, Salt, etc) please vouch for it here: #2310 |
This feature was removed from 5.0. It does not currently have a target release because it will most likely require some changes.
Related to #3709
Goal is to provide API endpoints for the creation of Kibana index patterns and index templates. These will be implemented in the Kibana server.
Here is a rough initial stab at what the endpoints might look like:
POST /api/kibana/ingest
Create a new index pattern and template.
Requires the JSON formatted index pattern in the body of the request.
Properties include:
title
: String (Required)timeFieldName
: String (optional, only needed for time based index patterns)intervalName
: Stringfields
: Object (optional, auto-generated if missing and existing indexes match pattern)fieldFormatMap
: Object (optional, map of non-default formatters to user for fields)Need a place for mapping info. This might go in the fields object, or it might go in a separate property like
fieldFormatMap
Title will be used as the document ID.
DELETE /api/kibana/ingest/{id}
Delete an index pattern and its template.
The text was updated successfully, but these errors were encountered: