Sno Station
Sno Station은 AI 에이전트를 하나의 팀으로 묶는 오픈소스 워크스테이션으로, 로컬 머신에서 에이전트 협업을 가능하게 함
데이터를 수집·저장·검색해 Elastic Stack으로 활용합니다. 중앙 플랫폼에서 즉시 확장 가능한 Elastic 통합을 제공합니다
Collect, store, and search data from any source to power your use cases with the Elastic Stack. Scale quickly from a centralized platform with out-of-the-box Elastic integrations to capture relevant i
플러그인Handlebars · GoGitHub @elastic온라인운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기Collect, store, and search data from any source to power your use cases with the Elastic Stack. Scale quickly from a centralized platform with out-of-the-box Elastic integrations to capture relevant i...
저장소 README에서 가져옴
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
This repository contains sources for Elastic Integrations. Each Elastic Integration is an Elastic Package that defines how to observe a specific product with the Elastic Stack.
An Elastic Package may define configuration for the Elastic Agent as well as assets (such as Kibana dashboards and Elasticsearch index templates) for the Elastic Stack. It should also define documentation about the package. Finally, a package may also define tests to ensure that it is functioning as expected.README 전문 보기 ↗This repository contains sources for Elastic Integrations. Each Elastic Integration is an Elastic Package that defines how to observe a specific product with the Elastic Stack.
An Elastic Package may define configuration for the Elastic Agent as well as assets (such as Kibana dashboards and Elasticsearch index templates) for the Elastic Stack. It should also define documentation about the package. Finally, a package may also define tests to ensure that it is functioning as expected.
Elastic Packages have a certain, well-defined structure. This structure is described by the Package Specification. The repository is also used for discussions about extending the specification (with proposals).
While this repository contains sources for Elastic Integrations, built Elastic Integrations are published into a storage based on Google Cloud bucket (more info here) and served up via the Package Registry. The Fleet UI in Kibana connects to the Package Registry and allows users to discover, install, and configure Elastic Packages.
Public documentation is compiled and exported to our Elastic docs.
Please review the Contributing Guide to learn how to build and develop packages, understand the release procedure and explore the builder tools.
If you're using an AI coding agent, we recommend installing the Agent skills below before you start.
More information about the CI pipelines that are available in this repository here.
Companion agent skills for building, reviewing, and maintaining Elastic integration packages are available in elastic/integration-skills. They work with Cursor, Codex, Gemini, Claude Code, and any other LLM-powered coding environment that can read skill/instruction files from a directory. Install them with:
npx skills add elastic/integration-skills
Claude Code users can instead install the skills natively as a plugin - see CLAUDE.md.