graylog-prd
Tools for interaction with graylog production environment
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Tools for interaction with graylog production environment
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Tools for interaction with countly production environment
Tools for interaction with countly testing environment
Tools for gathering documentation details
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks
Tools for interaction with grafana production environment
Tools for interaction with grafana testing environment
| name | graylog-prd |
| description | Tools for interaction with graylog production environment |
#graylog-prdAccess Graylog production environment for real-time log search, aggregation, and analysis. Use for production incident response, error investigation, and system behavior tracking. Logs are organized into streams and stored in indices. Queries use Lucene syntax.
list_fields) before queryinglist_indices to check data availability and health.list_fields first to discover valid field names before building queries.level:ERROR AND source:api-server). Leading wildcards are disabled by default.Include #graylog-prd tag in your prompt to activate this skill.
#graylog-prd Search production logs for errors related to payment processing in last 2 hours
#graylog-prd Count errors grouped by source in production last 1 hour
#graylog-prd Show authentication failures in last 24 hours
#graylog-prd List available fields in the production application stream
#graylog-prd #fetch Analyze current error spike in production
Do NOT search the filesystem for mcp-config.json or similar files directly.
Do NOT read .copilot/mcp-config.json directly — always route through custom agent file.
MCP server is configured in the graylog-prd.agent.md custom agent file.
Use environment variables defined in .copilot/.env.
Before taking any action, verify the Graylog Production MCP server is reachable:
get_system_status as a lightweight probe.list_streams first to get stream IDs, then scope searches using streams parameterlist_fields before querying to discover valid field names for the target streamaggregate_messages instead of search_messages for counting/groupingrange_seconds parameter — never embed time in the query stringCRITICAL: Never use #graylog-prd and #graylog-tst in the same request. Choose one environment per query.