Would you like to present? Tag @kris@dtaivpp@nateynate and we’ll work to get you added to the agenda!
Feel free to comment on this agenda before the meeting if you want to add an item or have a question.
After the meeting, we will post the chat log and any meeting notes. We welcome you to keep the conversation going here on the forum.
======== By joining the OpenSearch Community Meeting, you grant OpenSearch, and our affiliates the right to record, film, photograph, and capture your voice and image during the OpenSearch Community Meeting (the “Recordings”). You grant to us an irrevocable, nonexclusive, perpetual, worldwide, royalty-free right and license to use, reproduce, modify, distribute, and translate, for any purpose, all or any part of the Recordings and Your Materials. For example, we may distribute Recordings or snippets of Recordings via our social media outlets.
15:05:12 From Kris Freedain to Everyone:
OpenSearchCon 2023 - Call for Presentations!!! OpenSearchCon 2023 Call for Presentations · OpenSearch
15:05:46 From Kris Freedain to Everyone:
See you at Berlin Buzzwords this year! https://2023.berlinbuzzwords.de/
15:06:13 From Kris Freedain to Everyone:
OpenSearch 2.7.0 is out!! Get Started with OpenSearch 2.7.0 · OpenSearch
15:06:57 From Kris Freedain to Everyone:
OpenSearch 1.3.10 is out as well! Opensearch 1.3.10 · OpenSearch
15:08:01 From Joshua Bright to Everyone:
Woot flat objects!
15:08:36 From Simeon Widdis to Everyone:
Was just saying last week “man it would be cool if opensearch let me cleanly index flat objects”
15:11:02 From dtip to Everyone:
Simeon I am glad we could come in clutch for you
15:11:20 From Kris Freedain to Everyone:
Give us your feedback! Thank you https://amazonmr.au1.qualtrics.com/jfe/form/SV_1BxJNrtCo4LbweW
15:11:33 From Daniel Doubrovkine to Everyone:
Intel has contributed ZSTD and is working on a blog post. We’ve benchmarked the change and are seeing a 14% throughput (!) improvement with ZSTD NO-DICT over LZ4.
15:11:48 From Daniel Doubrovkine to Everyone:
Throughput on write.
15:11:55 From Joshua Bright to Everyone:
We love Windows
15:13:15 From Nitin Chandra (AWS) to Everyone:
Woot for OpenTelemetry !
15:18:39 From Nitin Chandra (AWS) to Everyone:
I have a telescope just like that! Alas, my kid never got interested in astronomy, so now the spiders in my garage use it to get an advance view on the insects
15:22:22 From lior perry to Everyone: GitHub - YANG-DB/opentelemetry-demo at opensearch-observability-otel
15:23:35 From Ani ( OpenSearch ) to Everyone:
Direct PromQL is also supported/
15:24:01 From GSmith to Everyone:
Do you envision storing metrics in Prometheus as a standard thing or is that just to show how “open” things are?
15:26:18 From Nitin Chandra (AWS) to Everyone:
Great demo - Lior!
15:26:23 From Ani ( OpenSearch ) to Everyone:
Thanks a ton, @lior!
15:26:26 From Joshua Bright to Everyone: META - Augmenting Visualizations with Alerts · Issue #457 · opensearch-project/alerting-dashboards-plugin · GitHub
15:26:49 From lior perry to Everyone:
Thanks so much for having me - sorry but have to drop
15:31:59 From Nathan Boot to Everyone:
So the line graph represents the number of anomalies?
15:33:20 From Joshua Bright to Everyone:
In the first release, we will support creating per query monitors from visualizations. Associating monitors for per bucket, per document, or per cluster metric can be associated as well.
15:34:17 From Joshua Bright to Everyone:
The line graph represents an aggregation… one can create a monitor or detector based on the aggregation(s)
15:34:35 From ohltyler to Everyone:
There will be tooltips on the event triangles with more details
15:36:06 From Nathan Boot to Everyone:
Won’t yo uhave to restart the detector since you’ve changed its features?
15:36:59 From ohltyler to Everyone:
Replying to “Won’t yo uhave to re…”
The detectors/monitors aren’t created until the user creates. We just try to pre-populate some configuration based on the visualizations
