mstdn.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A general-purpose Mastodon server with a 500 character limit. All languages are welcome.

Administered by:

Server stats:

12K
active users

#elasticsearch

4 posts4 participants1 post today

Habe grad Spaß dabei, die manuell grenzwertig zu lesenden Catalina-Logs von Tomcat-Servern mittels Prometheus-Exporter schön sauber nach Elasticsearch und auf die Kibana-Dashboards zu bringen.

Erstmal nur als Test.

Aber wenn das gut funktioniert, lichtet sich das Dickicht auf so vielen Systemen.

Any #OpenSearch / #ElasticSearch folks (users, developers, experts, aficionados, etc) out here?

I’m doing some search tuning and would love to have something that can take the “explain” output and convert it to something more human readable. Getting something per individual result would be useful, but even more helpful would be something that can take all the explanations from all the results of a query and help to explain why one result was ranked above others.

Also, if you know of good resources to guide someone through the tuning/improvement process (both on the searching and indexing side), that’d be helpful, too.

My biggest issue right now is exact matches not beating out prefix matches (e.g. a search for “Foo” returning “Foo Bar” before “Foo”).

#elasticsearch 9.1 / 8.19 release: continuing the optimizations, also for time-series — LogsDB and TSDS (time-series datastream)
storage is commonly the most painful part, especially with longer retentions. but we're getting to 2x to 4x improvements over default indices 1/6

#elasticsearch 9.1 / 8.19 release 🥳: how to improve ranking, latency & cost for dense vector search at the same time — by defaulting to better binary quantization (BBQ). even if improving all 3 is counter intuitive
quick overview of what's new with a focus on semantic_text but dense_vector is similar 1/6

thread + article on #elasticsearch alerting options:
* kibana alerts if you need something simple
* watcher for way more options

watcher example for: "alert when users from the US, Germany, and India dropped below 1000 in the last hour compared to yesterday"

also covering the pattern of writing alerts to an index to operate on them there. and how to automate all of it with #GitOps

full article: one2n.io/blog/transforming-ale

Continued thread

Yeah now I've a purely #elasticsearch #esc issue, When I try to send a new event the call fails with a 500 and cryptic error, and google is not helpful...

STATUS: 500, BODY: {
"error": {
"reason": "[_data_stream_timestamp] meta field has been disabled",
"root_cause": [
{
"reason": "[_data_stream_timestamp] meta field has been disabled",
"type": "illegal_state_exception"
}
],
"type": "illegal_state_exception"
},
"status": 500
}

Hey rustaceans, I need to plug my #axum server which uses the tracing crate for logs to our elasticsearch logging service, which uses ESC I believe?
It seems there's no off the shelf tracing_layer to talk to elasticsearch , and trying to write my own I'm running in the issue of needing to use an async method to send the message from a sync context (on_event() of tracing::Layer). Anything I've missed to make my live easier? #rustlang #tokio #elasticsearch

today is one of my favorite days: release day!
#elasticsearch and the entire elastic stack 9.1 and 8.19 are out. lots of great stuff in there — I'll pick one feature a day to dive into 🔬
but first, versions and updates: 2 majors in parallel? what about 7.x? how to upgrade? and what even is maintained today?