# elastic Published articles for elastic. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Elastic announces GA of cross-project search on Serverless, enabling teams to query across all linked projects without moving a byte DevFeed: [Elastic announces GA of cross-project search on Serverless, enabling teams to query across all linked projects without moving a byte]() Original publisher: [Read original article]() Author: Jordi Mon Companys,Lucy Wang Published: 2026-09-16T00:00:00Z Content type: release Language: en Sources: [Elastic Blog - Elasticsearch, Kibana, and ELK Stack]() Topics: [Serverless](), [Elastic Cloud](), [Cloud](), [observability](), [Security](), [SIEM, Security, Observability]() Tags: [architecture-cloud-migration-migrating-cloud-native-scaling-search-analytics-search-applicatio](), [cloud](), [cloud-elasticsearch-platform](), [customers](), [elastic](), [elastic-cloud](), [observability](), [observability-security-search](), [security](), [serverless]() ### AI overview Elastic announced the general availability of cross-project search for Elastic Cloud Serverless. It lets teams query multiple linked projects in a single session across regions, project types, and cloud providers, while keeping data in place and avoiding certificates, remote-cluster configuration, and per-connection authentication. ### Source excerpt Cross-project search is now GA on Elastic Cloud Serverless. Link multiple projects and query all of them from a single Discover or ES|QL session: no certificates, no remote cluster config, and three clicks to set up. Available from September 1, 2026. ## Elastic build machines now use Turborepo cache hits to prevent downgrades DevFeed: [Elastic build machines now use Turborepo cache hits to prevent downgrades]() Original publisher: [Read original article]() Author: Anthony Shew Published: 2026-08-24T16:11:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Cache](), [Caching](), [cpu]() Tags: [cache](), [cpu](), [documentation](), [elastic](), [memory]() ### AI overview Vercel's Elastic build machines now account for Turborepo cache hits when deciding whether to downgrade build resources. Warm-cache builds no longer cause a downgrade, helping ensure later cold-cache builds have enough CPU and memory to complete successfully. ### Source excerpt Elastic build machines now consider Turborepo cache hits when deciding whether to use a smaller build machine. A warm-cache build no longer triggers a downgrade. A warm-cache build can use less CPU and memory than the same build with a cold cache. Downgrading based on that lower usage could leave a later cold-cache build without enough resources to complete successfully. This change applies automatically to all builds using Elastic build machines. No action is required. Learn more in the build documentation. Read more ## How CockroachDB v26.1 Uses Elastic Admission Control and Go Scheduler Changes for Background Work DevFeed: [How CockroachDB v26.1 Uses Elastic Admission Control and Go Scheduler Changes for Background Work]() Original publisher: [Read original article]() Author: David Taylor Published: 2026-04-14T00:00:00Z Content type: article Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [Go Language](), [Concurrent Programming](), [Latency](), [cpu]() Tags: [background-work](), [backups](), [cockroachdb](), [elastic](), [latency](), [processes](), [statistics](), [work]() ### AI overview This article explains how CockroachDB v26.1 uses elastic admission control and a change to the Go runtime scheduler to let background work use spare CPU capacity while limiting its impact on query latency. ### Source excerpt CockroachDB runs background work -- backups, schema changes, statistics collection, changefeeds -- in the same processes that serve user queries. Traditionally, this creates a tension... ## Introducing Chainguard Commercial Builds: Secure-by-default containers for commercial software DevFeed: [Introducing Chainguard Commercial Builds: Secure-by-default containers for commercial software]() Original publisher: [Read original article]() Published: 2026-03-17T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [chainguard commercial builds](), [Containers](), [open-source-security](), [supply-chain-security](), [Open Source](), [Security]() Tags: [azul](), [chainguard](), [chainguard-commercial-builds](), [chainguard-containers](), [containers](), [elastic](), [f5-nginx](), [gitlab](), [grafana-labs](), [open-source-software](), [partnership](), [provenance](), [sbom](), [secure-by-default](), [supply-chain-security](), [vulnerabilities]() ### AI overview Chainguard announces Commercial Builds, a partnership program with commercial and open source software providers. The program packages their software with the Chainguard Factory to provide hardened container images and support more consistent software supply chain security. ### Source excerpt Chainguard Commercial Builds is a new partnership program with commercial and open source software providers to package software using the Chainguard Factory. ## How Lansweeper scaled IT, OT, and IoT insights with ClickHouse Cloud DevFeed: [How Lansweeper scaled IT, OT, and IoT insights with ClickHouse Cloud]() Original publisher: [Read original article]() Author: ClickHouse Published: 2025-07-11T16:46:03Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [elasticsearch](), [Internet of things](), [real-time](), [Databases](), [Kafka](), [MongoDB](), [Cloud]() Tags: [analytics](), [architecture](), [clickhouse](), [elastic](), [iot](), [kafka](), [mongodb](), [real-time](), [vulnerabilities]() ### AI overview The article describes how Lansweeper evolved its analytics architecture as its technology asset intelligence platform expanded across IT, OT, and IoT environments. After MongoDB became insufficient for fast, flexible analytics and Elasticsearch became expensive at scale, Lansweeper moved through an Elasticsearch-based pipeline and ClickHouse OSS before adopting ClickHouse Cloud for high-performance, real-time querying. ### Source excerpt "ClickHouse outperformed Elastic in every single test. Sometimes it was 10 times faster--even on slower hardware, because we were testing ClickHouse on our laptops and Elastic on production machines." Juan Carlos Lloret Hernández, Lead Developer ## Heroku at TDX 2025: Empowering Developers for the Future DevFeed: [Heroku at TDX 2025: Empowering Developers for the Future]() Original publisher: [Read original article]() Author: Emily Todd Published: 2025-02-10T15:00:00Z Content type: article Language: en Sources: [Heroku]() Topics: [Heroku](), [developer-relations](), [Slack](), [gateway]() Tags: [2025](), [agentforce](), [developer-tools](), [developers](), [dynos](), [elastic](), [event](), [events](), [heroku](), [heroku-connect](), [integration](), [integrations](), [news](), [platform](), [real-time](), [salesforce](), [slack](), [software-engineering](), [workshops]() ### AI overview Heroku previews its TDX 2025 sessions and activities in San Francisco, covering integrations with Agentforce and Salesforce technologies. The program includes topics such as Flow and Apex, Heroku Connect, MuleSoft Flex Gateway, Slack apps, custom code, and workshops and demos. ### Source excerpt TDX25 comes to San Francisco this March 5-6. Heroku, a Salesforce company, has a packed schedule with a variety of sessions and activities designed to enhance your knowledge of our platform and integrations with Agentforce and Salesforce technologies. Whether you're new to Heroku or a seasoned pro, there's something for everyone at this year's event. [...] The post Heroku at TDX 2025: Empowering Developers for the Future appeared first on Heroku. ## Know your tools: The full range of Elastic Security's detection engineering capabilities DevFeed: [Know your tools: The full range of Elastic Security's detection engineering capabilities]() Original publisher: [Read original article]() Author: Kseniia Ignatovych Published: 2024-11-12T05:00:00Z Content type: article Language: en Sources: [Elastic Blog - Elasticsearch, Kibana, and ELK Stack]() Topics: [Detection engineering](), [Security](), [SIEM, Security](), [threat detection](), [alert triage](), [Tooling]() Tags: [alert-fatigue](), [alert-triage](), [automated](), [automated-threat-protection-cybersecurity-defense-security-compliance](), [blog](), [detection-engineering](), [elastic](), [features](), [latest-features](), [quality](), [security](), [security-siem](), [siem](), [threat-detection](), [tools](), [workflows]() ### AI overview This Elastic Security blog provides an overview of detection engineering capabilities, including customizable prebuilt rules, alert suppression, manual rule runs, automated case creation, and machine learning jobs. ### Source excerpt This blog provides a comprehensive overview of the detection capabilities available in Elastic Security. Learn about the latest features and get useful tips and tricks for your detection practice! ## End-to-end SAP Observability with Elastic, Google Cloud, and Kyndryl: A deep dive DevFeed: [End-to-end SAP Observability with Elastic, Google Cloud, and Kyndryl: A deep dive]() Original publisher: [Read original article]() Author: Valerio Arvizzigno,Francesco Di Stefano Published: 2024-07-08T00:00:00Z Content type: article Language: en Sources: [Elastic Blog - Elasticsearch, Kibana, and ELK Stack]() Topics: [observability](), [Google Cloud Platform (GCP)](), [dashboards](), [log management](), [Monitoring](), [hosting](), [Security](), [networking]() Tags: [anomaly-detection-cloud-migration-sap-monitoring-real-time-analysis-network-visibility-google-c](), [cloud](), [deep-dive](), [elastic](), [enterprise](), [google](), [google-cloud](), [industries](), [infrastructure](), [integrations](), [kibana](), [kyndryl](), [logs](), [metrics](), [monitoring](), [networking](), [observability](), [observability-log-analytics-metrics-business-analytics-cloud](), [operations](), [platforms](), [security]() ### AI overview This article presents a full-stack observability approach for complex SAP environments, developed by Elastic in collaboration with Google Cloud and Kyndryl. It describes using Kibana and Elastic integrations to provide visibility across hybrid infrastructure, applications, business processes, logs, metrics, traces, security, and compliance. ### Source excerpt Companies across almost all industries rely on robust complex SAP systems to power their core operations. At Elastic, with the collaboration of Kyndryl and Google Cloud, we designed a full-stack observability experience for your SAP environment. ## Reducing false positives with automated SIEM investigations from Elastic and Tines DevFeed: [Reducing false positives with automated SIEM investigations from Elastic and Tines]() Original publisher: [Read original article]() Author: Aaron Jewitt Published: 2024-05-31T00:00:00Z Content type: article Language: en Sources: [Elastic Blog - Elasticsearch, Kibana, and ELK Stack]() Topics: [SIEM, Security](), [SOC](), [Security](), [elasticsearch](), [Amazon Web Services](), [Software as a service](), [API]() Tags: [analysts](), [api](), [automated-threat-protection-anomaly-detection-cybersecurity-network-visibility-security-analytic](), [aws](), [blog-post](), [elastic](), [endpoint-security-security](), [false-positives](), [logs](), [security](), [server](), [soc](), [token](), [workflows]() ### AI overview Elastic's InfoSec team uses Tines to automate initial SIEM alert investigations, helping reduce false positives and analyst fatigue. The workflow queries Elasticsearch using alert data such as source.ip, closes alerts associated with trusted devices or known benign activity, and escalates cases that cannot be resolved automatically. ### Source excerpt Discover how Elastic's InfoSec team saves thousands of hours per month by using Tines to automate SIEM alert investigations while reducing false positives and detect compromised accounts. ## Team Qualities Behind a Digital Observability Team's Peak-Season Upgrade DevFeed: [Team Qualities Behind a Digital Observability Team's Peak-Season Upgrade]() Original publisher: [Read original article]() Author: Target Brands, Inc Published: 2017-05-23T05:00:00Z Content type: opinion Language: en Sources: [Target]() Topics: [observability](), [Logging](), [upgrade]() Tags: [agile](), [culture](), [devops](), [elastic](), [leadership](), [logging](), [observability](), [on-call](), [organizational](), [quality](), [support](), [team](), [upgrade]() ### AI overview A reflection on a digital observability team after a major Elastic logging-cluster upgrade ahead of Black Friday. The author identifies leadership support, mutual respect, and cooperation during on-call work as qualities that contributed to the team's accomplishments. ### Source excerpt It is 7:30 AM on a Monday morning in late October. I am waiting in line at Cafe Donuts to bring my team breakfast for our mandated 'no work for one hour'. We just wrapped up a strenuous week of implementing a major upgrade to our Elastic logging cluster. Many digital teams are relying on this upgrade to position themselves to confidently monitor their application health during the most important day in retail - Black Friday. It was a successful, much anticipated upgrade that resulted in many hours of overtime, late night calls, and cross-team performance tests. Morale is high, but it hasn't always been. It has been over three months since the team disassembled to work on new initiatives. I have since had a chance to reflect on the qualities of the team that made it so unique. I can't speak for my colleagues, but the accomplishments we made over six months are my proudest achievements in my five year tenure at Target. Leadership support Our leaders truly supported and enabled our work to be successful. They gave us the resources and confidence to confront organizational blockers and competing priorities. They helped us celebrate wins by providing recognition through updates to high level executives and advertising our achievements in forums. They took risks for us, trusted us to make decisions, and went to bat for us even when there was doubt that we could deliver on our promises. Respect This quality is near and dear to my heart. I never witnessed competition, resentment, distrust, or judgement among the team. Everyone truly respected one another and their unique perspectives. We were all aligned, working towards the same goals, and were in it together. Lead engineers partnered with junior engineers to ensure they understood the entire tech stack and could independently support our customers. I personally felt like my opinions and ideas mattered. On call schedules were set, but we supported one another through escalations and incidents. As a primary on call member,