Sriram Hariharan’s Post

Users can quickly implement Elasticsearch on AlmaLinux by following simple installation steps to get robust data management and search features. https://lnkd.in/gRc5B_2f

Users can quickly implement Elasticsearch on AlmaLinux by following simple installation steps to get robust data management and search features. https://lnkd.in/gdwf_5Zh

Users can quickly implement Elasticsearch on AlmaLinux by following simple installation steps to get robust data management and search features. https://lnkd.in/eF-kPAXG

Users can quickly implement Elasticsearch on AlmaLinux by following simple installation steps to get robust data management and search features. https://lnkd.in/gvjdSZJT

Users can quickly implement Elasticsearch on AlmaLinux by following simple installation steps to get robust data management and search features. https://lnkd.in/er8AghKM

Users can quickly implement Elasticsearch on AlmaLinux by following simple installation steps to get robust data management and search features. https://lnkd.in/eyHuusUd

Need to run 𝑲𝑸𝑳 𝒒𝒖𝒆𝒓𝒊𝒆𝒔 against multiple 𝘫𝘴𝘰𝘯 𝘧𝘪𝘭𝘦𝘴 archived as blobs, maybe in a complex containers hierarchy, in 𝑨𝒛𝒖𝒓𝒆 𝑺𝒕𝒐𝒓𝒂𝒈𝒆 𝑨𝒄𝒄𝒐𝒖𝒏𝒕𝒔? The best option is to use 𝐀𝐳𝐮𝐫𝐞 𝐃𝐚𝐭𝐚 𝐄𝐱𝐩𝐥𝐨𝐫𝐞𝐫 (𝐀𝐃𝐗) as described here: https://lnkd.in/dZNCi3JA #MicrosoftLogAnalytics #MicrosoftSentinel #AzureDataExplorer

#BigQuery's native integration with Delta Lake’s log allows its query engine to leverage valuable metadata, simplifying the process of querying Delta tables with improved performance and granular security controls. In this blog post, learn how to query Delta tables using BigQuery. 🔗 https://lnkd.in/eacAaCr4 cc Gaurav Saxena, Justin Levandoski #opensource #oss #deltalake #lfaidata

If it’s not in the logs, did it really happen? Logs are the foundational data of any #observability effort. Learn how #Elasticsearch allows us to store, search and analyze huge volumes of data quickly. https://okt.to/ZmXYA3

I see a lot of amazing people sharing great KQL queries on here, but if you want to supercharge the results from your queries, where possible, change those 'contains' operators to using 'has', why? Each string in Kusto is broken into terms that are 3 or more alphanumerical characters, and they are then indexed for you. So, if you have '1234-abcd-LinkedIn', you get the terms '1234', 'abcd' and 'LinkedIn'. You can then use 'has' to find any of those terms a lot faster than 'contains' ever would, for instance. | where Data has "abcd" If a term is fewer than 3 characters, or you use 'contains' Kusto will scan the values in the column to find them, much slower! 'has' is especially valuable for security telemetry, because a lot of the data we work with is naturally indexed for us, for example, a file path c:\users\downloads\bad.exe - use 'has' to find users, downloads, bad, exe Anything that is JSON will be wrapped in quotes and commas for you, domains are separated by full stops, so they are all indexed ready to search on. Then you can use operators like has_any, or has_all or !has. Try them out, I guarantee it will be much faster! https://lnkd.in/gVnwysSY