Fresh Install if ELK 7.10 floods deprecation log

Elastic Stack Elasticsearch
#1

A fresh install of ELK 7.10 fills the deprecation log once Kibana is installed.

[2020-12-29T14:12:46,624][DEPRECATION][o.e.d.a.a.i.a.g.TransportGetAliasesAction] [app01] this request accesses system indices: [.kibana_1], but in a future major version, direct access to system indices will be prevented by default
[2020-12-29T14:12:46,977][DEPRECATION][o.e.d.c.m.IndexNameExpressionResolver] [app01] this request accesses system indices: [.kibana_1], but in a future major version, direct access to system indices will be prevented by default

In the JSON log they are de-duplicated, but in the plaintext log they generate several per second.

Fresh Install if ELK 7.10 floods deprecation log
#2

Welcome to our community! :smiley:

Do you want to disable this, or are you looking for something else?

#3

Well, I would have expected that on a clean install that the elastic components themselves would not be using deprecated features. Additionally, Why are they spamming? Shouldn't they be deduplicated like they are in the .json version?

I've seen all over the place that it's bad practice to disable the deprecation log, so I don't think that's the right answer. Is there a way to disable the .log version but keep the .json version so that they don't cause excessive writes to the disk as they spam like crazy?

#4

That sounds like a reasonable expectation, I suggest you ask the Kibana folks about this. The deprecation seems to have been added just before feature freeze so maybe it slipped through the net.

That's also a good question. These messages are deduplicated, but not if they all use different X-Opaque-Id headers. Perhaps that's what is happening?

#5

How can I get that information from the log? I'd love to help troubleshoot.

#6

Weirdly I think the X-Opaque-Id header is logged, but only in the JSON output. I don't really understand how to align what you've reported with what I'm reading in the code, but this isn't an area with which I'm very familiar so I'm sure it makes sense to someone else.

#7

Hopefully someone from the Kibana team sees this. I haven't figured out how to add that tag to this post.

#8

Ah I meant that I was suggesting opening a thread on the Kibana forum.

#10

Done and done: Fresh Install if ELK 7.10 floods deprecation log

:grinning:

1 Like