markmcdowell / NLog.Targets.ElasticSearch

NLog target for Elasticsearch
MIT License
176 stars 89 forks source link

Writing to data stream in elastic returns an error #132

Closed hmlmartins closed 4 years ago

hmlmartins commented 4 years ago

Hello,

I set up my index to be a data stream in elastic but I get an error stating the request should have op_type: create.

Is there a way to overcome, or is this not ready yet to work with data streams?

Thank you

snakefoot commented 4 years ago

@hmlmartins You can try this pre-release nuget-package (Artifact from PR #133) to see if resolves your problem (Just place in local nuget-folder).

It introduces a new option called OpCodeCreate that can be used like this:

<target xsi:type="ElasticSearch" uri="http://localhost:9200/" opCodeCreate="true" />
hmlmartins commented 4 years ago

unfortunately the lib version we are using comes bundled with another software tool we have in place.

I will have to wait for them to update. Is it possible to get notice of when it is no longer pre-release?

Thanks

On Wed, Oct 28, 2020 at 7:08 PM Rolf Kristensen notifications@github.com wrote:

@hmlmartins https://github.com/hmlmartins You can try this pre-release nuget-package https://ci.appveyor.com/api/buildjobs/nws831ap6fnwg1pt/artifacts/src%2FNLog.Targets.ElasticSearch%2Fbin%2FRelease%2FNLog.Targets.ElasticSearch.7.1.20-alpha-bamrajut.nupkg to see if resolves your problem (Just place in local nuget-folder).

It introduces a new option called OpCodeCreate that can be used like this:

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/markmcdowell/NLog.Targets.ElasticSearch/issues/132#issuecomment-718148138, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABL7K5U665JP2EJ7XP6NK6DSNBT3RANCNFSM4TBRPZJQ .

snakefoot commented 4 years ago

Sadly enough it will stay pre-release until someone validates it is working.

So maybe create a small test tool that depends on the provided pre-release nuget-package. And do a quick test?

hmlmartins commented 4 years ago

Thanks for the feedback

We have a small dev environment, maybe I will be able to test it. Not really sure when. Best estimate at the moment is the end of year. But I'll keep an eye out for changes and eventually provide some feedback.

Regards,

On Thu, Oct 29, 2020 at 8:26 AM Rolf Kristensen notifications@github.com wrote:

Sadly enough it will stay pre-release until someone validates it is working.

So maybe create a small test tool that depends on the provided pre-release nuget-package. And do a quick test?

Sent from my Sony Xperia

---- hmlmartins wrote ----

unfortunately the lib version we are using comes bundled with another software tool we have in place.

I will have to wait for them to update. Is it possible to get notice of when it is no longer pre-release?

Thanks

On Wed, Oct 28, 2020 at 7:08 PM Rolf Kristensen notifications@github.com wrote:

@hmlmartins https://github.com/hmlmartins You can try this pre-release nuget-package < https://ci.appveyor.com/api/buildjobs/nws831ap6fnwg1pt/artifacts/src%2FNLog.Targets.ElasticSearch%2Fbin%2FRelease%2FNLog.Targets.ElasticSearch.7.1.20-alpha-bamrajut.nupkg

to see if resolves your problem (Just place in local nuget-folder).

It introduces a new option called OpCodeCreate that can be used like this:

<target xsi:type="ElasticSearch" uri="http://localhost:9200/" opCodeCreate="true" />

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/markmcdowell/NLog.Targets.ElasticSearch/issues/132#issuecomment-718148138 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABL7K5U665JP2EJ7XP6NK6DSNBT3RANCNFSM4TBRPZJQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub< https://github.com/markmcdowell/NLog.Targets.ElasticSearch/issues/132#issuecomment-718453818>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/ACXZ7HAQD7FCKJWQAWHTNYTSNEOSBANCNFSM4TBRPZJQ

.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/markmcdowell/NLog.Targets.ElasticSearch/issues/132#issuecomment-718472932, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABL7K5WS47LK2AHKSAO4EHTSNERLBANCNFSM4TBRPZJQ .

snakefoot commented 4 years ago

But I'll keep an eye out for changes and eventually provide some feedback.

Excellent. Looking forward to hear about the test results.

TheDruidsKeeper commented 4 years ago

I ran into this issue as well, so I took the time to test the PR build and it worked perfectly for me. I'm using elastic v7.9.1, and verified with the prelease package that I could still write to traditional (non data stream) indexes both with & without opCodeCreate="true". Writing to the datastream isn't successful without the opCodeCreate enabled (as expected), and is successful with it. image

snakefoot commented 4 years ago

ElasticSearch ver. 7.5.0 has been released: https://www.nuget.org/packages/NLog.Targets.ElasticSearch