-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Help with slow logs getting cut off #76515
Comments
Pinging @elastic/es-search (Team:Search) |
Pinging @elastic/es-core-infra (Team:Core/Infra) |
@nik9000 I guess you are talking about plaintext slow logs in version before 7.x? or the config is stale? for indexing slow log we still truncate and it is configurable by can you confirm the version and the provide the logging config? |
We discussed it in a fix-it meeting. Having requests cut off in the slowlog is a big deal for troubleshooting production issues, and even if we had it entirely by raising the maximum length of a slowlog entry, the fact that it's so verbose makes it hard to read by a human. So the preferred route would be to stop serializing parameters when they have the default value. We couldn't think of a component that would break if we stopped serializing default values. @nik9000 will try out by no longer serializing the |
This removes defaults from the output of the `match` query's `toXContent`. That'll make it take up less room in the slow log. And anywhere else is shows up. Relates to elastic#76515
It looks like it's been omitting the default |
This removes the `boost` from the `toXContent` of `rank_feature` if it is the default. It also removes the score function if it is the default. Relates to elastic#76515
This removes the defaults from the `toXContent` of the `has_child` query so slow logs that contain it are marginally easier to read. Relates to elastic#76515
This removes the `boost` from the `toXContent` of `rank_feature` if it is the default. It also removes the score function if it is the default. Relates to #76515
This removes the defaults from the `toXContent` of the `has_child` query so slow logs that contain it are marginally easier to read. Relates to #76515
This removes the defaults from the slow log for the remaining queries in the `parent-join` module. So it should be easier to read the slow log when it contains these queries. Relates to elastic#76515
This removes the defaults from the slow log for the remaining queries in the `parent-join` module. So it should be easier to read the slow log when it contains these queries. Relates to #76515
|
Relates to elastic#76515
This removes the defaults from the slow log for the remaining queries in the `parent-join` module. So it should be easier to read the slow log when it contains these queries. Relates to elastic#76515
Mostly this is just removing boosts, but it also simplifies span_not slightly. It also removes the boost parameter from term, as that shares an implementation with span_term. Relates to #76515
This slims down the representations of all remaining queries not in the core * percolate * function_score * script_score * pinned Relates to #76515
Pinging @elastic/es-search-foundations (Team:Search Foundations) |
One of our key features for debugging is the slow log - but when folks have very large _searches we can end up with cut off slow logs. Something chops them. I recall that we had something to do that but I can't find it at the moment. Maybe its some external tool doing the chopping
Anyway! Maybe we could make the slow logs shorter by not outputting default parameters when we toXContent the search's source. Or something. I dunno. I've just been frustrated lately when looking at slow logs from folks that are cut off and want to do something about it.
The text was updated successfully, but these errors were encountered: