Table of Contents Splunk 관리 시작 Splunk 관리자용 매뉴얼 Splunk 관리 방법 Splunk 작업에서 *nix 및 Windows의 기능적 차이점 먼저 수행할 작업 Splunk 시작 및 중지 부팅 시 시작하도록 Splunk 구성 라이선스 설치

Splunk 5.0 관리자 매뉴얼 생성일: 2012년 10월 31일 오후 2시 44분 Copyright 2012 Splunk, Inc. All Rights Reserved Copyright (c) 2013 Splunk, Inc. All Rights Reserved

Table of Contents Splunk 관리 시작 Splunk 관리자용 매뉴얼 Splunk 관리 방법 Splunk 작업에서 *nix 및 Windows의 기능적 차이점 먼저 수행할 작업 Splunk 시작 및 중지 부팅 시 시작하도록 Splunk 구성 라이선스 설치 기본값 변경 Splunk를 IP에 바인드 IPv6용 Splunk 구성 Splunk Web 사용 Splunk Web 및 Splunk 관리자 정보 프록시 서버 지정 Windows 관리자용 시작 지침 Windows 관리자를 위한 지침 Splunk 시험 사용 Splunk 기능에 대해 알아보기 엔터프라이즈에 Splunk 통합 Splunk 최대한 활용하기 Splunk를 최고 성능으로 최적화하는 방법 시스템 이미지에 Splunk 배치 범용 전달기(Universal Forwarder)를 시스템 이미지에 통합 Splunk를 시스템 이미지에 통합 Windows에 Splunk 배포 Splunk 라이선스 관리 Splunk 라이선싱 방식 Splunk 라이선스 유형 그룹, 스택, 풀 및 기타 용어 라이선스 설치 라이선스 마스터 구성 라이선스 슬레이브 구성 라이선스 풀 만들기 또는 편집 라이선스 풀에 인덱스 추가 라이선스 관리 라이선스 위반에 대하여 새로운 Splunk 라이선서로 마이그레이션 Splunk Free 추가 정보 CLI를 통해 라이선스 관리 Splunk 앱 정보 앱 및 추가 기능 정의 더 많은 앱과 추가 기능 찾기 5 5 6 8 9 9 10 11 11 14 14 16 16 17 18 18 18 19 19 19 20 20 21 22 22 24 24 25 26 27 28 28 29 30 31 31 33 34 35 37 37 39

앱 아키텍처 및 개체 소유권 앱 및 추가 기능 개체 관리 앱 구성 및 속성 관리 Splunk 구성 Splunk 구성 방법 Splunk 관리자에 대하여 구성 파일에 대하여 구성 파일 리스트 구성 파일 우선 순위 단일 props.conf 파일 내의 속성 우선 순위 구성 매개 변수 및 데이터 파이프라인 구성 정보 백업 사용자 관리 사용자 및 역할에 대하여 사용자 언어 및 로케일 구성 사용자 Session timeout 구성 Splunk 명령줄 인터페이스(CLI) 사용 CLI에 대하여 CLI 도움말 보기 CLI 관리 명령 CLI를 사용하여 원격 Splunk 서버 관리 구성 파일 참조 alert_actions.conf app.conf audit.conf authentication.conf authorize.conf commands.conf crawl.conf default.meta.conf deploymentclient.conf distsearch.conf eventdiscoverer.conf event_renderers.conf eventtypes.conf fields.conf indexes.conf inputs.conf limits.conf literals.conf macros.conf multikv.conf outputs.conf pdf_server.conf perfmon.conf procmon-filters.conf props.conf pubsub.conf 40 41 42 43 43 44 45 47 48 52 53 54 55 55 55 56 57 57 58 59 61 62 62 66 70 73 79 83 86 88 89 92 96 97 98 100 101 112 127 145 146 147 150 159 163 165 166 180

regmon-filters.conf restmap.conf savedsearches.conf searchbnf.conf segmenters.conf server.conf serverclass.conf serverclass.seed.xml.conf setup.xml.conf source-classifier.conf sourcetypes.conf splunk-launch.conf sysmon.conf tags.conf tenants.conf times.conf transactiontypes.conf transforms.conf user-seed.conf web.conf wmi.conf workflow_actions.conf viewstates.conf 181 183 186 193 196 197 210 214 216 218 219 220 222 224 225 226 228 230 237 238 245 249 252

Splunk 관리 시작 Splunk 관리자용 매뉴얼 이 관리자 매뉴얼은 Splunk 관리자를 위한 중요한 정보와 절차가 수록되어 있는 여러 문서 중 하나입니다. 본인이 직 접 사용하기 위해 또는 다른 사용자를 위해 Splunk를 서비스로 구성, 실행 및 유지 관리해야 할 경우에는 이 문서를 먼 저 읽어보십시오. Splunk 관리와 관련하여 특정 영역에 대한 자세한 내용은 다음 매뉴얼을 참조하십시오. 데이터 가져오기 인덱서 및 클러스터 관리 분산 배포 보안 문제 해결 설치 Splunk 관리에 필요한 매뉴얼에 대해 알아보기 이 테이블에서는 Splunk 관리자에게 기본적으로 필요한 문서를 소개합니다. 관리자 매뉴얼 데이터 가져오기 인덱서 및 클러스터 관리 분산 배포 내용 Splunk 관리 - Splunk 관리, 라이선스, 구성 파 일 및 CLI에 관한 기본적인 사항 데이터 입력 지정 및 Splunk에서 데이터를 처리 하는 방법 개선 Splunk 인덱서 및 인덱서의 클러스터 관리 엔터프라이즈의 요구에 맞춰 배포 조정 및 Forwarder, 검색 헤드, 배포 서버 등의 Splunk 분산 구성 요소에 대한 세부정보 제공 주요 항목 먼저 수행할 작업 Windows 관리자를 위한 시작 지침 Splunk 라이선스 관리 Splunk 구성 방법 사용자 관리 Splunk 명령줄 인터페이스 사용 파일 참조 구성 Splunk에 데이터를 가져오는 방법 이벤트 처리 구성 데이터 미리 보기 인덱싱 및 인덱서에 대하여 인덱스 관리 인덱스 백업 및 아카이브 클러스터 및 인덱스 복제에 대하여 클러스터 배포 분산 Splunk 개요 데이터 전달 다중 인덱서에서 검색 환경에 업데이트 배포 Splunk 보안 데이터 보안 및 사용자 인증 사용자 인증 및 역할 SSL을 사용하여 암호화 및 인증 감사 문제 해결 문제 해결 첫 단계 Splunk 로그 파일 일반 시나리오 설치 Splunk 설치 및 업그레이드 시스템 요구 사항 단계별 설치 절차 이전 버전에서 업그레이드 "Splunk 관리 방법" 항목에서는 관련 관리 작업에 대해 설명하는 문서에 대한 보다 상세한 가이드를 제공합니다. Splunk 관리자에게 유용한 기타 참조 문서 Splunk 설치 크기와 사용자가 담당하는 작업에 따라 주요 관리 작업에 대한 매뉴얼 외에도 다른 매뉴얼이 때때로 필 요할 수 있습니다. 다음은 Splunk 주요 매뉴얼에 포함되는 다른 매뉴얼입니다. Splunk 튜토리얼! 이 매뉴얼에서는 Splunk 사용에 대한 내용을 소개합니다. 지식 관리자. 이 매뉴얼에서는 event type, 태그, 룩업, 필드 추출, 워크플로 작업, 저장된 검색, 뷰 등의 Splunk Knowledge Object를 관리하는 방법에 대해 설명합니다. 경고. 이 매뉴얼에서는 Splunk 경고 및 모니터링 기능을 설명합니다. 데이터 시각화. 이 매뉴얼에서는 Splunk가 제공하는 시각화 범위를 설명합니다. 검색. 이 매뉴얼에서는 검색 방법과 Splunk 검색 언어 사용 방법을 설명합니다. 검색 참조. 이 참조에는 Splunk 검색 명령에 대한 상세 카탈로그가 포함되어 있습니다. Splunk Web용 뷰 및 앱 개발: 이 매뉴얼에서는 고급 XML을 사용하여 뷰 및 앱을 개발하는 방법에 대해 설명합 니다. 사용자 지정 스크립트와 Splunk 확장과 같은 기타 개발자 항목도 포함되어 있습니다. REST API 참조. 이 매뉴얼에서는 공개적으로 액세스 가능한 모든 REST API endpoint에 대한 정보를 제공합니 5

다. 릴리스 노트. 새로운 기능, 알려진 문제 및 해결된 문제에 대한 정보를 제공합니다. 전체 Splunk 매뉴얼 위에 나열한 매뉴얼을 포함한 Splunk 주요 매뉴얼 전체에 대한 링크는 Splunk 주요 매뉴얼에서 확인하십시오. 앱 매뉴얼을 포함한 모든 Splunk 매뉴얼에 액세스하려면 Splunk 설명서에 오신 것을 환영합니다 페이지를 참조하십 시오. PDF 만들기 이 매뉴얼의 PDF 버전을 원하는 경우 이 페이지 왼쪽의 목차 아래 빨간색 관리자 매뉴얼을 PDF로 다운로드 링크를 클릭하십시오. 해당 매뉴얼의 PDF 버전이 즉시 생성됩니다. 생성된 PDF는 나중에 볼 수 있도록 저장하거나 인쇄할 수 있습니다. Splunk 관리 방법 Splunk 관리에는 인덱스 관리, 데이터 입력 정의, 인증 구성, 데이터 보안 처리, 대규모 배포를 위한 Splunk 확장과 같 은 다양한 작업이 포함됩니다. Splunk 관리 작업은 규모가 크고 특성이 다양하기 때문에 매뉴얼 세트의 여러 매뉴얼 이 필요할 수 있습니다. 이 항목에서는 Splunk 관리자의 주요 작업에 대해 설명하고 관련 매뉴얼, 장 및 항목에 대한 링크를 제공합니다. Splunk 설치 및 업그레이드 설치 매뉴얼에서는 Splunk 설치 및 업그레이드 방법을 설명합니다. 관련 작업에 대한 내용은 다음을 참조하십시오. 작업 관련 항목 설치 요구 사항 이해 하드웨어 용량 요구 평가 Splunk 설치 Splunk 업그레이드 설치 계획 하드웨어 요구 사항 평가 Windows에 Splunk 설치 Unix, Linux 또는 MacOS에 Splunk 설치 이전 버전에서 업그레이드 기본적인 관리 작업 수행 현재 관리자 매뉴얼에서는 기본적인 관리 작업에 해당하는 거의 모든 정보를 제공합니다. 사용자 계정 설정과 같은 경 우 이 테이블에는 다른 매뉴얼(예: 보안 매뉴얼) 항목으로 연결되는 링크가 있습니다. 설치 후 첫 단계 Splunk Web 사용 작업 Windows에서 Splunk 시작하기 Splunk 라이선스 설치 및 관리 Splunk 앱 관리 Splunk 구성 사용자 관리 백업 수행 Splunk 명령줄 인터페이스(CLI) 사용 경고 정의 검색 작업 관리 먼저 수행할 작업 Splunk Web 사용 관련 항목 Windows 관리자용 시작 지침 Splunk 라이선스 관리 Splunk 앱 정보 Splunk 구성 사용자 관리 사용자 및 역할 기반 액세스 제어 사용자 설정 구성 정보 백업 인덱스된 데이터 백업 폐기 및 아카이브 정책 설정 CLI 사용 경고 정의 작업 관리자를 사용하여 검색 작업 감독 Splunk로 데이터 가져오기 데이터 가져오기에서는 외부 소스의 데이터를 사용하는 방법, 데이터의 가치를 향상시키는 방법 등과 같은 Splunk 데 이터 입력에 대한 정보를 설명합니다. 작업 6 관련 항목

외부 데이터 사용 방법에 대한 정보 파일 및 디렉터리 입력 구성 네트워크 입력 구성 Windows 입력 구성 기타 입력 구성 데이터 가치 향상 인덱싱 후 데이터가 어떻게 표시되는지 알아보기 프로세스 개선 Splunk로 데이터를 가져오는 방법 파일 및 디렉터리에서 데이터 가져오기 네트워크 이벤트 가져오기 Windows 데이터 가져오기 데이터를 가져오는 다른 방법 이벤트 처리 구성 타임스탬프 구성 인덱스된 필드 추출 구성 host 값 구성 source type 구성 이벤트 세그먼트화 관리 데이터 미리 보기 데이터 입력 프로세스 개선 인덱스 및 인덱서 관리 인덱서 및 클러스터 관리에서는 인덱스 구성 방법을 설명합니다. 또한 인덱스, 인덱서 및 인덱서의 클러스터를 유지 관리하는 구성 요소의 관리 방법에 대해서도 설명합니다. 작업 관련 항목 인덱싱에 대해 알아보기 인덱스 관리 인덱스 저장소 관리 인덱스 백업 인덱스 아카이브 클러스터 및 인덱스 복제에 대해 알아보기 클러스터 배포 클러스터 구성 클러스터 관리 클러스터 아키텍처에 대해 알아보기 인덱싱 개요 인덱스 관리 인덱스 저장소 관리 인덱스된 데이터 백업 폐기 및 아카이브 정책 설정 클러스터 및 인덱스 복제에 대하여 클러스터 배포 클러스터 구성 클러스터 관리 클러스터 작동 방식 Splunk 확장 분산 배포 매뉴얼에서는 Forwarder, 인덱서, 검색 헤드 등의 여러 구성 요소에 Splunk 기능을 분산하는 방법에 대해 설명합니다. 또한 배포 서버를 사용하여 배포를 관리하는 방법에 대해 설명합니다. 작업 관련 항목 분산 Splunk에 대해 알아보기 Splunk 배포를 위한 용량 계획 수행 데이터 전달 방법에 대해 알아보기 다중 인덱서에 검색 분산 배포 업데이트 분산 Splunk 개요 하드웨어 요구 사항 평가 데이터 전달 다중 인덱서에서 검색 환경에 구성 업데이트 배포 Splunk 보안 Splunk 보안에서는 Splunk 배포에 대한 보안 방법을 설명합니다. 작업 관련 항목 사용자 및 편집 역할 인증 SSL을 사용하여 Splunk 데이터 보안 Splunk 감사(Audit) 사용자 및 역할 기반 액세스 제어 보안 인증 및 암호화 Splunk 작업 감사(Audit) Splunk 문제 해결 문제 해결 매뉴얼에서는 Splunk 문제 해결에 대한 전체적인 가이드를 제공합니다. 또한 다른 매뉴얼의 항목에서도 특 7

정 문제에 대한 문제 해결 정보를 제공합니다. 작업 관련 항목 Splunk 문제 해결 도구에 대해 알아보기 Splunk 로그 파일에 대해 알아보기 Splunk 지원 작업 수행 일반적인 문제 해결 첫 단계 Splunk 로그 파일 Splunk 지원 문의 일반 시나리오 참조 및 기타 정보 Splunk 매뉴얼에는 Splunk 관리자에게 필요할 수 있는 다른 소스의 정보뿐만 아니라 여러 유용한 참조가 포함되어 있 습니다. 구성 파일 참조 REST API 참조 CLI 도움말 릴리스 정보 참조 관련 항목 관리자 매뉴얼의 구성 파일 참조 REST API 참조 매뉴얼 Splunk 인스턴스를 설치하면 제공됩니다. 이 도움말의 실행 방법에 대한 자세한 내용은 관리자 매뉴얼의 CLI 도움말 보기에서 확인하십시오. 릴리스 노트 Splunk 지식 관리에 대한 정보 지식 관리자 매뉴얼 Splunk 작업에서 *nix 및 Windows의 기능적 차이점 이 항목에서는 Splunk 작업에서 *nix와 Windows 운영 체제에서 발생하는 기능적 차이점에 대해 명확히 설명합니다. 두 OS에 대한 기술적 비교나 두 OS 중 한쪽을 옹호하는 것이 아니라 특정 OS 관련 Splunk 매뉴얼의 여러 페이지에 여러 방법으로 참조되는 이유에 대해 설명합니다. 경로 *nix 운영 체제에서 파일과 디렉터리를 처리하는 방식의 큰 차이점은 경로 이름의 파일 또는 디렉터리를 구분하기 위 해 사용하는 슬래시 유형입니다. *nix 시스템에서는 슬래시("/")를 사용하고, Windows에서는 백슬래시("\")를 사용합니 다. *nix 경로의 예: /opt/splunk/bin/splunkd Windows 경로의 예: C:\Program Files\Splunk\bin\splunkd.exe 환경 변수 운영 체제에 따라 환경 변수의 표시 방법이 다릅니다. 두 시스템은 모두 하나 이상의 환경 변수에 데이터를 일시적으 로 저장하는 방식을 사용합니다. *nix 시스템에서는 다음과 같이 환경 변수 이름 앞에 달러 기호("$")를 사용합니다. SPLUNK_HOME=/opt/splunk; export $SPLUNK_HOME Windows에서 환경 변수를 지정하는 방식은 약간 다릅니다. 퍼센트 기호("%")를 사용해야 합니다. 사용할 환경 변수 유형에 따라 환경 변수 이름 앞에, 또는 이름 앞이나 뒤에 한 두 개의 퍼센트 기호를 입력합니다. > set SPLUNK_HOME="C:\Program Files\Splunk" > echo %SPLUNK_HOME% C:\Program Files\Splunk > Windows 환경에서 %SPLUNK_HOME% 변수를 설정하려면 다음 두 가지 방법 중 하나를 사용하십시오. %SPLUNK_HOME%\etc에서 splunk-launch.conf를 편집합니다. "환경 변수" 창에 액세스하여 변수를 설정합니다. 탐색기 창을 열고 왼쪽 창에서 마우스 오른쪽 단추로 "내 컴퓨 터"를 클릭한 후 나타나는 창에서 "속성"을 선택합니다. 시스템 속성 창이 나타나면 "고급" 탭을 선택한 후 탭의 창 하단에 나타나는 "환경 변수" 단추를 클릭합니다. 8

먼저 수행할 작업 Splunk 시작 및 중지 이 항목에서는 Splunk를 시작하는 방법에 대해 간략히 설명합니다. Splunk를 처음 사용하는 경우 사용자 매뉴얼을 먼 저 읽어보는 것이 좋습니다. Windows에서 Splunk 시작 Windows에서 Splunk는 기본적으로 C:\Program Files\Splunk에 설치됩니다. Splunk 매뉴얼에 나오는 많은 예에서는 $SPLUNK_HOME을 사용하여 Splunk 설치 또는 홈, 디렉터리를 나타냅니다. Splunk를 기본 디렉터리에 설치한 경우 이 $SPLUNK_HOME(또는 Windows계열 %SPLUNK_HOME%) 문자열을 C:\Program Files\Splunk로 바꿀 수 있습니다. 다음 방법 중 하나를 사용하여 Windows에서 Splunk를 시작 및 중지할 수 있습니다. 1. Windows 서비스 제어판(Start -> Control Panel -> Administrative Tools -> Services에서 액세스)을 통해 Splunk 프 로세스를 시작 및 중지합니다. 서버 데몬: splunkd 웹 인터페이스: splunkweb 2. NET START <service> 또는 NET STOP <service> 명령을 사용하여 명령 프롬프트에서 Splunk 서비스를 시작 및 중지합 니다. 서버 데몬: splunkd 웹 인터페이스: splunkweb 3. %SPLUNK_HOME%\bin으로 이동하여 입력을 통해 두 프로세스를 동시에 시작, 중지 및 재시작합니다. > splunk [start stop restart] UNIX에서 Splunk 시작 Splunk 시작 Splunk 서버 호스트의 셸 프롬프트에서 다음 명령을 실행하십시오. splunk start 이 명령어를 입력하면 splunkd(인덱서 및 다른 백엔드 프로세스) 및 splunkweb(splunk Web 인터페이스)이 모두 시작됩 니다. 두 가지 프로세스를 각각 시작하려면 다음 명령어를 입력하십시오. splunk start splunkd 또는 splunk start splunkweb 참고: web.conf에서 startwebserver가 비활성화된 경우, splunkweb을 수동으로 시작하면 해당 설정이 무시되지 않습니 다. 구성 파일에서 해당 변수가 비활성화된 경우에는 시작되지 않습니다. Splunk(splunkd 또는 splunkweb)를 재시작하려면 다음 명령어를 입력하십시오. splunk restart splunk restart splunkd splunk restart splunkweb Splunk 중지 Splunk를 종료하려면 다음 명령을 실행하십시오. splunk stop splunkd 및 Splunk Web을 각각 중지하려면 다음 명령어를 입력하십시오. splunk stop splunkd 또는 splunk stop splunkweb Splunk가 실행 중인지 확인 9

Splunk가 실행 중인지 확인하려면 서버 호스트의 셸 프롬프트에서 다음 명령어를 입력하십시오. splunk status 다음과 같이 출력됩니다. splunkd is running (PID: 3162). splunk helpers are running (PIDs: 3164). splunkweb is running (PID: 3216). 참고: Unix 시스템에서는 Splunk를 실행하는 사용자로 로그인해야만 splunk status 명령을 실행할 수 있습니다. 다른 사용자는 상태 정보를 올바르게 보고하는 필요한 파일을 읽을 수 없습니다. 또한 ps를 사용하여 Splunk 프로세스가 실행 중인지 확인할 수 있습니다. ps aux grep splunk grep -v grep Solaris 사용자인 경우 aux 대신 -ef를 입력하십시오. ps -ef grep splunk grep -v grep Splunk Web에서 Splunk 재시작 Splunk Web에서 Splunk를 재시작할 수도 있습니다. 1. 관리자 > 서버 컨트롤로 이동합니다. 2. Splunk 재시작을 클릭합니다. 이렇게 하면 splunkd 및 splunkweb 프로세스가 모두 재시작됩니다. 부팅 시 시작하도록 Splunk 구성 Windows에서 Splunk는 기본적으로 컴퓨터를 시작할 때 시작됩니다. 이렇게 하지 않으려면 이 항목의 끝 부분에 나오 는 "Windows 부팅 시 시작 안 함"을 참조하십시오. *nix 플랫폼에서는 부팅 시 시작하도록 Splunk를 구성해야 합니다. *nix 플랫폼에서 부팅 시 시작 Splunk는 시스템 부팅 시 Splunk가 시작되도록 시스템 부팅 구성을 업데이트하는 유틸리티를 제공합니다. 이 유틸리 티는 적합한 init 스크립트를 생성하거나 OS에 따라 비슷한 구성 변경을 수행합니다. 루트로 다음 명령을 실행하십시오. $SPLUNK_HOME/bin/splunk enable boot-start Splunk를 루트로 시작하지 않으면 어떤 사용자가 Splunk를 시작하는지 지정하는 -user 매개 변수를 통과할 수 있습니 다. 예를 들어, Splunk를 사용자 bob으로 실행할 경우 다음을 루트로 실행하게 됩니다. $SPLUNK_HOME/bin/splunk enable boot-start -user bob 시스템을 시작할 때 Splunk를 실행하지 않으려면 다음 명령을 실행하십시오. $SPLUNK_HOME/bin/splunk disable boot-start 자세한 내용은 $SPLUNK_HOME/etc/init.d/README에서 확인할 수 있으며, 명령줄에서 help boot-start를 입력하여 도움말 을 볼 수도 있습니다. Mac 사용자 참고 사항 Splunk는 자동으로 스크립트 및 구성 파일을 /System/Library/StartupItems 디렉터리에 생성합니다. 이 스크립트는 시 스템 시작 시 실행되고, 시스템 종료 시 Splunk를 자동으로 중지합니다. 참고: Mac OS를 사용하는 경우 루트 레벨 권한이 있거나 sudo를 사용해야 합니다. sudo를 사용하려면 관리자 권한 이 필요합니다. 예: Mac OS에서 시스템 시작 시 Splunk를 시작하도록 다음과 같이 설정하십시오. 10

CLI만 사용:./splunk enable boot-start sudo를 사용하는 CLI 사용: sudo./splunk enable boot-start Windows에서 부팅 시 시작 안 함 기본적으로 Splunk는 Windows 컴퓨터를 시작할 때 자동으로 시작됩니다. Splunk 프로세스(SplunkWeb 및 Splunkd) 를 수동으로 시작하도록 Windows 서비스 관리자에서 구성할 수 있습니다. 라이선스 설치 Splunk를 처음 다운로드하면 등록하라는 메시지가 나타납니다. 등록하면 60일 동안 임시로 사용할 수 있는 Enterprise 평가판 라이선스가 제공되며, 이 라이선스로 사용할 수 있는 1 일 최대 인덱싱 볼륨은 500MB입니다. 이 라이선스는 다운로드에 포함되어 있습니다. Enterprise 라이선스는 다음 기능을 제공합니다. 다중 사용자 계정 및 액세스 제어 분산 검색 및 데이터 경로 설정 배포 관리 Splunk 라이선싱에 대한 자세한 내용은 이 매뉴얼의 Splunk 라이선싱 방식에서 확인하십시오. 새 라이선스는 어디에 있습니까? 새 라이선스를 요청하면 Splunk에서 보낸 이메일을 통해 라이선스를 받습니다. splunk.com 내 주문 페이지에서 새 라 이선스에 액세스할 수도 있습니다. Splunk Web을 통해 라이선스를 설치하고 업데이트하려면 관리자 > 라이선싱으로 이동한 후 해당 지침을 따르십시 오. 기본값 변경 현재 환경에 대한 Splunk 구성을 시작하기 전에 다음 기본값 설정을 자세히 확인하고 변경하려는 항목이 있는지 확인 하십시오. 관리자의 기본 암호 변경 Splunk Enterprise 라이선스의 기본 관리 계정 및 암호는 admin/changeme입니다. 이 기본값은 변경하는 것이 좋습니 다. Splunk CLI 또는 Splunk Web을 통해 이 작업을 수행할 수 있습니다. Splunk Web 사용 관리자의 기본 암호를 변경하려면: 1. Splunk Web에 관리자로 로그인합니다. 2. 인터페이스의 오른쪽 상단에 있는 관리자를 클릭합니다. 3. 화면의 사용자 및 인증 섹션에서 액세스 제어를 클릭합니다. 4. 사용자를 클릭합니다. 5. 관리자 사용자를 클릭합니다. 6. 암호를 업데이트하고 저장을 클릭합니다. Splunk CLI 사용 Splunk CLI 명령어는 다음과 같습니다. splunk edit user 참고: 암호를 변경하려면 먼저 기존 암호를 인증해야 합니다. CLI를 통해 또는 -auth 매개 변수를 사용하여 Splunk에 로그인하십시오. 예를 들어, 이 명령은 관리자 암호 changeme를 foo로 변경합니다. 11

splunk edit user admin -password foo -role admin -auth admin:changeme 참고: 셸에 의해 해석될 수 있는 특수 문자(예: '$' 또는 '!')를 포함하는 암호는 이스케이프하거나 작은따옴표로 처리해 야 합니다. 예: splunk edit user admin -password 'fflanda$' -role admin -auth admin:changeme 또는 splunk edit user admin -password fflanda\$ -role admin -auth admin:changeme 네트워크 포트 변경 Splunk는 설치 시 다음 두 가지 포트를 구성합니다. HTTP/HTTPS 포트. 이 포트는 Splunk Web용 소켓을 제공합니다. 기본값은 8000입니다. 관리 포트: 이 포트는 splunkd 데몬과 통신하는 데 사용됩니다. Splunk Web은 명령줄 인터페이스 및 다른 서버 에서 분산된 연결과 마찬가지로 이 포트를 통해 splunkd와 통신합니다. 이 포트의 기본값은 8089입니다. 중요: 설치할 때 이러한 포트 값을 기본값과 다르게 설정했을 수도 있습니다. 참고: Forwarder에서 데이터를 수신하는 Splunk 인스턴스는 추가 포트인 수신기 포트로 구성되어야 합니다. Splunk 인스턴스는 이 포트를 사용하여 Forwarder에서 들어오는 데이터를 수신합니다. 이 구성은 설치 과정에서 나오지 않습 니다. 기본 수신기 포트는 9997입니다. 자세한 내용은 분산 배포 매뉴얼의 "수신기 활성화"를 참조하십시오. Splunk Web 사용 설치 설정에서 포트를 변경하려면: 1. Splunk Web에 관리자로 로그인합니다. 2. 인터페이스의 오른쪽 상단에 있는 관리자를 클릭합니다. 3. 화면의 시스템 섹션에서 시스템 설정 링크를 클릭합니다. 4. 일반 설정을 클릭합니다. 5. 관리 포트 또는 웹 포트 값을 변경하고 저장을 클릭합니다. Splunk CLI 사용 Splunk CLI를 통해 포트 설정을 변경하려면 CLI 명령어 set를 사용하십시오. 예를 들어, 이 명령은 Splunk Web 포트 를 9000으로 설정합니다. splunk set web-port 9000 이 명령은 splunkd 포트를 9089로 설정합니다. splunk set splunkd-port 9089 기본 Splunk 서버 이름 변경 Splunk 서버 이름 설정은 Splunk Web 내에서 표시되는 이름과 분산 설정으로 다른 Splunk 서버에 전송된 이름을 모 두 제어합니다. 기본 이름은 Splunk 서버 호스트의 DNS 또는 IP 주소에서 가져옵니다. Splunk Web 사용 Splunk 서버 이름을 변경하려면: 1. Splunk Web에 관리자로 로그인합니다. 2. 인터페이스의 오른쪽 상단에 있는 관리자를 클릭합니다. 3. 화면의 시스템 섹션에서 시스템 설정 링크를 클릭합니다. 4. 일반 설정을 클릭합니다. 5. Splunk 서버 이름 값을 변경하고 저장을 클릭합니다. 12

Splunk CLI 사용 CLI를 통해 서버 이름을 변경하려면 set servername 명령을 사용하십시오. 예를 들어, 이 명령은 서버 이름을 foo로 설 정합니다. splunk set servername foo 데이터 저장소 위치 변경 데이터 저장소는 Splunk 서버가 인덱스된 모든 데이터를 저장하는 최상위 레벨 디렉터리입니다. 참고: 이 디렉터리를 변경할 경우 Splunk 서버가 이전 데이터 저장소 파일을 마이그레이션하지 못합니다. 대신 새로 운 위치에서 다시 시작됩니다. 데이터를 다른 디렉터리로 마이그레이션하려면 "인덱스 이동"의 지침을 따르십시오. Splunk Web 사용 데이터 저장소 위치를 변경하려면: 1. Splunk Web에 관리자로 로그인합니다. 2. 인터페이스의 오른쪽 상단에 있는 관리자를 클릭합니다. 3. 화면의 시스템 섹션에서 시스템 설정 링크를 클릭합니다. 4. 일반 설정을 클릭합니다. 5. 인덱스 경로에서 경로를 변경하고 저장을 클릭합니다. 6. CLI를 사용하여 Splunk를 재시작합니다. $SPLUNK_HOME/bin/(*nix) 또는 %SPLUNK_HOME%\bin(Windows)으로 이동한 후 다음 명령을 실행합니다. splunk restart 중요: 관리자 내에서 재시작 기능을 사용하지 마십시오. 이렇게 하면 인덱스 디렉터리로 인해 수행되는 작업이 변경되 지 않습니다. CLI를 통해 재시작해야 합니다. Splunk CLI 사용 CLI를 통해 데이터 저장소 디렉터리를 변경하려면 set datastore-dir 명령을 사용하십시오. 예를 들어, 이 명령은 데이 터 저장소 디렉터리를 /var/splunk/로 설정합니다. splunk set datastore-dir /var/splunk/ 사용 가능한 최소 디스크 공간 설정 사용 가능한 최소 디스크 공간 설정은 Splunk가 인덱싱을 중지하기 전 데이터 저장소 위치의 사용 가능한 최소 디스 크 공간을 제어합니다. 사용 가능한 공간이 확보되면 인덱싱이 다시 시작됩니다. Splunk Web 사용 사용 가능한 최소 디스크 공간을 설정하려면: 1. Splunk Web에 관리자로 로그인합니다. 2. 인터페이스의 오른쪽 상단에 있는 관리자를 클릭합니다. 3. 화면의 시스템 섹션에서 시스템 설정 링크를 클릭합니다. 4. 일반 설정을 클릭합니다. 5. 사용 가능한 디스크 공간이 부족할 경우 인덱스 중지 값을 변경하고 저장을 클릭합니다. Splunk CLI 사용 CLI를 통해 사용 가능한 최소 공간 값을 변경하려면 set minfreemb 명령을 입력하십시오. 예를 들어, 이 명령은 사용 가 능한 최소 공간을 2000MB로 설정합니다. 13

splunk set minfreemb 2000 기타 기본 설정 Splunk Web 관리자의 일반 설정 화면에는 변경할 수 있는 기타 기본 설정이 있습니다. 해당 기본 설정의 옵션 범위를 살펴 보십시오. Splunk를 IP에 바인드 지정된 IP 주소 포트에 Splunk를 강제로 바인드할 수 있습니다. 기본적으로 Splunk는 사용 가능한 모든 IP 주소를 의 미하는 IP 주소 0.0.0.0에 바인드합니다. Splunk의 바인드 IP 변경은 Splunk 데몬(splunkd)에만 적용되며 다음을 수신합니다. TCP 포트 8089(기본값) 다음에 대해 구성된 포트: SplunkTCP 입력 TCP 또는 UDP 입력 Splunk Web 프로세스(splunkweb)를 특정 IP에 바인드하려면 web.conf의 server.socket_host 설정을 사용하십시오. 임시 변경 이 값을 임시로 변경하려면 Splunk를 시작하기 전에 환경 변수 SPLUNK_BINDIP=<ipaddress>를 설정하십시오. 영구 변경 이 값을 현재 작동 환경에서 영구적으로 변경하려면 SPLUNK_BINDIP 속성과 <ipaddress> 값을 포함하도록 $SPLUNK_HOME/etc/splunk-launch.conf를 수정하십시오. 예를 들어, Splunk 포트를 127.0.0.1(로컬 루프백에만 해당)에 바 인드하려면 splunk-launch.conf가 다음과 같아야 합니다. Modify the following line to suit the location of your Splunk install. If unset, Splunk will use the parent of the directory this configuration file was found in SPLUNK_HOME=/opt/splunk SPLUNK_BINDIP=127.0.0.1 중요: web.conf에서 mgmthostport 속성의 기본값은 127.0.0.1:8089입니다. SPLUNK_BINDIP를 127.0.0.1과 다른 값으로 변경 하려면 동일한 IP 주소를 사용하도록 mgmthostport도 변경해야 합니다. 예를 들어, splunk-launch.conf에서 이렇게 변경 하려면: SPLUNK_BINDIP=10.10.10.1 web.conf에서도 다음과 같이 변경해야 합니다(관리 포트를 8089로 가정한 경우). mgmthostport=10.10.10.1:8089 mgmthostport 속성에 대한 자세한 내용은 web.conf를 참조하십시오. IPv6 고려사항 버전 4.3부터는 대괄호로 묶은 경우 IPv6 주소를 사용할 수 있도록 web.conf mgmthostport 설정이 확장되었습니다. 따라 서 (이 매뉴얼의 "IPv6용 Splunk 구성"에서 설명한 server.conf 설정을 통해) splunkd가 IPv6만 수신하도록 구성하려면 이 값을 127.0.0.1:8089에서 [::1]:8089로 변경해야 합니다. IPv6용 Splunk 구성 이 항목에서는 Splunk의 IPv6 지원과 IPv6을 위한 구성 방법에 대해 설명합니다. 이 항목의 절차를 수행하기 전에 다 음 매뉴얼을 읽어 보시면 도움이 됩니다. Splunk의 구성 파일 작동에 대해 알아보려면 이 매뉴얼의 "구성 파일에 대하여"를 읽어 보십시오. 데이터 가져오기 매뉴얼의 "TCP 및 UDP 포트에서 데이터 가져오기"를 읽어 보십시오. server.conf 구성 파일에서 사용 가능한 옵션 참조를 보려면 이 매뉴얼의 "server.conf"를 읽어 보십시오. inputs.conf 구성 파일에서 사용 가능한 옵션 참조를 보려면 이 매뉴얼의 "inputs.conf"를 읽어 보십시오. Splunk 버전 4.3부터 IPv6이 지원됩니다. IPv6 네트워크를 통해 Splunk Web에 연결하고 CLI를 사용하며 데이터를 전 달할 수 있습니다. 14

IPv6 플랫폼 지원 모든 Splunk 지원 OS 플랫폼(설치 매뉴얼의 "지원되는 OS" 참조)은 다음을 제외하고 IPv6 구성을 사용할 수 있도록 지원됩니다. HPUX PA-RISC Solaris 8 및 9 AIX IPv6 네트워크를 수신하도록 Splunk 구성 IPv6을 수신하도록 Splunk를 구성할 때 몇 가지 옵션이 있습니다. 다음과 같이 Splunk를 구성할 수 있습니다. IPv6 주소에만 연결하고 DNS의 모든 IPv4 결과는 무시 IPv4 및 IPv6 주소에 모두 연결 IPv6 주소 우선 연결 IPv4 주소 우선 연결 IPv4 주소에만 연결하고 DNS의 모든 IPv6 결과는 무시 Splunk가 IPv6을 수신하는 방법을 구성하려면 다음을 추가하도록 $SPLUNK_HOME/etc/system/local의 server.conf 복사본 을 편집하십시오. listenonipv6=[yes no only] yes는 splunkd가 IPv6 및 IPv4 둘 다로부터 연결을 수신함을 의미합니다. no는 splunkd가 IPv4만 수신함을 의미합니다. 이 값은 기본 설정입니다. only는 Splunk가 IPv6에서 들어오는 연결만 수신함을 의미합니다. connectusingipversion=[4-first 6-first 4-only 6-only auto] 4-first는 IPv4 주소에 우선 연결을 시도하고, 실패할 경우 IPv6을 시도함을 의미합니다. 6-first는 4-first와 반대입니다. 이것은 웹 브라우저와 같은 대부분의 IPv6 지원 클라이언트 앱에서 사용하는 정책입니다. 그러나 IPv6 배포의 초기 단계에서는 그 성능이 떨어질 수 있습니다. 4-only는 splunkd가 DNS의 모든 IPv6 결과를 무시함을 의미합니다. 6-only는 splunkd가 DNS의 모든 IPv4 결과를 무시함을 의미합니다. auto는 splunkd가 listenonipv6의 설정에 기반한 합리적인 정책을 선택함을 의미합니다. 이 값은 기본값입니다.. splunkd가 IPv4만 수신할 경우 이것은 4-only를 지정한 것처럼 작동합니다. splunkd가 IPv6만 수신할 경우 이것은 6-only를 지정한 것처럼 작동합니다. splunkd가 둘 다 수신 대기할 경우 이것은 6-first를 지정한 것처럼 작동합니다. 중요: 이 설정은 DNS 룩업에만 영향을 미칩니다. 예를 들어, connectusingipversion = 6-first를 설정하면 명시적 IPv4 주소(예: "server=10.1.2.3:9001")가 포함된 스탠자가 작동합니다. 입력이 몇 개 있지만 전체 배포에서 IPv6을 사용하지 않으려는 경우 IPv6을 통해 수신되는 몇 가지 데이터 소스가 있지만 전체 Splunk 배포에서 IPv6을 사용하지 않으려면 위에서 설명한 listenonipv6 설정을 inputs.conf의 모든 [udp], [tcp], [tcp-ssl], [splunktcp] 또는 [splunktcp-ssl] 스탠자에 추가하십 시오. 이 경우 특정 입력에 대한 server.conf의 동일한 이름 설정이 무시됩니다. IPv6을 통해 데이터 전달 Splunk Forwarder는 IPv6을 통해 전달할 수 있습니다. outputs.conf에서 다음과 같이 지원됩니다. [tcpout] 스탠자의 server 설정에는 표준 [host]:port 형식의 IPv6 주소가 포함될 수 있습니다. [tcpout-server] 스탠자는 표준 [host]:port 형식의 IPv6 주소를 사용할 수 있습니다. [syslog] 스탠자의 server 설정에는 표준 [host]:port 형식의 IPv6 주소가 포함될 수 있습니다. IPv6용 분산 검색 구성 Splunk 분산 검색 배포는 IPv6을 사용할 수 있습니다. distsearch.conf에서 다음과 같이 지원됩니다. servers 설정에는 표준 [host]:port 형식의 IPv6 주소가 포함될 수 있습니다. 그러나 heartbeatmcastaddr가 IPv6 주소를 지원하도록 업데이트되지 않았습니다. 이 설정은 Splunk 4.3에서 더 이상 사용되지 않아 이후 릴리스 제품부터 제거될 예정입니다. IPv6을 통해 Splunk Web에 액세스 네트워크 정책이 웹 브라우저에서 IPv6 연결을 허용하거나 요구할 경우 splunkd와 다르게 작동하도록 splunkweb 서 비스를 구성할 수 있습니다. web.conf는 4.3부터 listenonipv6 설정을 지원합니다. 이 설정은 위에서 설명한 server.conf의 설정과 동일하게 작동하지만, Splunk Web에만 적용됩니다. 대괄호로 묶어서 IPv6 주소를 사용할 수 있도록 기존 web.conf mgmthostport 설정이 확장되었습니다. 따라서 (앞에서 설 명한 server.conf 설정을 통해) splunkd가 IPv6만 수신하도록 구성할 경우 이 값을 127.0.0.1:8089에서 [::1]:8089로 변 경해야 합니다. 15

Splunk CLI 및 IPv6 Splunk CLI는 IPv6을 통해 splunkd와 통신할 수 있습니다. web.conf에 mgmthostport를 설정했거나 $SPLUNK_URI 환경 변 수를 정의했거나 -uri 명령줄 옵션을 사용한 경우 이렇게 작동합니다. -uri 옵션을 사용할 경우에는 IPv6 IP 주소를 대 괄호로 묶어야 하고 전체 주소와 포트는 큰따옴표로 묶으십시오. -uri "[2001:db8::1]:80". IPv6 및 SSO SSO과 함께 IPv6을 사용할 경우 아래 예와 같이 trustedip 속성에 대괄호 표기법을 사용하지 마십시오. 이 규칙은 web.conf 및 server.conf에 모두 적용됩니다. 다음 web.conf 예에서 mgmthostport 속성은 대괄호 표기법을 사용했지만 trustedip 속성은 대괄호 표기법을 사용하지 않 았습니다. [settings] mgmthostport = [::1]:8089 startwebserver = 1 listenonipv6=yes trustedip=2620:70:8000:c205:250:56ff:fe92:1c7,::1,2620:70:8000:c205::129 SSOMode = strict remoteuser = X-Remote-User tools.proxy.on = true SSO에 대한 자세한 내용은 이 매뉴얼의 "Splunk에서 SSO 사용"을 참조하십시오. Splunk Web 사용 Splunk Web 및 Splunk 관리자 정보 Splunk Web은 Splunk의 인터랙티브 동적 브라우저 기반 인터페이스입니다. Splunk Web은 문제를 조사하고, 결과 를 보고하고, Splunk 배포를 관리하는 기본 인터페이스입니다. 지원되는 운영 체제 및 브라우저 리스트는 해당 시스 템 요구 사항을 참조하십시오. Splunk Web 실행 다음으로 이동합니다. http://mysplunkhost:<port> 설치할 때 선택한 호스트와 포트를 사용합니다. Enterprise 라이선스를 사용하여 Splunk에 처음 로그인할 때 기본 로그인 정보는 다음과 같습니다. 사용자 이름 - admin 암호 - changeme 참고: 무료 라이선스를 사용하여 Splunk를 실행할 경우 액세스를 제어할 수 없으므로, 로그인 정보를 묻는 창이 나타 나지 않습니다. 참고: Splunk 버전 4.1.4부터 $SPLUNK_HOME/etc/local/server.conf를 편집하고 allowremotelogin을 Always로 설정하기 전 에는 원격 브라우저를 통해 Splunk Free에 액세스할 수 없습니다. Splunk Enterprise를 실행할 경우 기본 암호를 변경 하기 전까지 관리자의 원격 로그인을 기본적으로 사용할 수 없습니다(requireSetPassword로 설정되어 있음). Splunk 홈 Splunk에 처음 로그인하면 Splunk 홈으로 이동됩니다. 이 페이지의 맨 위에는 환영 탭과 Splunk 홈 탭의 두 가지 탭 이 있습니다. 환영 화면에는 데이터 추가 단추가 있습니다. 이 단추를 누르면 Splunk를 인덱스하도록 구성할 수 있는 데이터 유형 리스트 페이지로 이동됩니다. 설치된 앱을 보려면 Splunk 홈을 클릭하십시오. 16

이 페이지에서는 현재 사용 가능한 앱 리스트에서 앱을 선택할 수 있습니다. 더 많은 앱을 찾으려면 추가 앱 찾기 단추 를 클릭하십시오. 앱에 대해 자세히 알려면 계속 읽으십시오. Splunk 관리자 찾기 Splunk Web은 Splunk 작업의 대부분을 관리할 수 있는 편리한 인터페이스인 Splunk 관리자를 제공합니다. 관리자 에 액세스하려면 Splunk Web의 오른쪽 상단 모서리에 있는 링크를 클릭하십시오. 관리자를 사용하여 Splunk를 구성하는 방법은 "Splunk 관리자에 대하여"를 참조하십시오. 프록시 서버 지정 Splunk Web이 프록시 서버 뒤에 있을 경우 Splunk 웹 사이트에 액세스하는 Splunk Web 링크에 문제가 발생할 수 있 습니다. 예를 들어, 일부 관리자 페이지는 Splunk 앱 다운로드 사이트에 직접 연결됩니다. 이 문제를 해결하려면 http_proxy 환경 변수를 설정해야 합니다. 영구적인 결과를 얻기 위해 *nix 시스템의 경우 $SPLUNK_HOME/etc/, Windows의 경우 %SPLUNK_HOME%\etc\에 있는 splunk-launch.conf 구성 파일에서 해당 설정을 지정할 수 있습니다. splunk-launch.conf에서 다음 속성/값 쌍을 추가하십시오. http_proxy = <IP address or host name>:<port number> 예: http_proxy = 10.1.8.11:8787 중요: 프록시 서버가 HTTPS 요청만 처리할 경우 다음 속성/값 쌍을 사용하십시오. https_proxy = <IP address or host name>:<port number> 예: 17

https_proxy = 10.1.8.11:8888 Windows 관리자용 시작 지침 Windows 관리자를 위한 지침 환영합니다! 이 페이지는 Windows 관리자를 위한 시작하기 장으로, Splunk for Windows에 대한 정보를 확인할 수 있습니다. 이 장의 목적은 무엇입니까? Splunk는 Windows 관리자가 Windows 네트워크에서 발생하는 문제를 해결할 수 있는 효과적이고 강력한 도구입니 다. 즉시 사용이 가능한 기능 세트는 Windows 관리자에게 아주 유용합니다. 기능을 강화해주는 앱을 추가할 수 있는 기능을 통해 더 확장될 수 있습니다. 그리고 사용자 커뮤니티도 계속 늘어나고 있습니다. 이 페이지는 이 그룹의 사용자들을 대상으로 작성되었습니다. Splunk의 기능을 최대한 이용할 수 있도록 Windows 관 리자가 참고할 수 있는 중앙 리소스입니다. 이 장에서는 Splunk를 Windows에 설치하는 방법, Splunk 평가, 배포, 유 지 관리, 문제 해결 방법에 대한 매뉴얼과 링크를 제공합니다. 따라서 Windows 사용자들이 Splunk를 Windows 환경 에 맞게 구현하고 사용자 지정하는 방법에 관련된 참조 자료와 절차를 찾아보는 것이 훨씬 쉬워졌습니다. 이 장의 사용 방법 이 장은 Splunk를 학습 및 배포하고 Splunk 기능을 최대한 이용하는 데 유용한 항목으로 구성되어 있습니다. 각 항목 은 Windows 관리자에게 도움이 되는 다른 Splunk 매뉴얼을 참조합니다. Splunk 시험 사용에서는 Splunk 평가 방법에 대해 설명합니다. 이 장에서는 Splunk가 무엇인 지에 대해 알아봅니다. 또한 Splunk 설치 방법과 Splunk를 시험 사용하기 위해 필요한 시스템 요구 사항이 무엇인지 알아봅니다. 이 항목은 Windows에서 Splunk를 사용해본 경험이 없는 사용자나 제품을 평가하려는 초보 사용자에게 적합합니다. Splunk 기능에 대해 알아보기에서는 Splunk 기능에 대해 설명합니다. 이 항목에서는 Splunk로 들어오는 데이터 인 덱스, 검색, 보고 및 경고 방법에 대해 자세히 설명하는 여러 영역의 매뉴얼 링크를 제공합니다. 이 항목에서는 Splunk 가 Windows 플랫폼에서 어떻게 작동되고, 어떤 Windows 구성 요소를 모니터링할 수 있는지 알아봅니다. 이 항목은 Splunk의 내부 작동 원리를 이해하고자 하는 관리자에게 적합합니다. 엔터프라이즈에 Splunk 통합에서는 기존 Windows 네트워크에 Splunk를 추가하는 방법 또는 새 네트워크에 Splunk 를 통합하는 방법에 대한 가이드를 제공합니다. 이것은 선임 관리자 또는 IT 담당자에게 유용한 내용입니다. 이 항목 에는 시스템과 네트워크에 Splunk를 통합하는 방법에 대한 다양한 단계별 절차뿐만 아니라 Splunk 통합을 위한 높은 수준의 계획 시나리오도 포함되어 있습니다. Splunk 최대한 활용하기 항목은 현재 환경에 Splunk를 이미 통합하고 사용하면서 Splunk를 실행하는 데 유용한 참 고 자료나 팁을 원하는 관리자나 책임자에게 유용합니다. Splunk 사용 중에 발생할 수 있는 Windows 관련 문제를 해 결하는 방법에 대한 팁을 제공합니다. 현재 상황과 경험 수준에 따라 이 항목에 있는 여러 가지 내용을 하나씩 읽으면 도움이 됩니다. 순서대로 읽어도 되고 필요한 부분을 먼저 읽어도 됩니다. 나중에 필요할 때 이 항목을 참고 자료로 활용할 수 있습니다. Windows에서 Splunk를 처음 사용하는 경우에는 이 장을 처음부터 끝까지 읽어보시기 바랍니다. Splunk 사용 방법은 이미 알고 있지만 기술 정보나 참고 정보를 보고자 할 경우에는 이 항목의 뒷 부분을 읽어보시면 좋습니다. 도움이 필요한 경우 Splunk에 대해 상세히 알려는 경우 많은 교육 프로그램이 준비되어 있습니다. Splunk를 본격적으로 시작하게 되면 이용할 수 있는 대형 무료 지원 인프라가 제공됩니다. Splunk 응답 Splunk 커뮤니티 위키 Splunk IRC(Internet Relay Chat) 채널(EFNet splunk) (IRC 클라이언트 필수) 질문에 대한 답변이 여전히 없는 경우에는 Splunk 지원 팀에 연락하십시오. 지원 문의 페이지에 문의 방법이 자세히 나와 있습니다. 참고: 커뮤니티 레벨보다 높은 지원 레벨을 이용하려면 Enterprise 라이선스가 필요합니다. 이 라이선스를 받으려면 판매 팀에 문의해야 합니다. 읽어주셔서 감사합니다! Splunk 시험 사용 Splunk가 정확하게 어떻게 작동하고, 특히 사용자에게 어떤 이점이 있는 지에 대해 궁금할 것입니다. 가장 쉽고 빠른 방법은 직접 사용해 보는 것입니다. 사용자의 데스크톱이나 랩톱 컴퓨터를 사용하여 이 제품의 최초 평가를 수행할 수 18

있습니다. 다음은 처음에 수행해야 하는 단계입니다. 1. 시스템 요구 사항을 검토합니다. 이 단계는 Splunk를 실행하는 데 적합한 컴퓨터 유형을 확인하기 위한 중요한 첫 단계입니다. 참고: Splunk를 사용하여 수행할 작업에 따라 Splunk의 리소스 요구가 달라집니다. Splunk 평가를 위한 시스템 요구 사항은 Splunk의 어떤 부분을 평가하느냐에 따라 다릅니다. 로그 파일 수집 또는 성능 모니터링과 같은 기능을 평가 하는 것은 Splunk가 데스크톱이나 랩톱에 많은 부담을 주지 않습니다. 또한 이것은 가상 컴퓨터에서도 평가할 수 있 습니다. Splunk 사용 시 많은 데이터를 사용하는 경우에는 리소스가 집중적으로 사용됩니다. 평가 목적이더라도 서버에 소프트웨어를 설치하는 것이 좋습니다. 캡처를 원하는 데이터가 있는 서버에 소프트웨어 를 설치할 경우 평가 작업이 더 효율적으로 수행될 수 있습니다. 그리고 서버는 리소스가 집중적으로 사용되는 평가 작업을 처리할 수 있는 능력이 있어야 합니다. 프로덕션의 경우에는 하드웨어 계획을 더욱 세심히 고려해야 합니다. 관련 내용은 설치 매뉴얼에 나와 있습니다. 프로 덕션 레벨의 배포에는 어떤 종류의 하드웨어가 필요하며, 해당 배포에서 Splunk를 어떻게 분산해야 하는지 설명하는 관련 항목을 읽어 보시기 바랍니다. Splunk를 실행하기 전에 먼저 컴퓨팅 성능이 관련 요구를 충족할 수 있는지 항상 검토해야 합니다. 2. Splunk가 어떤 유형의 Windows 데이터에 액세스할 수 있는지 알아봅니다(데이터 가져오기 매뉴얼 참조). 3. 관련 사전 평가 정보 및 단계별 Windows 설치 지침은 사용자 매뉴얼의 "튜토리얼을 시작하기 전에" 항목에서 확인 합니다. 4. 평가 시스템에 Splunk를 설치합니다. 5. Splunk 튜토리얼을 참고합니다. 튜토리얼은 제품 평가를 시작하는 방법을 익히는 데 가장 효과적인 방법입니다. Splunk 기능에 대해 알아보기 Splunk를 시험 사용한 후에는 Windows 데이터를 어떻게 제어할 수 있는지 알아보십시오. Microsoft System Center 제품군과 같은 유틸리티와 Splunk를 비교하여 그 차이를 알고 싶거나, Splunk를 사용하여 일상적인 시스템 관리 작업 을 개선하는 방법이 궁금하다면 이 절에서 확인하십시오. 이벤트 로그, 레지스트리 등의 입력을 포함하여 Splunk가 제공하는 다양한 Windows 관련 데이터 입력을 사용하여 Splunk에 데이터를 가져오는 방법에 대해 알아보십시오. 또는 Splunk가 Active Directory에 대한 성능 또는 변경 사항 을 어떻게 모니터링하는지 알아보십시오. 추가 Windows 관심 항목: 설치된 모든 Splunk for Windows 서비스에 대한 개요(설치 매뉴얼 참조) Splunk의 모니터 대상(데이터 가져오기 매뉴얼 참조) 원격 Windows 데이터를 모니터링하는 방법을 결정할 때 고려할 사항(데이터 가져오기 매뉴얼 참조) 여러 컴퓨 터의 데이터를 원격으로 가져오는 방법에 대한 중요한 정보는 이 항목에서 확인하십시오. 여러 컴퓨터의 데이터 통합(분산 배포 매뉴얼 참조) 기타 유용한 정보: 내 데이터는 어디에 있습니까? (데이터 가져오기 매뉴얼 참조) Splunk 명령줄 인터페이스(CLI) 사용(데이터 가져오기 매뉴얼 참조) source, sourcetype 및 필드(데이터 가져오기 매뉴얼 참조) 필드 및 필드 추출(지식 관리자 매뉴얼 참조) 실시간 검색(사용자 매뉴얼 참조) 저장된 검색(사용자 매뉴얼 참조) 대시보드 생성(사용자 매뉴얼 참조) 엔터프라이즈에 Splunk 통합 앞에서 이 제품을 평가했으며 Windows 데이터에 대한 이해를 높이는 방법에 대해 알아 보았습니다. 이제 네트워크의 모든 컴퓨터에서 데이터를 가져올 수 있도록 제품을 배포해 보겠습니다. 통합은 Splunk 배포에서 매우 중요한 단계입니다. 이 절은 문제 없이 원활하게 통합하는 가장 좋은 방법을 결정하는 데 도움이 됩니다. 시작하는 방법은 다음과 같습니다. 일반적인 배포 시나리오에 대한 정보는 Windows에 Splunk 배포에서 이 항목을 찾아 보십시오. 시스템 이미지에 Splunk 배치 방법에 대해서는 계속 읽어 내려가십시오. Splunk 분산 배포 기능에 대해 알아보기 (분산 배포 매뉴얼 참조) Splunk를 Windows 컴퓨터에 설치했으면 다음과 같은 작업을 수행할 수 있습니다. 경고 구성 방법에 대해 알아보기 (관리자 매뉴얼 참조) 이 배포 모니터를 사용하여 Splunk 인스턴스에서 구성 파일 관리 Splunk 최대한 활용하기 19

네트워크에 Splunk를 설치 및 통합한 후에는 다음과 같은 작업을 비롯하여 여러 작업을 수행할 수 있습니다. 최고 성능으로 계속 실행하는 방법에 대해 알아보기 효율적으로 실행되지 않을 때 이 문제를 해결하는 방법에 대해 알아보기 Windows 앱(Microsoft Exchange용 앱)과 같은 플러그인과 Microsoft System Center Operations Manager에 대 한 추가 지원을 통해 Splunk의 기능 확장 Splunk를 최고 성능으로 최적화하는 방법 다른 많은 서비스와 마찬가지로 Windows에 설치된 Splunk 또한 최고 성능으로 실행하려면 적절한 유지 관리가 필요 합니다. 이 항목에서는 배포 과정에서 또는 배포 완료 후 Windows에 설치된 Splunk 배포를 올바르게 실행하기 위해 적용할 수 있는 방법에 대해 설명합니다. Splunk의 최고 성능을 유지하려면: 하나 이상의 컴퓨터를 Splunk 작업 전용으로 준비하십시오. Splunk는 수평적으로 확장됩니다. 즉, 단일 컴퓨터 에 더 많은 리소스를 지정하는 것이 아니라 Splunk 전용 물리적 컴퓨터를 더 많이 지정하기 때문에 더 나은 성능 을 발휘할 수 있습니다. 가능하다면 인덱싱 및 검색 작업을 여러 컴퓨터로 분할하고, 해당 컴퓨터에서는 기본 Splunk 서비스만 실행하십시오. 다른 서비스를 공유하는 서버에서 Splunk를 실행할 경우 범용 전달기 (Universal Forwarder)를 제외한 다른 성능이 저하됩니다. Splunk 인덱스 전용으로 가장 빠른 디스크를 지정하십시오. 시스템에서 Splunk 인덱싱에 사용 가능한 디스크 가 빠를수록 Splunk도 더 빠르게 실행됩니다. 가능하면 스핀들 속도가 10,000RPM 이상인 디스크를 사용하십 시오. Splunk 전용 중복 저장소를 지정할 경우 하드웨어 기반 RAID 1+0(또한 RAID 10으로도 알려짐)을 사용하 십시오. 이것은 속도와 중복에 대한 최적의 균형을 제공합니다. Windows 디스크 관리 유틸리티를 통한 소프트 웨어 기반 RAID 구성은 권장하지 않습니다. 바이러스 백신 프로그램이 Splunk 작업에 사용되는 디스크를 스캔하지 않도록 하십시오. 액세스할 때 바이러 스 백신 파일 시스템 드라이버가 파일에서 바이러스를 스캔할 경우 성능이 현저히 저하됩니다. 특히 Splunk에 서 최근에 인덱스된 데이터를 내부적으로 에이징할 경우에는 더욱 성능이 저하됩니다. Splunk가 실행되는 서버 에서 바이러스 백신 프로그램을 사용해야 할 경우 모든 Splunk 디렉터리와 프로그램을 파일 스캔에서 제외하십 시오. 가능하면 여러 인덱스를 사용하십시오. Splunk에서 인덱스된 데이터를 서로 다른 인덱스에 분산하십시오. 모든 데이터를 기본 인덱스로 보내면 시스템에서 I/O 병목 현상이 발생할 수 있습니다. 해당될 경우 가능하면 시스템 의 서로 다른 물리적 볼륨을 가리키도록 인덱스를 구성하십시오. 인덱스 구성 방법에 대한 내용은 이 매뉴얼의 "인덱스 구성"에서 확인하십시오. 운영 체제와 동일한 물리적 디스크 또는 파티션에 인덱스를 저장하지 마십시오. Windows OS 디렉터리 (%WINDIR%) 또는 해당 스왑 파일이 있는 디스크는 Splunk 데이터 저장소로 권장되지 않습니다. Splunk 인덱스를 시스템의 다른 디스크에 저장하십시오. 데이터베이스 버킷 유형, Splunk에서 데이터를 저장하고 에이징하는 방법 등을 포함하여 인덱스가 어떻게 저장되는 지 자세히 알아보려면 이 매뉴얼의 "Splunk에서 인덱스를 저장하는 방법"을 참조하십시오. Splunk 인덱스의 hot/warm 데이터베이스 버킷을 네트워크 볼륨에 저장하지 마십시오. 네트워크 지연으로 인 해 성능이 현저히 저하됩니다. Splunk 인덱스의 hot/warm 버킷용 로컬 고속 디스크를 예약하십시오. 인덱스의 cold/frozen 버킷을 위해 DFS(Distributed File System) 볼륨 또는 NFS(Network File System) 마운트와 같은 네 트워크 공유를 지정할 수 있습니다. 그러나 cold 데이터베이스 버킷에 저장된 데이터를 포함하는 검색은 더 느 려집니다. Splunk 인덱서에 대한 디스크 가용성, 대역폭 및 공간을 유지 관리하십시오. Splunk 인덱스가 저장된 디스크 볼 륨의 사용 가능한 공간이 항상 20% 이상을 유지해야 합니다. 디스크 검색 시간이 늘어나므로 사용 가능한 공간 과 비례하여 디스크 성능이 저하됩니다. 이는 Splunk가 데이터를 인덱스하는 속도에 영향을 미치고, 검색 결과, 보고서 및 경고를 얼마나 빨리 반환하는 지도 결정합니다. 기본 Splunk 설치에서 인덱스를 포함하는 드라이브 의 사용 가능한 공간은 최소 2048MB(2GB) 이상이어야 합니다. 그렇지 않으면 인덱싱이 일시 중지됩니다. 시스템 이미지에 Splunk 배치 이 항목에서는 Splunk를 모든 Windows 시스템 이미지 또는 설치 프로세스의 일부로 만드는 개념에 대해 설명합니다. 그리고 사용하는 이미징 유틸리티와 관계 없이 일반적인 통합 프로세스를 안내합니다. Windows 데이터를 Splunk로 가져오는 것과 관련된 내용은 데이터 가져오기 매뉴얼의 "Windows 데이터 및 Splunk에 대하여"에서 확인하십시오. 분산 Splunk 배포에 대한 내용은 분산 배포 매뉴얼의 "분산 개요"에서 확인하십시오. 이 개요는 사용하는 운영 체제와 관계 없이 Splunk 배포 설정 방법을 이해하는 데 꼭 필요한 내용입니다. Splunk 분산 배포 기능에 대해서 도 알 수 있습니다. 대규모 Splunk 배포 계획에 대한 내용은 설치 매뉴얼의 "대규모 Splunk 배포를 위한 하드웨어 용량 계획"과 이 매뉴얼의 "Windows에 Splunk 배포"에서 확인하십시오. Windows에서의 시스템 통합 개념 Splunk를 Windows 시스템 이미지에 통합하는 주요 이유는 엔터프라이즈에서 사용할 컴퓨터를 활성화했을 때 Splunk를 즉시 사용할 수 있도록 하기 위해서입니다. 이렇게 하면 활성화 후 Splunk를 설치 및 구성해야 할 필요가 없 어집니다. 20

이 시나리오에서는 Windows 시스템을 활성화하고 부팅하면 Splunk가 즉시 실행됩니다. 그런 다음 설치된 Splunk 인 스턴스 유형과 지정된 구성에 따라 Splunk가 컴퓨터에서 데이터를 수집하고 수집한 데이터를 인덱서로 전달하거나 (대부분의 경우) 또는 다른 Windows 컴퓨터에서 전달된 데이터의 인덱싱을 시작합니다. 또한 시스템 관리자는 Splunk 인스턴스를 배포 서버에 접속할 수 있도록 구성하여 추가 구성 및 업데이트 관리를 할 수 있습니다. 대부분의 일반적인 환경에서 Windows 컴퓨터의 범용 전달기(Universal Forwarder)는 중앙 인덱서 또는 인덱서 그룹 으로 데이터를 전송합니다. 그러면 특정 요구에 따라 데이터의 검색, 보고 및 경고가 허용됩니다. 시스템 통합 시 고려 사항 Splunk를 Windows 시스템 이미지에 통합하려면 계획이 필요합니다. 대부분의 경우 범용 전달기(Universal Forwarder)는 Windows 시스템 이미지와의 통합 시 선호되는 Splunk 구성 요소 입니다. 범용 전달기(Universal Forwarder)는 다른 역할을 수행하는 컴퓨터의 리소스를 공유하며, 훨씬 적은 비용으로 인덱서가 수행할 수 있는 많은 작업을 수행합니다. 또한 변경하기 위해 Splunk Web을 사용할 필요 없이 Splunk의 배 포 서버 또는 엔터프라이즈 범위의 구성 관리자를 사용하여 범용 전달기(Universal Forwarder)를 수정할 수 있습니다. 상황에 따라 Splunk의 전체 인스턴스를 시스템 이미지에 통합할 수도 있습니다. 적합한 시기와 위치는 특정 요구와 리소스 가용성에 따라 다릅니다. Splunk는 Forwarder에 대한 인덱서의 특정 용량 요구가 없는 경우 다른 유형의 역할을 수행하는 서버의 이미지에 Splunk의 전체 버전을 포함하는 것을 권장하지 않습니다. 엔터프라이즈에 여러 인덱서를 설치하더라도 인덱싱 성능 이나 속도를 추가로 제공하지 않으며 바람직하지 않은 결과로 이어질 수 있습니다. Splunk를 시스템 이미지에 통합하기 전에 다음을 고려하십시오. Splunk에서 인덱스할 데이터 양, 그리고 해당 데이터를 보낼 위치(있는 경우). 이러한 정보는 디스크 공간 계산 에 직접 사용되며 최우선으로 고려해야 할 사항입니다. 이미지 또는 컴퓨터에 설치할 Splunk 인스턴스의 유형. 범용 전달기(Universal Forwarder)는 다른 작업을 수행 하는 워크스테이션이나 서버에 설치할 경우 상당한 장점이 있지만, 그렇지 않은 경우도 있습니다. 이미징된 컴퓨터의 사용 가능한 시스템 리소스. 이미징된 각 시스템에서 사용할 수 있는 디스크 공간, RAM 및 CPU 리소스는 얼마나 됩니까? Splunk 설치를 지원합니까? 네트워크의 리소스 요구 사항. WMI를 사용하여 데이터를 수집하기 위해 원격 컴퓨터에 연결하는 데 Splunk를 사용하든지 아니면 각 컴퓨터에 Forwarder를 설치하고 데이터를 인덱서로 보내기 위해 Splunk를 사용하든지 Splunk에는 네트워크 리소스가 필요합니다. 이미지에 설치된 다른 프로그램의 시스템 요구 사항. Splunk가 다른 서버와 리소스를 공유할 경우 다른 프로그 램의 사용 가능한 리소스가 사용될 수 있습니다. Splunk의 전체 인스턴스를 실행 중인 워크스테이션 또는 서버 에 다른 프로그램을 설치할지 여부를 고려하십시오. 범용 전달기(Universal Forwarder)는 경량으로 설계되어 있 으므로 이러한 경우에 보다 효율적으로 작동합니다. 이미징된 컴퓨터가 현재 환경에서 수행하는 역할. Office와 같은 생산성 애플리케이션을 실행하는 워크스테이 션의 역할만 합니까? 아니면 Active Directory 포리스트를 위한 작업 마스터 도메인 컨트롤러의 역할을 합니까? Splunk를 시스템 이미지에 통합 앞에서 말한 체크리스트의 질문에 대한 답변을 결정했으면 그 다음 단계는 Splunk를 시스템 이미지에 통합하는 것입 니다. 나열된 단계는 선호하는 시스템 이미징 또는 구성 도구를 사용하여 작업을 완료하는 일반적인 단계입니다. 시스템 통합에 대한 다음 옵션 중 하나를 선택하십시오. 범용 전달기(Universal Forwarder)를 시스템 이미지에 통합 Splunk의 전체 버전을 시스템 이미지에 통합 범용 전달기(Universal Forwarder)를 시스템 이미지에 통합 이 항목에서는 Splunk 범용 전달기(Universal Forwarder)를 Windows 시스템 이미지에 통합하는 절차에 대해 설명합 니다. Splunk와 이미지 통합에 대한 자세한 내용은 "Splunk를 시스템 이미지에 통합"을 참조하십시오. 범용 전달기(Universal Forwarder)를 시스템 이미지에 통합하려면: 1. 참조 컴퓨터를 사용하여 필요한 Windows 기능, 패치 및 기타 구성 요소 등과 함께 원하는 위치에 Windows를 설치 및 구성합니다. 2. Splunk의 시스템 및 하드웨어 용량 요구 사항을 고려하여 필요한 애플리케이션을 설치 및 구성합니다. 3. 명령줄에서 범용 전달기(Universal Forwarder)를 설치 및 구성합니다. 이것은 최소한 LAUNCHSPLUNK=0 명령줄 플래그 를 제공합니다. 중요: 설치를 완료한 후 Splunk가 실행되지 않도록 하려면 LAUNCHSPLUNK=0 명령줄 플래그를 지정해야 합니다. 4. 설치에서 그래픽 부분을 수행합니다. 여기서 필요한 입력, 배포 서버 또는 Forwarder 대상을 선택합니다. 5. 설치가 완료되면 명령 프롬프트를 엽니다. 21

6. 설치 관리자에서 구성할 수 없는 추가 구성 파일을 이 프롬프트에서 편집합니다. 7..\splunk clean eventdata를 실행하여 모든 이벤트 데이터를 정리합니다. 8. 명령 프롬프트 창을 닫습니다. 9. 서비스 제어판에서 시작 유형을 '자동'으로 설정하여 splunkd 및 splunkweb 서비스가 자동으로 시작되도록 설정했는 지 확인합니다. 10. SYSPREP(Windows XP 및 Windows Server 2003/2003 R2인 경우) 또는 WSIM(Windows 시스템 이미지 관리 자)(Windows Vista, Windows 7 및 Windows Server 2008/2008 R2인 경우)과 같은 유틸리티를 사용하여 도메인 참여 를 위한 시스템 이미지를 준비합니다. 참고: Microsoft는 복제하기 전에 컴퓨터 SID(보안 식별자)를 변경하는 방법으로 타사 도구(Ghost Walker 또는 NTSID 등)를 사용하는 것보다 SYSPREP 및 WSIM을 사용할 것을 권장합니다. 11. 이미지를 위한 시스템 구성을 완료했으면 컴퓨터를 재부팅하고 선호하는 이미징 유틸리티를 사용하여 복제합니 다. 이제 배포할 이미지가 준비되었습니다. Splunk를 시스템 이미지에 통합 이 항목에서는 Splunk의 전체 버전을 Windows 시스템 이미지에 통합하는 절차에 대해 설명합니다. Splunk와 이미지 통합에 대한 자세한 내용은 "Splunk를 시스템 이미지에 통합"을 참조하십시오. Splunk의 전체 버전을 시스템 이미지에 통합하려면: 1. 참조 컴퓨터를 사용하여 필요한 Windows 기능, 패치 및 기타 구성 요소 등과 함께 원하는 위치에 Windows를 설치 및 구성합니다. 2. Splunk의 시스템 및 하드웨어 용량 요구 사항을 고려하여 필요한 애플리케이션을 설치 및 구성합니다. 3. Splunk를 설치 및 구성합니다. 중요: GUI 설치 관리자를 사용하여 설치할 수도 있지만 명령줄을 통해 패키지를 설치할 경우 더 많은 옵션이 있습니 다. 4. Splunk 입력을 구성했으면 명령 프롬프트를 엽니다. 5. 이 프롬프트에서 %SPLUNK_HOME%\bin 디렉터리로 변경하고.\splunk stop을 실행하여 Splunk를 중지합니다. 6..\splunk clean eventdata를 실행하여 모든 이벤트 데이터를 정리합니다. 7. 명령 프롬프트 창을 닫습니다. 8. 서비스 제어판에서 시작 유형을 '자동'으로 설정하여 splunkd 및 splunkweb 서비스가 자동으로 시작되도록 설정했는 지 확인합니다. 9. SYSPREP(Windows XP 및 Windows Server 2003/2003 R2인 경우) 또는 WSIM(Windows 시스템 이미지 관리 자)(Windows Vista, Windows 7 및 Windows Server 2008/2008 R2인 경우)과 같은 유틸리티를 사용하여 도메인 참여 를 위한 시스템 이미지를 준비합니다. 참고: Microsoft는 복제하기 전에 컴퓨터 SID(보안 식별자)를 변경하는 방법으로 타사 도구(Ghost Walker 또는 NTSID 등)를 사용하는 것보다 SYSPREP 및 WSIM을 사용할 것을 권장합니다. 10. 이미지를 위한 시스템 구성을 완료했으면 컴퓨터를 재부팅하고 선호하는 이미징 유틸리티를 사용하여 복제합니 다. 이제 배포할 이미지가 준비되었습니다. Windows에 Splunk 배포 여러 가지 방법으로 Windows 환경에 Splunk를 통합할 수 있습니다. 이 항목에서는 몇 가지 시나리오를 설명하고, 엔 터프라이즈에 Splunk for Windows 배포를 최적으로 적용하는 방법에 대한 지침을 제공합니다. 이 항목은 Windows 환경에 Splunk를 배포하는 데 초점을 맞추고 있습니다. 또한 Splunk 자체가 Windows 엔터프라 이즈에 Splunk를 통합할 때 배포 기능을 분산합니다. 분산 배포 매뉴얼은 수많은 컴퓨터에 Splunk 서비스를 배포하는 것에 대한 많은 정보를 제공합니다. 대규모 환경에서 Windows에 Splunk를 배포할 때 자체 배포 유틸리티(예: System Center Configuration Manager 또 는 Tivoli/BigFix)를 사용하여 Splunk 및 Splunk 구성을 모두 엔터프라이즈의 컴퓨터에 배포할 수 있습니다. 또는 Splunk를 시스템 이미지에 통합한 후 Splunk의 배포 서버를 사용하여 Splunk 구성과 앱을 배포할 수 있습니다. 개념 22

Splunk를 Windows 네트워크에 배포할 경우 Splunk는 컴퓨터에서 데이터를 수집한 후 중앙에 저장합니다. 데이터가 중앙에 저장되어 있으면 인덱스된 데이터를 기반으로 보고서와 대시보드를 검색하고 만들 수 있습니다. 시스템 관리 자 입장에서 더 중요한 것은 데이터가 도착할 때 어떤 일이 발생하는지 알 수 있게 Splunk가 경고를 보낼 수 있다는 점 입니다. 일반적인 배포에서는 인덱싱 용도로 사용할 전용 하드웨어를 Splunk에 지정한 다음 범용 전달기(Universal Forwarder)와 WMI(Windows Management Instrumentation)를 함께 사용하여 엔터프라이즈의 다른 컴퓨터에서 데이 터를 수집합니다. 고려 사항 Windows 엔터프라이즈에 Splunk를 배포하려면 수많은 계획 단계가 필요합니다. 먼저, 물리적 네트워크에서 시작하여 해당 네트워크의 컴퓨터를 개별적으로 구성하는 방법에 이르기까지 엔터프라이 즈를 인벤토리해야 합니다. 다음과 같은 작업을 수행해야 합니다. 환경에 있는 컴퓨터 개수를 세고 Splunk를 설치해야 하는 컴퓨터의 서브셋을 정의합니다. 이렇게 하면 Splunk 토폴로지의 초기 프레임워크가 정의됩니다. 기본 사이트 및 원격 또는 외부 사이트에서 모두 네트워크 대역폭을 계산합니다. 이 작업을 수행하면 기본 Splunk 인스턴스를 설치할 위치와 Splunk Forwarder 설치 위치 및 사용 방식이 결정됩니다. 특히, 네트워크가 구분되는 영역에서 네트워크의 현재 상태를 평가합니다. 에지 라우터 및 스위치가 올바르게 작동해야 배포 중과 배포 후에 네트워크 성능 기준을 설정할 수 있습니다. 다음으로, 배포를 시작하기 전에 다음과 같은 질문에 대한 답을 생각해야 합니다. 컴퓨터의 어떤 데이터를 인덱싱해야 하는가? 검색, 보고, 경고하려는 것이 이 데이터의 어떤 부분인가? 이것은 배포를 고려할 때 가장 중요한 고려 사항일 것입니다. 이러한 질문에 대한 답은 다른 고려 사항을 어떻게 처리할 지 결정합니다. Splunk를 설치할 위치와 이 설치에 사용할 Splunk 유형을 결정하고, Splunk에서 잠재적으로 사 용하게 되는 컴퓨팅 및 네트워크 대역폭도 결정합니다. 네트워크가 어떻게 배치되었나? 외부 사이트 링크가 어떻게 구성되었나? 이러한 링크에 어떤 보안이 제공되는 가? 네트워크 토폴로지에 대한 완벽한 이해는 Splunk를 어떤 컴퓨터에 설치하고, 네트워크 관점에서 해당 컴퓨 터에 어떤 유형의 Splunk(인덱서 또는 Forwarder)를 설치할지 쉽게 결정할 수 있습니다. 씬 LAN 또는 WAN 링크가 있는 사이트의 경우에는 사이트 간에 전송되는 Splunk 데이터 양을 고려해야 합니다. 예를 들어, 중앙 사이트가 지사 사이트에 연결된 hub-and-spoke 유형의 네트워크인 경우에는 지사 사이트의 컴퓨터에 Forwarder를 배포하는 것이 더 좋을 수도 있습니다. 이렇게 하면 각 지사의 중간 Forwarder로 데이터가 전송됩니다. 그런 다음, 중간 Forwarder가 데이터를 중앙 사이트로 다시 보냅니다. 이 방법은 지사 사이트의 모든 컴퓨터에서 중앙 사이트의 인덱서로 데이터를 전달하는 것보다 훨씬 비용이 적게 듭니다. 파일, 인쇄 또는 데이터베이스 서비스를 사용하는 외부 사이트인 경우에는 트래픽도 고려해야 합니다. AD(Active Directory)가 어떻게 구성되었나? 도메인 컨트롤러(DC)에서 작업 마스터 역할이 어떻게 정의되었 나? 모든 도메인 컨트롤러가 중앙에 있는가? 또는 위성 사이트에 위치한 컨트롤러를 가지고 있는가? AD가 분 산되어 있는 경우 브리지헤드 서버가 올바르게 구성되었는가? ISTG(Inter-site Topology Generator) 역할 서버 가 제대로 작동하는가? Windows Server 2008 R2를 실행 중인 경우 지사 사이트에 RODC(읽기 전용 도메인 컨 트롤러)가 있는가? 해당될 경우 Splunk 및 기타 네트워크 트래픽뿐만 아니라 AD 복제 트래픽의 영향도 고려해 야 합니다. 네트워크의 서버들은 어떤 다른 역할을 하는가? Splunk 인덱서는 최고 성능으로 실행하기 위해 리소스가 필요 합니다. 다른 리소스 집약 애플리케이션이나 서비스(예: Microsoft Exchange, SQL Server, Active Directory 자 체)와 서버를 공유할 경우 해당 컴퓨터에 설치된 Splunk에 잠재적으로 문제가 발생할 수 있습니다. Splunk 인덱 서와의 서버 리소스 공유에 대한 자세한 내용은 설치 매뉴얼의 "대규모 Splunk 배포를 위한 하드웨어 용량 계 획"을 참조하십시오. 사용자들과 배포에 대해 어떻게 커뮤니케이션할 것인가? Splunk 설치는 환경이 바뀐다는 것을 의미합니다. Splunk가 어떻게 구현되었는 지에 따라 컴퓨터에 새로운 소프트웨어가 설치됩니다. 사용자들은 새로운 설치로 인해 각 사용자 컴퓨터에 문제가 발생했거나 속도가 느려졌다고 잘못 생각할 수 있습니다. 배포와 관련된 지원 문의를 줄이려면 사용자들이 변경 사항에 대해 항상 알 수 있어야 합니다. Windows 배포에서 Splunk 준비 Splunk를 기존 환경에 어떻게 배치하는 지는 Splunk에 대한 요구에 따라 다릅니다. 사용 가능한 컴퓨팅 리소스, 물리 적 레이아웃 및 네트워크 레이아웃 그리고 회사 인프라와의 균형을 맞춰야 합니다. Splunk를 배포하는 방법이 하나만 있는 것이 아니므로 따라야 할 단계별 지침이 없습니다. 그러나 준수해야 할 일반적인 지침은 있습니다. 성공적인 Splunk 배포를 위한 지침: 네트워크를 준비합니다. Splunk를 환경에 통합하기 전: 네트워크가 올바르게 작동해야 하고 모든 스위치, 라우터 및 배선이 올바르게 구성되어 있어야 합니다. 고장났거나 결함이 있는 장비는 교체합니다. 모든 VLAN(가상 LAN)이 올바르게 설정되어야 합니다. 특히, 씬 네트워크 링크가 있는 사이트 간의 네트워크 처리량을 테스트합니다. Active Directory를 준비합니다. AD가 Splunk를 실행하는 데 필수적인 사항은 아니지만 배포 전에 AD가 올바 르게 작동하는지 확인하는 것이 좋습니다. 다음과 같은 작업을 수행해야 합니다. 모든 도메인 컨트롤러 및 작업 마스터 역할 식별. 지사 사이트에 RODC가 있는 경우, 작업 마스터 도메인 23

컨트롤러에 최대한 가장 빠른 연결을 제공해야 합니다. AD 복제가 올바르게 작동하고 모든 사이트 링크에는 전역 카탈로그의 복사본이 있는 도메인 컨트롤러가 있어야 합니다. 포리스트가 여러 사이트로 나누어져 있을 경우 ISTG 역할 서버가 올바르게 작동하거나 또는 사이트에 브 리지헤드 서버(하나는 기본, 하나는 백업용)를 두 개 이상 할당해야 합니다. DNS 인프라가 올바르게 작동해야 합니다. 필요한 경우 배치 중에 최고 AD 작업 및 복제 성능을 위해 네트워크의 다른 서브넷에 도메인 컨트롤러를 배치하고 유 연한 단일 마스터 작업(FSMO 또는 작업 마스터) 역할을 수행해야 할 수도 있습니다. Splunk 배포를 정의합니다. Windows 네트워크가 올바르게 준비되었으면 이제 Splunk를 네트워크의 어디에 배치할지 결정해야 합니다. 다음 사항을 고려하십시오. 각 컴퓨터에서 Splunk가 인덱스할 데이터 집합을 결정하고, 수집한 데이터에 대한 경고를 Splunk에서 보 내야 할지 여부를 결정합니다. 가능하면 Splunk 인덱싱을 처리할 각 네트워크 세그먼트에 하나 이상의 전용 컴퓨터를 지정합니다. 분산 Splunk 배포를 위한 용량 계획에 대한 자세한 내용은 설치 매뉴얼의 "대규모 Splunk 배포를 위한 하드웨 어 용량 계획"을 참조하십시오. AD(특히, FSMO 역할을 보유한 도메인 컨트롤러), Exchange(모든 버전), SQL Server 또는 컴퓨터 가상화 제품(예: Hyper-V 또는 VMWare)과 같이 리소스 집중 서비스를 실행하는 컴퓨터에는 Splunk의 전체 버전 을 설치하지 마십시오. 대신 범용 전달기(Universal Forwarder)를 사용하거나 WMI를 통해 이러한 컴퓨터 에 연결하십시오. Windows Server 2008/2008 R2 Core를 실행 중인 경우, 컴퓨터에 Splunk를 설치할 때 Splunk Web을 사 용하여 변경할 수 있는 GUI가 없습니다. 특히, 씬 WAN 링크에서 최소한의 네트워크 리소스를 사용하도록 Splunk 레이아웃을 정리합니다. 범용 전달기(Universal Forwarder)는 유선을 통한 Splunk 관련 트래픽 양을 크게 줄입니다. 사용자에게 배포 계획을 제대로 알립니다. 배포 과정 중에 배포 상태에 대해 사용자가 알 수 있도록 하는 것이 중 요합니다. 이렇게 하면 나중에 지원 관련 문의를 많이 줄일 수 있습니다. Splunk 라이선스 관리 Splunk 라이선싱 방식 Splunk는 관리자가 지정한 소스로부터 데이터를 가져와서 Splunk에서 분석할 수 있도록 데이터를 처리합니다. 이 프 로세스를 "인덱싱"이라고 합니다. 정확한 인덱싱 프로세스에 대한 내용은 데이터 가져오기 매뉴얼의 "Splunk의 데이 터 작업"을 참조하십시오. Splunk 라이선스는 역일(라이선스 마스터 시계 기준 자정에서 다음 자정까지의 24시간)당 인덱스할 수 있는 데이터 의 양을 지정합니다. 이렇게 하려면 인덱싱을 수행하는 Splunk 인프라의 모든 호스트에 라이선스가 있어야 합니다. 라이선스가 로컬로 설 치되어 있는 독립형 인덱서를 실행하거나 또는 Splunk 인스턴스 중 하나를 라이선스 마스터로 구성하고 라이선스 슬 레이브로 구성된 다른 인덱서에서 가져와 사용할 수 있는 라이선스 풀을 설정할 수 있습니다. 볼륨 인덱싱뿐만 아니라 Splunk Enterprise의 일부 기능을 사용하려면 Enterprise 라이선스가 필요합니다. 서로 다른 라이선스 유형에 대한 자세한 내용은 이 매뉴얼의 Splunk 라이선스 유형에서 확인하십시오. 라이선스 마스터와 라이선스 슬레이브 간의 연결에 대하여 라이선스 마스터 인스턴스가 구성되었으며 라이선스 슬레이브가 추가된 경우에는 라이선스 슬레이브는 분 단위로 라 이선스 마스터에게 사용을 알립니다. 라이선스 마스터에 연결할 수 없는 경우 라이선스 슬레이브는 24시간 타이머를 시작합니다. 라이선스 슬레이브가 24시간 동안 라이선스 마스터에 연결할 수 없는 경우 (인덱싱이 계속되더라도) 라 이선스 슬레이브에 대한 검색은 차단됩니다. 슬레이브가 라이선스 마스터에 다시 연결될 때까지 사용자는 라이선스 슬레이브에 있는 인덱스의 데이터를 검색할 수 없습니다. Splunk 라이선스 수명 주기 다운로드한 Splunk 사본을 처음 설치할 경우 Splunk의 해당 인스턴스는 60일 평가판 Enterprise 라이선스를 사용합 니다. 이 라이선스로 60일 동안 Splunk의 모든 Enterprise 기능을 사용할 수 있으며 하루에 최대 500MB까지 데이터를 인덱스할 수 있습니다. 60일 평가 기간이 끝난 후 Enterprise 라이선스를 구입하여 설치하지 않으면 Splunk Free로 전환할 수 있는 옵션이 표 시됩니다. Splunk Free에는 Splunk Enterprise 기능의 하위 집합이 포함되어 있으며, 독립형 배포 및 단기간 포렌식 조사 용도로 사용할 수 있습니다. Splunk Free는 무기한으로 하루에 최대 500MB의 데이터를 인덱스할 수 있습니다. 중요: 인증 또는 예약된 검색/경고는 Splunk Free에 포함되지 않습니다. 즉, Splunk Web 또는 CLI를 통해 Splunk 설 치에 액세스하는 사용자는 자격 증명을 제공할 필요가 없습니다. 또한 예약된 저장 검색/경고는 더 이상 실행할 수 없 게 됩니다. 60일 평가 기간이 만료된 후 Splunk의 Enterprise 기능을 계속 사용하려면 Enterprise 라이선스를 구입해야 합니다. 자세히 알아보려면 Splunk 판매 담당자에게 문의하십시오. Enterprise 라이선스를 구입하고 다운로드한 후에는 Splunk 인스턴스에 이 라이선스를 설치하고 Splunk Enterprise 기능에 액세스할 수 있습니다. Enterprise 기능에 대한 자세한 내용은 이 매뉴얼의 "Splunk 라이선스 유형"을 참조하 24

십시오. Splunk 라이선스 유형 각 Splunk 인스턴스에는 라이선스가 필요합니다. Splunk 라이선스는 지정된 Splunk 인스턴스가 인덱스할 수 있는 데 이터의 양을 지정하고, 액세스할 수 있는 기능을 지정합니다. 이 항목에서는 다양한 라이선스 유형과 옵션에 대해 설 명합니다. 일반적으로 다음 네 가지 라이선스 유형이 있습니다. Enterprise 라이선스는 인증 및 분산 검색 등의 모든 엔터프라이즈 기능을 제공합니다. Free 라이선스는 인덱싱 볼륨이 제한되고, 인증 기능을 사용할 수 없습니다. Forwarder 라이선스는 데이터 전달 기능과 인증 기능을 제공하지만, 인덱스 기능은 제공하지 않습니다. Beta 라이선스는 일반적으로 엔터프라이즈 기능을 제공하지만, Splunk 베타 릴리스로 제한됩니다. 또한 이 항목에서는 분산 검색 또는 인덱스 복제를 포함하는 배포의 경우 특별 라이선스 고려 사항에 대해서도 다룹니 다. Enterprise 라이선스 Splunk Enterprise는 표준 Splunk 라이선스입니다. 이 라이선스를 통해 인증, 분산 검색, 배포 관리, 경고 예약, 역할 기 반 액세스 제어를 포함한 Splunk의 모든 엔터프라이즈 기능을 사용할 수 있습니다. Enterprise 라이선스는 구입해서 사용할 수 있으며 모든 인덱싱 볼륨이 될 수 있습니다. 자세한 내용은 Splunk 판매부에 문의하십시오. 다음은 Enterprise 라이선스의 추가 유형으로, 동일한 기능이 모두 포함되어 있습니다. Enterprise 평가판 라이선스 Splunk를 처음 다운로드하면 등록하라는 메시지가 나타납니다. 등록하면 Enterprise 평가판 라이선스를 수신하며 이 라이선스는 하루에 최대 인덱싱 볼륨 500MB를 제공합니다. Enterprise 평가판 라이선스는 Splunk 사용을 시작한 날 로부터 60일 후에 만료됩니다. Enterprise 평가판 라이선스를 사용하다가 만료되면 Splunk Free 라이선스로 전환해 야 합니다. Splunk를 설치했으면 Enterprise 평가판 라이선스가 만료될 때까지 평가판 라이선스로 Splunk를 실행할 것인지, Enterprise 라이선스를 구입할지 또는 Free 라이선스로 전환(포함되어 있음)할지 선택할 수 있습니다. 참고: Enterprise 평가판 라이선스를 "다운로드 평가판"으로도 부릅니다. Sales 평가판 라이선스 Splunk Sales를 사용할 경우 크기와 기간이 다양한 Enterprise 평가판 라이선스를 요청할 수 있습니다. 기본 평가 기 간은 60일입니다. 대규모 배포의 파일럿을 준비하고 있으며 평가판 사용 기간 동안 사용 기간 또는 인덱싱 볼륨을 늘 려야 할 경우 Splunk Sales로 문의해 주십시오. 담당자가 바로 처리해드립니다. Free 라이선스 Free 라이선스는 하루 500MB의 인덱싱 볼륨을 무료로 만료 기간 없이 제공합니다. Enterprise 라이선스 버전에서 사용할 수 있는 다음 기능은 Splunk Free에서는 사용할 수 없습니다. 다중 사용자 계정 및 역할 기반 액세스 제어 분산 검색 TCP/HTTP 형식으로 전달(다른 Splunk 인스턴스로 데이터를 전달할 수 있지만 비 Splunk 인스턴스에는 전달 할 수 없음) 배포 관리(클라이언트용으로 포함) 경고/모니터링 자세한 내용은 이 매뉴얼 후반부에 나오는 Splunk 무료 버전에 대해 알아보기를 참조하십시오. Forwarder 라이선스 이 라이선스는 데이터의 무제한 전달(인덱스 기능은 제공 안 됨)이 가능하고, 사용자 액세스에 사용자 이름 및 암호를 제공하므로 인스턴스 보안이 가능합니다. (무료 라이선스는 무제한 데이터 전달에 사용할 수 있지만 보안이 되지 않습 니다.) Forwarder 라이선스는 Splunk에 포함되어 있으므로 별도로 구입할 필요가 없습니다. Splunk는 다양한 Forwarder 옵션을 제공합니다. 범용 전달기(Universal Forwarder)는 Forwarder 라이선스가 자동으로 적용되어 있으므로, 설치 후에 추가 작업 이 필요하지 않습니다. 경량형 전달기(Light Forwarder)도 동일한 라이선스를 사용하지만, Forwarder 라이선스 그룹으로 변경하여 직 접 라이선스를 활성화해야 합니다. 중량형 전달기(Heavy Forwarder)도 Forwarder 라이선스 그룹으로 직접 변환해야 합니다. 인덱싱 작업을 수행 할 경우 Enterprise 라이선스 스택에 대한 액세스가 필요합니다. Splunk 라이선스 용어에 대한 자세한 내용은 이 25

매뉴얼의 "그룹, 스택, 풀 및 기타 용어"에서 확인하십시오. Beta 라이선스 Splunk Beta 릴리스는 다른 Splunk 릴리스와 호환되지 않는 다른 라이선스가 필요합니다. 또한 Splunk Beta 릴리스 를 평가할 경우 Free 또는 Enterprise 라이선스로는 실행되지 않습니다. Beta 라이선스는 일반적으로 Enterprise 기능 을 제공하지만 Beta 릴리스로 제한됩니다. Splunk Beta 버전을 평가하는 경우 자체 라이선스가 함께 제공됩니다. 검색 헤드(분산 검색)를 위한 라이선스 검색 헤드는 검색을 다른 Splunk 인덱서로 배포하는 Splunk 인스턴스입니다. 검색 헤드는 일반적으로 데이터를 로컬 에서 인덱스하지 않지만, 여전히 액세스를 제한하기 위해 라이선스를 사용하고자 합니다. 검색 헤드에는 특수 라이선스 유형인 "검색 헤드 라이선스"가 없습니다. 그러나 검색 헤드를 구성하려면 Enterprise 라이선스가 필요하며 검색 헤드의 라이선싱은 Splunk 버전에 따라 다릅니다. 4.2 이전 버전의 Splunk는 각 검색 헤드에 대한 Forwarder 별도 라이선스를 사용할 것을 권장했습니다. 그 이유 는 Forwarder 라이선스가 인덱스를 허용하지 않고 검색 헤드 액세스에 대한 인증을 요구하기 때문입니다. 4.2 이후 버전의 Splunk는 각 피어에 별도 라이선스를 할당하는 대신 데이터를 인덱싱할 필요가 없는 경우에도 Enterprise 라이선스 풀에 검색 헤드를 추가하는 것을 권장합니다. 자세한 내용은 "그룹, 스택, 풀 및 기타 용어" 및 "라이선스 풀 만들기 또는 편집"에서 확인하십시오. 참고: 기존 검색 헤드에 4.2 이전 버전의 Forwarder 라이선스가 설치된 경우 업그레이드 후에는 이 Forwarder 라이선 스가 인식되지 않습니다. 클러스터 구성원을 위한 라이선스(인덱스 복제용) 어떤 Splunk 배포에서도 인덱서가 처리하는 데이터 볼륨에 따라 라이선스 요구 사항이 달라집니다. 추가 라이선스 볼 륨 구입은 Splunk 판매 담당자에게 문의하십시오. 인덱스 복제와 관련하여 다음과 같은 라이선스 문제가 있습니다. 마스터, 피어 및 검색 헤드를 포함한 모든 클러스터 구성원은 데이터를 인덱싱할 필요가 없는 경우에도 Enterprise 라이선스가 필요합니다. 클러스터 구성원은 동일한 라이선싱 구성을 공유해야 합니다. 수신 데이터만 라이선스로 카운트되고, 복제 데이터는 카운트되지 않습니다. Free 라이선스에서는 인덱스 복제를 사용할 수 없습니다. 자세한 내용은 인덱서 및 클러스터 관리 매뉴얼의 "시스템 요구 사항 및 기타 배포 고려 사항"에서 확인하십시오. 그룹, 스택, 풀 및 기타 용어 Splunk의 라이선싱 기능은 4.2 버전부터 많이 변경되었습니다. 호환되는 라이선스를 사용 가능한 라이선스 볼륨 스택 에 집계할 수 있고, 인덱서 풀을 정의하여 지정된 스택의 라이선스 볼륨을 사용할 수 있습니다. Splunk Free 사용자: 이 기능은 Enterprise 라이선스에만 해당됩니다. 독립형 인스턴스 Splunk Free를 사용하는 경우 에는 그룹, 풀 및 스택이 필요하지 않습니다. 풀 4.2 버전부터는 지정된 라이선스 스택에서 라이선스 볼륨의 풀을 정의할 수 있으며, 다른 인덱싱 Splunk 인스턴스를 볼륨 사용 및 추적을 위한 풀의 구성원으로 지정할 수 있습니다. 라이선스 풀은 단일 라이선스 마스터로 구성되며, Splunk의 0개 이상의 라이선스 슬레이브 인스턴스가 집합 라이선 26

스 또는 라이선스 스택의 라이선싱 볼륨을 사용하도록 구성됩니다. 스택 4.2 버전부터는 특정 유형의 Splunk 라이선스를 함께 집계하거나, 스택으로 쌓아둘 수 있습니다. 따라서 사용 가능한 라이선스 볼륨은 개별 라이선스 볼륨의 합계가 됩니다. 즉, 시간이 지남에 따라 필요한 경우 라이선스를 바꾸지 않고도 인덱스 볼륨 용량을 늘릴 수 있습니다. 대신 추가 용량 을 구입하여 해당 스택에 추가해야 합니다. 그룹 Enterprise 라이선스와 Sales 평가판 라이선스는 같이 서로 스택할 수 있습니다. 표준 Splunk 다운로드 패키지가 함께 포함되어 있는 Enterprise *평가판* 라이선스는 한 스택에 포함될 수 없습 니다. Enterprise 평가판 라이선스는 독립형으로 사용할 수 있으며 자체 그룹입니다. Enterprise 또는 판매용 평 가판 라이선스를 설치하기 전까지 스택을 만들거나 사용할 다른 인덱서의 풀을 정의할 수 없습니다. Splunk Free 라이선스는 Splunk Free 라이선스를 포함하여 다른 라이선스와 함께 스택할 수 없습니다. Forwarder 라이선스는 Forwarder 라이선스를 포함하여 다른 라이선스와 함께 스택할 수 없습니다. 라이선스 그룹에는 하나 이상의 스택이 포함됩니다. 스택은 하나의 그룹에만 속하는 구성원이므로 Splunk를 설치할 때 하나의 그룹만 "활성" 상태가 될 수 있습니다. 특히 이것은 지정된 라이선스 마스터가 한 번에 하나의 그룹 유형에 속하는 라이선스 풀만 관리할 수 있음을 의미합니다. 그룹은 다음과 같습니다. Enterprise/Sales 평가판 그룹 - 이 그룹은 구입한 Enterprise 라이선스와 Sales 평가판 라이선스(이것은 만료 기 한이 설정된 Enterprise 라이선스이며, 다운로드한 Enterprise 평가판과 동일한 라이선스가 아님)를 스택할 수 있습니다. Enterprise 평가판 그룹 - 이 그룹은 새 Splunk 인스턴스를 처음 설치할 경우 기본 그룹입니다. 여러 Enterprise 평가판 라이선스를 하나의 스택으로 결합하여 풀을 만들 수 없습니다. 다른 그룹으로 전환할 경우 Enterprise 평가판 그룹으로 다시 전환할 수 없게 됩니다. Free 그룹 - 이 그룹은 Splunk Free 설치를 수용하는 데 필요합니다. Enterprise 평가판 라이선스가 60일 후에 만 료될 경우 해당 Splunk 인스턴스는 Free 그룹으로 전환됩니다. 여러 Splunk Free 라이선스를 하나의 스택으로 결합하여 풀을 만들 수 없습니다. Forwarder 그룹 - 이 그룹은 Splunk를 범용 전달기(Universal Forwarder) 또는 경량형 전달기(Light Forwarder) 로 구성하는 데 필요합니다. 이러한 유형의 Forwarder는 인덱스를 수행하지 않습니다. 따라서 관리자의 라이선 싱 페이지를 통해 관리되지 않고 라이선스 그룹에 속하게 됩니다. Splunk 인스턴스의 라이선스 그룹을 Forwarder 그룹으로 변경할 경우 Splunk 인스턴스는 Forwarder로 구성되고 데이터를 인덱스하지 않는다고 가 정합니다. 자세한 내용은 Forwarder 및 "Forwarder 라이선스"를 참조하십시오. 라이선스 슬레이브 라이선스 슬레이브는 하나 이상의 라이선스 풀의 구성원입니다. 라이선스 볼륨에 대한 라이선스 슬레이브 액세스는 라이선스 마스터에 의해 제어됩니다. 라이선스 마스터 라이선스 마스터는 하나 이상의 라이선스 슬레이브를 제어합니다. 라이선스 마스터에서 풀을 정의하고 라이선싱 용 량을 추가하며 라이선스 슬레이브를 관리할 수 있습니다. 라이선스 설치 이 항목에서는 새 라이선스 설치에 대해 설명합니다. Splunk 라이선스 마스터에 여러 라이선스를 설치할 수 있습니 다. 계속하기 전에 다음 항목을 참조하십시오. Splunk 라이선싱에 대한 소개 내용은 이 매뉴얼의 "Splunk 라이선싱 방식"에서 확인하십시오. Splunk 라이선스 용어에 대한 자세한 내용은 이 매뉴얼의 "그룹, 스택, 풀 및 기타 용어"에서 확인하십시오. 새 라이선스 추가 새 라이선스를 추가하려면: 1. 관리자 > 라이선싱으로 이동합니다. 2. 라이선스 추가를 클릭합니다. 27

3. 파일 선택을 클릭하고 라이선스 파일을 찾아서 선택합니다. 또는 라이선스 XML을 직접 복사하여 붙여넣습니다를 클릭하여 라이선스 파일 내용을 제공된 필드에 붙여넣습니다. 4. 설치를 클릭합니다. Enterprise 라이선스를 처음 설치하는 경우 Splunk를 재시작해야 합니다. 라이선스가 설치되었 습니다. 라이선스 마스터 구성 이 항목에서는 Splunk 인스턴스를 라이선스 마스터로 구성하는 것에 대해 설명합니다. 계속하기 전에 다음 항목을 참 조하십시오. Splunk 라이선싱에 대한 소개 내용은 이 매뉴얼의 "Splunk 라이선싱 방식"에서 확인하십시오. Splunk 라이선스 용어에 대한 자세한 내용은 이 매뉴얼의 "그룹, 스택, 풀 및 기타 용어"에서 확인하십시오. 라이선스 마스터 종류 다음과 같은 두 가지 기본 스타일의 라이선스 마스터가 있습니다. 독립형 라이선스 마스터 단일 Splunk 인덱서가 있는 경우 이 인덱서의 라이선스를 관리하려면 이 Splunk 인덱서를 라이선스 마스 터로 실행하고 이 Splunk 인덱서에 Enterprise 라이선스를 하나 이상 설치하십시오. 그러면 단일 Splunk 인덱서가 라이선스 슬레이브로 자체 관리합니다. Splunk를 처음 다운로드하고 설치하면 500MB 60일 Enterprise 평가판 라이선스가 포함되어 있습니다. Splunk의 이 인스턴스는 독립형 라이선스 마스터로 자동 구성되며 이 유형의 라이선스에 대해서는 풀을 만들거나 라이선스 슬레이브를 정의할 수 없습니다. 하나 이상의 스택 또는 풀을 만들고 여러 인덱서를 할 당하려면 Enterprise 라이선스를 구입하여 설치해야 합니다. 라이선스를 설치하려면 이 매뉴얼의 "라이선 스 설치" 설명을 참조하십시오. 중앙 라이선스 마스터 둘 이상의 인덱서가 있으며 구입한 라이선스 용량에 대한 액세스를 중앙 위치에서 관리하려면 중앙 라이 선스 마스터를 구성하고 인덱서를 라이선스 슬레이브로 마스터에 추가해야 합니다. 라이선스 마스터가 인덱서인 경우에도 이것은 자체 라이선스 마스터가 되지만, 검색 헤드가 있는 경우에 는 이것을 라이선스 마스터로 지정하는 것이 좋습니다. 검색 헤드가 여러 개인 대규모 환경에서는 다음 두 가지 이유에서 라이선스 마스터가 아닌 일부 또는 전체 검색 헤드를 라이선스 마스터에 검색 분산을 수행해야 합니다. 라이선스 로그에 대해 검색을 실행할 수 있습니다. 시간 기반 라이선스를 가진 상태에서 5일 안에 만료되는 경우와 같은 드문 조건이 검색 헤드에서 발 생할 경우, 검색이 실행될 때 검색 결과에 첨부되는 정보 메시지의 일부로 이 조건이 해당 검색 헤드 에 표시됩니다. 중앙 라이선스 마스터 구성 기본적으로 Splunk의 독립형 인스턴스는 자체 라이선스 마스터입니다. 중앙 라이선스 마스터를 구성하려면 하나 이 상의 Enterprise 라이선스를 설치하십시오. Enterprise 라이선스를 설치했으면 하나 이상의 스택 및 풀을 생성하여 설치된 라이선스에 액세스할 수 있으며, 라이 선스 마스터에서 이를 관리할 수 있습니다. 라이선스 슬레이브 구성 이 항목에서는 Splunk 인덱서를 라이선스 슬레이브로 구성하는 방법에 대해 설명합니다. 계속하기 전에 다음 항목을 참조하십시오. Splunk 라이선싱에 대한 소개 내용은 이 매뉴얼의 "Splunk 라이선싱 방식"에서 확인하십시오. Splunk 라이선스 용어에 대한 자세한 내용은 이 매뉴얼의 "그룹, 스택, 풀 및 기타 용어"에서 확인하십시오. 라이선스 마스터를 설정하는 방법은 이 매뉴얼의 "라이선스 마스터 구성"에서 확인하십시오. 명령줄에서 이러한 작업 수행에 대한 도움이 필요하면 이 매뉴얼의 "CLI를 통해 라이선스 관리"에서 확인하십 시오. 1. 라이선스 슬레이브로 구성할 인덱서에서 Splunk Web에 로그인한 후 관리자 > 라이선싱으로 이동합니다. 2. 슬레이브로 변경을 클릭합니다. 3. 이 Splunk 인스턴스 <이 인덱서>을(를) 마스터 라이선스 서버로 지정 라디오 단추를 선택 취소하고 다른 Splunk 인스턴스를 마스터 라이선스 서버로 지정을 선택합니다. 4. 이 라이선스 슬레이브가 보고할 라이선스 마스터를 지정합니다. IP 주소 또는 호스트 이름과 Splunk 관리 포트를 입력해야 합니다. 이 관리 포트는 기본적으로 8089입니다. 참고: IP 주소는 IPv4 또는 IPv6 형식으로 지정할 수 있습니다. IPv6 지원에 대한 자세한 내용은 이 매뉴얼의 "IPv6용 28

Splunk 구성"을 확인하십시오. 5. 저장을 클릭합니다. 이 인스턴스에 Enterprise 라이선스를 아직 설치하지 않은 경우 Splunk를 재시작해야 합니다. 이제 이 인덱서가 라이선스 슬레이브로 구성됩니다. 다시 전환하려면 관리자 > 라이선싱으로 이동하고 로컬 마스터로 전환을 클릭합니다. 이 인스턴스에 Enterprise 라이 선스를 아직 설치하지 않은 경우 이 변경 사항을 적용하려면 Splunk를 재시작해야 합니다. 라이선스 풀 만들기 또는 편집 이 항목에서는 설치된 하나 이상의 라이선스에서 라이선스 풀 만들기와 기존 라이선스 풀을 편집하는 방법에 대해 설 명합니다. 계속하기 전에 다음 항목을 참조하십시오. Splunk 라이선싱에 대한 소개 내용은 이 매뉴얼의 "Splunk 라이선싱 방식"에서 확인하십시오. Splunk 라이선스 용어에 대한 자세한 내용은 이 매뉴얼의 "그룹, 스택, 풀 및 기타 용어"에서 확인하십시오. 라이선스 설치에 대해 자세히 알아보려면 "라이선스 설치"에서 확인하십시오. 명령줄에서 이러한 작업 수행에 대한 도움이 필요하면 이 매뉴얼의 "CLI를 통해 라이선스 관리"에서 확인하십 시오. Splunk를 처음 다운로드하고 설치하면 500MB 60일 Enterprise 평가판 라이선스가 포함되어 있습니다. Splunk의 이 인스턴스는 독립형 라이선스 마스터로 자동 구성되며 이 유형의 라이선스에 대해서는 풀을 만들거나 라이선스 슬레 이브를 정의할 수 없습니다. 하나 이상의 스택 또는 풀을 만들고 여러 인덱서를 할당하려면 Enterprise 라이선스를 구 입하여 설치해야 합니다. 다음 예제에서는 5MB Enterprise 라이선스가 새로운 Splunk 설치에 설치되었습니다. 새로운 Splunk 서버에 Enterprise 라이선스를 설치할 경우 Splunk는 Enterprise 라이선스 스택(또는 Splunk 29

Enterprise Stack)을 자동으로 만들고 해당 기본 라이선스 풀(auto_generated_pool_enterprise)을 정의합니다. 이 기본 풀에 대한 기본 구성은 이 라이선스 마스터에 연결된 모든 라이선스 슬레이브를 풀에 추가합니다. 풀을 편집 하여 이 구성을 변경하거나 풀에 인덱서를 더 많이 추가하거나 이 스택에서 새로운 라이선스 풀을 만들 수 있습니다. 기존 라이선스 풀을 편집하려면 1. 편집할 라이선스 풀 옆에 있는 편집을 클릭합니다. 라이선스 풀 편집 페이지가 나타납니다. 2. 할당을 변경하거나 인덱서가 이 풀에 액세스하는 방식을 변경할 수 있습니다. 풀 이름은 변경할 수 없지만 설명은 변경할 수 있습니다. 3. 제출을 클릭합니다. 새 라이선스 풀을 만드는 방법 중요: 기본 Enterprise 스택에서 새 라이선스 풀을 만들려면 먼저 auto_generated_pool_enterprise 풀을 편집하고 풀 할 당을 줄이거나 풀 전체를 삭제하여 사용 가능한 인덱스 볼륨을 확보하십시오. 풀 이름 옆에 있는 삭제를 클릭하여 해 당 풀을 삭제하십시오. 1. 를 클릭합니다. 새 라이선스 풀 만들기 페이지가 나타납니다. 2. 풀의 이름을 지정하고 설명(옵션)을 입력합니다. 3. 이 풀의 할당을 설정합니다. 이 할당은 전체 스택 라이선싱 볼륨 중에서 이 풀에 속하는 인덱서가 사용할 수 있는 볼 륨을 지정합니다. 이 할당은 특정 값으로 지정될 수 있고, 다른 풀에 할당되지 않은 경우에는 해당 스택에서 사용 가능 한 전체 인덱스 볼륨이 이 값이 될 수 있습니다. 4. 인덱스가 이 풀에 액세스하는 방식을 지정합니다. 다음 옵션이 있습니다. 라이선스 슬레이브로 구성된 환경의 인덱서는 이 라이선스 풀에 연결하여 이 풀 내에서 라이선스 할당을 사용할 수 있습니다. 지정한 인덱서만 이 풀에 연결할 수 있으며 이 풀 내에서 라이선스 할당을 사용할 수 있습니다. 5. 허용할 인덱서를 지정하려면 사용 가능한 인덱서 리스트에서 인덱서 이름 옆에 있는 더하기 기호를 클릭합니다. 해 당 인덱서가 연결된 인덱서 리스트로 이동합니다. 라이선스 풀에 인덱스 추가 이 항목에서는 기존 라이선스 풀에 인덱서를 추가하는 방법에 대해 설명합니다. 계속하기 전에 다음 항목을 참조하십 시오. Splunk 라이선싱에 대한 소개 내용은 이 매뉴얼의 "Splunk 라이선싱 방식"에서 확인하십시오. Splunk 라이선스 용어에 대한 자세한 내용은 이 매뉴얼의 "그룹, 스택, 풀 및 기타 용어"에서 확인하십시오. 인덱서가 라이선스 풀에 액세스하는 방식 라이선스 풀의 스택에 대한 액세스는 해당 풀의 라이선스 마스터에 의해 제어됩니다. 특정 인덱서에게만 액세스를 허 용하도록 풀을 구성하거나, 라이선스 마스터의 URI와 관리 포트를 지정하여, 이와 연결된 인덱서에 대한 액세스는 모 두 허용하도록 구성할 수 있습니다. 특정 인덱서 추가 지정된 라이선스 풀의 스택에 대한 특정 인덱서의 액세스를 허용하려면 다음 기본적인 두 단계를 수행하십시오. 1. 인덱서를 라이선스 슬레이브로 구성하고 인덱서에 라이선스 마스터의 URI와 관리 포트를 지정합니다. 자세한 내용 30

1. 인덱서를 라이선스 슬레이브로 구성하고 인덱서에 라이선스 마스터의 URI와 관리 포트를 지정합니다. 자세한 내용 은 이 매뉴얼의 "라이선스 슬레이브 구성" 지침에 따르십시오. 2. 인덱서에서 액세스를 허용하도록 라이선스 관리자에서 풀을 구성합니다. 이 작업을 수행하려면 "라이선스 풀 만들 기 또는 편집" 지침에 따라 라이선스 풀을 편집하고 특정 인덱서에 대한 액세스만 허용하도록 라디오 단추 옵션을 선 택한 후 "사용 가능한 인덱서" 리스트에서 인덱서 이름 옆의 더하기 기호를 클릭하여 "연결된 인덱서" 리스트로 이동 시키십시오. 연결된 모든 인덱서 추가 다음 단계에 따라 이 라이선스 마스터에 연결된 모든 인덱서에 라이선스 풀 스택에 대한 액세스를 제공하십시오. 1. 인덱서를 라이선스 슬레이브로 구성하고 인덱서에 라이선스 마스터의 URI와 관리 포트를 지정합니다. 자세한 내용 은 이 매뉴얼의 "라이선스 슬레이브 구성" 지침에 따르십시오. 2. 인덱서에서 액세스를 허용하도록 라이선스 관리자에서 풀을 구성합니다. 이 작업을 수행하려면 "라이선스 풀 만들 기 또는 편집" 지침에 따라 라이선스 풀을 편집하고 연결하는 임의 인덱서에 대한 액세스를 허용하는 라디오 단추 옵 션을 선택하십시오. 라이선스 관리 이 항목에서는 Splunk 라이선스 관리에 대해 설명합니다. 계속하기 전에 다음 항목을 참조하십시오. Splunk 라이선싱에 대한 소개 내용은 이 매뉴얼의 "Splunk 라이선싱 방식"에서 확인하십시오. Splunk 라이선스 용어에 대한 자세한 내용은 이 매뉴얼의 "그룹, 스택, 풀 및 기타 용어"에서 확인하십시오. 명령줄에서 이러한 작업 수행에 대한 도움이 필요하면 이 매뉴얼의 "CLI를 통해 라이선스 관리"에서 확인하십 시오. 라이선스 삭제 라이선스가 만료되면 해당 라이선스를 삭제할 수 있습니다. 하나 이상의 라이선스를 삭제하려면 다음 작업을 수행하 십시오. 1. 라이선스 마스터에서 관리자 > 라이선싱으로 이동합니다. 2. 삭제할 라이선스 옆의 삭제를 클릭합니다. 3. 삭제를 클릭하여 다시 확인합니다. 참고: 라이선스 마스터에서 라이선스 리스트 중 마지막 라이선스는 삭제할 수 없습니다. 라이선스 사용량 보기 Splunk 배포 모니터 앱을 통해 라이선스 사용량을 모니터링할 수 있습니다. 이 배포 모니터의 라이선스 사용량 페이 지에는 다양한 내역 정보가 표시됩니다. 그리고 라이선스 보고서 페이지에서는 60일 기간 동안 일별 라이선스 사용량 에 대한 세부정보를 제공합니다. 배포 모니터 앱에 대해 자세히 알아보고 이 앱이 라이선스 사용량을 모니터링하는 데 어떻게 도움이 되는지 알아보려 면 Splunk 배포 모니터 앱 배포 및 사용 매뉴얼을 읽어보십시오. 라이선스 위반에 대하여 이 항목에서는 라이선스 위반이 어떤 것이며, 어떤 경우에 발생하고 어떻게 해결하는지 설명합니다. 계속하기 전에 다 음 항목을 참조하십시오. Splunk 라이선싱에 대한 소개 내용은 이 매뉴얼의 "Splunk 라이선싱 방식"에서 확인하십시오. Splunk 라이선스 용어에 대한 자세한 내용은 이 매뉴얼의 "그룹, 스택, 풀 및 기타 용어"에서 확인하십시오. 라이선스 위반 및 경고의 정의 라이선스가 허용하는 최대 인덱스 볼륨을 초과할 때 위반이 발생합니다. 역일(자정에서 다음 자정까지의 24시간)의 라이선스 일별 볼륨을 초과할 경우 위반 경고가 발생합니다. 이 메시지는 14일간 나타납니다. 30일 기간 동안 계속 Enterprise 라이선스에서 5개 이상의 경고가 발생하거나 Free 라이선스에서 3개의 경고가 발생할 경우 라이선스 위 반에 해당됩니다. 이 경우 문제가 되는 풀은 검색할 수 없지만 다른 풀은 계속 검색할 수 있고 영향을 받지 않습니다. 이전 30일 동안 경고가 5개보다 적거나(Enterprise), 3개보다 적을 때(Free) 또는 임시 Reset 라이선스(Enterprise만 해당됨)를 적용할 경우에는 검색 기능을 다시 사용할 수 있습니다. Reset 라이선스를 받으려면 판매 담당자에게 문의 하십시오. 라이선스는 라이선스 적용 지침이 함께 제공됩니다. 31

참고: 라이선스 위반이 발생하더라도 요약 인덱싱 볼륨은 라이선스에 카운트되지 않습니다. 요약 인덱싱은 내부가 아 닌 다른 검색 동작을 중지합니다. 위반 경고가 발생할 경우 라이선스 마스터가 자정까지 이 경고를 해결하면 30일 기간 내에 총 경고 수로 카운트되지 않습니다. 라이선스 위반 기간 중에는 다음에 유의하십시오. Splunk는 데이터 인덱싱을 중지하지 않습니다. 라이선스를 초과할 경우에만 검색이 차단됩니다. _internal 인덱스는 검색할 수 없습니다. 즉, 인덱스 상태 대시보드에는 계속 액세스할 수 있으며 _internal에 대 한 검색을 통해 라이선스 문제를 진단할 수도 있음을 의미합니다. 라이선스 경고 표시 풀에 있는 인덱서가 해당 풀에 할당된 라이선스 볼륨을 초과할 경우 Splunk Web 상단에 노란색 경고 배너가 표시됩 니다. 배너에 나온 링크를 클릭하면 관리자 > 라이선싱으로 이동됩니다. 이 페이지의 경고 섹션 아래 경고가 표시됩니다. 경 고를 클릭하면 자세한 정보가 나타납니다. 위반이 발생하면 라이선스 슬레이브에도 비슷한 배너가 표시됩니다. 다음은 라이선싱 경고가 생성되는 몇 가지 조건입니다. 슬레이브가 고아가 되면 경고(자정 전까지는 수정 가능한 일시적 오류)가 발생합니다. 풀이 용량을 초과하면 경고(자정 전까지는 수정 가능한 일시적 오류)가 발생합니다. 스택이 최대 용량을 초과하면 경고(자정 전까지는 수정 가능한 일시적 오류)가 발생합니다. 하나 이상의 슬레이브에 경고가 발생하면 이 경고가 마지막 30일 기간 동안 계속 유효하다면 경고가 계속 나타 납니다. 라이선스 마스터와 라이선스 슬레이브 간의 연결에 대하여 라이선스 마스터 인스턴스가 구성되었으며 라이선스 슬레이브가 추가된 경우에는 라이선스 슬레이브는 분 단위로 라 이선스 마스터에게 사용을 알립니다. 라이선스 마스터에 연결할 수 없는 경우 라이선스 슬레이브는 24시간 타이머를 시작합니다. 라이선스 슬레이브가 24시간 동안 라이선스 마스터에 연결할 수 없는 경우 (인덱싱이 계속되더라도) 라 이선스 슬레이브에 대한 검색은 차단됩니다. 슬레이브가 라이선스 마스터에 다시 연결될 때까지 사용자는 라이선스 슬레이브에 있는 인덱스의 데이터를 검색할 수 없습니다. 라이선스 슬레이브가 라이선스 마스터에 도달하지 못했는지 알아보려면 splunkd.log에서 failed to transfer rows가 포함된 이벤트를 검색하거나 내부 인덱스에서 검색하십시오. 라이선스 위반을 방지하는 방법 라이선스 위반을 방지하려면 라이선스 사용량을 모니터링하여 충분한 라이선스 볼륨을 항상 유지해야 합니다. 라이 선스 볼륨이 충분하지 않을 경우 라이선스를 늘리거나 인덱싱 볼륨을 줄여야 합니다. 다음은 라이선스 사용량 모니터링을 위한 몇 가지 옵션입니다. 배포 모니터에서 라이선스 사용량 탭을 통해 현재 배포에서 라이선스 용량이 어떻게 사용되고 있는지 확인할 수 있습니다. 자세한 내용은 이 매뉴얼의 "라이선스 관리"를 확인하십시오. 관리자 > 라이선싱으로 이동하여 라이선스 경고 및 위반 사항 등의 라이선스 세부정보를 표시합니다. 인프라의 인덱스 볼륨에 대한 세부정보를 보려면 검색 앱에서 "볼륨 인덱스" 상태 대시보드를 사용하십시오. 개 요에는 사용자 라이선스에 포함되지 않는 내부 인덱싱이 포함됩니다. 볼륨 인덱스 상태 대시보드 액세스 "볼륨 인덱스" 대시보드를 보려면: 1. Splunk Web에 로그인하고 검색 앱으로 이동합니다. 2. 상태 > 인덱스 작업 > 볼륨 인덱스를 클릭합니다. 3. 서버, "분할 기준" 옵션(source, source type, index 또는 host별 볼륨 인덱스를 보기 위해) 및 시간 범위를 선택합니 다. 대시보드는 결과를 자동으로 재로드하고 업데이트합니다. 4. 더 자세히 드릴다운하려면 리스트에서 해당 행을 클릭합니다. 여기서 시간 표시줄의 이벤트를 볼 수 있습니다. 이벤 트 페이지를 보려면 시간 표시줄에서 해당 막대를 클릭합니다. 32

라이선스 위반 문제 해결 이 커뮤니티 위키 항목은 인덱스된 데이터 볼륨의 문제를 해결하는 데 도움이 됩니다. 답변 질문이 있으십니까? Splunk 응답 페이지에 가면 라이선스 위반과 관련하여 Splunk 커뮤니티에서 올린 질문과 답변을 볼 수 있습니다. 새로운 Splunk 라이선서로 마이그레이션 이 항목에서는 4.2 이전 Splunk 배포에서 새로운 (4.2+) 라이선서 모델로 라이선스 구성을 마이그레이션하는 방법에 대해 설명합니다. 이 항목에서 Splunk 전체 배포에 대한 마이그레이션을 모두 설명하지는 않습니다. Splunk 배포를 마이그레이션하기 전에 설치 매뉴얼에서 이 마이그레이션 항목의 내용을 읽어보십시오. 계속하기 전에 다음 항목을 참조하십시오. Splunk 라이선싱에 대한 소개 내용은 이 매뉴얼의 "Splunk 라이선싱 방식"에서 확인하십시오. Splunk 라이선스 용어에 대한 자세한 내용은 이 매뉴얼의 "그룹, 스택, 풀 및 기타 용어"에서 확인하십시오. 이전 라이선스 이전 버전에서 마이그레이션하는 경우는 대부분 다음 두 가지 범주 중 하나에 해당됩니다. 현재 Splunk 4.0 이상을 실행하는 경우 라이선스는 4.2에서 작동합니다. 4.0 이전 버전에서 마이그레이션할 경우 Splunk 판매부 담당자에게 연락하여 새 라이선스를 받아야 합니다. 이 마이그레이션을 계속하기 전에 해당 마이그레이션 매뉴얼을 읽어보는 것이 좋습니다. Splunk 버전에 따라 구성 을 유지 관리하기 위해 여러 단계로 마이그레이션할 수 있습니다. 검색 헤드 마이그레이션 검색 헤드가 이전 Forwarder 라이선스를 사용하는 경우 다운로드 평가판 그룹으로 자동 전환됩니다. 계속하기 전에 설정된 Enterprise 라이선스 풀에 검색 헤드를 추가하는 것이 좋습니다. 독립형 인스턴스 마이그레이션 단일 4.1.x Splunk 인덱서를 사용할 경우 단일 라이선스가 설치되어 있으면 업그레이드하여 계속 사용하시면 됩니다. 해당 플랫폼용 설치 매뉴얼 지침을 따르십시오. "먼저 읽을 내용" 설명서를 먼저 읽어보시기 바랍니다. 33

기존 라이선스가 새 라이선서에서 작동하고 기본 풀 구성원으로서 인덱서와 함께 유효한 스택을 보여줍니다. 분산 인덱싱 배포 마이그레이션 자체 라이선스를 가진 4.1.x 인덱서가 여러 개 있는 경우 배포를 마이그레이션하려면 아래 단계를 순서대로 수행하십 시오. Splunk 인스턴스 중 하나를 라이선스 마스터로 지정합니다. 검색 헤드를 가지고 있다면 검색 헤드를 사용하는 것이 좋습니다. 설치 매뉴얼의 표준 지침에 따라 선택한 Splunk 인스턴스를 라이선스 마스터로 설치하거나 업그레이드합니다. 원하는 경우 인덱서의 연결을 허용하도록 라이선스 마스터를 구성합니다. 한 번에 하나씩 각 인덱서를 업그레이드합니다. 다음 단계를 수행하십시오. 설치 매뉴얼의 지침에 따라 인덱서를 4.2로 업그레이드합니다. 다음 단계를 수행하기 전까지는 독립형 라 이선스 마스터로 작동합니다. 인덱서의 Enterprise 라이선스 파일(4.2 이전 라이선스 파일은 각 인덱서의 $SPLUNK_HOME/etc/splunk.license에 있음)의 사본을 만들어 라이선스 마스터에 설치합니다. 인덱서를 추가 할 스택과 풀에 사본이 추가됩니다. 인덱서를 라이선스 슬레이브로 구성하고 라이선스 마스터를 지정합니다. 라이선스 마스터에서 관리자 > 라이선싱으로 이동하여 해당 풀에 연결된 인덱서 리스트를 확인하여 라이 선스 슬레이브가 올바르게 연결되어 있는지 확인합니다. 라이선스 슬레이브가 올바르게 연결되어 있으면 동일한 단계에 따라 다음 인덱서를 계속 업그레이드합니 다. Forwarder 마이그레이션 경량형 전달기(Light Forwarder)를 배포한 경우 새 분산 배포 매뉴얼의 이 장에서 새로운 범용 전달기(Universal Forwarder)에 대한 정보를 참조하십시오. 범용 전달기(Universal Forwarder)에는 자체 라이선스가 포함되어 있기 때 문에 특별한 라이선스 구성 없이 기존 경량형 전달기(Light Forwarder)를 새로운 범용 전달기(Universal Forwarder)로 업그레이드할 수 있습니다. 중량형 전달기(Heavy Forwarder)(다른 Splunk 인스턴스로 전달하기 전에 인덱싱을 수행하는 Splunk의 전체 인스턴 스)를 배포한 경우 인덱서와 비슷하게 처리하면 됩니다. 즉, 다른 인덱서와 함께 라이선스 풀에 추가하십시오. Splunk Free 추가 정보 Splunk Free는 Splunk의 무료 버전으로, 하루에 최대 500MB를 인덱스할 수 있고 만료 기한이 없습니다. 이 500MB 제한은 하루에 추가(인덱싱)할 수 있는 새 데이터의 양이지만, 매일 더 많은 데이터를 추가하여 유지할 수 있으며 원하 는 만큼 저장할 수 있습니다. 예를 들어, 하루에 500MB 데이터를 추가할 수 있으며 최종적으로 Splunk에 10TB 데이 터를 저장할 수 있습니다. 하루에 500MB보다 많은 데이터가 필요한 경우 라이선스를 구입해야 합니다. Splunk는 라이선스 위반을 추적하여 라이선스 사용을 규제합니다. 30일간 4번 이상 1일 500MB 제한을 초과할 경우, Splunk는 데이터를 계속 인덱스하지만 30일 기간 동안 3번 이하로 경고 수를 줄일 때까지 검색을 사용할 수 없습니다. 적합한 용도 Splunk Free는 IT 데이터의 개인, 임시 검색 및 시각화에 적합합니다. 하루 500MB 미만의 작은 볼륨의 데이터 인덱스 가 계속 있는 경우에는 Splunk Free를 사용할 수 있습니다. 또한 대용량 데이터 집합의 단기간 대량 로드 및 분석에 사 용할 수 있으며, Splunk Free는 30일 기간 동안 최대 3번까지 대용량 데이터 집합의 대량 로드를 허용합니다. 이 기능 은 대용량 데이터 집합의 포렌식 검토에 사용할 수 있습니다. 포함된 기능 Splunk Free는 단일 사용자 제품으로, 다음을 제외한 Splunk의 모든 기능이 지원됩니다. 여러 사용자 계정 및 역할 기반 액세스 제어(Splunk Free 사용 시 인증 없음) 분산 검색 TCP/HTTP 형식으로 전달(다른 Splunk 인스턴스로 데이터를 전달할 수 있지만 비 Splunk 인스턴스에는 전달 할 수 없음) 배포 관리 경고/모니터링 Free 인스턴스를 (Splunk 인덱서에 대한) Forwarder로 사용할 수는 있지만 배포 서버의 클라이언트로 지정할 수는 없 습니다. 인증 및 액세스 제어가 없다는 것은 무슨 의미입니까? 로그인이 없다는 뜻입니다. 명령줄 또는 브라우저에서 사용자/암호 프롬프트 없이 Splunk의 모든 기능을 액세 스하고 제어할 수 있습니다. 관리자와 동일하게 모든 액세스가 가능하고 관리자 역할만 있으며 구성 불가능합니다. 더 많은 역할을 추가하거 나 사용자 계정을 만들 수 없습니다. 모든 공용 인덱스에서 검색이 실행됩니다('index=*'). 사용자 할당량, 최대 검색별 시간 범위, 검색 필터와 같은 검색 제한 기능은 지원되지 않습니다. 기능 시스템이 비활성화되어 있지만 Splunk에 액세스하는 모든 사용자에 대한 모든 기능은 활성화되어 있습니 다. 34

Enterprise 평가판 라이선스에서 Free 라이선스로 전환 Splunk를 처음 다운로드하고 설치하면 Enterprise 평가판 라이선스를 자동으로 사용하게 됩니다. 사용자의 요구 사항 에 따라 Enterprise 평가판 라이선스가 만료될 때까지 Enterprise 평가판을 계속 사용하거나 Free 라이선스로 전환할 수 있습니다. Free 라이선스로 전환할 때 알아야 할 사항 Splunk Enterprise 평가판을 사용하면 Splunk Free에서 사용할 수 없는 많은 기능에 액세스할 수 있습니다. Free 라이 선스로 전환할 경우 다음 내용을 참고하십시오. 평가판에서 만든 사용자 계정이나 역할은 더 이상 사용할 수 없습니다. Free 인스턴스로 연결하는 사용자는 모두 '관리자'로 자동 로그인됩니다. 업데이트 확인은 표시되지만 로그인 화면은 더 이상 나타나지 않습니다. '관리자'가 아닌 사용자가 만든 Knowledge Object(예: event type, transaction, source type 정의) 및 전역 공유되 지 않은 개체는 사용할 수 없습니다. Splunk Free로 전환한 후에도 이러한 Knowledge Object를 계속 사용하려 면 다음 작업 중 하나를 수행하십시오. Free로 전환하기 전에 이 항목의 지침에 따라 관리자를 사용하여 해당 Knowledge Object를 전역으로 사 용할 수 있도록 승격합니다. 해당 Knowledge Object를 승격하려면 여기에 나온 설명대로 구성 파일을 직접 편집합니다. 대시보드 및 요약 인덱싱을 위해 실행할 검색을 계속 예약할 수는 있지만 정의한 경고는 더 이상 작동하지 않습 니다. Splunk로부터 더 이상 경고를 수신하지 않게 됩니다. TCP 또는 HTTP 형식으로 타사 애플리케이션에 전달할 수 있는 outputs.conf 구성이 작동하지 않습니다. Enterprise 평가판 라이선스를 사용하는 동안 관리자에서 위에서 언급한 구성을 만들려고 하면 Free Splunk에서 해당 제한에 대한 경고가 발생합니다. Splunk Free로 전환하는 방법 현재 Splunk Enterprise(평가판 포함)를 사용 중이면 Enterprise 라이선스가 만료될 때까지 기다리거나 언제든지 Free 라이선스로 전환할 수 있습니다. Free 라이선스로 전환하려면 다음 작업을 수행하십시오. 1. Splunk Web에 관리자 권한으로 로그인하여 관리자 > 라이선싱으로 이동합니다. 2. 페이지 상단에 있는 라이선스 그룹 변경을 클릭합니다. 3. Free 라이선스를 선택하고 저장을 클릭합니다. 4. 재시작하라는 메시지가 나타납니다. CLI를 통해 라이선스 관리 이 항목에서는 Splunk CLI를 사용하여 Splunk 라이선스를 모니터링하고 관리하는 방법에 대해 설명합니다. 계속하기 전에 다음 항목을 검토하십시오. Splunk 라이선싱에 대한 소개 내용은 이 매뉴얼의 "Splunk 라이선싱 방식"에서 확인하십시오. Splunk 라이선스 용어에 대한 자세한 내용은 이 매뉴얼의 "그룹, 스택, 풀 및 기타 용어"에서 확인하십시오. 이 항목에서는 Splunk의 라이선서 관련 개체와 상호작용하는 데 사용할 수 있는 CLI 명령에 대해서만 설명합니다. 해 당 명령 중 일부에는 각 개체에 대해 지정할 수 있는 필수/선택적 인수도 있습니다. 전체 구문과 사용 예제를 보려면 Splunk CLI 도움말을 참조하십시오. Splunk 명령줄 인터페이스 사용에 대한 소개는 이 매뉴얼의 "CLI에 대하여"에서 확인하십시오. Splunk의 REST API를 통한 라이선스 관리에 대한 내용은 REST API 참조 매뉴얼의 "라이선스"를 참조하십시오. CLI 라이선서 명령 및 개체 Splunk CLI를 사용하여 라이선스 및 라이선서 관련 개체를 추가, 편집, 나열 및 제거할 수 있습니다. 사용 가능한 명령 은 다음과 같습니다. 35

명령 add edit list licenses, licenser-pools 개체 licenser-localslave, licenser-pools licenser-groups, licenser-localslave, licensermessages, licenser-pools, licenser-slaves, licenserstacks, licenses 설명 라이선스 또는 라이선스 풀을 라이선스 스택에 추가합니다. 이 명령은 Enterprise 라이선스가 있는 경우에만 사용할 수 있습니다. 라이선스 스택 내의 로컬 licenser-slave 노드 또는 라이선스 풀의 속성을 편집합니다. 이 명령은 Enterprise 라이선스가 있는 경우에만 사용할 수 있 습니다. 지정된 라이선서 관련 개체에 따라 해당 개체 속성 또는 개체 구성원을 나 열합니다. remove licenser-pools, licenses 라이선스 스택에서 라이선스 또는 라이선스 풀을 제거합니다. 라이선스 관련 개체는 다음과 같습니다. 개체 설명 licenser-groups licenser-localslave licensermessages licenser-pools licenser-slaves licenser-stacks licenses 전환할 수 있는 다른 라이선스 그룹입니다. 로컬 인덱서의 구성입니다. 라이선스 상태에 대한 경고입니다. 풀 또는 가상 라이선스입니다. 스택은 각 풀의 할당량을 공유하는 여러 슬레이브와 함께 다양한 풀로 나눌 수 있습니다. 마스터에 연결된 모든 슬레이브입니다. 이 개체는 라이선스 스택을 나타냅니다. 스택에는 동일한 유형의 라이선스가 포함되며 누적됩니다. 이 Splunk 인스턴스의 모든 라이선스입니다. 공통 라이선서 관련 작업 다음은 공통 라이선서 관련 작업의 예제입니다. 라이선스 관리 라이선스 스택에 새 라이선스를 추가하려면 라이선스 파일에 경로를 지정하십시오../splunk add licenses /opt/splunk/etc/licenses/enterprise/enterprise.lic 라이선스 스택의 모든 라이선스를 나열하려면 다음 작업을 수행하십시오../splunk list licenses 리스트에는 각 라이선스의 속성이 표시됩니다. 예를 들어, 사용할 수 있는 기능(features), 속해 있는 라이선스 그룹 및 스택(group_id, stack_id), 허용되는 인덱스 할당량(quota), 각 라이선스에 제공되는 고유한 라이선스 키 (license_hash) 등이 있습니다. 라이선스가 만료되면 라이선스 스택에서 해당 라이선스를 제거할 수 있습니다. 라이선스 스택에서 라이선스를 제거 하려면 라이선스 해시를 지정하십시오../splunk remove licenses BM+S8VetLnQEb1F+5Gwx9rR4M4Y91AkIE=781882C56833F36D 라이선스 풀 관리 라이선스 스택에 있는 하나 이상의 라이선스에서 라이선스 풀을 만들 수 있습니다(Enterprise 라이선스가 있는 경우). 기본적으로 라이선스 스택은 여러 라이선서 풀로 분할됩니다. 각 풀은 풀 할당량을 공유하는 둘 이상의 라이선스 슬레 이브를 가집니다. 모든 라이선스 스택의 모든 라이선스 풀을 보려면:./splunk list licenser-pools 스택에 라이선스 풀을 추가하려면 풀 이름을 지정하고 풀에 추가할 스택과 풀에 할당할 인덱스 볼륨을 지정해야 합니 다../splunk add licenser-pools pool01 -quota 10mb -slaves guid1,guid2 -stack_id enterprise 또한 풀에 대한 설명과 풀의 구성원에 속하는 슬레이브에 대한 설명을 지정할 수 있습니다(선택 사항). 36

라이선스 풀의 설명, 인덱싱 할당량 및 슬레이브를 다음과 같이 편집할 수 있습니다../splunk edit licenser-pools pool01 -description "Test" -quota 15mb -slaves guid3,guid4 -append_slaves true 이것은 기본적으로 풀에 대한 설명("Test")을 추가하고, 할당량을 10mb에서 15mb로 변경하고, (guid1 및 guid2를 덮 어쓰거나 바꾸는 대신) 슬레이브 guid3 및 guid4를 풀에 추가합니다. 스택에서 라이선스 풀을 제거하려면 다음과 같이 이름을 지정합니다../splunk remove pool01 라이선스 슬레이브 관리 라이선스 슬레이브는 하나 이상의 라이선스 풀의 구성원입니다. 라이선스 볼륨에 대한 라이선스 슬레이브 액세스는 라이선스 마스터에 의해 제어됩니다. 라이선스 마스터에 연결된 모든 라이선스 슬레이브를 나열하려면:./splunk list licenser-slaves 로컬 라이선스 슬레이브의 모든 속성을 나열하려면:./splunk list licenser-localslave 라이선스 슬레이브를 추가하고 해당 로컬 라이선스 슬레이브 노드의 속성을 편집하려면(splunkd 라이선스 마스터 인 스턴스의 URI 지정 또는 '자신'):./splunk edit licenser-localslave -master_uri 'https://master:port' 라이선스 상태 모니터링 list 명령어를 사용하여 라이선스 상태에 대한 메시지(경고)를 볼 수 있습니다../splunk list licenser-messages Splunk 앱 정보 앱 및 추가 기능 정의 앱은 미리 구성된 대시보드, 보고서, 데이터 입력 및 저장된 검색을 통해 IT 시스템을 파악할 수 있는 특별한 기능을 제 공합니다. 앱에는 Splunk에서 표시되는 방식을 재구성할 수 있는 새로운 뷰와 대시보드가 포함될 수 있습니다. 또는 앱은 Splunk REST API를 사용하는 완전히 새로운 프로그램만큼 복잡할 수 있습니다. 더 구체적으로 말하면 앱은 자 체 UI 컨텍스트를 가지고 있는 즉시 사용 가능한 셀프 서비스 확장입니다. 앱은 Splunk Web의 오른쪽 상단 모서리에 나타나는 앱 리스트에서 선택할 수 있습니다. 추가 기능을 통해 특정 데이터 문제를 직접 해결할 수 있습니다. 추가 기능은 Splunk의 모양 및 느낌을 변경하거나, 사 용자 간의 정보를 공유할 수 있는 더 작고 재사용 가능한 구성 요소입니다. 추가 기능은 하나 이상의 event type 정의 또는 저장된 검색 모음처럼 단순합니다. 앱과 달리 추가 기능에는 GUI 구성 요소가 없으며 Splunk Web의 홈 리스트 또는 앱 메뉴에 표시되지 않습니다. Splunk를 사용할 경우 대부분 앱을 항상 사용하며, 일반적으로 앱 "내부"에 있는 것으로 참조합니다. 기본 앱은 검색 앱입니다. 앱 및 추가 기능의 장점 앱 및 추가 기능을 통해 단일 Splunk 인스턴스 위에 서로 다른 환경을 구축할 수 있습니다. 조직 내 다른 Splunk 사용 자 커뮤니티에 대한 개별 인터페이스를 만들 수 있습니다. 예를 들어, 이메일 서버 문제 해결을 위한 앱 하나, 웹 분석 을 위한 다른 앱, 일선 지원 팀에서 사용할 룩업 테이블을 연결하는 추가 기능 등을 만들 수 있습니다. 즉, 모든 사용자 들이 동일한 Splunk 인스턴스를 사용하지만 각기 관심 있는 관련 데이터와 도구만 볼 수 있습니다. 앱 및 추가 기능의 위치 Splunk를 설치하고 처음 로그인하면 Splunk 홈으로 이동됩니다. 이 페이지의 맨 위에는 환영 탭과 Splunk 홈 탭의 두 가지 탭이 있습니다. 설치된 앱을 보려면 Splunk 홈을 클릭하십시오. 이 인터페이스는 사용자를 위해 미리 설치된 앱 리스트를 보여줍니다. 기본적으로 이러한 앱 중 하나가 시작하기 앱입 니다. 이 앱은 새 사용자에게 Splunk 기능을 소개하기 위해 만들었습니다. Splunk를 처음 사용하는 사용자에게는 이 37

앱을 추천합니다. 사용해보시고 의견을 보내주십시오! 단일 사용자에 대해 Splunk 홈 무시 Splunk에 로그인할 때마다 Splunk 홈을 표시하지 않으려면 기본 앱이 처음에 표시되도록 구성하십시오. 이 구성은 기 본적으로 사용자별로 수행할 수 있습니다. 예를 들어, 처음 표시되는 기본 앱인 검색 앱을 지정하려면: 1. 사용자의 로컬 디렉터리에 user-prefs.conf 파일을 만듭니다. etc/users/<user>/user-prefs/local/user-prefs.conf admin 사용자인 경우 다음 위치에 이 파일이 생성됩니다. etc/users/admin/user-prefs/local/user-prefs.conf test 사용자인 경우 다음 위치에 이 파일이 생성됩니다. etc/users/test/user-prefs/local/user-prefs.conf 2. user-prefs.conf 파일에 다음 줄을 입력합니다. default_namespace = search 모든 사용자에 대해 Splunk 홈 무시 로그인하면 처음 표시되는 모든 사용자용 기본 앱을 지정할 수 있습니다. 예를 들어, 검색 앱을 전역 기본값으로 지정 하려면 $SPLUNK_HOME/etc/apps/user-prefs/local/user-prefs.conf를 편집 및 지정하십시오. [general_default] default_namespace = search 참고: 검색 앱에 액세스할 수 있는 권한이 없는 사용자에게는 오류가 표시됩니다. 기본적으로 제공하는 기능 Splunk는 시작하기 앱 외에도 검색 앱을 함께 제공합니다. 검색 앱 인터페이스는 Splunk의 핵심 기능을 제공하며 일 반적인 용도에 사용되도록 설계되었습니다. 이전에 Splunk를 사용해 본 경우 검색 앱은 이전 버전의 기본 Splunk Web 기능을 대신합니다. 검색 앱에서는 검색란과 그래프로 채워진 대시보드를 볼 수 있습니다. 검색 앱 창의 왼쪽 상 단에 있는 대시보드 및 뷰 드롭다운 메뉴에서 하나를 새로 선택하여 대시보드 또는 뷰를 변경할 수 있습니다. 이 앱을 변경하려면 오른쪽 상단에 있는 앱 드롭다운 메뉴에서 하나를 새로 선택합니다. 38

나중에 Splunk 홈으로 돌아가서 또 다른 앱을 선택할 수 있습니다. 더 많은 앱 다운로드 다른 여러 앱도 다운로드할 수 있습니다. 예를 들어, 변경 관리 또는 PCI(결제 카드 산업) 규제 준수와 같이 대용량 데 이터 작업이 필요한 경우에는 Splunk에서 해당 용도로 사용하도록 특별히 설계된 앱을 사용하십시오. OS용 앱(Splunk for Windows 또는 Splunk for *NIX)을 다운로드할 수 있습니다. 이러한 앱은 특정 플랫폼에서 Splunk 를 최대한 활용하는 데 도움이 되는 대시보드와 미리 작성된 검색을 제공합니다. 더 많은 앱을 찾으려면 Splunk 홈 탭에서 추가 앱 찾기 단추를 클릭하십시오. 자세한 내용은 더 많은 앱 및 추가 기능 찾기를 참조하십시오. Splunk Web을 사용하여 앱 관리 Splunk Web에서 Splunk 관리자를 사용하여 앱을 만들고 다운로드 및 관리할 수 있습니다. 관리자 > 앱을 선택하십시 오. 이 페이지에서는 다음 작업을 수행할 수 있습니다. 앱 다운로드, 설치 또는 만들기 설치된 앱에 대한 권한 설정 앱 실행 또는 앱 속성 편집 앱과 연결된 개체 보기 앱과 관련된 Splunk 개체 저장 및 공유 방법 Splunk 지식에는 Splunk 데이터를 풍부하게 해주는 항목, 예를 들어 저장된 검색, event type, 태그 등의 개체가 포함 되며, 사용자가 필요로 하는 것을 보다 쉽게 알 수 있게 해줍니다. Splunk에서는 이것을 Knowledge Object라고 부릅 니다. Splunk Web에 로그인한 사용자는 사용자의 "내부"(필요한 권한이 있다고 가정했을 때) 앱에 있는 사용자 디렉터리에 Knowledge Object를 만들고 저장할 수 있습니다. 이것은 사용자가 개체를 저장할 때마다 발생하는 기본 동작으로, 현 재 실행 중인 앱의 사용자 디렉터리에 적용됩니다. 사용자가 특정 앱에 개체를 저장했으면 저장된 개체는 해당 앱의 사용자만 사용할 수 있습니다. 다른 사용자도 사용할 수 있게 하려면 다음 작업 중 하나를 수행해야 합니다. 그리고 이 작업을 수행하려면 올바른 권한이 있어야 합니다. 동일한 앱에서 다른 특정 역할 또는 사용자와 개체 공유 해당 앱에 액세스하는 모든 사용자가 사용할 수 있도록 개체 승격 모든 앱(및 사용자)에서 전역으로 사용할 수 있도록 개체 승격 자세한 내용은 이 매뉴얼의 앱 아키텍처 및 개체 소유권을 참조하십시오. 더 많은 앱과 추가 기능 찾기 http://www.splunkbase.com/apps에서 새로운 앱과 추가 기능을 찾을 수 있습니다. Splunk 홈에서 Splunkbase에 액세스하면 Splunk 내에서 앱을 직접 다운로드하고 설치할 수 있습니다. Splunk 홈 탭 에서 앱 더 찾아보기 단추를 클릭하십시오. Splunk Web에 로그인하면 기본적으로 Splunk 홈이 표시됩니다. Splunk 제공 앱의 기본 페이지의 오른쪽 상단 모서 리에 있는 앱 메뉴에서 Splunk 홈으로 언제든지 돌아갈 수 있습니다. 인터넷에 연결된 경우 Splunk 서버 또는 클라이언트 컴퓨터가 인터넷에 연결되어 있으면 Splunk 홈에서 앱을 직접 다운로드할 수 있습니다. 1. Splunk 홈에서 Splunk 홈 탭을 클릭합니다. 그런 다음 오른쪽에 있는 앱 더 찾아보기 단추를 클릭합니다. 이렇게 하 면 이 버전의 Splunk에 사용할 수 있는 앱과 추가 기능을 다운로드할 수 있는 Splunkbase로 연결됩니다. 2. 원하는 앱 또는 추가 기능을 선택하고 설치를 선택합니다. 3. splunk.com 사용자 이름과 암호(사용자의 Splunk 사용자 이름/암호가 아님)로 splunk.com에 로그인하라는 메시지 가 나타납니다. 39

4. 앱 또는 추가 기능이 설치됩니다. Web GUI 구성 요소(대부분의 추가 기능에는 event type 정의와 같은 Knowledge Object만 포함되고 GUI 컨텍스트는 없음)가 있는 경우에는 Splunk 홈에서 이 구성 요소로 이동할 수 있습니다. 중요: Splunk Web이 프록시 서버 뒤에 있을 경우 Splunkbase에 액세스할 때 문제가 발생할 수 있습니다. 이 문제를 해결하려면 "프록시 서버 지정"에서 설명한 대로 http_proxy 환경 변수를 설정해야 합니다. 인터넷에 연결되지 않은 경우 Splunk 서버 및 클라이언트가 인터넷에 연결되어 있지 않은 경우 SplunkBase에서 앱을 다운로드하여 서버에 복사해 야 합니다. 1. 인터넷에 연결된 컴퓨터인 경우 Splunkbase에서 원하는 앱 또는 추가 기능을 탐색합니다. 2. 앱 또는 추가 기능을 다운로드합니다. 3. 이 앱을 Splunk 서버에 복사합니다. 4. $SPLUNK_HOME/etc/apps 디렉터리에 앱을 배치합니다. 5. tar -xvf(*nix의 경우) 또는 WinZip(Windows의 경우)과 같은 도구를 사용하여 앱 또는 추가 기능 파일의 압축을 풉 니다. Splunk 앱은 tar 및 gzip로 압축했더라도 SPL 확장자로 패키지되어 있습니다. 사용자의 도구가 이 확장자를 인 식할 수 있도록 설정해야 할 수도 있습니다. 6. 앱 또는 추가 기능의 내용에 따라 Splunk를 재시작해야 할 경우가 있습니다. 7. 앱 또는 추가 기능이 설치되었으며 Splunk 홈(웹 UI 구성 요소가 있는 경우)에서 사용할 수 있습니다. 앱 아키텍처 및 개체 소유권 앱 및 추가 기능은 Splunk Knowledge Object에서 일반적으로 작성됩니다. Splunk Knowledge Object에는 Splunk 배포를 풍부하게 해주는 데이터 유형, 예를 들어 저장된 검색, event type, 태그 등의 개체가 포함되며, 사용자가 필요 로 하는 것을 쉽게 알 수 있게 해줍니다. Splunk Web에 로그인한 사용자는 사용자의 "내부"(필요한 권한이 있다고 가정했을 때) 앱에 있는 사용자 디렉터리에 Knowledge Object를 만들고 저장할 수 있습니다. 이것은 사용자가 개체를 저장할 때마다 발생하는 기본 동작으로, 현 재 실행 중인 앱의 사용자 디렉터리에 적용됩니다. 사용자 디렉터리는 $SPLUNK_HOME/etc/users/<user_name>/<app_name>/local에 있습니다. 사용자가 앱에 개체를 저장했으면 이 저장된 개체는 해당 앱에 있는 사용자만 사용할 수 있습니다. 다른 사용자도 사용할 수 있게 하려면 다음 작업 중 하나를 수행해야 합 니다. 해당 앱에 액세스하는 모든 사용자가 사용할 수 있도록 개체 승격 특정 역할 또는 사용자로 개체 제한(앱의 컨텍스트 내에서) 모든 앱과 사용자가 사용할 수 있도록 개체를 전역으로 표시(역할/사용자에 의해 명시적으로 제한하지 않는 경 우) 참고: 개체를 앱 레벨로 승격하려면 앱에 대한 쓰기 권한이 있어야 합니다. Splunk 지식 승격 및 공유 사용자는 권한 대화 상자를 통해 다른 사용자와 Splunk Knowledge Object를 공유할 수 있습니다. 즉, 앱에서 사용자 가 읽기 권한을 가지고 있어야 공유 개체를 보거나 사용할 수 있습니다. 예를 들어, 사용자가 저장된 검색을 공유할 경 우 다른 사용자도 이 저장된 검색을 볼 수 있지만 해당 검색이 생성된 앱 내에서만 볼 수 있습니다. "Fflanda" 앱에서 저장된 검색을 만들고 이 검색을 공유할 경우 Fflanda에 대한 읽기 권한이 있는 다른 사용자는 이 저장된 검색을 볼 수 있습니다. 쓰기 권한이 있는 사용자는 개체를 앱 레벨로 승격할 수 있습니다. 즉, 사용자 디렉터리에서 앱 디렉터리로 개체가 복 사됩니다. 원본 위치: $SPLUNK_HOME/etc/users/<user_name>/<app_name>/local/ 대상 위치: $SPLUNK_HOME/etc/apps/<app_name>/local/ 사용자에게 앱에 쓰기 권한이 있는 경우에만 이 작업을 수행할 수 있습니다. Splunk Knowledge Object 전역 설정 마지막으로, 승격 시 사용자는 개체를 전역으로 사용할지 여부를 결정할 수 있습니다. 전역으로 설정하면 모든 앱에서 해당 개체를 볼 수 있습니다. 다시 말하면 이 작업을 수행하려면 사용자에게 원본 앱에 대한 쓰기 권한이 있어야 합니 다. 관리자 내에서 이 작업을 수행하는 것이 가장 쉽지만, 원하는 디렉터리로 관련 개체를 이동하여 나중에 이 작업을 수행할 수도 있습니다. 앱 "D"에서 사용자 "C"에 속한 개체 "A"("B.conf"에 정의됨)를 전역으로 설정하려면: 40

1. 개체 A를 정의하는 스탠자를 $SPLUNK_HOME/etc/users/C/D/B.conf에서 $SPLUNK_HOME/etc/apps/D/local/B.conf로 이동합 니다. 2. 앱의 local.meta 파일에 있는 개체 A의 스탠자에 export = system 설정을 추가합니다. 개체의 스탠자가 아직 없는 경 우에는 하나를 추가할 수 있습니다. 예를 들어, *Nix 앱에서 "fflanda" 이름의 사용자가 생성한 event type "rhallen"을 전역으로 사용할 수 있게 승격하려면 다음 작업을 수행하십시오. 1. $SPLUNK_HOME/etc/users/fflanda/unix/local/eventtypes.conf에서 $SPLUNK_HOME/etc/apps/unix/local/eventtypes.conf로 [rhallen] 스탠자를 이동합니다. 2. 다음 스탠자를 추가합니다. [eventtypes/rhallen] export = system 대상 위치: $SPLUNK_HOME/etc/apps/unix/metadata/local.meta 참고: 기본적으로 모든 이벤트를 전역으로 내보내기 때문에 검색 앱에서 event type을 공유할 때 export = system 설정 을 local.meta에 추가할 필요가 없습니다. 적용되는 개체 여기서 언급한 Knowledge Object는 액세스 제어에 따라 제한됩니다. 이러한 개체를 또한 앱 레벨 개체라고 부르며, Splunk 관리자의 앱 구성 탭에서 이 개체를 설정할 수 있습니다. 이 페이지는 생성 및 공유된 개체를 관리하는 모든 사 용자에게 제공됩니다. 이러한 개체에는 다음이 포함됩니다. 저장된 검색 및 보고서 Event type 뷰 및 대시보드 필드 추출 그리고 관리자 권한(특정 개체에 대한 읽기/쓰기 권한)을 가진 사용자만 사용할 수 있는 시스템 레벨 개체가 있습니다. 또한 이러한 개체는 Splunk 관리자를 통해 관리됩니다. 이러한 개체에는 다음이 포함됩니다. 사용자 역할 인증 분산 검색 입력 출력 배포 라이선스 서버 설정(예: 호스트 이름, 포트 등) 중요: 입력을 추가할 경우 Splunk는 실행 중인 앱에 속하는 inputs.conf 사본에 해당 입력을 추가합니다. 즉, 검색에서 바로 Splunk 관리자로 이동할 경우 사용자의 입력이 $SPLUNK_HOME/etc/apps/search/local/inputs.conf에 추가됩니다. 앱 구성 및 지식 우선 순위 Splunk에 지식을 추가하면 지식을 추가할 때 사용자가 위치한 앱의 컨텍스트에 지식이 추가됩니다. Splunk가 구성 및 지식을 평가할 때는 어떤 컨텍스트에서 어떤 지식 정의와 구성이 사용되는지 제어할 수 있도록 특정 우선 순위에 따라 구성과 지식을 평가합니다. Splunk 구성 파일과 우선 순위에 대한 자세한 내용은 "구성 파일에 대하여"를 참조하십시 오. 앱 및 추가 기능 개체 관리 Splunk 사용자가 앱 또는 추가 기능을 만든 경우 앱 또는 추가 기능을 구성하는 개체 모음이 생성됩니다. 이러한 개체 에는 뷰, 명령, 탐색 항목, event type, 저장된 검색, 보고서 등이 포함될 수 있습니다. 이러한 각 개체에는 개체를 보거 나 변경할 수 있는 사용자를 결정하기 위한 개체와 연결된 권한이 있습니다. 기본적으로 관리자에게는 Splunk 시스템 의 모든 개체를 바꿀 수 있는 권한이 있습니다. 자세한 내용은 다음 항목을 참조하십시오. 앱에 대한 개요는 이 매뉴얼의 "앱 및 추가 기능 정의"를 참조하십시오. 앱 및 추가 기능 권한에 대한 자세한 내용은 이 매뉴얼의 앱 아키텍처 및 개체 소유권을 참조하십시오. 앱 및 추가 기능을 직접 만드는 방법에 대해 자세히 알아보려면 개발자 매뉴얼을 참조하십시오. 관리자에서 앱/추가 기능 개체 보기 및 관리 시스템에서 모든 앱에 대한 개체를 보고 제어하려면 Splunk Web에서 Splunk 관리자를 사용하십시오. Splunk를 배포 할 때 다음과 같은 방법으로 관리자를 사용하여 개체를 볼 수 있습니다. 41

시스템의 모든 앱/추가 기능에 대한 개체를 모두 보려면 관리자 > 모든 구성을 선택하십시오. 저장된 검색 및 보고서 개체를 모두 보려면 관리자 > 검색 및 보고서를 선택하십시오. 모든 event type을 보려면 관리자 > Event type을 선택하십시오. 모든 필드 추출을 보려면 관리자 > 필드를 선택하십시오. 다음 작업을 수행할 수 있습니다. 정렬 화살표 를 사용하여 페이지에서 개체를 보고 조작할 수 있습니다. 뷰를 필터링하여 앱 컨텍스트 창에서 지정한 앱 또는 추가 기능의 개체, 특정 사용자가 소유한 개체 또는 특정 문 자열을 포함하는 개체만 볼 수 있습니다. 앱 컨텍스트 창의 검색 필드를 사용하여 필드 문자열을 검색합니다. 기본적으로 Splunk는 사용 가능한 모든 필드의 문자열을 검색합니다. 특정 필드 내에서 검색하려면 필드를 지정하십시오. 와일드카드가 지원됩니다. 참고: 검색 명령 페이지에서 개별 검색 명령에 대한 자세한 내용은 검색 참조 매뉴얼을 참조하십시오. CLI를 사용하여 앱 업데이트 CLI를 사용하여 Splunk 인스턴스에서 기존 앱을 업데이트하려면:./splunk install app <app_package_filename> -update 1 -auth <username>:<password> Splunk는 설치 패키지에 있는 정보를 기준으로 앱을 업데이트합니다. CLI를 사용하여 앱 비활성화 CLI를 통해 앱을 비활성화하려면:./splunk disable app [app_name] -auth <username>:<password> 참고: Splunk Free를 실행할 경우 사용자 이름과 암호를 제공할 필요가 없습니다. 앱 제거 Splunk 설치에서 설치된 앱을 제거하려면: 1. (선택 사항) 앱의 인덱스된 데이터를 제거합니다. 일반적으로 삭제된 앱에서 인덱스된 데이터에는 액세스하지 못합니다. 그러나 앱을 삭제하기 전에 Splunk CLI 정리 명령어를 사용하여 앱에서 인덱스된 데이터를 제거할 수 있습니다. CLI 명령어를 사용하여 인덱스에서 데이터 제거를 참조하십시오. 2. 앱 디렉터리를 수동으로 삭제합니다: $SPLUNK_HOME/etc/apps/<appname> 3. 다음과 같이 지정된 파일을 삭제하여 해당 앱을 위해 특별히 생성된 사용자 관련 앱 디렉터리를 제거합니다. $SPLUNK_HOME/splunk/etc/users/*/<appname> 앱 구성 및 속성 관리 Splunk 인스턴스에 설치된 앱 및 추가 기능의 구성과 속성을 관리할 수 있습니다. Splunk 인스턴스에 설치된 앱을 나 열하려면 관리자 > 앱으로 이동하십시오. 이 페이지에서 다음 작업을 수행할 수 있습니다. 앱의 권한 편집 앱 활성화 또는 비활성화 앱 실행, 속성 편집 및 앱 개체 보기와 같은 작업 수행 각 앱에서 사용 가능한 구성은 앱의 액세스 제어 권한에 따라 다릅니다. 구성과 속성을 편집할 수 있는지 여부는 사용 자가 앱의 소유자인지 앱의 사용자인 지에 따라 다릅니다. 앱 속성 편집 관리자 > 앱으로 이동하고 앱의 속성 편집을 선택합니다. Splunk 인스턴스에 설치된 앱의 다음 요소를 편집할 수 있습 니다. 이름 Splunk Web에서 앱의 표시 이름을 변경합니다. 버전 앱의 버전을 변경합니다. 앱의 소유자인 경우에만 버전을 변경할 수 있습니다. Splunk는 버전을 기준으로 업데이트를 확인합니다. 업데이트 확인 앱의 업데이트 확인 기능은 기본적으로 활성화되어 있습니다. 기본값을 재정의하고 업데이트 확 인을 비활성화할 수 있습니다. 자세한 내용은 앱 업데이트 확인을 참조하십시오. 표시 여부 뷰가 포함된 앱만 나타납니다. 일반적으로 뷰가 없는 추가 기능은 표시 여부 속성을 비활성화합니다. 42

작성자 앱의 작성자를 표시합니다. 설명 Splunk 홈 페이지에 앱에 대한 설명이 나옵니다. 자산 업로드 앱에서 액세스할 수 있는 HTML, JavaScript, CSS 파일과 같은 로컬 파일 자산 파일을 이 필드에서 선택할 수 있습니다. 이 창에서 한 번에 하나의 파일만 업로드할 수 있습니다. 앱 및 추가 기능 참조: 앱 및 추가 기능의 구성 및 속성 정보에 대한 설명을 제공합니다. 앱 업데이트 확인 Splunk 4.2부터 Splunkbase가 앱 업데이트를 확인할지 여부를 구성할 수 있습니다. 기본적으로 업데이트 확인 기능 은 활성화되어 있습니다. 관리자 > 앱 > 속성 편집에서 이 속성을 편집하여 앱 업데이트 확인을 비활성화할 수 있습니 다. 그러나 Splunk 관리자에서 이 속성을 사용할 수 없는 경우, 업데이트 확인을 비활성화하려면 앱 app.conf 파일을 직접 편집해야 합니다. 업데이트 확인을 비활성화하려면 $SPLUNK_HOME/etc/apps/<app_name>/local/app.conf에서 다음 스탠자 를 만들거나 편집하십시오. [package] check_for_updates = 0 참고: app.conf의 로컬 버전(기본 버전이 아님)을 편집하십시오. 이렇게 하면 앱의 다음 업데이트로 현재 설정이 덮어 쓰기되지 않습니다. Splunk 구성 Splunk 구성 방법 Splunk는 구성 파일 집합의 구성 정보를 유지 관리합니다. 다음 방법으로 Splunk를 구성할 수 있습니다. 구성 파일 직접 편집 Splunk Web에서 Splunk 관리자를 사용하여 필드 채우기 Splunk CLI 명령 지정 Splunk REST API를 사용하여 구성을 업데이트하는 앱 설정 화면 이 모든 방법은 기본 구성 파일의 내용을 변경합니다. 분산 환경을 구성 및 관리하는 데 Splunk 배포 서버를 사용할 수 있습니다. 구성 파일 Splunk의 구성 정보는 대부분.conf 파일에 저장됩니다. 이러한 파일은 /etc/system 아래 Splunk 설치 디렉터리(설명서 에서는 주로 언급되는 $SPLUNK_HOME)에 위치합니다. 표준 텍스트 편집기를 사용하여 이러한 파일을 변경할 수 있습니 다. 구성 파일 편집을 시작하기 전에 "구성 파일에 대하여"를 읽어보십시오. Splunk 관리자 Splunk Web에서 Splunk 관리자를 사용하여 대부분의 일반적인 구성 작업을 수행할 수 있습니다. Splunk Web은 기 본적으로 Splunk가 설치되어 있는 호스트의 포트 8000에서 실행됩니다. 로컬 컴퓨터에서 Splunk를 실행하는 경우, Splunk Web에 액세스하는 URL은 http://localhost:8000입니다. 원격 컴퓨터에서 Splunk를 실행하는 경우, Splunk Web에 액세스하는 URL은 http://<hostname>:8000입니다. 여 기서 <hostname>는 Splunk가 실행되고 있는 컴퓨터의 이름입니다. Splunk 관리자에 액세스하려면 Splunk Web에 로그인한 후 오른쪽 상단 모서리의 관리자를 클릭하십시오. Splunk CLI 많은 구성 옵션은 CLI를 통해 사용할 수 있습니다. 이러한 옵션은 각 항목에서 자세히 설명합니다. 또는 Splunk 실행 중에 help 명령을 사용하여 전체 CLI 도움말 참조를 확인할 수 있습니다../splunk help CLI에 대한 자세한 내용은 이 매뉴얼의 "CLI에 대하여"를 참조하십시오. 앱의 설정 화면 개발자들은 사용자가 구성 파일을 직접 편집하지 않고도 앱 구성을 설정할 수 있게 도와주는 앱의 설정 화면을 만들 수 있습니다. 설정 화면을 통해 앱을 다른 환경에 배포하거나 특별한 용도로 앱을 사용자 지정할 수 있습니다. 43

설정 화면에서 Splunk REST API를 사용하여 앱 구성 파일을 관리합니다. 설정 화면에 대한 자세한 내용은 Splunk Web용 뷰 및 앱 개발 매뉴얼의 "앱 설정 화면 구성"을 참조하십시오. 분산 환경 관리 Splunk 배포 서버는 분산 환경을 위한 중앙 관리 및 구성을 제공합니다. 이 배포 서버를 사용하여 구성 파일 집합이나 다른 콘텐츠를 회사 전체의 Splunk 인스턴스 그룹으로 배포할 수 있습니다. 배포 관리에 대한 내용은 "다른 Splunk 인스턴스에 배포"를 참조하십시오. 구성 변경 후 재시작 구성 파일 변경 사항을 적용하려면 Splunk를 재시작해야 합니다. 변경 사항을 적용할 때 재시작해야 할지 여부를 알 려면 구성 파일 또는 해당 참조 항목을 확인하십시오. 관리자에서 변경 작업을 수행할 경우 재시작 여부를 묻는 메시지가 나타납니다. 변경 사항을 적용하려면 다음과 같은 작업을 수행해야 합니다. Splunk Web에서 다음 검색을 입력하여 props.conf 또는 transforms.conf에서 수행한 구성 변경 사항을 활성화합 니다. extract reload=t authentication.conf를 다시 로드하려면 Splunk Web을 사용합니다. 관리자 > 액세스 제어 > 인증 방법으로 이동 하여 인증 구성 다시 로드 단추를 클릭합니다. 이렇게 하면 인증 캐시가 새로 고쳐지지만 현재 사용자의 연결은 끊어지지 않습니다. Splunk 관리자에 대하여 Splunk Web에서 Splunk를 구성하려면 Splunk 관리자를 사용하십시오. Splunk 관리자에 액세스하려면 Splunk Web 에 로그인한 후 오른쪽 상단의 관리자를 클릭하십시오. 관리자 권한이 있는 사용자는 관리자의 모든 영역에 액세스할 수 있습니다. 관리자 권한이 없는 사용자는 관리자의 일 부 기능에만 액세스할 수 있습니다. 관리자 페이지는 다음과 같은 많은 영역으로 구성됩니다. 앱 앱 영역에서는 다음을 관리할 수 있습니다. 지식 앱: 설치된 앱의 권한을 편집하거나, 새 앱을 만들거나, 커뮤니티에서 만든 앱을 Splunkbase에서 찾아봅니다. 지식 영역에서는 다음을 관리할 수 있습니다. 시스템 검색 및 보고서: 검색 및 보고서에 대한 권한을 보거나 편집 및 설정합니다. 경고 및 요약 인덱싱을 설정합니다. Event type: 이벤트 유형에 대한 권한을 보거나 편집 및 설정합니다. 태그: 필드 값의 태그를 관리합니다. 필드: 필드 추출에 대한 권한을 보거나 편집 및 설정합니다. 이벤트 워크플로 작업 및 필드 별칭을 정의합니다. source type 이름을 변경합니다. 룩업: 룩업 테이블과 룩업을 구성합니다. 사용자 인터페이스: 뷰, 대시보드 및 탐색 메뉴를 만들고 편집합니다. 고급 검색: 검색 매크로를 만들고 편집합니다. 검색 명령어에 대한 권한을 설정합니다. 모든 구성: 모든 앱과 관련된 구성을 모두 확인합니다. 시스템 영역에서는 다음을 관리할 수 있습니다. 시스템 설정: 포트, 호스트 이름, 인덱스 경로, 이메일 서버 설정(경고) 및 시스템 로깅을 포함하여 시스템 설정을 관리합니다. 클러스터링: 구성 요소 및 뷰 상태를 활성화합니다. 라이선싱: 라이선스 사용량 통계를 확인하고 새 라이선스를 적용합니다. 44

데이터 서버 컨트롤: Splunk를 재시작합니다. 데이터 영역에서는 다음을 관리할 수 있습니다. 배포 데이터 입력: 스크립트, 파일, 디렉터리 및 네트워크 포트에서 데이터를 Splunk에 추가합니다. 전달 및 수신: 데이터를 보내고 받을 수 있도록 이 Splunk 인스턴스를 구성합니다. 인덱스: 새 인덱스를 만든 후 인덱스 크기 기본 설정을 관리합니다. 빠른 보고서 작성 요약: 저장된 검색 요약을 관리합니다. 배포 영역에서는 다음을 관리할 수 있습니다. 분산 검색: 여러 Splunk 인스턴스에 배포된 검색을 설정합니다. 배포: 여러 Splunk 인스턴스에 구성 설정을 배포하고 관리합니다. 사용자 및 인증 사용자 및 인증 영역에서는 다음을 관리할 수 있습니다. 액세스 제어: 인증 메소드(Splunk 또는 LDAP)를 지정하고 사용자를 만들거나 수정하며 역할을 관리합니다. 사용자 계정: 이름, 이메일 주소, 기본 앱, 시간대 또는 암호를 변경합니다. 구성 파일에 대하여 Splunk의 구성 정보는 확장자가.conf인 구성 파일에 저장됩니다. 이러한 파일은 $SPLUNK_HOME/etc 아래에 있습니다. Splunk Web에서 Splunk 관리자를 사용하여 구성 설정을 변경하면 관련 구성 파일이 변경됩니다. 이러한 변경은 $SPLUNK_HOME/etc 아래 디렉터리의 구성 파일 복사본에 작성됩니다(실제 디렉터리는 나중에 설명할 여러 요인에 따라 다를 수 있음). 이 속성의 기본값은 $SPLUNK_HOME/etc/system/default에 남아 있습니다. 관리자에서 많은 설정을 구성할 수 있지만 일부 고급 사용자 지정을 수행하려면 구성 파일을 직접 편집해야 합니다. 구성 파일의 전체 리스트는 "구성 파일 리스트"를 참조하십시오. 구성 디렉터리 구조 다음은 $SPLUNK_HOME/etc에 존재하는 구성 디렉터리 구조입니다. $SPLUNK_HOME/etc/system/default 미리 구성된 구성 파일이 포함됩니다. 이 디렉터리의 파일은 수정하지 마십시오. $SPLUNK_HOME/etc/system/local 모든 앱에서 사용 가능한 설정과 같은 사이트 범위의 로컬 변경 사항이 여기에 적용됩니다. $SPLUNK_HOME/etc/slave-apps/cluster/default/ 클러스터 피어 노드만 해당됨. 모든 피어 노드의 공통 기본 구성 파일이 포함됩니다. 이 디렉터리의 해당 파일은 수정하거나 새 파일로 덮어쓰지 마십시오. 자세한 내용은 인덱서 및 클러스터 관리 매뉴얼의 "공통 피어 구성 업데이트"를 참조하십시오. $SPLUNK_HOME/etc/slave-apps/cluster/local/ 클러스터 피어 노드만 해당됨. 모든 피어 노드의 공통 구성 파일이 포함됩니다. 이 디렉터리의 해당 파일은 수정하거나 새 파일로 덮어쓰지 마십시오. 이 디렉터리에 새 파일 또는 수정된 파일을 배포하려면 클러스터 마스터 노드를 사용해야 합니다. 자세한 내용은 인덱서 및 클러스터 관리 매뉴얼의 "공통 피어 구성 업데이트"를 참조하십시오. $SPLUNK_HOME/etc/apps/<app_name>/local 구성을 변경할 때 사용자가 현재 앱에 있을 경우 앱의 /local 디렉터리에 있는 구성 파일에 해당 설정이 적 용됩니다. 예를 들어, 기본 Splunk 검색 앱의 search-time 설정에 대한 편집 내용은 다음 위치에 적용됩니다: $SPLUNK_HOME/etc/apps/search/local/. 특정 앱에만 변경 사항이 적용되도록 구성 파일을 편집하려면 구성 파일을 앱의 /local 디렉터리에 복사한 후 변경을 수행하십시오. $SPLUNK_HOME/etc/users 사용자별 구성 변경 사항이 여기에 적용됩니다. $SPLUNK_HOME/etc/system/README 이 디렉터리에는 지원 참조 설명서가 포함됩니다. 대부분의 구성 파일에는.spec 및.example의 두 개의 참 조 파일이 있습니다(예: inputs.conf.spec 및 inputs.conf.example)..spec 파일은 사용 가능한 속성 및 변수 리스트를 비롯한 구문을 지정합니다..example 파일에는 실제 환경에서의 사용 예가 포함됩니다. 단일 Splunk 인스턴스에는 일반적으로 이러한 여러 디렉터리에 걸친 여러 버전의 구성 파일이 있습니다. 예를 들어, 기본, 로컬 및 앱 디렉터리에 동일한 이름의 구성 파일을 가질 수 있습니다. 이것은 현재 사용자 및 현재 앱과 같은 요 인을 기준으로 구성 우선 순위를 결정하는 데 레이어드 효과를 제공합니다. Splunk 구성 파일에 적용되는 우선 순위 규칙에 대해 이해하려면 "구성 파일 우선 순위" 항목을 읽어보십시오. 이 항목에서는 파일의 우선 순위를 어떻게 결정 45

하는지 설명합니다. 참고: 지정된 구성 파일에서 사용할 수 있는 가장 정확한 설정 리스트는 해당 구성 파일의.spec 파일에 있습니다. "구 성 파일 참조" 또는 $SPLUNK_HOME/etc/system/README에서.spec 및.example 파일의 최신 버전을 찾을 수 있습니다. 기본 디렉터리 "모든 환경은 /default를 제외하고 사용자의 환경에 따라 다릅니다." -- duckfez, 2010 $SPLUNK_HOME/etc/system/default에 있는 구성 파일의 기본 버전은 편집하지 마십시오. Splunk를 업그레이드할 때마다 기본 파일이 덮어쓰기됩니다. 대신, $SPLUNK_HOME/etc/system/local와 같은 다른 구성 디렉터리에 파일을 만들거나 편집하십시오. 이러한 디렉터리는 업그레이드 중에 덮어쓰지 않습니다. Splunk는 항상 마지막 기본 디렉터리를 우선하므로, 다른 구성 디렉터리 중 하나에서 변경한 속성이나 스탠자가 기본 버전보다 우선됩니다. Splunk를 통해 구성 파일을 필터링할 수 있고 Splunk에서 사용할 수 있는 다른 속성 값으로 구 성 파일의 여러 버전을 만들 수 있습니다. 스키마 레이어링에 대한 설명은 "구성 파일 우선 순위"를 참조하십시오. 그 러나 대부분의 배포에서 $SPLUNK_HOME/etc/system/local 디렉터리를 사용하여 구성을 변경할 수 있습니다. 기본 구성 파일을 다른 구성 디렉터리에 복사한 다음, 복사본을 편집하는 방법은 권장되지 않습니다. Splunk 업그레 이드에 의해 기본 구성 파일이 변경될 경우 복사한 파일의 버전에 의해 변경이 차단될 수 있습니다. 예를 들어, 기본 구 성 파일에 값이 50인 속성이 있을 경우 이 Splunk 엔지니어링 조직에서 해당 속성을 100으로 설정하면 50보다 더 잘 작동한다고 판단할 수 있습니다. 따라서 이들은 후속 릴리스에서 이 속성 값을 100으로 변경합니다. 다음에 Splunk를 업그레이드할 경우 속성 값이 100으로 설정된 새 버전의 구성 파일이 이전 버전을 덮어쓰게 됩니다. 이렇게 하면 아무 문제가 없습니다. 그러나 중간에 $SPLUNK_HOME/etc/system/local에 있는 이전 파일 버전을 복사했다면 Splunk는 기본 디 렉터리의 값보다 우선인 $SPLUNK_HOME/etc/system/local의 속성 값 50인 파일을 계속 사용하게 됩니다. 제한적인 상황에서 상당한 주의를 기울여 기본 파일에서 스탠자를 복사하여 편집한 후 이 스탠자를 $SPLUNK_HOME/etc/system/local 또는 비슷한 다른 위치에 새 파일 버전으로 저장할 수도 있습니다. 그러나 위에서 설명 한 대로 편집해야 할 스탠자와 속성의 경우에만 이렇게 하고, 실제로 변경해야 하는 구성 파일은 여러 개 복사해 두지 마십시오. 참고: 일부 구성 파일에는 기본 버전이 없습니다. 이러한 구성 파일에는 여전히.spec 및.example 파일이 있습니다. 비 UTF-8 운영 체제에서 구성 파일 만들기 및 편집 Splunk의 구성 파일은 ASCII/UTF-8 형식입니다. 비 UTF-8인 운영 체제에서 구성 파일을 편집하거나 만들 경우에는 파일을 ASCII/UTF-8로 저장하도록 사용할 편집기를 구성해야 합니다. 구성 파일 구조 구성 파일은 하나 이상의 스탠자 또는 섹션으로 구성됩니다. 각 스탠자는 각괄호로 구분된 스탠자 헤더로 시작됩니다. 이 헤더 다음에는 구성 설정을 지정하는 일련의 속성/값 쌍이 있습니다. 스탠자 유형에 따라 속성이 필수적이거나 선 택적일 수 있습니다. 다음은 기본 패턴입니다. [stanza1_header] <attribute1> = <val1> comment <attribute2> = <val2>... [stanza2_header] <attribute1> = <val1> <attribute2> = <val2>... 중요: 속성은 대소문자를 구분합니다. 예를 들어, sourcetype = my_app은 SOURCETYPE = my_app과 동일하지 않습니다. 하 나는 작동하고, 다른 하나는 작동하지 않습니다. 스탠자 범위 구성 파일은 우선 순위를 가진 더 많은 특정 스탠자와 함께 다양한 영역의 스탠자를 가진 경우가 많습니다. 예를 들어, Forwarder를 구성하는 데 사용하는 outputs.conf 구성 파일의 아래 예제를 보십시오. [tcpout] indexandforward=true compressed=true 46

[tcpout:my_indexersa] autolb=true compressed=false server=mysplunk_indexer1:9997, mysplunk_indexer2:9997 [tcpout:my_indexersb] autolb=true server=mysplunk_indexer3:9997, mysplunk_indexer4:9997 이 예제 파일에는 다음과 같은 두 가지 레벨의 스탠자가 있습니다. 모든 TCP 전달에 영향을 미치는 설정이 포함된 전역 [tcpout] 설정이 각 대상 그룹에 정의된 인덱서에만 영향을 미치는 두 가지 [tcpout:<target_list>] 스탠자 my_indexers에 있는 인덱서의 경우 [tcpout:my_indexersa]의 compressed 설정은 [tcpout]의 해당 속성 설정보다 우선합 니다. Forwarder 및 outputs.conf에 대한 자세한 내용은 "outputs.conf에서 Forwarder 구성"을 참조하십시오. 기타 구문 참고 사항 앞에서 설명한 내용 외에도 구성 파일을 편집할 때 몇 가지 주의할 사항이 있습니다. 속성 지우기 속성을 null로 설정하여 속성을 지울 수 있습니다. 예: forwardedindex.0.whitelist = 이렇게 하면 기본 파일에 설정된 값을 포함하여 속성에 저장된 이전 값이 지워집니다. 주석 사용 구성 파일에 주석을 삽입할 수 있습니다. 주석을 삽입하려면 기호를 사용하십시오. This stanza forwards some log files. [monitor:///var/log] 중요: 주석은 왼쪽 여백에서 시작합니다. 스탠자 또는 속성과 같은 줄에 주석을 작성하지 마십시오. [monitor:///var/log] This is a really bad place to put your comment. 구성 파일 리스트 다음은 각 conf 파일에 해당하는 spec 파일과 example 파일의 최신 리스트입니다. spec 또는 example 파일이 함께 제 공되지 않는 conf 파일도 있습니다. 이런 conf 파일을 편집하려면 지원 부서에 문의하십시오. 중요: $SPLUNK_HOME/etc/system/default/에 있는 conf 파일의 기본 복사본은 편집하지 마십시오. $SPLUNK_HOME/etc/system/local/ 또는 $SPLUNK_HOME/etc/apps/<app_name>/local에 있는 파일을 복사한 후 해당 복사본을 편 집하십시오. 파일 admon.conf alert_actions.conf app.conf audit.conf authentication.conf authorize.conf commands.conf crawl.conf default.meta.conf 용도 Windows Active Directory 모니터링을 구성합니다. 경고를 만듭니다. 사용자 지정 앱을 구성합니다. 감사(audit) 및 이벤트 해시를 구성합니다. Splunk 기본 제공 인증 또는 LDAP으로 전환하고 LDAP을 구성합니다. 세분화된 액세스 제어를 포함하여 역할을 구성합니다. 검색 명령어를 사용자 지정 검색 스크립트에 연결합니다. 크롤링을 구성하여 새 데이터 소스를 찾습니다. 앱별 default.meta 파일을 만들 때 사용하는 템플릿 파일입니다. 47

deploymentclient.conf distsearch.conf eventdiscoverer.conf event_renderers.conf eventtypes.conf fields.conf indexes.conf inputs.conf limits.conf literals.conf macros.conf multikv.conf outputs.conf pdf_server.conf procmon-filters.conf props.conf pubsub.conf regmon-filters.conf report_server.conf restmap.conf savedsearches.conf searchbnf.conf segmenters.conf server.conf serverclass.conf serverclass.seed.xml.conf source-classifier.conf sourcetypes.conf sysmon.conf tags.conf tenants.conf times.conf transactiontypes.conf transforms.conf user-seed.conf web.conf wmi.conf workflow_actions.conf 배포 서버의 클라이언트 동작을 지정합니다. 분산 검색 동작을 지정합니다. typelearner(이벤트 검색)에서 무시하도록 조건을 설정합니다. 이벤트 렌더링 속성을 구성합니다. event type 정의를 만듭니다. 다중값 필드를 만들고 인덱스 필드에 검색 기능을 추가합니다. 인덱스 설정을 관리 및 구성합니다. 데이터 입력을 설정합니다. 검색 명령어에 대한 여러 제한(예: 최대 결과 크기 또는 실시간 동시 검색 수)을 설정합니다. Splunk Web에 표시되는 검색 오류 문자열과 같은 텍스트를 사용자 지정합니다. 검색 언어 매크로를 정의합니다. 테이블 유형의 이벤트(ps, netstat, ls)에 대한 추출 규칙을 구성합니다. 전달 동작을 설정합니다. Splunk pdf 서버를 구성합니다. Windows 프로세스 데이터를 모니터링합니다. 시간대 오프셋, 사용자 지정 source type 규칙 및 패턴 충돌 우선 순위 등의 인덱싱 속성 구성을 설정합니다. 또 한 이벤트 속성에 대한 변형을 매핑합니다. 배포 서버의 사용자 지정 클라이언트를 정의합니다. Windows 레지스트리 모니터링 필터를 만듭니다. 보고서 서버를 구성합니다. 사용자 지정 REST endpoint를 만듭니다. 저장된 검색과 관련 스케줄 및 경고를 정의합니다. 검색 길잡이를 구성합니다. 세그먼트화를 구성합니다. Splunk 백엔드용 SSL을 활성화하고 인증 위치를 지정합니다. 배포 서버에서 사용할 배포 서버 클래스를 정의합니다. 시작 시 앱에서 배포 클라이언트를 시드하는 방법을 구성합니다. source type을 만들 때 무시할 조건(예: 중요한 데이터)입니다. source type 학습 규칙을 저장하는 컴퓨터 생성 파일입니다. Windows 레지스트리 모니터링을 설정합니다. 필드 태그를 구성합니다. 멀티테넌트 환경에서 배포를 구성합니다. 검색 앱에서 사용할 사용자 지정 시간 범위를 정의합니다. 트랜잭션 검색을 위해 트랜잭션 유형을 추가합니다. 데이터 입력에서 수행할 regex 변형을 구성합니다. props.conf와 함께 사용합니다. 기본 사용자 및 암호를 설정합니다. Splunk Web를 구성하고 HTTPS를 활성화합니다. WMI(Windows Management Instrumentation) 입력을 설정합니다. 워크플로 작업을 구성합니다. 구성 파일 우선 순위 이 항목에서는 Splunk가 구성 파일의 레이어를 주의깊게 살펴보고 사용할 설정을 결정하는 방법에 대해 설명합니다. 구성 파일에 대한 일반적인 내용은 "구성 파일에 대하여"에서 확인하십시오. 우선 순위 48

Splunk는 구성 파일을 사용하여 동작의 여러 측면을 판단합니다. 단일 Splunk 인스턴스에는 서로 다른 유형의 많은 구성 파일이 있을 뿐만 아니라 단일 Splunk 인스턴스에서는 동일한 구성 파일의 복사본을 여러 개 만들어 사용자, 앱 및 시스템별로 분류된 디렉터리에 차례로 배치합니다. 구성 파일을 사용할 때 Splunk는 위치 기반 우선 순위 지정 구 조를 사용하여 구성 파일의 모든 복사본에 있는 설정을 병합합니다. 서로 다른 복사본에서 속성 값이 충돌할 경우(즉, 동일한 속성에 다른 값이 설정된 경우), Splunk는 가장 높은 우선 순위 파일의 값을 사용합니다. Splunk는 디렉터리 구조에서 구성 파일의 위치에 따라 구성 파일의 우선 순위를 결정합니다. 가장 일반적으로는 구성 파일이 시스템, 앱 또는 사용자 디렉터리 중 어디에 있는 지에 따라 우선 순위가 정해집니다. Splunk 구성을 지능적으로 관리하려면 이러한 우선 순위가 어떻게 결정되는지 알고 있어야 합니다. 컨텍스트를 잘 이 해하면 전혀 복잡하지 않습니다. Splunk가 특정 파일을 어떤 컨텍스트에서 사용하는지 알면 우선 순위가 정해지는 방 식을 쉽게 이해할 수 있습니다. 참고: 파일의 여러 복사본의 구성 설정을 해결하는 것 외에도, Splunk가 단일 파일 내의 설정을 해결해야 할 경우가 있 습니다. 단일 props.conf 파일 내에서 우선 순위를 결정하는 방식은 "단일 props.conf 파일 내의 속성 우선 순위"를 참조 하십시오. 앱/사용자 컨텍스트 구성 파일의 복사본 중에서 우선 순위를 결정할 때 Splunk는 특정 구성이 앱/사용자 컨텍스트(현재 앱 및 사용자와 관 련된 경우)의 작업과 관련이 있는지 여부에 따라 두 가지 기본 구조를 사용합니다. 검색과 같은 작업은 앱/사용자 컨텍 스트에서 수행되며, 인덱싱과 같은 작업은 앱 또는 사용자와 관계 없이 전역 컨텍스트에서 수행됩니다. 인스턴스의 경우, 인덱싱 또는 모니터링 동작을 결정하는 구성 파일은 앱/사용자 이외의 컨텍스트에서 발생하며, 이러 한 구성 파일은 전역입니다. 데이터 입력 시 또는 이벤트 인덱싱 시 어떤 사용자 또는 어떤 앱에서 데이터 또는 이벤트 에 나중에 액세스하는 지는 중요하지 않습니다. 반면에 앱/사용자 컨텍스트는 검색 시간 처리에 매우 중요합니다. 여 기서 특정 knowledge object 또는 작업은 특정 앱의 특정 사용자에게만 유효할 수 있습니다. 피어 노드 구성 구성의 컨텍스트가 우선 순위에 미치는 영향 외에도 클러스터 피어 노드 전역 구성의 확장된 우선 순위가 있습니다. 그 이유는 indexes.conf와 같은 일부 구성 파일이 전체 피어 노드에서 동일해야 하기 때문입니다. 이 목적을 위해 해당 파일은 클러스터 마스터에서 관리되고, 클러스터 마스터는 이러한 파일을 피어 노드의 특정 위치에 배포합니다. 이 프 로세스는 인덱서 및 클러스터 관리 매뉴얼의 "공통 피어 구성 업데이트"에서 설명됩니다. 컨텍스트에 따른 우선 순위 방식 컨텍스트가 전역인 경우 앱/사용자 컨텍스트가 없으면 디렉터리 우선 순위는 시스템/로컬에서 앱, 시스템/기본으로 내 려갑니다. 시스템 로컬 디렉터리 - 가장 높은 우선 순위 앱 디렉터리(로컬이 기본보다 우선함) 시스템 기본 디렉터리 - 가장 낮은 우선 순위 inputs.conf 등의 전역 구성을 사용할 때 Splunk는 system/local에 있는 해당 파일의 복사본에서 속성을 먼저 가져옵니 다. 그런 다음 앱 디렉터리에 있는 파일의 복사본을 찾습니다. 앱 디렉터리에 있는 속성을 추가하지만 시스템/로컬에 서 이미 발견된 속성은 무시합니다. 마지막으로, 시스템 또는 앱 레벨에 명시적으로 할당되지 않은 속성에는 system/default 디렉터리에 있는 파일의 기본값이 할당됩니다. 클러스터 피어 노드의 전역 컨텍스트에는 가장 높은 우선 순위에서 몇 가지 추가 피어별 디렉터리가 있습니다. slave-apps/cluster/local 디렉터리(클러스터 피어만 해당) - 가장 높은 우선 순위 slave-apps/cluster/default 디렉터리(클러스터 피어만 해당) 시스템 로컬 디렉터리 앱 디렉터리(로컬이 기본보다 우선함) 시스템 기본 디렉터리 - 가장 낮은 우선 순위 앱/사용자 컨텍스트인 경우 디렉터리 우선 순위는 사용자에서 앱, 시스템 순으로 내려갑니다. 사용자 디렉터리 - 가장 높은 우선 순위 현재 실행 중인 앱의 앱 디렉터리(로컬이 기본보다 우선함) 다른 모든 앱의 앱 디렉터리(로컬이 기본보다 우선함) - 내보낸 설정만 해당 시스템 디렉터리(로컬이 기본보다 우선함) - 가장 낮은 우선 순위 savedsearches.conf의 속성은 예를 들어, 사용자, 앱, 시스템의 세 가지 레벨에서 모두 설정될 수 있습니다. Splunk는 앱 또는 시스템 레벨에서 설정된 동일한 속성보다 우선적으로 항상 사용자 레벨 속성 값을 사용합니다. 앱 디렉터리 이름이 우선 순위에 미치는 영향 참고: 이 하위 절에 나오는 내용은 중요하다고 볼 수는 없지만, 특정 순서로 평가 또는 문제 해결을 수행해야 할 경우에 는 유용할 수 있습니다. 앱 디렉터리 모음에서 우선 순위를 결정하기 위해 Splunk는 ASCII 정렬 순서를 사용합니다. 앱 디렉터리 이름의 "A" 파일은 앱 디렉터리 이름의 "B" 등의 파일보다 더 높은 우선 순위를 가집니다. 또한 숫자 디렉터리는 알파벳 디렉터리 보다 더 높은 우선 순위를 가지며, 숫자가 아닌 사전 순서로 평가됩니다. 예를 들어, 다음은 내림차순으로 평가됩니다. 49

$SPLUNK_HOME/etc/apps/myapp1 $SPLUNK_HOME/etc/apps/myapp10 $SPLUNK_HOME/etc/apps/myapp2 $SPLUNK_HOME/etc/apps/myapp20... $SPLUNK_HOME/etc/apps/myappApple $SPLUNK_HOME/etc/apps/myappBanana $SPLUNK_HOME/etc/apps/myappZabaglione... $SPLUNK_HOME/etc/apps/myappapple $SPLUNK_HOME/etc/apps/myappbanana $SPLUNK_HOME/etc/apps/myappzabaglione... 참고: 앱/사용자 컨텍스트에서 우선 순위를 결정할 때 디렉터리 명명 방식에 상관없이 현재 실행 중인 앱의 디렉터리 가 다른 모든 앱의 디렉터리보다 우선합니다. 또한 다른 앱은 내보낸 설정만 검사됩니다. 디렉터리 우선 순위 요약 디렉터리 우선 순위 순서는 다음과 같습니다. 전역 컨텍스트인 경우 $SPLUNK_HOME/etc/system/local/* $SPLUNK_HOME/etc/apps/A/local/*... $SPLUNK_HOME/etc/apps/z/local/* $SPLUNK_HOME/etc/apps/A/default/*... $SPLUNK_HOME/etc/apps/z/default/* $SPLUNK_HOME/etc/system/default/* 클러스터 피어 노드의 전역 컨텍스트인 경우 $SPLUNK_HOME/etc/slave-apps/cluster/local/* $SPLUNK_HOME/etc/slave-apps/cluster/default/* $SPLUNK_HOME/etc/system/local/* $SPLUNK_HOME/etc/apps/A/local/*... $SPLUNK_HOME/etc/apps/z/local/* $SPLUNK_HOME/etc/apps/A/default/*... $SPLUNK_HOME/etc/apps/z/default/* $SPLUNK_HOME/etc/system/default/* 앱/사용자 컨텍스트인 경우 $SPLUNK_HOME/etc/users/* $SPLUNK_HOME/etc/apps/Current_running_app/local/* $SPLUNK_HOME/etc/apps/Current_running_app/default/* $SPLUNK_HOME/etc/apps/A/local/*, $SPLUNK_HOME/etc/apps/A/default/*,... $SPLUNK_HOME/etc/apps/z/local/*, $SPLUNK_HOME/etc/apps/z/default/* (but see note below) $SPLUNK_HOME/etc/system/local/* $SPLUNK_HOME/etc/system/default/* 중요: 앱/사용자 컨텍스트에서 현재 실행 중인 앱의 모든 구성 파일은 다른 모든 앱의 파일보다 우선합니다. 이러한 우 선 순위는 앱의 로컬 및 기본 디렉터리에 해당됩니다. 따라서 현재 컨텍스트가 앱 C인 경우 Splunk는 다른 앱의 로컬 또는 기본 디렉터리를 평가하기 전에 $SPLUNK_HOME/etc/apps/C/local/* 및 $SPLUNK_HOME/etc/apps/C/default/*를 모두 평 가합니다. 또한 Splunk는 앱 권한 설정에 대해 이 항목에서 설명한 것처럼, 앱의 default.meta 파일을 통해 데이터를 전 역으로 내보낸 경우에는 다른 앱의 구성 데이터만 살펴봅니다. 또한 /etc/users/는 특정 사용자가 로그인하거나 검색을 수행할 때만 평가됩니다. 속성 우선 순위 방식을 보여주는 예 50

속성 우선 순위를 보여주는 이 예에서는 props.conf를 사용합니다. 이 파일의 컨텍스트는 Splunk의 파일 평가 시기에 따라 전역 또는 앱/사용자가 되기 때문에 props.conf 파일은 흔하게 볼 수 없습니다. Splunk는 인덱스 시간(전역)과 검 색 시간(앱/사용자)에서 모두 props.conf를 평가합니다. $SPLUNK_HOME/etc/system/local/props.conf에 다음 스탠자가 포함된 것으로 가정하고, [source::/opt/locke/logs/error*] sourcetype = fatal-error 및 $SPLUNK_HOME/etc/apps/t2rss/local/props.conf에는 이와 동일한 스탠자의 다른 버전이 포함되어 있는 것으로 가정합 니다. [source::/opt/locke/logs/error*] sourcetype = t2rss-error SHOULD_LINEMERGE = True BREAK_ONLY_BEFORE_DATE = True t2rss에서 라인 병합 속성 할당은 파일의 해당 버전에서만 발생하므로 항상 적용됩니다. 그러나 sourcetype 속성과 충 돌합니다. /system/local 버전에서 sourcetype은 "fatal-error" 값을 가지고, /apps/t2rss/local 버전에서는 "t2rss-error" 값 을 가집니다. 이것은 인덱스 시간에 적용되는 sourcetype 할당이므로 Splunk는 디렉터리 우선 순위를 결정하는 데 전역 컨텍스트를 사용합니다. 전역 컨텍스트에서 Splunk는 system/local의 속성 할당에 가장 높은 우선 순위를 제공합니다. 따라서 sourcetype 속성에는 "fatal-error" 값이 할당됩니다. 내부적으로 병합된 파일의 최종 버전은 다음과 같습니다. [source::/opt/locke/logs/error*] sourcetype = fatal-error SHOULD_LINEMERGE = True BREAK_ONLY_BEFORE_DATE = True 구성 파일 및 컨텍스트 리스트 Splunk는 파일이 전역 또는 앱/사용자 내에서 작동하는 컨텍스트를 기반으로 구성 파일을 어떻게 평가할지 결정합니 다. 일반적으로 데이터 입력, 인덱싱 또는 배포 작업에 영향을 미치는 파일은 전역이고, 검색 작업에 영향을 미치는 파 일은 보통 앱/사용자 컨텍스트를 가집니다. props.conf 및 transforms.conf 파일은 Splunk가 이러한 파일을 인덱스 시간 또는 검색 시간에 사용하는 지에 따라 앱/사 용자 또는 전역 컨텍스트로 평가됩니다. 전역 구성 파일 admon.conf authentication.conf authorize.conf crawl.conf deploymentclient.conf distsearch.conf indexes.conf inputs.conf outputs.conf pdf_server.conf procmonfilters.conf props.conf -- global and app/user context pubsub.conf regmonfilters.conf report_server.conf restmap.conf searchbnf.conf segmenters.conf server.conf serverclass.conf serverclass.seed.xml.conf source-classifier.conf sourcetypes.conf sysmon.conf tenants.conf transforms.conf -- global and app/user context 51

user_seed.conf -- special case: Must be located in /system/default web.conf wmi.conf 앱/사용자 구성 파일 alert_actions.conf app.conf audit.conf commands.conf eventdiscoverer.conf event_renderers.conf eventtypes.conf fields.conf limits.conf literals.conf macros.conf multikv.conf props.conf -- global and app/user context savedsearches.conf tags.conf times.conf transactiontypes.conf transforms.conf -- global and app/user context user-prefs.conf workflow_actions.conf 구성 우선 순위 및 기타 문제 해결 Splunk의 구성 파일 시스템은 다른 많은 위치에서 많은 구성 파일이 중복되는 것을 지원합니다. 이러한 유연성이 주 는 장점은 Splunk 설치에서 어떤 구성 옵션의 어떤 값이 가끔씩 복잡해지는지 알아낼 수 있다는 것입니다. 지정된 상 황에서 어떤 구성 설정이 사용되는지 쉽게 알 수 있으려면 문제 해결 매뉴얼의 "btool을 사용하여 구성 문제 해결"을 읽어보십시오. 단일 props.conf 파일 내의 속성 우선 순위 파일 간 속성 우선 순위에 대해 잘 알고 있는 동시에 단일 props.conf 파일 내의 속성 우선 순위도 고려해야 할 경우가 있습니다. 동일한 대상에 영향을 미치는 스탠자 집합 내의 우선 순위 둘 이상의 스탠자가 동일한 항목에 영향을 미치는 동작을 지정할 경우 스탠자의 ASCII 순서에 따라 항목이 평가됩니 다. 예를 들어, props.conf에서 다음 스탠자를 지정한다고 가정해 보십시오. [source::.../bar/baz] attr = val1 [source::.../bar/*] attr = val2 attr의 두 번째 스탠자 값이 사용됩니다. 그 이유는 해당 경로가 ASCII 순서에서 더 높은 우선 순위를 가지기 때문입니 다. props.conf의 기본 속성 우선 순위 재정의 props.conf의 기본 ASCII 우선 순위를 재정의하는 방법이 있습니다. priority 키를 사용하여 지정된 스탠자에 더 높거 나 더 낮은 우선 순위를 지정할 수 있습니다. 예를 들어, 소스가 다음과 같고 source::az 패턴은 다음과 같다고 가정하십시오. [source::...a...] sourcetype = a [source::...z...] 52

sourcetype = z 이 경우 "source::...a..." 패턴에 의해 제공된 설정이 "source::...z..."에 의해 제공된 설정보다 우선되는 것이 기본 동작입 니다. 따라서 sourcetype의 값은 "a"가 됩니다. 기본 ASCII 순서를 재정의하려면 priority 키를 사용하십시오. [source::...a...] sourcetype = a priority = 5 [source::...z...] sourcetype = z priority = 10 두 번째 스탠자에 더 높은 우선 순위를 할당하면 sourcetype의 값이 "z"가 됩니다. 고려해야 할 또 다른 속성 우선 순위 문제가 있습니다. 기본적으로 문자열이 문자 그대로 일치하는 스탠자("리터럴 일 치 스탠자")는 regex 패턴 일치 스탠자보다 우선됩니다. 이것은 priority 키의 기본값 때문입니다. 0은 패턴 일치 스탠자의 기본값입니다. 100은 리터럴 일치 스탠자의 기본값입니다. 따라서 priority 키를 명시적으로 설정하여 이 동작을 변경하지 않을 경우 리터럴 일치 스탠자는 항상 패턴 일치 스탠 자보다 우선됩니다. priority 키를 사용하여 sourcetype 패턴, host 패턴과 같은 동일한 유형의 패턴 간에 발생하는 충돌을 해결할 수 있습니 다. 그러나 priority 키는 spec 유형 전체에서 우선 순위에 영향을 미치지 않습니다. 예를 들어, 우선 순위 키 값에 상관 없이 source 패턴은 host 및 sourcetype 패턴보다 우선됩니다. 여러 속성 할당에서 이벤트의 우선 순위 props.conf 파일은 host, source 또는 sourcetype(및 event type)에 의해 개별 이벤트를 처리하는 속성을 설정합니다. 따 라서 하나의 이벤트가 기본 필드(source, host 또는 sourcetype)의 동일한 속성을 다르게 설정할 수 있습니다. 우선 순 위는 다음과 같습니다. source host sourcetype 기본 props.conf 설정을 재정의할 수도 있습니다. 예를 들어, mylogfile.xml(기본적으로 sourcetype = xml_file로 레이블 이 지정됨)를 사용자 지정한다고 가정합니다. 이 구성은 source에 의해 속성이 설정되었기 때문에 다른 sourcetype을 수동으로 지정하더라도 구성이 변경될 때마다 전체 파일을 다시 인덱스합니다. 이 작업을 재정의하려면 source별 명 시적 구성을 추가하십시오. [source::/var/log/mylogfile.xml] CHECK_METHOD = endpoint_md5 구성 매개 변수 및 데이터 파이프라인 데이터는 원시 입력 상태에서 검색 가능한 이벤트로 변환되기까지 여러 단계를 거칩니다. 이러한 프로세스를 데이터 파이프라인이라고 하며, 데이터 파이프라인은 네 단계로 구성됩니다. 입력 파싱 인덱싱 검색 분산 배포 매뉴얼의 "Splunk를 통해 데이터가 이동되는 방식: 데이터 파이프라인"에서 데이터 파이프라인에 대해 자 세히 설명하고 있습니다. 그리고 "구성 요소 및 역할"에서는 다양한 Splunk 구성 요소(예: Forwarder, 인덱서)가 파이 프라인의 다른 단계에서 어떻게 상관(correlate)되는 지에 대해 설명합니다. 예를 들어, 입력 단계는 Forwarder 또는 인 덱서에 의해 처리되고, 검색 단계는 인덱서 또는 검색 헤드에 의해 처리됩니다. 핵심 구성 파일의 매개 변수는 데이터 파이프라인의 특정 단계와 관련이 있습니다. 어떤 단계에서 매개 변수가 작동하 는지 알면 매개 변수의 정확한 기능을 쉽게 이해할 수 있습니다. 또한 이를 통해 Splunk 토폴로지의 어느 부분(특정 Splunk 구성 요소)에서 해당 매개 변수를 설정해야 하는지 빠르게 식별할 수 있습니다. 예를 들어, 검색 헤드가 사용자 의 토폴로지에서 검색을 처리할 경우, 해당 검색 헤드에 대한 검색 관련 매개 변수를 설정해야 하며, 인덱서에 대해서 는 설정할 필요가 없습니다. 단계별 구성 매개 변수 이것은 어떤 구성 매개 변수가 어떤 단계에 사용되는지 보여주는 non-exhaustive 리스트입니다. 토폴로지에 대한 지 식, 그리고 특히, 어떤 Splunk 구성 요소가 각 특정 단계를 처리하는 지를 이해하는 동시에 이 정보에 대해서도 잘 알 53

고 있으면 분산 배포 매뉴얼의 "구성 요소 및 역할"에서 설명한 것처럼 어떤 구성 요소에서 해당 설정을 필요로 하는지 판단할 수 있습니다. 입력 파싱 인덱싱 검색 기타 inputs.conf props.conf CHARSET NO_BINARY_CHECK CHECK_METHOD sourcetype wmi.conf regmon-filters.conf props.conf LINE_BREAKER, SHOULD_LINEMERGE, BREAK_ONLY_BEFORE_DATE 및 다른 모든 라인 병합 설 정 TZ, DATETIME_CONFIG, TIME_FORMAT, TIME_PREFIX 및 다른 모든 시간 추출 설정과 규칙 TRANSFORMS*에는 이벤트당 대기열 필터링, 이벤트당 인덱스 할당, 이벤트당 경로 설정이 포함되고, 정의된 순서대로 적용됩니다. SEDCMD* MORE_THAN*, LESS_THAN* transforms.conf props.conf의 TRANSFORMS* 절에서 참조되는 스탠자 LOOKAHEAD, DEST_KEY, WRITE_META, DEFAULT_VALUE, REPEAT_MATCH datetime.xml props.conf SEGMENTATION* indexes.conf segmenters.conf props.conf EXTRACT* REPORT* LOOKUP* KV_MODE FIELDALIAS* 이름 변경 transforms.conf props.conf의 REPORT* 절에서 참조되는 스탠자 filename, external_cmd 및 기타 모든 룩업 관련 설정 FIELDS, DELIMS MV_ADD 룩업 폴더의 룩업 파일 bin 폴더의 검색 및 룩업 스크립트 검색 명령어 및 룩업 스크립트 savedsearches.conf eventtypes.conf tags.conf commands.conf alert_actions.conf macros.conf fields.conf transactiontypes.conf multikv.conf 분산된 Splunk 환경에서는 제대로 작동하지 않는 설정이 있습니다. 이는 예외적인 경향이 있으며 해당 설정은 다음과 같습니다. props.conf CHECK_FOR_HEADER, LEARN_MODEL, maxdist. 파싱 단계에서 생성되지만, 생성된 구성을 검색 단 계 구성 위치로 이동시켜야 합니다. 구성 정보 백업 54

Splunk의 모든 구성 정보는 구성 파일에 포함됩니다. 구성 파일 집합을 백업하려면 $SPLUNK_HOME/etc/의 아카이브를 만 들거나 사본을 만드십시오. 이 디렉터리에는 하위 디렉터리와 함께 저장된 검색, 사용자 계정, 태그, 사용자 지정 source type 이름 및 기타 구성 정보를 비롯하여 Splunk 설치와 기타 모든 앱에 대한 모든 기본 설정과 사용자 지정 설 정이 포함됩니다. 복원할 새 Splunk 인스턴스에 이 디렉터리를 복사합니다. 이 작업을 위해 Splunk를 중지하지 않아도 됩니다. 기본 디렉터리 구조를 비롯하여 구성 파일에 대한 자세한 내용은 "구성 파일에 대하여"를 확인하십시오. 사용자 관리 사용자 및 역할에 대하여 Splunk Enterprise를 실행할 경우 암호와 함께 사용자를 만들고 이 사용자에게 역할을 할당할 수 있습니다. Splunk Free는 사용자 인증을 지원하지 않습니다. Splunk에는 단일 기본 사용자인 admin 사용자가 포함되어 있습니다. admin 사용자의 기본 암호는 changeme입니 다. 이 암호는 Splunk를 설치한 후에 바로 변경해야 합니다. 사용자 만들기 Splunk는 세 가지 유형의 인증 시스템에 대한 지원을 제공하며, 보안 매뉴얼에서 이 내용에 대해 설명합니다. Splunk 기본 제공 시스템. 자세한 내용은 "Splunk 기본 제공 시스템을 통한 사용자 인증에 대하여"를 참조하십 시오. LDAP. Splunk는 내부 인증 서비스 또는 기존 LDAP 서버를 이용한 인증을 지원합니다. 자세한 내용은 "LDAP 을 사용하여 사용자 인증 설정"을 참조하십시오. 스크립트 인증 API. 스크립트 인증을 사용하여 Splunk 인증을 RADIUS, PAM과 같은 외부 인증 시스템과 연결 합니다. 자세한 내용은 "외부 시스템을 사용하여 사용자 인증 설정"을 참조하십시오. 역할에 대하여 사용자마다 역할이 할당되고, 역할에는 기능 집합이 포함됩니다. 기능은 역할에 해당하는 작업을 지정합니다. 예를 들 어, 기능은 특정 역할을 가진 사용자에게 입력 추가 또는 저장된 검색 편집을 허용할지 여부를 결정합니다. 보안 매뉴 얼의 "역할 추가 및 편집"에 다양한 기능이 나열되어 있습니다. 기본적으로 Splunk는 다음 역할이 미리 정의된 상태로 제공됩니다. admin -- 관리자에게 할당되는 대부분의 기능을 가집니다. power -- 모든 공유 개체(저장된 검색 등)와 경고, 태그 이벤트 및 기타 유사한 작업을 편집할 수 있습니다. user -- 자체 소유한 저장된 검색을 만들거나 편집할 수 있고, 검색을 실행할 수 있으며, 자체 기본 설정을 편집할 수 있고, event type을 만들거나 편집할 수 있으며 기타 유사한 작업을 수행할 수 있습니다. 역할과 역할에 사용자를 할당하는 방법은 보안 매뉴얼의 "사용자 및 역할 기반 액세스 제어" 장을 참조하십시오. 기존 사용자 및 역할 찾기 관리자에서 기존 사용자 또는 역할을 찾으려면 Splunk 관리자의 "액세스 제어" 섹션에서 "사용자 또는 역할" 페이지 의 상단에 있는 검색란을 사용하십시오. 와일드카드가 지원됩니다. 기본적으로 Splunk는 사용 가능한 모든 필드에 입 력된 문자열을 검색합니다. 특정 필드를 검색하려면 필드를 지정하십시오. 예를 들어, 이메일 주소만 검색하려면 "email=<email address or address fragment>:를 입력하십시오. 또는 "이름" 필드만 검색하려면 "realname=<name or name fragment>를 입력하십시오. 지정된 역할의 사용자를 검색하려면 "roles="를 사용하십시오. 사용자 언어 및 로케일 구성 사용자가 로그인하면 Splunk는 자동으로 사용자의 브라우저에 설정된 언어를 사용합니다. 언어를 바꾸려면 브라우 저의 로케일 설정을 변경하십시오. 로케일 구성은 브라우저와 관련되어 있습니다. Splunk는 로케일 문자열을 탐지합니다. 로케일 문자열은 언어 지정자와 현지화 지정자의 두 가지 요소로 구성됩니다. 로케일 문자열은 일반적으로 소문자 2개와 대문자 2개를 밑줄로 연결하여 표시됩니다. 예를 들어, "en_us"는 미국 영 어를 의미하고, "en_gb"는 영국 영어를 의미합니다. 국가마다 날짜, 시간, 숫자 엔티티의 형식 지정에 다른 표준을 사용하므로, 사용자의 로케일은 날짜, 시간, 숫자 등의 형식에도 영향을 미칩니다. Splunk는 이러한 로케일에 대해 기본적인 지원을 제공합니다. 55

en_gb en_us ja_jp zh_cn zh_tw 추가 언어에 대한 현지화를 추가하려면 개발자 매뉴얼의 "Splunk 번역"을 참조하십시오. 그런 다음 사용자의 브라우 저에서 적합한 로케일을 지정하도록 할 수 있습니다. 브라우저 로케일이 타임스탬프 형식 지정에 미치는 영향 기본적으로 Splunk의 타임스탬프 형식은 브라우저 로케일에 따라 결정됩니다. 브라우저가 미국 영어로 구성된 경우 타임스탬프는 미국 방식인 MM/DD/YYYY:HH:MM:SS로 표시됩니다. 브라우저가 영국 영어로 구성된 경우 타임스탬프는 다 음과 같이 전통적인 유럽 날짜 표기 방식으로 표시됩니다: DD/MM/YYYY:HH:MM:SS. 타임스탬프 형식 지정에 대한 자세한 내용은 데이터 가져오기 매뉴얼의 "타임스탬프 인식 구성"을 참조하십시오. 브라우저 로케일 재정의 Splunk에 액세스하는 데 사용하는 URL을 수정하여 지정된 세션에 대해 Splunk가 사용하는 로케일을 변경할 수 있습 니다. Splunk URL은 http://host:port/locale/... 형식을 따릅니다. 예를 들어, Splunk에 로그인하기 위해 액세스할 때 URL이 미국 영어 로케일인 경우 http://hostname:8000/en-us/account/login으로 나타납니다. 영국 영어 설정을 사용하 려면 이 로케일 문자열을 http://hostname:8000/en-gb/account/login으로 변경하십시오. 그러면 이 세션 중에는 영국 영 어 형식으로 타임스탬프가 제공되고 허용됩니다. Splunk 인터페이스를 현지화한 로케일이 아닌 다른 로케일을 요청할 경우 다음과 같은 메시지가 표시됩니다: Invalid language Specified. Splunk 현지화에 대한 자세한 내용은 개발자 매뉴얼의 "Splunk 번역"을 참조하십시오. 사용자 Session timeout 구성 Splunk 사용자 세션이 제한 시간에 도달하기까지 걸리는 시간은 다음 세 가지 제한 시간 설정 간의 상호 작용에 따라 다릅니다. splunkweb Session timeout splunkd Session timeout 브라우저 Session timeout splunkweb 및 splunkd 제한 시간은 브라우저와 Splunk 간의 상호 작용에서 최대 유휴 시간을 결정합니다. 브라우저 Session timeout은 사용자와 브라우저 간의 상호 작용에서 최대 유휴 시간을 결정합니다. splunkweb 및 splunkd 제한 시간 값은 일반적으로 동일한 관리자 필드에 설정한 값과 동일합니다. Splunk 관리자에서 제한 시간을 설정하려면: 1. Splunk Web의 오른쪽 상단 모서리에 있는 관리자를 클릭합니다. 2. 시스템 구성에서 시스템 설정을 클릭합니다. 3. 일반 설정을 클릭합니다. 4. 시스템 제한 시간 필드에 제한 시간 값을 입력합니다. 5. 저장을 클릭합니다. 이렇게 하면 splunkweb 및 splunkd의 모든 사용자 Session timeout 값이 설정됩니다. 처음에는 모두 동일한 값(60분)을 공유하며, 관리자를 통해 이 값을 변경할 경우 모두 동일한 값을 계속 유지하게 됩니다. 경우에 따라 splunkweb 및 splunkd의 제한 시간을 서로 다른 값으로 설정해야 할 경우 기본 구성 파일 web.conf(tools.sessions.timeout 속성)과 server.conf(sessiontimeout 속성)를 편집하여 설정할 수 있습니다. 사실 이 값들 을 서로 다르게 지정할 이유가 없습니다. 사용자가 SplunkWeb(splunkweb)을 사용하여 Splunk 인스턴스(splunkd)에 액 세스할 경우 두 개의 제한 시간 속성 중에서 더 짧은 시간이 우선됩니다. 따라서 web.conf에서 tools.sessions.timeout의 값이 "90"(분)이고 server.conf에서 sessiontimeout의 값이 "1h"(1시간 또는 60분)일 경우 이 세션의 제한 시간은 60분이 됩니다. splunkweb/splunkd 세션 값 설정뿐만 아니라 web.conf에서 ui_inactivity_timeout 값을 편집하여 사용자 브라우저 세션의 제한 시간을 지정할 수도 있습니다. 이 값에 도달하면 Splunk 브라우저 세션을 사용할 수 없게 됩니다. 기본값은 60분 입니다. ui_inactivity_timeout을 1 미만으로 설정하면 제한 시간이 없게 되므로, 브라우저가 열려 있는 동안 계속 연결 이 유지됩니다. splunkweb/splunkd Session timeout은 브라우저 세션이 제한 시간 값에 도달하기 전까지는 카운트다운이 시작되지 않 습니다. 따라서 제한 시간 전에 사용자가 얼마나 있는지 결정하려면 splunkweb 및 splunkd의 제한 시간 값 중에서 더 적 은 값에 ui_inactivity_timeout의 값을 추가하십시오. 예를 들어, 다음을 가정해 보십시오. 56

splunkweb 제한 시간: 15m splunkd 제한 시간: 20m 브라우저(ui_inactivity_timeout) 제한 시간: 10m 이 사용자 세션은 25m(15m+10m) 동안 활성 상태를 유지합니다. 25분이 지나서도 사용하지 않으면 다시 로그인하라 는 메시지가 나타납니다. 참고: 관리자 또는 구성 파일에서 제한 시간 값을 변경할 경우 변경 사항을 적용하려면 Splunk를 재시작해야 합니다. Splunk 명령줄 인터페이스(CLI) 사용 CLI에 대하여 Splunk 명령줄 인터페이스(CLI)를 사용하여 Splunk 서버에서 검색을 모니터링, 구성 및 실행할 수 있습니다. Splunk 역할 구성에는 실행할 수 있는 작업(명령)이 나와 있습니다. 대부분의 작업에는 Splunk 관리자 권한이 필요합니다. Splunk 사용자 및 역할 설정과 관리에 대한 내용은 관리자 매뉴얼의 "사용자 및 역할에 대하여" 항목을 참조하십시오. CLI 도움말은 제품에 있으며 터미널이나 셸 인터페이스를 통해 액세스할 수 있습니다. 이 항목에서는 이 정보에 액세 스하는 방법과 사용 가능한 명령에 대해 설명합니다. CLI에 액세스하는 방법 Splunk CLI는 $SPLUNKHOME/bin/splunk에 있습니다. Splunk CLI에 액세스하려면 다음 중 하나가 필요합니다. Splunk 서버에 대한 셸 액세스 또는 원격 Splunk 서버에서 올바른 포트에 액세스할 수 있는 권한 관리자 또는 루트 권한이 있는 경우 Splunk 설치의 최상위 디렉터리를 셸 경로에 추가하여 CLI 액세스를 단순화할 수 있습니다. $SPLUNK_HOME 변수는 최상위 디렉터리를 나타냅니다. SPLUNK_HOME 환경 변수를 설정하고 $SPLUNK_HOME/bin을 셸의 경로에 추가하십시오. 이 예제는 기본 위치에 Splunk를 설치한 Linux/BSD/Solaris 사용자에 해당됩니다. export SPLUNK_HOME=/opt/splunk export PATH=$SPLUNK_HOME/bin:$PATH 이 예제는 기본 위치에 Splunk를 설치한 Mac 사용자에 해당됩니다. export SPLUNK_HOME=/Applications/Splunk export PATH=$SPLUNK_HOME/bin:$PATH 이제 다음을 사용하여 CLI 명령어를 호출할 수 있습니다../splunk <command> 참고: Windows를 사용하는 경우 Splunk는 CLI 명령어를 실행하기 위해 "./"가 필요하지 않습니다. CLI 명령어 관리자 권한이 있을 경우 CLI를 사용하여 Splunk 서버를 검색할 뿐만 아니라 구성 및 모니터링도 수행할 수 있습니다. Splunk 구성 및 모니터링에 사용되는 CLI 명령어는 검색 명령어가 아닙니다. 검색 명령은 search 및 dispatch CLI 명령 어에 대한 인수입니다. 일부 명령을 사용하려면 사용자 이름 및 암호로 인증해야 하거나 대상 Splunk 서버를 지정해 야 합니다. 자세한 내용은 이 매뉴얼의 "CLI 도움말 보기" 및 "CLI 관리 명령"을 참조하십시오. Mac 사용자 참고 사항 Mac OS X에서는 시스템 파일 또는 디렉터리에 액세스하는 명령을 실행하려면 수퍼사용자 레벨 액세스가 필요합니 다. 새로운 셸에 대해 루트로 sudo 또는 "su -"를 사용하여 CLI 명령어를 실행하십시오. sudo를 사용하는 방법이 권장 됩니다. (기본적으로 사용자 "루트"는 활성화되지 않았지만 관리자는 sudo를 사용할 수 있습니다.) Windows에서 CLI 작업 Windows에서 CLI 명령어에 액세스하고 사용하려면 관리자로서 cmd.exe를 먼저 실행하십시오. 57

답변 질문이 있으십니까? Splunk 응답 페이지에 가면 CLI 사용과 관련하여 Splunk 커뮤니티에서 올린 질문과 답변을 볼 수 있습니다. CLI 도움말 보기 이 항목에서는 CLI 명령어와 명령을 사용하는 방법에 대한 정보가 포함되어 있는 Splunk 기본 제공 CLI 도움말 참조 에 액세스하는 방법을 설명합니다. 또한 CLI 명령어와 함께 사용할 수 있는 매개 변수인 범용 매개 변수에 대해서도 간 략하게 설명합니다. CLI 도움말 참조 액세스 CLI 명령어 또는 CLI 명령어 구문을 찾아야 할 경우 Splunk 기본 제공 CLI 도움말 참조를 사용하십시오. help 명령을 사용하여 기본 도움말 정보에 액세스할 수 있습니다../splunk help Splunk에서 다음 내용을 반환합니다. Welcome to Splunk's Command Line Interface (CLI). Try typing these commands for more help: help [command] type a command name to access its help page help [object] type an object name to access its help page help [topic] type a topic keyword to get help on a topic help clustering commands that can be used to configure the clustering setup help commands & nbsp; display a full list of CLI commands help control, controls tools to start, stop, manage Splunk processes help datastore manage Splunk's local filesystem use help distributed manage distributed configurations such as data cloning, routing, and distributed search help forwarding manage deployments & nbsp; help input, inputs manage data inputs help licensing manage licenses for your Splunk server help settings manage settings for your Splunk server help simple, cheatsheet display a list of common commands with syntax help tools tools to help your Splunk server help search help with Splunk searches & nbsp; Universal Parameters: The following parameters are usable by any command. For more details on each parameter, type "help [parameter]". Syntax: [command] [object] [-parameter <value> <value>]... [-uri][-auth] app auth owner uri specify the App or namespace to run the command; for search, defaults to the Search App specify login credentials to execute commands that require you to be logged in specify the owner/user context associated with an object; if not specified, defaults to the currently logged in user execute a command on any specified Splunk server, user the format: <ip>:<port> 모든 CLI 명령어 리스트를 보려면 다음을 입력하십시오../splunk help commands 또는 다음 명령어를 입력하여 Splunk 검색 명령에 대한 도움말 페이지에 액세스할 수 있습니다../splunk help search-commands 자세한 내용은 이 매뉴얼의 "CLI 관리 명령"을 참조하십시오. CLI를 사용한 데이터 검색 구문에 대한 자세한 내용은 58

검색 참조 매뉴얼의 "CLI 검색에 대하여"를 참조하십시오. 참고: "검색"과 "명령"의 두 단어 사이에 대시(-)를 사용하십시오. 그 이유는 Splunk CLI에서 공백을 구분선으로 인식 하기 때문입니다. 둘 이상의 단어로 구성된 항목 이름에서 단어 사이에 대시를 사용하십시오. 범용 매개 변수 일부 명령을 사용하려면 사용자 이름 및 암호로 인증해야 하거나 대상 호스트 또는 앱을 지정해야 합니다. 이러한 명 령에는 범용 매개 변수 auth, app 또는 uri 중 하나를 포함할 수 있습니다. auth CLI 명령어에 인증이 필요할 경우 Splunk는 사용자 이름과 암호를 제공하도록 요청합니다. 또한 -auth 플래그를 사용 하면 이 명령으로 해당 정보를 인라인으로 전달할 수 있습니다. 또한 auth 매개 변수는 현재 로그인한 사용자의 권한이 아닌 다른 권한을 요구하는 명령을 실행해야 할 경우에도 유용합니다. 참고: auth는 CLI 명령어 인수에 지정되는 마지막 매개 변수여야 합니다. 구문:./splunk command object [-parameter value]... -auth username:password uri 원격 Splunk 서버에서 명령을 실행하려면 -uri 플래그를 사용하여 대상 호스트를 지정하십시오. 구문:./splunk command object [-parameter value]... -uri specified-server 다음 형식으로 대상 Splunk 서버를 지정하십시오. [http https]://name_of_server:management_port IPv4 및 IPv6 형식은 모두 IP 주소 지정에 대해 지원됩니다. 예: 127.0.0.1:80 또는 "[2001:db8::1]:80". 기본적으로 splunkd는 IPv4만 수신 대기합니다. IPv6 지원을 사용하려면 "IPv6용 Splunk 구성"의 설명을 참조하십시오. 예: 다음 예제는 포트 8089의 원격 "splunkserver"에서 검색 결과를 반환합니다../splunk search "host=fflanda error 404 *.gif" -auth admin -uri https://splunkserver:8089 참고: 원격 서버에서 실행할 수 있는 CLI 명령어에 대한 자세한 내용은 이 장의 다음 항목을 참조하십시오. CLI 관리 명령 이 항목에서는 Splunk CLI를 사용하여 관리 기능을 수행하는 것에 대한 정보를 포함합니다. 참고 항목: 일반적인 정보는 "CLI 도움말 보기"를 참조하십시오. CLI를 사용한 검색 구문에 대한 자세한 내용은 검색 참조 매뉴얼의 "CLI 검색에 대하여"를 참조하십시오. Splunk CLI 명령어 구문 다음은 CLI 명령어에 대한 일반 구문입니다../splunk <command> [<object>] [[-<parameter>] <value>]... 다음 사항을 고려하십시오. 일부 명령의 경우 개체 또는 매개 변수가 필요하지 않습니다. 일부 명령의 경우 값 단독으로 지정할 수 있는 기본 매개 변수가 있습니다. 명령 및 개체 명령은 수행하는 작업입니다. 개체는 수행하는 작업의 대상입니다. 다음은 지원되는 명령 및 개체의 리스트입니다. 59

[command] [objects] add [exec forward-server index licenser-pools licenses monitor oneshot saved-search search-server tcp udp user] apply [cluster-bundle] anonymize source clean & nbsp; [all eventdata globaldata userdata inputdata] diag NONE disable [app boot-start deploy-client deploy-server dist-search index listen local-index webserver web-ssl] display & nbsp; [app boot-start deploy-client deploy-server dist-search index jobs listen local-index] edit [app cluster-config exec forward-server index licenser-localslave licenses licenser-groups monitor saved-search search-server tcp udp user] enable [app deploy-client deploy-server dist-search index listen local-index boot-start webserver web-ssl] export [eventdata] import [userdata] install [app] find logs help NONE list & nbsp; [cluster-config cluster-generation cluster-peers cluster-buckets deployclients exec forward-server index licenser-groups licenser-localslave licenser-messages licenserpools licenser-slaves licenser-stacks licenses jobs master-info monitor peer-info peerbuckets saved-search search-server source sourcetype tcp udp user] login,logout NONE & nbsp; package app refresh deploy-clients reload [auth deploy-server] remove [app exec forward-server jobs licenser-pools licenses monitor saved-search search-server source sourcetype tcp udp user] rolling-restart [cluster-peers] & nbsp; rtsearch [app batch detach header index_earliest index_latest max_time maxout output preview timeout wrap] search [app batch detach header index_earliest index_latest max_time maxout output preview timeout wrap] set & nbsp; [datastore-dir deploy-poll default-hostname default-index minfreemb servername server-type splunkd-port web-port] show [config cluster-bundle-status datastore-dir deploy-poll default-hostname default-index jobs minfreemb servername splunkd-port web-port] spool NONE start,stop,restart [splunkd splunkweb] 60

status & nbsp; [splunkd splunkweb] CLI를 사용하여 원격 Splunk 서버 관리 CLI 명령어에서 uri 매개 변수를 사용하여 다른 Splunk 서버로 명령을 전송하고 로컬 서버에서 그 결과를 볼 수 있습 니다. 이 항목에서는 다음에 대해 설명합니다. uri 매개 변수를 사용한 구문 원격으로 사용할 수 없는 CLI 명령어 참고: 4.1.4부터는 기본 암호를 변경하기 전까지 관리자의 원격 CLI 액세스를 기본적으로 사용할 수 없습니다. 원격 액세스 활성화 Splunk Free를 실행할 경우(로그인 자격 증명 필요 없음) $SPLUNK_HOME/etc/system/local/server.conf를 편집하고 값을 설정할 때까지 기본적으로 원격 액세스를 사용할 수 없습니다. allowremotelogin=always 구성 파일 편집에 대한 자세한 내용은 이 매뉴얼의 구성 파일에 대하여를 참조하십시오. CLI 명령어를 원격 서버로 전송 CLI 명령어에서 uri 매개 변수를 사용하는 일반 구문은 다음과 같습니다../splunk command object [-parameter <value>]... -uri <specified-server> uri 값인 specified-server 형식은 다음과 같이 지정됩니다. [http https]://name_of_server:management_port 또한 name_of_server는 원격 Splunk 서버의 완전한 도메인 이름이거나 IP 주소입니다. 중요: 이 uri 값은 원격 Splunk 서버의 web.conf에 정의된 mgmthostport 값입니다. 자세한 내용은 이 매뉴얼의 "web.conf 참조"를 참조하십시오. CLI에 대한 일반적인 내용은 이 매뉴얼의 "CLI에 대하여" 및 "CLI 도움말 보기"를 참조하십시오. 원격 서버 검색 다음 예제는 원격 "splunkserver"의 검색 결과를 반환합니다../splunk search "host=fflanda error 404 *.gif" -uri https://splunkserver:8089 CLI를 사용한 검색 구문에 대한 자세한 내용은 검색 참조 매뉴얼의 "CLI 검색에 대하여"를 참조하십시오. 원격 서버에 설치된 앱 보기 다음 예제는 원격 "splunkserver"에 설치된 앱 리스트를 반환합니다../splunk display app -uri https://splunkserver:8089 기본 URI 값 변경 SPLUNK_URI 환경 변수를 사용하여 기본 URI 값을 설정할 수 있습니다. 이 값이 원격 서버의 URI 값이 되도록 변경 할 경우 해당 원격 서버에 액세스할 때마다 uri 매개 변수를 포함할 필요가 없습니다. SPLUNK_URI의 값을 변경하려면 다음과 같이 입력하십시오. $ export SPLUNK_URI=[http https]://name_of_server:management_port For Unix shells C:\> set SPLUNK_URI=[http https]://name_of_server:management_port For Windows shell 위의 예제에서는 다음과 같이 입력하여 SPLUNK_URI 값을 변경할 수 있습니다. 61

$ export SPLUNK_URI=https://splunkserver:8089 원격으로 실행할 수 없는 CLI 명령어 서버를 제어하는 명령을 제외한 모든 CLI 명령어를 원격으로 실행할 수 있습니다. 이러한 서버 제어 명령에는 다음이 포함됩니다. 시작, 중지, 재시작 상태, 버전 CLI 도움말 참조에 액세스하여 모든 CLI 명령어를 볼 수 있습니다. 자세한 내용은 이 매뉴얼의 "CLI 도움말 보기"를 참 조하십시오. 구성 파일 참조 alert_actions.conf 다음은 alert_actions.conf의 사양 및 예제 파일입니다. alert_actions.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attributes and values for configuring global saved search actions in alert_actions.conf. Saved searches are configured in savedsearches.conf. There is an alert_actions.conf in $SPLUNK_HOME/etc/system/default/. To set custom configurations, place an alert_actions.conf in $SPLUNK_HOME/etc/system/local/. For examples, see alert_actions.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. & nbsp; * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. maxresults = <integer> * Set the global maximum number of search results sent via alerts. * Defaults to 100. hostname = <string> * Sets the hostname used in the web link (url) sent in alerts. * This value accepts two forms. * hostname examples: splunkserver, splunkserver.example.com * protocol://hostname:port examples: http://splunkserver:8000, https://splunkserver.example.com:443 * When this value is a simple hostname, the protocol and port which are configured within splunk are used to construct the base of the url. * When this value begins with 'http://', it is used verbatim. NOTE: This means the correct port must be specified if it is not the default port for http or https. * This is useful in cases when the Splunk server is not aware of how to construct an externally referencable url, such as SSO environments, other proxies, or when the Splunk server hostname is not generally resolvable. * Defaults to current hostname provided by the operating system, or if that fails, "localhost". * When set to empty, default behavior is used. 62

ttl = <integer>[p] * optional argument specifying the minimum time to live (in seconds) of the search artifacts, if this action is triggered. * if p follows integer, then integer is the number of scheduled periods. * If no actions are triggered, the artifacts will have their ttl determined by the "dispatch.ttl" attribute in savedsearches.conf. * Defaults to 10p * Defaults to 86400 (24 hours) for: email, rss * Defaults to 600 (10 minutes) for: script * Defaults to 120 (2 minutes) for: summary_ index, populate_lookup maxtime = <integer>[m s h d] * The maximum amount of time that the execution of an action is allowed to take before the action is aborted. * Use the d, h, m and s suffixes to define the period of time: d = day, h = hour, m = minute and s = second. For example: 5d means 5 days. * Defaults to 5m for everything except rss. * Defaults to 1m for rss. track_alert = [1 0] * indicates whether the execution of this action signifies a trackable alert. * Defaults to 0 (false). command = <string> * The search command (or pipeline) which is responsible for executing the action. * Generally the command is a template search pipeline which is realized with values from the saved search - to reference saved search field values wrap them in dollar signs ($). * For example, to reference the savedsearch name use $name$. To reference the search, use $search$ EMAIL: these settings are prefaced by the [email] stanza name [email] * Set email notification options under this stanza name. * Follow this stanza name with any number of the following attribute/value pairs. * If you do not specify an entry for each attribute, Splunk will use the default value. from = <string> * Email address from which the alert originates. * Defaults to splunk@$localhost. to = <string> & nbsp; * to email address receiving alert. cc = <string> * cc email address receiving alert. bcc = <string> * bcc email address receiving alert. subject = <string> * Specify an alternate email subject. * Defaults to SplunkAlert-<savedsearchname>. format = [plain html raw csv] * Specify the format of text in the email. * Acceptable values: plain, html, raw, and csv. * This value will also apply to any attachments. sendresults = [1 0] * Specify whether the search results are included in the email. The results can be attached or inline, see inline (action.email.inline) * Defaults to 0 (false). 63

inline = [1 0] * Specify whether the search results are contained in the body of the alert email. * Defaults to 0 (false). mailserver = <host>[:<port>] * You must have a Simple Mail Transfer Protocol (SMTP) server available to send email. This is not included with Splunk. * The SMTP mail server to use when sending emails. & nbsp; * <host> can be either the hostname or the IP address. * Optionally, specify the SMTP <port> that Splunk should connect to. * When the "use_ssl" attribute (see below) is set to 1 (true), you must specify both <host> and <port>. (Example: "example.com:465") * Defaults to $LOCALHOST:25. use_ssl = [1 0] * Whether to use SSL when communicating with the SMTP server. * When set to 1 (true), you must also specify both the server name or & nbsp; IP address and the TCP port in the "mailserver" attribute. * Defaults to 0 (false). use_tls = [1 0] * Specify whether to use TLS (transport layer security) when communicating with the SMTP server (starttls) * Defaults to 0 (false). auth_username = <string> * The username to use when authenticating with the SMTP server. If this is not defined or is set to an empty string, no authentication is attempted. NOTE: your SMTP server might reject unauthenticated emails. * Defaults to empty string. auth_password = <string> * The password to use when authenticating with the SMTP server. Normally this value will be set when editing the email settings, however you can set a clear text password here and it will be encrypted on the next Splunk restart. * Defaults to empty string. sendpdf = [1 0] * Specify whether to create and send the results as a PDF. * Defaults to 0 (false). pdfview = <string> * Name of view to send as a PDF reportserverenabled = [1 0] * Specify whether the PDF server is enabled. * Defaults to 0 (false). reportserverurl = <url> * The URL of the PDF report server, if one is set up and available on the network. * For a default locally installed report server, the URL is http://localhost:8091/ reportpapersize = [letter legal ledger a2 a3 a4 a5] * Default paper size for PDFs * Acceptable values: letter, legal, ledger, a2, a3, a4, a5 * Defaults to "letter". reportpaperorientation = [portrait landscape] * Paper orientation: portrait or landscape * Defaults to "portrait". reportincludesplunklogo = [1 0] * Specify whether to include a Splunk logo in Integrated PDF Rendering * Defaults to 1 (true) 64

reportcidfontlist = <string> * Specify the set (and load order) of CID fonts for handling Simplified Chinese(gb), Traditional Chinese(cns), Japanese(jp), and Korean(kor) in Integrated PDF Rendering. * Specify in space separated list * If multiple fonts provide a glyph for a given character code, the glyph from the first font specified in the list will be used * To skip loading any CID fonts, specify the empty string * Defaults to "gb cns jp kor" width_sort_columns = <bool> * Whether columns should be sorted from least wide to most wide left to right. * Valid only if format=text * Defaults to true preprocess_results = <search-string> * Supply a search string to Splunk to preprocess results before emailing them. Usually the preprocessing consists of filtering out unwanted internal fields. * Defaults to empty string (no preprocessing) RSS: these settings are prefaced by the [rss] stanza [rss] * Set RSS notification options under this stanza name. * Follow this stanza name with any number of the following attribute/value pairs. * If you do not specify an entry for each attribute, Splunk will use the default value. items_count = <number> * Number of saved RSS feeds. * Cannot be more than maxresults (in the global settings). * Defaults to 30. script: Used to configure any scripts that the alert triggers. [script] filename = <string> * The filename of the script to trigger. * Defaults to empty string. summary_index: these settings are prefaced by the [summary_index] stanza [summary_index] inline = [1 0] * Specfies whether the summary index search command will run as part of the scheduled search or as a follow-on action. This is useful when the results of the scheduled search are expected to be large. * Defaults to 1 (true). _name = <string> * The name of the summary index where Splunk will write the events. * Defaults to "summary". populate_lookup: these settings are prefaced by the [populate_lookup] stanza [populate_lookup] dest = <string> * the name of the lookup table to populate (stanza name in transforms.conf) or the lookup file path to where you want the & nbsp; data written. If a path is specified it MUST be relative to $SPLUNK_HOME and a valid lookups directory. For example: "etc/system/lookups/<file-name>" or "etc/apps/<app>/lookups/<file-name>" * The user executing this action MUST have write permissions to the app for this action to work properly. 65

alert_actions.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This is an example alert_actions.conf. Use this file to configure alert actions for saved searches. To use one or more of these configurations, copy the configuration block into alert_actions.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles [email] keep the search artifacts around for 24 hours ttl = 86400 if no @ is found in the address the hostname of the current machine is appended from = splunk $name$ will be substituted from the scheduled search subject = Splunk Alert: $name$. format = html reportserverurl = http://localhost:8091/ inline = false sendresults = true hostname = CanAccessFromTheWorld.com command = sendemail "to=$action.email.to$" "server=$action.email.mailserver{default=localhost}$" "from=$action.email.from{default=splunk@localhost}$" "subject=$action.email.subject{recurse=yes}$" "format=$action.email.format{default=csv}$" "sssummary=saved Search [$name$]: $counttype$($results.count$)" "sslink=$results.url$" "ssquery=$search$" "ssname=$name$" "inline=$action.email.inline{default=false}$" "sendresults=$action.email.sendresults{default=false}$" "sendpdf=$action.email.sendpdf{default=false}$" "pdfview=$action.email.pdfview$" "searchid=$search_id$" "graceful=$graceful{default=true}$" maxinputs="$maxinputs{default=1000}$" maxtime="$action.email.maxtime{default=5m}$" _validate-1 = action.email.sendresults, validate( is_bool('action.email. sendresults'), "Value of argument 'action.email.sendresults' must be a boolean") [rss] at most 30 items in the feed items_count=30 keep the search artifacts around for 24 hours ttl = 86400 command = createrss "path=$name$.xml" "name=$name$" "link=$results.url$" "descr=alert trigger: $name$, results.count=$results.count$ " "count=30" "graceful=$graceful{default=1}$" maxtime="$action.rss.maxtime{default=1m}$" [summary_index] don't need the artifacts anytime after they're in the summary index ttl = 120 make sure the following keys are not added to marker (command, ttl, maxresults, _*) command = summaryindex addtime=true index="$action.summary_index._name{required=yes}$" file="$name$_$random$.stash" name="$name$" marker="$action.summary_index*{format=$key=\\\"$val\\\", key_regex="action.summary_index.(?! (?:command maxresults ttl (?:_.*))$)(.*)"}$" app.conf 다음은 app.conf의 사양 및 예제 파일입니다. 66

app.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file maintains the state of a given app in Splunk. It may also be used to customize certain aspects of an app. There is no global, default app.conf. Instead, an app.conf may exist in each app in Splunk. You must restart Splunk to reload manual changes to app.conf. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles Settings for how this app appears in Launcher (and online on Splunkbase) [launcher] global setting remote_tab = <bool> * Set whether the Launcher interface will connect to splunkbase.splunk.com. * This setting only applies to the Launcher app and should be not set in any other app * Defaults to true. per-application settings version = <version string> * Version numbers are a number followed by a sequence of numbers or dots. * Pre-release versions can append a space and a single-word suffix like "beta2". Examples: * 1.2 * 11.0.34 * 2.0 beta * 1.3 beta2 * 1.0 b2 * 12.4 alpha * 11.0.34.234.254 description = <string> * Short explanatory string displayed underneath the app's title in Launcher. * Descriptions should be 200 characters or less because most users won't read long descriptions! author = <name> * For apps you intend to post to Splunkbase, enter the username of your splunk.com account. * For internal-use-only apps, include your full name and/or contact info (e.g. email). Your app can include an icon which will show up next to your app in Launcher and on Splunkbase. You can also include a screenshot, which will show up on Splunkbase when the user views info about your app before downloading it. Icons are recommended, although not required. Screenshots are optional. There is no setting in app.conf for these images. Instead, icon and screenshot images should be placed in the appserver/static dir of your app. They will automatically be detected by Launcher and Splunkbase. For example: <app_directory>/appserver/static/appicon.png (the capital "I" is required!) <app_directory>/appserver/static/screenshot.png An icon image must be a 36px by 36px PNG file. An app screenshot must be 623px by 350px PNG file. [package] defines upgrade-related metadata, and will be used in future versions of Splunk to streamline app upgrades. 67

[package] id = <appid> * id should be omitted for internal-use-only apps which are not intended to be uploaded to Splunkbase * id is required for all new apps uploaded to Splunkbase. Future versions of Splunk will use appid to correlate locally-installed apps and the same app on Splunkbase (e.g. to notify users about app updates) * id must be the same as the folder name in which your app lives in $SPLUNK_HOME/etc/apps * id must adhere to cross-platform folder-name restrictions: - must contain only letters, numbers, "." (dot), and "_" (underscore) characters - must not end with a dot character - must not be any of the following names: CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9 check_for_updates = < bool> * Set whether Splunk should check Splunkbase for updates to this app. * Defaults to true. Set install settings for this app [install] state = disabled enabled * Set whether app is disabled or enabled. * If an app is disabled, its configs are ignored. * Defaults to enabled. state_change_requires_restart = true false * Set whether changing an app's state ALWAYS requires a restart of Splunk. * State changes include enabling or disabling an app. * When set to true, changing an app's state always requires a restart. * When set to false, modifying an app's state may or may not require a restart depending on what the app contains. This setting cannot be used to avoid all restart requirements! * Defaults to false. is_configured = true false * Stores indication of whether the application's custom setup has been performed * Defaults to false build = < integer> * Required. * Must be a positive integer. * Increment this whenever you change files in appserver/static. * Every release must change both "version" and "build" settings. * Ensures browsers don't use cached copies of old static files in new versions of your app. * Build is a single integer, unlike version which can be a complex string like 1.5.18. allows_disable = true false * Set whether an app allows itself to be disabled. * Defaults to true. Handle reloading of custom.conf files (4.2+ versions only) [triggers] reload.<conf_file_name> = [ simple rest_endpoints access_endpoints <handler_url> ] * Splunk will reload app configuration after every app-state change: install, update, enable, and disable. * If your app does not use a custom config file (e.g. myconffile.conf) then it won't need a [triggers] stanza, because 68

$SPLUNK_HOME/etc/system/default/app.conf already includes a [triggers] stanza which automatically reloads config files normally used by Splunk. * If your app uses a custom config file (e.g. myconffile.conf) and you want to avoid unnecessary Splunk restarts, you'll need to add a reload value in the [triggers] stanza. * If you don't include [triggers] settings and your app uses a custom config file, a Splunk restart will be required after every state change. * Specifying "simple" implies that Splunk will take no special action to reload your custom conf file. * Specify "access_endpoints" and a URL to a REST endpoint, and Splunk will call its _reload() method at every app state change. * "rest_endpoints" is reserved for Splunk's internal use for reloading restmap.conf. * Examples: & nbsp; [triggers] Do not force a restart of Splunk for state changes of MyApp Do not run special code to tell MyApp to reload myconffile.conf Apps with custom config files will usually pick this option reload.myconffile = simple Do not force a restart of Splunk for state changes of MyApp. Splunk calls the /admin/myendpoint/_reload method in my custom EAI handler. Use this advanced option only if MyApp requires custom code to reload its configuration when its state changes reload.myotherconffile = access_endpoints /admin/myendpoint Set UI-specific settings for this app [ui] is_visible = true false * Indicates if this app should be visible/navigable as a UI app * Apps require at least 1 view to be available from the UI is_manageable = true false * Indicates if Splunk Manager should be used to manage this app * Defaults to true * This setting is deprecated. label = <string> * Defines the name of the app shown in the Splunk GUI and Launcher * Recommended length between 5 and 80 characters. * Must not include "Splunk For" prefix. * Label is required. * Examples of good labels: IMAP Monitor SQL Server Integration Services FISMA Compliance Credential-verification scripting (4.2+ versions only) [credentials_settings] verify_script = <string> * Optional setting. * Command line to invoke to verify credentials used for this app. * For scripts, the command line should include both the interpreter and the script for it to run. * Example: "$SPLUNK_HOME/bin/python" "$SPLUNK_HOME/etc/apps/<myapp>/bin/$MY_SCRIPT" * The invoked program is communicated with over standard in / standard out via the same protocol as splunk scripted auth. * Paths incorporating variable expansion or explicit spaces must be quoted. * For example, a path including $SPLUNK_HOME should be quoted, as likely will expand to C:\Program Files\Splunk [credential:<realm>:<username>] password = <string> * Password that corresponds to the given username for the given realm. Note that realm is optional 69

* The password can be in clear text, however when saved from splunkd the password will always be encrypted app.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 The following are example app.conf configurations. Configure properties for your custom application. There is NO DEFAULT app.conf. To use one or more of these configurations, copy the configuration block into props.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles [config:coldindexpath] targetconf=indexes targetstanza=sampledata targetkey=coldpath targetkeydefault=$splunk_db/sampledata/colddb conflabel=cold DB Path for Sample Data Index [config:thawedindexpath] targetconf=indexes targetstanza=sampledata targetkey=thawedpath targetkeydefault=$splunk_db/sampledata/thaweddb conflabel=thawed DB Path for Sample Data Index [config:homeindexpath] targetconf=indexes targetstanza=sampledata targetkey=homepath targetkeydefault=$splunk_db/sampledata/db conflabel=home DB Path for Sample Data Index [launcher] author=<author of app> description=<textual description of app> version=<version of app> audit.conf 다음은 audit.conf의 사양 및 예제 파일입니다. audit.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attributes and values you can use to configure auditing and event signing in audit.conf. There is NO DEFAULT audit.conf. To set custom configurations, place an audit.conf in $SPLUNK_HOME/etc/system/local/. For examples, see audit.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. 70

* Each conf file should have at most one default stanza. If there are multiple default & nbsp; stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. EVENT HASHING: turn on SHA256 event hashing. [eventhashing] * This stanza turns on event hashing -- every event is SHA256 hashed. * The indexer will encrypt all the signatures in a block. * Follow this stanza name with any number of the following attribute/value pairs. filters=mywhitelist,myblacklist... * (Optional) Filter which events are hashed. * Specify filtername values to apply to events. * NOTE: The order of precedence is left to right. Two special filters are provided by default: blacklist_all and whitelist_all, use them to terminate the list of your filters. For example if your list contains only whitelists, then terminating it with blacklist_all will result in signing of only events that match any of the whitelists. The default implicit filter list terminator is whitelist_all. FILTER SPECIFICATIONS FOR EVENT HASHING [filterspec:<event_whitelist event_blacklist>:<filtername>] * This stanza turns on whitelisting or blacklisting for events. & nbsp; * Use filternames in "filters" entry (above). * For example [filterspec:event_whitelist:foofilter]. all=[true false] * The 'all' tag tells the blacklist to stop 'all' events. * Defaults to 'false.' source=[string] host=[string] sourcetype=[string] Optional list of blacklisted/whitelisted sources, hosts or sourcetypes (in order from left to right). * Exact matches only, no wildcarded strings supported. * For example: source=s1,s2,s3... host=h1,h2,h3... sourcetype=st1,st2,st3... KEYS: specify your public and private keys for encryption. [audittrail] * This stanza turns on cryptographic signing for audit trail events (set in inputs.conf) and hashed events (if event hashing is enabled above). privatekey=/some/path/to/your/private/key/private_key.pem publickey=/some/path/to/your/public/key/public_key.pem * You must have a private key to encrypt the signatures and a public key to decrypt them. * Set a path to your own keys * Generate your own keys using openssl in $SPLUNK_HOME/bin/. queueing=[true false] * Turn off sending audit events to the indexqueue -- tail the audit events instead. * If this is set to 'false', you MUST add an inputs.conf stanza to tail the audit log in order to have the events reach your index. * Defaults to true. audit.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 71

This is an example audit.conf. Use this file to configure auditing and event hashing. There is NO DEFAULT audit.conf. To use one or more of these configurations, copy the configuration block into audit.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles [audittrail] privatekey=/some/path/to/your/private/key/private_key.pem publickey=/some/path/to/your/public/key/public_key.pem If this stanza exists, audit trail events will be cryptographically signed. You must have a private key to encrypt the signatures and a public key to decrypt them. Generate your own keys using openssl in $SPLUNK_HOME/bin/. EXAMPLE 1 - hash all events: [eventhashing] This performs a SHA256 hash on every event other than ones going the _audit index (which are handled their own way). NOTE: All you need to enable hashing is the presence of the stanza 'eventhashing'. EXAMPLE 2 - simple blacklisting [filterspec:event_blacklist:myblacklist] host=somehost.splunk.com, 45.2.4.6, 45.3.5.4 [eventhashing] filters=myblacklist Splunk does NOT hash any events from the hosts listed - they are 'blacklisted'. All other events are hashed. EXAMPLE 3 - multiple blacklisting [filterspec:event_blacklist:myblacklist] host=somehost.splunk.com, 46.45.32.1 source=/some/source sourcetype=syslog, apache.error [eventhashing] filters=myblacklist DO NOT hash all events with the following, sources, sourcetypes and hosts - they are all blacklisted. All other events are hashed. EXAMPLE 4 - whitelisting [filterspec:event_whitelist:mywhitelist] sourcetype=syslog source=aa, bb (these can be added as well) host=xx, yy [filterspec:event_blacklist:nothingelse] The 'all' tag is a special boolean (defaults to false) that says match *all* events all=true 72

[eventsigning] filters=mywhitelist, nothingelse Hash ONLY those events which are of sourcetype 'syslog'. All other events are NOT hashed. Note that you can have a list of filters and they are executed from left to right for every event. If an event passed a whitelist, the rest of the filters do not execute. Thus placing the whitelist filter before the 'all' blacklist filter says "only hash those events which match the whitelist". authentication.conf 다음은 authentication.conf의 사양 및 예제 파일입니다. authentication.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attributes and values for configuring authentication via authentication.conf. There is an authentication.conf in $SPLUNK_HOME/etc/system/default/. To set custom configurations, place an authentication.conf in $SPLUNK_HOME/etc/system/local/. For examples, see authentication.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. [authentication] * Follow this stanza name with any number of the following attribute/value pairs. authtype = [Splunk LDAP Scripted] * Specify which authentication system to use. * Supported values: Splunk, LDAP, Scripted. * Defaults to Splunk. authsettings = <authsettings-key>,<authsettings-key>,... * Key to look up the specific configurations of chosen authentication system. & nbsp; * <authsettings-key> is the name of a stanza header that specifies attributes for an LDAP strategy or for scripted authentication. Those stanzas are defined below. * For LDAP, specify the LDAP strategy name(s) here. If you want Splunk to query multiple LDAP servers, enter a comma-separated list of all strategies. Each strategy must be defined in its own stanza. The order in which you specify the strategy names will be the order Splunk uses to query their servers when looking for a user. * For scripted authentication, <authsettings-key> should be a single stanza name. LDAP settings [<authsettings-key>] * Follow this stanza name with the attribute/value pairs listed below. * For multiple strategies, you will need to specify multiple instances of this stanza, each with its own stanza name and a separate set of attributes. * The <authsettings-key> must be one of the values listed in the authsettings attribute, specified above in the [authentication] stanza. host = <string> * REQUIRED * This is the hostname of LDAP server. 73

* Be sure that your Splunk server can resolve the host name. SSLEnabled = [0 1] * OPTIONAL * Defaults to disabled (0) * See the file $SPLUNK_HOME/etc/openldap/openldap.conf for SSL LDAP settings port = <integer> * OPTIONAL * This is the port that Splunk should use to connect to your LDAP server. * Defaults to port 389 for non-ssl and port 636 for SSL binddn = <string> * OPTIONAL but usually required due to LDAP security settings. * Leave this blank if your LDAP entries can be retrieved with anonymous bind * Distinguished name of the user that will be retrieving the LDAP entries * This user must have read access to all LDAP users and groups you wish to use in Splunk. binddnpassword = <string> * OPTIONAL, leave this blank if anonymous bind is sufficient * Password for the binddn user. userbasedn = <string> * REQUIRED * This is the distinguished names of LDAP entries whose subtrees contain the users * Enter a ';' delimited list to search multiple trees. userbasefilter = < string> * OPTIONAL * This is the LDAP search filter you wish to use when searching for users. * Highly recommended, especially when there are many entries in your LDAP user subtrees * When used properly, search filters can significantly speed up LDAP queries * Example that matches users in the IT or HR department: * userbasefilter = ( (department=it)(department=hr)) * See RFC 2254 for more detailed information on search filter syntax * This defaults to no filtering. usernameattribute = <string> * REQUIRED * This is the user entry attribute whose value is the username. * NOTE: This attribute should use case insensitive matching for its values, and the values should not contain whitespace * Users are case insensitive in Splunk * In Active Directory, this is 'samaccountname' * A typical attribute for this is 'uid' realnameattribute = <string> * REQUIRED * This is the user entry attribute whose value is their real name (human readable). * A typical attribute for this is 'cn' groupmappingattribute = <string> * OPTIONAL * This is the user entry attribute whose value is used by group entries to declare membership. * Groups are often mapped with user DN, so this defaults to 'dn' * Set this if groups are mapped using a different attribute * Usually only needed for OpenLDAP servers. * A typical attribute used to map users to groups is 'uid' * For example, assume a group declares that one of its members is 'splunkuser' * This implies that every user with 'uid' value 'splunkuser' will be mapped to that group groupbasedn = [<string>;<string>;...] * REQUIRED * This is the distinguished names of LDAP entries whose subtrees contain the groups. * Enter a ';' delimited list to search multiple trees. * If your LDAP environment does not have group entries, there is a configuration that can treat each user as its own group * Set groupbasedn to the same as userbasedn, which means you will search for groups in the same place as users * Next, set the groupmemberattribute and groupmappingattribute to the same attribute as usernameattribute * This means the entry, when treated as a group, will use the username value as its only member * For clarity, you should probably also set groupnameattribute to the same value as usernameattribute as 74

well groupbasefilter = <string> * OPTIONAL * The LDAP search filter Splunk uses when searching for static groups * Like userbasefilter, this is highly recommended to speed up LDAP queries * See RFC 2254 for more information * This defaults to no filtering dynamicgroupfilter = <string> * OPTIONAL * The LDAP search filter Splunk uses when searching for dynamic groups * Only configure this if you intend to retrieve dynamic groups on your LDAP server * Example: '(objectclass=groupofurls)' dynamicmemberattribute = <string> * OPTIONAL * Only configure this if you intend to retrieve dynamic groups on your LDAP server * This is REQUIRED if you want to retrieve dynamic groups * This attribute contains the LDAP URL needed to retrieve members dynamically * Example: 'memberurl' groupnameattribute = <string> * REQUIRED * This is the group entry attribute whose value stores the group name. * A typical attribute for this is 'cn' (common name) * Recall that if you are configuring LDAP to treat user entries as their own group, user entries must have this attribute groupmemberattribute = <string> * REQUIRED * This is the group entry attribute whose values are the groups members * Typical attributes for this are 'member' and 'memberuid' * For example, consider the groupmappingattribute example above using groupmemberattribute 'member' * To declare 'splunkuser' as a group member, its attribute 'member' must have the value 'splunkuser' nestedgroups = <bool> * OPTIONAL * Controls whether Splunk will expand nested groups using the 'memberof' extension. * Set to 1 if you have nested groups you want to expand and the 'memberof' extension on your LDAP server. charset = <string> & nbsp; * OPTIONAL * ONLY set this for an LDAP setup that returns non-utf-8 encoded data. LDAP is supposed to always return UTF-8 encoded data (See RFC 2251), but some tools incorrectly return other encodings. * Follows the same format as CHARSET in props.conf (see props.conf.spec) * An example value would be "latin-1" anonymous_referrals = <bool> * OPTIONAL * Set this to 0 to turn off referral chasing * Set this to 1 to turn on anonymous referral chasing * IMPORTANT: We only chase referrals using anonymous bind. We do NOT support rebinding using credentials. * If you do not need referral support, we recommend setting this to 0 * If you wish to make referrals work, set this to 1 and ensure your server allows anonymous searching * Defaults to 1 sizelimit = <integer> * OPTIONAL * Limits the amount of entries we request in LDAP search * IMPORTANT: The max entries returned is still subject to the maximum imposed by your LDAP server * Example: If you set this to 5000 and the server limits it to 1000, you'll still only get 1000 entries back * Defaults to 1000 timelimit = <integer> * OPTIONAL * Limits the amount of time in seconds we will wait for an LDAP search request to complete * If your searches finish quickly, you should lower this value from the default * Defaults to 15 network_timeout = <integer> 75

* OPTIONAL * Limits the amount of time a socket will poll a connection without activity * This is useful for determining if your LDAP server cannot be reached * IMPORTANT: As a connection could be waiting for search results, this value must be higher than 'timelimit' * Like 'timelimit', if you have a fast connection to your LDAP server, we recommend lowering this value * Defaults to 20 Map roles [rolemap_<authsettings-key>] * The mapping of Splunk roles to LDAP groups for the LDAP strategy specified by <authsettings-key> * IMPORTANT: this role mapping ONLY applies to the specified strategy. * Follow this stanza name with several Role-to-Group(s) mappings as defined below. <Splunk RoleName> = <LDAP group string> & nbsp;* Maps a Splunk role (from authorize.conf) to LDAP groups * This LDAP group list is semicolon delimited (no spaces). * List several of these attribute value pairs to map several Splunk roles to LDAP Groups Scripted authentication [<authsettings-key>] * Follow this stanza name with the following attribute/value pairs: scriptpath = <string> * REQUIRED * This is the full path to the script, including the path to the program that runs it (python) * For example: "$SPLUNK_HOME/bin/python" "$SPLUNK_HOME/etc/system/bin/$MY_SCRIPT" * Note: If a path contains spaces, it must be quoted. The example above handles the case where $SPLUNK_HOME contains a space scriptsearchfilters = [1 0] * OPTIONAL - Only set this to 1 to call the script to add search filters. * 0 disables (default) [cachetiming] * Use these settings to adjust how long Splunk will use the answers returned from script functions before calling them again. userloginttl = <time range string> * Timeout for the userlogin script function. * These return values are cached on a per-user basis. * The default is '0' (no caching) getuserinfottl = <time range string> * Timeout for the getuserinfo script function. * These return values are cached on a per-user basis. * The default is '10s' getusersttl = <time range string> * Timeout for the getusers script function. * There is only one global getusers cache (it is not tied to a specific user). * The default is '10s' * All timeouts can be expressed in seconds or as a search-like time range * Examples include '30' (30 seconds), '2mins' (2 minutes), '24h' (24 hours), etc. * You can opt to use no caching for a particular function by setting the value to '0' * Be aware that this can severely hinder performance as a result of heavy script invocation * Choosing the correct values for cache timing involves a tradeoff between new information latency and general performance * High values yield better performance from calling the script less, but introduces a latency in picking up changes * Low values will pick up changes in your external auth system more quickly, but may slow down performance due to increased script invocations authentication.conf.example 76

Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This is an example authentication.conf. authentication.conf is used to configure LDAP and Scripted authentication in addition to Splunk's native authentication. To use one of these configurations, copy the configuration block into authentication.conf in $SPLUNK_HOME/etc/system/local/. You must reload auth in manager or restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles Use just Splunk's built-in authentication (default): [authentication] authtype = Splunk LDAP examples Basic LDAP configuration example [authentication] authtype = LDAP authsettings = ldaphost [ldaphost] host = ldaphost.domain. com port = 389 SSLEnabled = 0 binddn = cn=directory Manager binddnpassword = password userbasedn = ou=people,dc=splunk,dc=com userbasefilter = (objectclass=splunkusers) groupbasedn = ou=groups,dc=splunk,dc=com groupbasefilter = (objectclass=splunkgroups) usernameattribute = uid realnameattribute = givenname groupmappingattribute = dn groupmemberattribute = uniquemember groupnameattribute = cn timelimit = 10 network_timeout = 15 This stanza maps roles you have created in authorize.conf to LDAP Groups [rolemap_ldaphost] admin = SplunkAdmins Example using the same server as 'ldaphost', but treating each user as their own group [authentication] authtype = LDAP authsettings = ldaphost_usergroups [ldaphost_usergroups] host = ldaphost.domain.com port = 389 SSLEnabled = 0 binddn = cn=directory Manager binddnpassword = password userbasedn = ou=people,dc=splunk,dc=com userbasefilter = (objectclass=splunkusers) groupbasedn = ou=people,dc=splunk,dc=com groupbasefilter = (objectclass=splunkusers) usernameattribute = uid realnameattribute = givenname groupmappingattribute = uid groupmemberattribute = uid groupnameattribute = uid timelimit = 10 network_timeout = 15 [rolemap_ldaphost_usergroups] admin = admin_user1;admin_user2;admin_user3;admin_user4 power = power_user1;power_user2 77

user = user1;user2;user3 Sample Configuration for Active Directory (AD) [authentication] authsettings = AD authtype = LDAP [AD] SSLEnabled = 1 binddn = ldap_bind@splunksupport.kom binddnpassword = ldap_bind_user_password groupbasedn = CN=Groups,DC=splunksupport,DC=kom groupbasefilter = groupmappingattribute = dn groupmemberattribute = member groupnameattribute = cn host = ADbogus.splunksupport.kom port = 636 realnameattribute = cn userbasedn = CN=Users, DC=splunksupport,DC=kom userbasefilter = usernameattribute = samaccountname timelimit = 15 network_timeout = 20 anonymous_referrals = 0 [rolemap_ad] admin = SplunkAdmins power = SplunkPowerUsers user = SplunkUsers Sample Configuration for Sun LDAP Server [authentication] authsettings = SunLDAP authtype = LDAP [SunLDAP] SSLEnabled = 0 binddn = cn=directory Manager binddnpassword = Directory_Manager_Password groupbasedn = ou=groups,dc=splunksupport,dc=com groupbasefilter = groupmappingattribute = dn groupmemberattribute = uniquemember groupnameattribute = cn host = ldapbogus.splunksupport.com port = 389 realnameattribute = givenname userbasedn = ou=people,dc=splunksupport,dc=com userbasefilter = usernameattribute = uid timelimit = 5 network_timeout = 8 [rolemap_sunldap] admin = SplunkAdmins power = SplunkPowerUsers user = SplunkUsers Sample Configuration for OpenLDAP [authentication] authsettings = OpenLDAP authtype = LDAP [OpenLDAP] binddn = uid=directory_bind,cn=users,dc=osx,dc=company,dc=com binddnpassword = directory_bind_account_password groupbasefilter = groupnameattribute = cn SSLEnabled = 0 port = 389 userbasedn = cn=users,dc=osx,dc=company,dc=com 78

host = hostname_or_ip userbasefilter = usernameattribute = uid groupmappingattribute = uid groupbasedn = dc=osx,dc=company,dc=com groupmemberattribute = memberuid realnameattribute = cn timelimit = 5 network_timeout = 8 dynamicgroupfilter = (objectclass=groupofurls) dynamicmemberattribute = memberurl nestedgroups = 1 [rolemap_openldap] admin = SplunkAdmins power = SplunkPowerUsers user = SplunkUsers Scripted Auth examples The following example is for RADIUS authentication: [authentication] authtype = Scripted authsettings = script [script] scriptpath = "$SPLUNK_HOME/bin/python" "$SPLUNK_HOME/share/splunk/authScriptSamples/radiusScripted.py" Cache results for 1 second per call [cachetiming] userloginttl = 1 getuserinfottl = 1 getusersttl = 1 The following example works with PAM authentication: [authentication] authtype = Scripted authsettings = script [script] scriptpath = "$SPLUNK_HOME/bin/python" "$SPLUNK_HOME/share/splunk/authScriptSamples/pamScripted.py" Cache results for different times per function [cachetiming] userloginttl = 30s getuserinfottl = 1min getusersttl = 5mins authorize.conf 다음은 authorize.conf의 사양 및 예제 파일입니다. authorize.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attribute/value pairs for creating roles in authorize.conf. You can configure roles and granular access controls by creating your own authorize.conf. There is an authorize.conf in $SPLUNK_HOME/etc/system/default/. To set custom configurations, place an authorize.conf in $SPLUNK_HOME/etc/system/local/. For examples, see authorize.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS 79

Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. & nbsp;* Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. [capability::<capability>] * DO NOT edit, remove, or add capability stanzas. The existing capabilities are the full set of Splunk system capabilities. * Splunk adds all of its capabilities this way * For the default list of capabilities and assignments, see authorize.conf under the 'default' directory * Descriptions of specific capabilities are listed below. [role_<rolename>] <capability> = <enabled> * A capability that is enabled for this role. * You can list many of these. * Note that 'enabled' is the only accepted value here, as capabilities are disabled by default. * Roles inherit all capabilities from imported roles, and inherited capabilities cannot be disabled. * Role names cannot have uppercase characters. User names, however, are case-insensitive. importroles = <string> * Semicolon delimited list of other roles and their associated capabilities that should be imported. & nbsp; * Importing other roles also imports the other aspects of that role, such as allowed indexes to search. * By default a role imports no other roles. srchfilter = <string> * Semicolon delimited list of search filters for this Role. * By default we perform no search filtering. * To override any search filters from imported roles, set this to '*', as the 'admin' role does. srchtimewin = <number> * Maximum time span of a search, in seconds. * This time window limit is applied backwards from the latest time specified in a search. * By default, searches are not limited to any specific time window. * To override any search time windows from imported roles, set this to '0' (infinite), as the 'admin' role does. * -1 is a special value that implies no search window has been set for this role * This is equivalent to not setting srchtimewin at all, which means it can be easily overriden by an imported role srchdiskquota = <number> * Maximum amount of disk space (MB) that can be used by search jobs of a user that belongs to this role * Defaults to '100', for 100 MB. srchjobsquota = <number> * Maximum number of concurrently running historical searches a member of this role can have. & nbsp; * This excludes real-time searches, see rtsrchjobsquota. * Defaults to 3. rtsrchjobsquota = <number> * Maximum number of concurrently running real-time searches a member of this role can have. * Defaults to 6. srchmaxtime = <number><unit> * Maximum amount of time that searches of users from this role will be allowed to run. * Once the search has been ran for this amount of time it will be auto finalized, If the role * inherits from other roles, the maximum srchmaxtime value specified in the included roles. * This maximum does not apply to real- time searches. * Examples: 1h, 10m, 2hours, 2h, 2hrs, 100s etc... * Defaults to 100days srchindexesdefault = <string> * Semicolon delimited list of indexes to search when no index is specified * These indexes can be wildcarded, with the exception that '*' does not match internal indexes * To match internal indexes, start with '_'. All internal indexes are represented by '_*' * Defaults to none, but the UI will automatically populate this with 'main' in manager srchindexesallowed = <string> 80

* Semicolon delimited list of indexes this role is allowed to search * Follows the same wildcarding semantics as srchindexesdefault * Defaults to none, but the UI will automatically populate this with '*' in manager Descriptions of Splunk system capabilities [capability::admin_all_objects] * A role with this capability has access to objects in the system (user objects, search jobs, etc.) * This bypasses any ACL restrictions (similar to root access in a *nix environment) * We check this capability when accessing manager pages and objects [capability::change_authentication] * Required to change authentication settings through the various authentication endpoints. * Also controls whether authentication can be reloaded [capability::change_own_password] * Self explanatory. Some auth systems prefer to have passwords be immutable for some users. [capability::delete_by_keyword] * Required to use the 'delete' search operator. Note that this does not actually delete the raw data on disk. * Delete merely masks the data (via the index) from showing up in search results. [capability::edit_deployment_client] * Self explanatory. The deployment client admin endpoint requires this cap for edit. [capability::edit_deployment_server] * Self explanatory. The deployment server admin endpoint requires this cap for edit. [capability::edit_dist_peer] * Required to add and edit peers for distributed search. [capability::edit_ forwarders] * Required to edit settings for forwarding data. * Used by TCP and Syslog output admin handlers * Includes settings for SSL, backoff schemes, etc. [capability::edit_httpauths] * Required to edit and end user sessions through the httpauth-tokens endpoint [capability::edit_input_defaults] * Required to change the default hostname for input data in the server settings endpoint. [capability::edit_monitor] * Required to add inputs and edit settings for monitoring files. * Used by the standard inputs endpoint as well as the one-shot input endpoint. [capability::edit_roles] & nbsp; * Required to edit roles as well as change the mappings from users to roles. * Used by both the users and roles endpoint. [capability::edit_scripted] * Required to create and edit scripted inputs. [capability::edit_search_server] * Required to edit general distributed search settings like timeouts, heartbeats, and blacklists [capability::edit_server] * Required to edit general server settings such as the server name, log levels, etc. [capability::edit_splunktcp] * Required to change settings for receiving TCP input from another Splunk instance. [capability::edit_splunktcp_ssl] * Required to list or edit any SSL specific settings for Splunk TCP input. [capability::edit_tcp] * Required to change settings for receiving general TCP inputs. [capability::edit_udp] * Required to change settings for UDP inputs. [capability::edit_user] 81

* Required to create, edit, or remove users. * Note that Splunk users may edit certain aspects of their information without this capability. * Also required to manage certificates for distributed search. [capability::edit_web_settings] * Required to change the settings for web.conf through the system settings endpoint. [capability::get_metadata] * Required to use the 'metadata' search processor. [capability:: get_typeahead] * Required for typeahead. This includes the typeahead endpoint and the 'typeahead' search processor. [capability::input_file] * Required for inputcsv (except for dispatch=t mode) and inputlookup [capability::indexes_edit] * Required to change any index settings like file size and memory limits. [capability::license_tab] * Required to access and change the license. [capability::list_forwarders] * Required to show settings for forwarding data. * Used by TCP and Syslog output admin handlers. [capability::list_httpauths] * Required to list user sessions through the httpauth-tokens endpoint. [capability::list_inputs] * Required to view the list of various inputs. * This includes input from files, TCP, UDP, Scripts, etc. [capability::output_file] * Required for outputcsv (except for dispatch=t mode) and outputlookup [capability::request_remote_tok] * Required to get a remote authentication token. * Used for distributing search to old 4.0.x Splunk instances. * Also used for some distributed peer management and bundle replication. [capability::rest_apps_management] * Required to edit settings for entries and categories in the python remote apps handler. * See restmap.conf for more information [capability::rest_apps_view] * Required to list various properties in the python remote apps handler. * See restmap.conf for more info [capability::rest_properties_get] * Required to get information from the services/properties endpoint. [capability::rest_properties_set] * Required to edit the services/properties endpoint. [capability::restart_splunkd] * Required to restart Splunk through the server control handler. [capability::rtsearch] * Required to run a realtime search. [capability::run_debug_commands] * Required to run debugging commands like 'summarize' [capability::schedule_search] * Required to schedule saved searches. [capability::search] * Self explanatory - required to run a search. [capability::use_file_operator] * Required to use the 'file' search operator. 82

authorize.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This is an example authorize.conf. Use this file to configure roles and capabilities. To use one or more of these configurations, copy the configuration block into authorize.conf in $SPLUNK_HOME/etc/system/local/. You must reload auth or restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles [role_ninja] rtsearch = enabled importroles = user srchfilter = host=foo srchindexesallowed = * srchindexesdefault = mail;main srchjobsquota = 8 rtsrchjobsquota = 8 srchdiskquota = 500 This creates the role 'ninja', which inherits capabilities from the 'user' role. ninja has almost the same capabilities as power, except cannot schedule searches. The search filter limits ninja to searching on host=foo. ninja is allowed to search all public indexes (those that do not start with underscore), and will search the indexes mail and main if no index is specified in the search. ninja is allowed to run 8 search jobs and 8 real time search jobs concurrently (these counts are independent). ninja is allowed to take up 500 megabytes total on disk for all their jobs. commands.conf 다음은 commands.conf의 사양 및 예제 파일입니다. commands.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attribute/value pairs for creating search commands for any custom search scripts created. Add your custom search script to $SPLUNK_HOME/etc/searchscripts/ or $SPLUNK_HOME/etc/apps/MY_APP/bin/. For the latter, put a custom commands.conf in $SPLUNK_HOME/etc/apps/MY_APP. For the former, put your custom commands.conf in $SPLUNK_HOME/etc/system/local/. There is a commands.conf in $SPLUNK_HOME/etc/system/default/. For examples, see commands.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. & nbsp; * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. [<STANZA_NAME>] * Each stanza represents a search command; the command is the stanza name. * The stanza name invokes the command in the search language. * Set the following attributes/values for the command. Otherwise, Splunk uses the defaults. type = <string> 83

* Type of script: python, perl * Defaults to python. filename = <string> * Name of script file for command. * <script-name>.pl for perl. * <script-name>.py for python. local = [true false] * If true, specifies that the command should be run on the search head only * Defaults to false perf_warn_limit = <integer> * Issue a performance warning message if more than this many input events are passed to this external command (0 = never) & nbsp; * Defaults to 0 (diabled) streaming = [true false] * Specify whether the command is streamable. * Defaults to false. maxinputs = <integer> * Maximum number of events that can be passed to the command for each invocation. * This limit cannot exceed the value of maxresultrows in limits.conf. * 0 for no limit. * Defaults to 50000. passauth = [true false] * If set to true, passes an authentication token on the start of input. * Defaults to false. run_in_preview = [true false] & nbsp; * Specify whether to run this command if generating results just for preview rather than final output. * Defaults to true enableheader = [true false] * Indicate whether or not your script is expecting header information or not. * Currently, the only thing in the header information is an auth token. * If set to true it will expect as input a head section + '\n' then the csv input * NOTE: Should be set to true if you use splunk.intersplunk * Defaults to true. retainsevents = [true false] * Specify whether the command retains events (the way the sort/dedup/cluster commands do) or whether it transforms them (the way the stats command does). * Defaults to false. generating = [true false] * Specify whether your command generates new events. If no events are passed to the command, will it generate events? * Defaults to false. generates_timeorder = [true false] * If generating = true, does command generate events in descending time order (latest first) * Defaults to false. overrides_timeorder = [true false] * If generating = false and streaming=true, does command change the order of events with respect to time? * Defaults to false. requires_preop = [true false] * Specify whether the command sequence specified by the 'streaming_preop' key is required for proper execution or is it an optimization only * Default is false (stremaing_preop not required) streaming_preop = <string> * A string that denotes the requested pre-streaming search string. required_fields = <string> * A comma separated list of fields that this command may use. * Informs previous commands that they should retain/extract these fields if possible. No error is generated if a field specified is missing. 84

& nbsp; * Defaults to '*' supports_multivalues = [true false] * Specify whether the command supports multivalues. * If true, multivalues will be treated as python lists of strings, instead of a flat string (when using Intersplunk to interpret stdin/stdout). * If the list only contains one element, the value of that element will be returned, rather than a list (for example, isinstance(val, basestring) == True). supports_getinfo = [true false] * Specifies whether the command supports dynamic probing for settings (first argument invoked == GETINFO or EXECUTE ). supports_ rawargs = [true false] * Specifies whether the command supports raw arguments being passed to it or if it prefers parsed arguments (where quotes are stripped). * If unspecified, the default is false requires_srinfo = [true false] * Specifies if the command requires information stored in SearchResultsInfo. If true, requires that enableheader be set to true, and the full pathname of the info file (a csv file) will be emitted in the header under the key 'infopath' * If unspecified, the default is false needs_empty_results = [true false] * Specifies whether or not this search command needs to be called with intermediate empty search results * If unspecified, the default is true changes_colorder = [true false] * Specify whether the script output should be used to change the column ordering of the fields. * Default is true outputheader = <true/false> * If set to true, output of script should be a header section + blank line + csv ouput * If false, script output should be pure csv only * Default is false clear_required_fields = [true false] * If true, required_fields repesents the *only* fields required. If false, required_fields are additive to any fields that may be required by subsequent commands. * In most cases, false is appropriate for streaming commands and true for reporting commands * Default is false stderr_dest = [log message none] * What do to with the stderr output from the script * 'log' means to write the output to the job's search.log. * 'message' means to write each line as an search info message. The message level can be set to adding that level (in ALL CAPS) to the start of the line, e.g. "WARN my warning message." * 'none' means to discard the stderr output & nbsp; * Defaults to log commands.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 Configuration for external search commands defaults for all external commands, exceptions are below in individual stanzas type of script: 'python', 'perl' TYPE = python default FILENAME would be <stanza-name>.py for python, <stanza-name>.pl for perl and <stanza-name> otherwise is command streamable? STREAMING = false maximum data that can be passed to command (0 = no limit) 85

MAXINPUTS = 50000 end defaults [crawl] FILENAME = crawl.py [createrss] FILENAME = createrss.py [diff] FILENAME = diff.py [gentimes] FILENAME = gentimes.py [head] FILENAME = head.py [iplocation] FILENAME = iplocation.py [loglady] FILENAME = loglady.py [marklar] FILENAME = marklar.py [runshellscript] FILENAME = runshellscript.py [sendemail] FILENAME = sendemail.py [translate] FILENAME = translate.py [transpose] FILENAME = transpose.py [uniq] FILENAME = uniq.py [windbag] filename = windbag.py supports_multivalues = true [xmlkv] FILENAME = xmlkv.py [xmlunescape] FILENAME = xmlunescape.py crawl.conf 다음은 crawl.conf의 사양 및 예제 파일입니다. crawl.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attribute/value pairs for configuring crawl. There is a crawl.conf in $SPLUNK_HOME/etc/system/default/. To set custom configurations, place a crawl.conf in $SPLUNK_HOME/etc/system/local/. For help, see crawl.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation 86

located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles Set of attribute-values used by crawl. If attribute, ends in _list, the form is: attr = val, val, val, etc. The space after the comma is necessary, so that "," can be used, as in BAD_FILE_PATTERNS's use of "*,v" GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. [default] [files] * Sets file crawler-specific attributes under this stanza header. * Follow this stanza name with any of the following attributes. root = <semi-colon separate list of directories> * Set a list of directories this crawler should search through. * Defaults to /;/Library/Logs bad_directories_list = <comma-separated list of bad directories> * List any directories you don't want to crawl. * Defaults to: bin, sbin, boot, mnt, proc, tmp, temp, dev, initrd, help, driver, drivers, share, bak, old, lib, include, doc, docs, man, html, images, tests, js, dtd, org, com, net, class, java, resource, locale, static, testing, src, sys, icons, css, dist, cache, users, system, resources, examples, gdm, manual, spool, lock, kerberos,.thumbnails, libs, old, manuals, splunk, splunkpreview, mail, resources, documentation, applications, library, network, automount, mount, cores, lost\+found, fonts, extensions, components, printers, caches, findlogs, music, volumes, libexec, bad_extensions_list = <comma-separated list of file extensions to skip> * List any file extensions and crawl will skip files that end in those extensions. * Defaults to: 0t, a, adb, ads, ali, am, asa, asm, asp, au, bak, bas, bat, bmp, c, cache, cc, cg, cgi, class, clp, com, conf, config, cpp, cs, css, csv, cxx, dat, doc, dot, dvi, dylib, ec, elc, eps, exe, f, f77, f90, for, ftn, gif, h, hh, hlp, hpp, hqx, hs, htm, html, hxx, icns, ico, ics, in, inc, jar, java, jin, jpeg, jpg, js, jsp, kml, la, lai, lhs, lib, license, lo, m, m4, mcp, mid, mp3, mpg, msf, nib, nsmap, o, obj, odt, ogg, old, ook, opt, os, os2, pal, pbm, pdf, pdf, pem, pgm, php, php3, php4, pl, plex, plist, plo, plx, pm, png, po, pod, ppd, ppm, ppt, prc, presets, ps, psd, psym, py, pyc, pyd, pyw, rast, rb, rc, rde, rdf, rdr, res, rgb, ro, rsrc, s, sgml, sh, shtml, so, soap, sql, ss, stg, strings, tcl, tdt, template, tif, tiff, tk, uue, v, vhd, wsdl, xbm, xlb, xls, xlw, xml, xsd, xsl, xslt, jame, d, ac, properties, pid, del, lock, md5, rpm, pp, deb, iso, vim, lng, list bad_file_matches_list = <comma-separated list of regex> * Crawl applies the specified regex and skips files that match the patterns. * There is an implied "$" (end of file name) after each pattern. * Defaults to: *~, *, *,v, *readme*, *install, (/ ^).*, *passwd*, *example*, *makefile, core.* packed_extensions_list = <comma-separated list of extensions> & nbsp; * Specify extensions of compressed files to exclude. * Defaults to: bz, bz2, tbz, tbz2, Z, gz, tgz, tar, zip collapse_threshold = <integer> * Specify the minimum number of files a source must have to be considered a directory. * Defaults to 1000. days_sizek_pairs_list = <comma-separated hyphenated pairs of integers> * Specify a comma-separated list of age (days) and size (kb) pairs to constrain what files are crawled. * For example: days_sizek_pairs_list = 7-0, 30-1000 tells Splunk to crawl only files last modified within 7 days and at least 0kb in size, or modified within the last 30 days and at least 1000kb in size. 87

* Defaults to 30-0. big_dir_filecount = <integer> * Skip directories with files above <integer> * Defaults to 10000. index = <$INDEX> * Specify index to add crawled files to. * Defaults to main. max_badfiles_per_dir = <integer> * Specify how far to crawl into a directory for files. * Crawl excludes a directory if it doesn't find valid files within the specified max_badfiles_per_dir. * Defaults to 100. [network] * Sets network crawler-specific attributes under this stanza header. * Follow this stanza name with any of the following attributes. host = <host or ip> * default host to use as a starting point for crawling a network * Defaults to 'localhost'. subnet = <int> * default number of bits to use in the subnet mask. Given a host with IP 123.123.123.123, a subnet value of 32, would scan only that host, and a value or 24 would scan 123.123.123.*. * Defaults to 32. crawl.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 The following are example crawl.conf configurations. Configure properties for crawl. To use one or more of these configurations, copy the configuration block into crawl.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles [files] bad_directories_list= bin, sbin, boot, mnt, proc, tmp, temp, home, mail,.thumbnails, cache, old bad_extensions_list= mp3, mpg, jpeg, jpg, m4, mcp, mid bad_file_matches_list= *example*, *makefile, core.* packed_extensions_list= gz, tgz, tar, zip collapse_threshold= 10 days_sizek_pairs_list= 3-0,7-1000, 30-10000 big_dir_filecount= 100 index=main max_badfiles_per_ dir=100 [network] host = myserver subnet = 24 default.meta.conf 다음은 default.meta.conf의 사양 및 예제 파일입니다. default.meta.conf.spec 88

Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 *.meta files contain ownership information, access controls, and export settings for Splunk objects like saved searches, event types, and views. Each app has its own default.meta file. Interaction of ACLs across app-level, category level, and specific object configuration: * To acess/use an object, users must have read access to: * the app containing the object * the generic category within the app (eg [views]) * the object itself * If any layer does not permit read access, the object will not be accessible. * To update/modify an object, such as to edit a saved search, users must have: * read and write access to the object * read access to the app, to locate the object * read access to the generic category within the app (eg. [savedsearches]) * If object does not permit write access to the user, the object will not be modifiable. * If any layer does not permit read access to the user, the object will not be accessible in order to modify * In order to add or remove objects from an app, users must have: * write access to the app * If users do not have write access to the app, an attempt to add or remove an object will fail. * Objects that are exported to other apps or to system context have no change to their accessability rules. Users must still have read access to the containing app, category, and object, despite the export. Set access controls on the app containing this metadata file. [] access = read : [ * ], write : [ admin, power ] * Allow all users to read this app's contents. Unless overridden by other metadata, allow only admin and power users to share objects into this app. Set access controls on this app's views. [views] access = read : [ * ], write : [ admin ] * Allow all users to read this app's views. Allow only admin users to create, * remove, share, or unshare views in this app. Set access controls on a specific view in this app. [views/index_status] access = read : [ admin ], write : [ admin ] * Allow only admin users to read or modify this view. Make this view available in all apps. export = system * To make this view available only in this app, set 'export = none' instead. owner = admin * Set admin as the owner of this view. default.meta.conf.example No example deploymentclient.conf 다음은 deploymentclient.conf의 사양 및 예제 파일입니다. deploymentclient.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 89

This file contains possible attributes and values for configuring a deployment client to receive content (apps and configurations) from a deployment server. To customize the way a deployment client behaves, place a deploymentclient.conf in $SPLUNK_HOME/etc/system/local/ on that Splunk instance. Configure what apps or configuration content is deployed to a given deployment client in serverclass.conf. Refer to serverclass.conf.spec and serverclass.conf.example for more information. You must restart Splunk for changes to this configuration file to take effect. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles ************************************************************************* ** Configure a Splunk deployment client. Note: At a minimum the [deployment-client] stanza is required in deploymentclient.conf for deployment client to be enabled. *************************************************************************** GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. [ deployment-client] disabled = [false true] * Defaults to false * Enable/Disable deployment client. clientname = deploymentclient * Defaults to deploymentclient. * A name that the deployment server can filter on. * Takes precedence over DNS names. workingdir = $SPLUNK_HOME/var/run/deploy-client * Temporary folder used by the deploymentclient to download apps and configuration content. repositorylocation = $SPLUNK_HOME/etc/apps * The location into which content is installed after being downloaded from a deployment server. * Apps and configuration content must be installed into the default location ($SPLUNK_HOME/etc/apps) or it will not be recognized by the Splunk instance on the deployment client. & nbsp;* Note: Apps and configuration content to be deployed may be located in an alternate location on the deployment server. Set both repositorylocation and serverrepositorylocationpolicy explicitly to ensure that the content is installed into the correct location ($SPLUNK_HOME/etc/apps) on the deployment client. * The deployment client uses the 'serverrepositorylocationpolicy' defined below to determine which value of repositorylocation to use. serverrepositorylocationpolicy = [acceptsplunkhome acceptalways rejectalways] * Defaults to acceptsplunkhome. * acceptsplunkhome - accept the repositorylocation supplied by the deployment server, only if it is rooted by $SPLUNK_HOME. * acceptalways - always accept the repositorylocation supplied by the deployment server. * rejectalways - reject the server supplied value and use the repositorylocation specified in the local deploymentclient.conf. endpoint=$deploymentserveruri$/services/streams/deployment?name=$serverclassname$:$appname$ * The HTTP endpoint from which content should be downloaded. * Note: The deployment server may specify a different endpoint from which to download each set of content (individual apps, etc). * The deployment client will use the serverendpointpolicy defined below to determine which value to use. * $deploymentserveruri$ will resolve to targeturi defined in the [target-broker] stanza below. * $serverclassname$ and $appname$ mean what they say. 90

serverendpointpolicy = [acceptalways rejectalways] * defaults to acceptalways * acceptalways - always accept the endpoint supplied by the server. * rejectalways - reject the endpoint supplied by the server. Always use the 'endpoint' definition above. phonehomeintervalinsecs = <integer in seconds> * Defaults to 60. * This determines how frequently this deployment client should check for new content. handshakeretryintervalinsecs = <integer in seconds> * Defaults to phonehomeintervalinsecs * This sets the handshake retry frequency. * Could be used to tune the initial connection rate on a new server Advanced! You should use this property only when you have a hierarchical deployment server installation, and have a Splunk instance that behaves as both a DeploymentClient and a DeploymentServer. reloaddsonappinstall = [false true] * Defaults to false * Setting this flag to true will cause the deploymentserver on this Splunk instance to be reloaded whenever an app is installed by this deploymentclient. The following stanza specifies deployment server connection information [target-broker:deploymentserver] targeturi= <deploymentserver>:<mgmtport> * URI of the deployment server. phonehomeintervalinsecs = see phonehomeintervalinsecs above deploymentclient.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 Example 1 Deployment client receives apps and places them into the same repositorylocation (locally, relative to $SPLUNK_HOME) as it picked them up from. This is typically $SPLUNK_HOME/etc/apps. There is nothing in [deployment-client] because the deployment client is not overriding the value set on the deployment server side. [deployment-client] [target-broker:deploymentserver] targeturi= deploymentserver.splunk.mycompany.com:8089 Example 2 Deployment server keeps apps to be deployed in a non-standard location on the server side (perhaps for organization purposes). Deployment client receives apps and places them in the standard location. Note: Apps deployed to any location other than $SPLUNK_HOME/etc/apps on the deployment client side will not be recognized and run. This configuration rejects any location specified by the deployment server and replaces it with the standard client-side location. [deployment-client] serverrepositorylocationpolicy = rejectalways repositorylocation = $SPLUNK_HOME/etc/apps [target-broker:deploymentserver] targeturi= deploymentserver.splunk.mycompany.com:8089 Example 3 Deployment client should get apps from an HTTP server that is different from the one specified by 91

the deployment server. [deployment-client] serverendpointpolicy = rejectalways endpoint = http://apache.mycompany.server:8080/$serverclassname$/$appname$.tar [target-broker:deploymentserver] targeturi= deploymentserver.splunk.mycompany.com:8089 Example 4 Deployment client should get apps from a location on the file system and not from a location specified by the deployment server [deployment-client] serverendpointpolicy = rejectalways endpoint = file:/< some_mount_point>/$serverclassname$/$appname$.tar [target-broker:deploymentserver] targeturi= deploymentserver.splunk.mycompany.com:8089 handshakeretryintervalinsecs=20 distsearch.conf 다음은 distsearch.conf의 사양 및 예제 파일입니다. distsearch.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attributes and values you can use to configure distributed search. There is NO DEFAULT distsearch.conf. To set custom configurations, place a distsearch.conf in $SPLUNK_HOME/etc/system/local/. For examples, see distsearch.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles These attributes are all configured on the search head, with the exception of the optional attributes listed under the SEARCH HEAD BUNDLE MOUNTING OPTIONS heading, which are configured on the search peers. GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. [distributedsearch] * Set distributed search configuration options under this stanza name. * Follow this stanza name with any number of the following attribute/value pairs. * If you do not set any attribute, Splunk uses the default value (if there is one listed). disabled = [true false] * Toggle distributed search off (true) and on (false). * Defaults to false (your distributed search stanza is enabled by default). heartbeatmcastaddr = <IP address> * This setting is deprecated heartbeatport = <port> * This setting is deprecated ttl = <integer> 92

* This setting is deprecated heartbeatfrequency = <int, in seconds> * This setting is deprecated statustimeout = <int, in seconds> * Set connection timeout when gathering a search peer's basic info (/services/server/info). * Note: Read/write timeouts are automatically set to twice this value. * Defaults to 10. removedtimedoutservers = [true false] * If true, remove a server connection that cannot be made within servertimeout. * If false, every call to that server attempts to connect. * Note: This may result in a slow user interface. * Defaults to false. checktimedoutserversfrequency = <integer, in seconds> * This attribute is ONLY relevant if removetimedoutservers is set to true. If removetimedoutservers is false, this attribute is ignored. * Rechecks servers at this frequency (in seconds). * If this is set to 0, then no recheck will occur. * Defaults to 60. autoaddservers = [true false] * This setting is deprecated besteffortsearch = [true false] * Whether to remove a peer from search when it does not have any of our bundles. * If set to true searches will never block on bundle replication, even when a peer is first adde - the * peers that don't have any common bundles will simply not be searched. * Defaults to false skipourselves = [true false] * This setting is deprecated servers = <comma separated list of servers> * Initial list of servers. disabled_servers = <comma separated list of servers> * A list of configured but disabled search peers. sharebundles = [true false] * Indicates whether this server will use bundle replication to share search time configuration with search peers. * If set to false, the search head assumes that all the search peers can access the correct bundles via share storage and have configured the options listed under "SEARCH HEAD BUNDLE MOUNTING OPTIONS". * Defaults to true. useshpbundlereplication = <bool> always * Relevant only in search head pooling environments. Whether the search heads in the pool should compete * with each other to decide which one should handle the bundle replication (every time bundle replication * needs to happen) or whether each of them should individually replicate the bundles. * When set to always and bundle mounting is being used then use the search head pool guid rather than * each individual server name to identify bundles (and search heads to the remote peers). * Defaults to true servertimeout = & lt;int, in seconds> * DEPRECATED, please use connectiontimeout, sendtimeout, receivetimeout connectiontimeout = <int, in seconds> * Amount of time in seconds to use as a timeout during search peer connection establishment. sendtimeout = <int, in seconds> * Amount of time in seconds to use as a timeout while trying to write/send data to a search peer. receivetimeout = <int, in seconds> * Amount of time in seconds to use as a timeout while trying to read/receive data from a search peer. ****************************************************************************** DISTRIBUTED SEARCH KEY PAIR GENERATION OPTIONS ****************************************************************************** 93

[tokenexchkeys] certdir = <directory> * This directory contains the local Splunk instance's distributed search key pair. * This directory also contains the public keys of servers that distribute searches to this Splunk instance. publickey = <filename> * Name of public key file for this Splunk instance. privatekey = <filename> * Name of private key file for this Splunk instance. genkeyscript = <command> * Command used to generate the two files above. ****************************************************************************** REPLICATION SETTING OPTIONS ****************************************************************************** [replicationsettings] connectiontimeout = <int, in seconds> * The maximum number of seconds to wait before timing out on inital connection to a peer. sendrcvtimeout = <int, in seconds> * The maximum number of seconds to wait for the sending of a full replication to a peer. replicationthreads = <int> * The maximum number of threads to use when performing bundle replication to peers. * Must be a positive number * Defaults to 5. maxmemorybundlesize = <int> * The maximum size (in MB) of bundles to hold in memory. If the bundle is larger than this * the bundles will be read and encoded on the fly for each peer the replication is taking place. * Defaults to 10 maxbundlesize = <int> * The maximum size (in MB) of the bundle for which replication can occur. If the bundle is larger than this * bundle replication will not occur and an error message will be logged. * Defaults to: 1024 (1GB) concerningreplicatedfilesize = <int> * Any individual file within a bundle that is larger than this value (in MB) will trigger a splunkd.log message. * Where possible, avoid replicating such files, e.g. by customizing your blacklists. * Defaults to: 50 allowstreamupload = <bool> * Whether to enable streaming bundle replication. * Defaults to: false allowskipencoding = <bool> * Whether to avoid URL-encoding bundle data on upload. * Defaults to: true allowdeltaupload = <bool> * Whether to enable delta-based bundle replication. * Defaults to: true sanitizemetafiles = <bool> * Whether to sanitize or filter *.meta files before replication. * This feature can be used to avoid unnecessary replications triggered by writes to *.meta files that have no real effect on search behavior. * The types of stanzas that "survive" filtering are configured via the replicationsettings:refineconf stanza. * The filtering process removes comments and cosmetic whitespace. * Defaults to: true [replicationsettings:refineconf] replicate.<conf_file_name> = <bool> * Controls whether Splunk replicates a particular type of *.conf file, along with any associated permissions in *.meta files. 94

* These settings on their own do not cause files to be replicated. A file must still be whitelisted (via replicationwhitelist) to be eligible for inclusion via these settings. * In a sense, these settings constitute another level of filtering that applies specifically to *.conf files and stanzas with *.meta files. * Defaults to: false ****************************************************************************** REPLICATION WHITELIST OPTIONS ****************************************************************************** [replicationwhitelist] <name> = <whitelist_pattern> * Controls Splunk's search-time conf replication from search heads to search nodes. * Only files that match a whitelist entry will be replicated. * Conversely, files which are not matched by any whitelist will not be replicated. * Only files located under $SPLUNK_HOME/etc will ever be replicated in this way. * The regex will be matched against the filename, relative to $SPLUNK_HOME/etc. Example: for a file "$SPLUNK_HOME/etc/apps/fancy_app/default/inputs.conf" & nbsp; this whitelist should match "apps/fancy_app/default/inputs.conf" * Similarly, the etc/system files are available as system/... user-specific files are available as users/username/appname/... * The 'name' element is generally just descriptive, with one exception: if <name> begins with "refine.", files whitelisted by the given pattern will also go through another level of filtering configured in the replicationsettings:refineconf stanza. * The whitelist_pattern is the Splunk-style pattern matching, which is primarily regex-based with special local behavior for '...' and '*'. *... matches anything, while * matches anything besides directory separators. See props.conf.spec for more detail on these. * Note '.' will match a literal dot, not any character. * Note that these lists are applied globally across all conf data, not to any particular app, regardless of where they are defined. Be careful to pull in only your intended files. ****************************************************************************** REPLICATION BLACKLIST OPTIONS ****************************************************************************** [replicationblacklist] <name> = <blacklist_pattern> * All comments from the replication whitelist notes above also apply here. * Replication blacklist takes precedence over the whitelist, meaning that a file that matches both the whitelist and the blacklist will NOT be replicated. * This can be used to prevent unwanted bundle replication in two common scenarios: * Very large files, which part of an app may not want to be replicated, & nbsp;especially if they are not needed on search nodes. * Frequently updated files (for example, some lookups) will trigger retransmission of all search head data. * Note that these lists are applied globally across all conf data. Especially for blacklisting, be careful to constrain your blacklist to match only data your application will not need. ****************************************************************************** SEARCH HEAD BUNDLE MOUNTING OPTIONS You set these attributes on the search peers only, and only if you also set sharebundles=false in [distributedsearch] on the search head. Use them to achieve replication-less bundle access. The search peers use a shared storage mountpoint to access the search head bundles ($SPLUNK_HOME/etc). ****************************************************************************** [searchhead:<searchhead-splunk- server-name>] * <searchhead-splunk-server-name> is the name of the related searchhead installation. * This setting is located in server.conf, servername = <name> mounted_bundles = [true false] * Determines whether the bundles belong to the search head specified in the stanza name are mounted. * You must set this to "true" to use mounted bundles. * Default is "false". bundles_location = <path_to_bundles> * The path to where the search head's bundles are mounted. This must be the mountpoint on the search peer, 95

* not on the search head. This should point to a directory that is equivalent to $SPLUNK_HOME/etc/. It must * contain at least the following subdirectories: system, apps, users. distsearch.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 These are example configurations for distsearch.conf. Use this file to configure distributed search. For all available attribute/value pairs, see distsearch.conf.spec. There is NO DEFAULT distsearch.conf. To use one or more of these configurations, copy the configuration block into distsearch.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles [distributedsearch] servers = 192.168.1.1:8059,192.168.1.2:8059 This entry distributes searches to 192.168.1.1:8059,192.168.1.2:8059. Attributes not set here will use the defaults listed in distsearch.conf.spec. this stanza controls the timing settings for connecting to a remote peer and the send timeout [replicationsettings] connectiontimeout = 10 sendrcvtimeout = 60 this stanza controls what files are replicated to the other peer each is a regex [replicationwhitelist] allconf = *.conf Mounted bundles example. This example shows two distsearch.conf configurations, one for the search head and another for each of the search head's search peers. It shows only the attributes necessary to implement mounted bundles. On a search head whose Splunk server name is "searcher01": [distributedsearch]... sharebundles = false On each search peer: [searchhead:searcher01] mounted_bundles = true bundles_location = /opt/shared_bundles/searcher01 eventdiscoverer.conf 다음은 eventdiscoverer.conf의 사양 및 예제 파일입니다. eventdiscoverer.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attributes and values you can use to configure event discovery through the search command "typelearner." There is an eventdiscoverer.conf in $SPLUNK_HOME/etc/system/default/. To set custom configurations, place an eventdiscoverer.conf in $SPLUNK_HOME/etc/system/local/. For examples, see eventdiscoverer.conf.example. You must restart Splunk to enable configurations. 96

To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. ignored_keywords = <comma-separated list of terms> * If you find that event types have terms you do not want considered (for example, "mylaptopname"), add that term to this list. * Terms in this list are never considered for defining an event type. * For more details, refer to $SPLUNK_HOME/etc/system/default/eventdiscoverer.conf). * Default = "sun, mon, tue,..." ignored_fields = <comma-separated list of fields> * Similar to ignored_keywords, except these are fields as defined in Splunk instead of terms. * Defaults include time-related fields that would not be useful for defining an event type. important_keywords = <comma-separated list of terms> * When there are multiple possible phrases for generating an eventtype search, those phrases with important_keyword terms are favored. For example, "fatal error" would be preferred over "last message repeated", as "fatal" is an important keyword. * Default = "abort, abstract, accept,..." (see $SPLUNK_HOME/etc/system/default/eventdiscoverer.conf). eventdiscoverer.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This is an example eventdiscoverer.conf. These settings are used to control the discovery of common eventtypes used by the typelearner search command. To use one or more of these configurations, copy the configuration block into eventdiscoverer.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles Terms in this list are never considered for defining an eventtype. ignored_keywords = foo, bar, application, kate, charlie Fields in this list are never considered for defining an eventtype. ignored_fields = pid, others, directory event_renderers.conf 다음은 event_renderers.conf의 사양 및 예제 파일입니다. event_renderers.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attribute/value pairs for configuring event rendering properties. There is an event_renderers.conf in $SPLUNK_HOME/etc/system/default/. To set custom configurations, place an event_renderers.conf in $SPLUNK_HOME/etc/system/local/, or your own custom app directory. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. 97

* You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. [<name>] * Stanza name. This name must be unique. eventtype = <event type> * Specify event type name from eventtypes.conf. priority = <positive integer> * Highest number wins!! template = <valid Mako template> * Any template from the $APP/appserver/event_renderers directory. css_class = <css class name suffix to apply to the parent event element class attribute> * This can be any valid css class value. * The value is appended to a standard suffix string of "splevent-". A css_class value of foo would result in the parent element of the event having an html attribute class with a value of splevent-foo (for example, class="splevent-foo"). You can externalize your css style rules for this in $APP/appserver/static/application.css. For example, to make the text red you would add to application.css:.splevent-foo { color:red; } event_renderers.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 DO NOT EDIT THIS FILE! Please make all changes to files in $SPLUNK_HOME/etc/system/local. To make changes, copy the section/stanza you want to change from $SPLUNK_HOME/etc/system/default into../local and edit there. This file contains mappings between Splunk eventtypes and event renderers. [event_renderer_1] eventtype = hawaiian_type priority = 1 css_class = EventRenderer1 [event_renderer_2] eventtype = french_food_type priority = 1 template = event_renderer2.html css_class = EventRenderer2 [event_renderer_3] eventtype = japan_type priority = 1 css_class = EventRenderer3 eventtypes.conf 다음은 eventtypes.conf의 사양 및 예제 파일입니다. eventtypes.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains all possible attributes and value pairs for an eventtypes.conf file. Use this file to configure event types and their properties. You can also pipe any search to the "typelearner" command to create event types. Event types created this way will be written to $SPLUNK_HOME/etc/systems/local/eventtypes.conf. 98

There is an eventtypes.conf in $SPLUNK_HOME/etc/system/default/. To set custom configurations, place an eventtypes.conf in $SPLUNK_HOME/etc/system/local/. For examples, see eventtypes.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. [<$EVENTTYPE>] * Header for the event type * $EVENTTYPE is the name of your event type. * You can have any number of event types, each represented by a stanza and any number of the following attribute/value pairs. * NOTE: If the name of the event type includes field names surrounded by the percent character (for example "%$FIELD%") then the value of $FIELD is substituted into the event type name for that event. For example, an event type with the header [cisco-%code%] that has "code=432" becomes labeled "cisco-432". disabled = [1 0] * Toggle event type on or off. * Set to 0 to disable. search = <string> * Search terms for this event type. * For example: error OR warn. priority = <integer, 1 through 10> * Value used to determine the order in which the matching eventtypes of an event are displayed. * 1 is the highest and 10 is the lowest priority. description = <string> * Optional human-readable description of this saved search. tags = <string> * DEPRECATED - see tags.conf.spec eventtypes.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains an example eventtypes.conf. Use this file to configure custom eventtypes. To use one or more of these configurations, copy the configuration block into eventtypes.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles The following example makes an eventtype called "error" based on the search "error OR fatal." [error] search = error OR fatal The following example makes an eventtype template because it includes a field name surrounded by the percent character (in this case "%code%"). The value of "%code%" is substituted into the event type name for that event. For example, if the following example event type is instantiated on an event that has a "code=432," it becomes "cisco-432". 99

[cisco-%code%] search = cisco fields.conf 다음은 fields.conf의 사양 및 예제 파일입니다. fields.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attribute and value pairs for: * Telling Splunk how to handle multi-value fields. * Distinguishing indexed and extracted fields. * Improving search performance by telling the search processor how to handle field values. Use this file if you are creating a field at index time (not advised). There is a fields.conf in $SPLUNK_HOME/etc/system/default/. To set custom configurations, place a fields.conf in $SPLUNK_HOME/etc/system/local/. For examples, see fields.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. [<field name>] * Name of the field you're configuring. * Follow this stanza name with any number of the following attribute/value pairs. * Field names can only contain a-z, A-Z, 0-9, and _, but cannot begin with a number or _ TOKENIZER indicates that your configured field's value is a smaller part of a token. For example, your field's value is "123" but it occurs as "foo123" in your event. TOKENIZER = <regular expression> * Use this setting to configure multivalue fields (refer to the online documentation for multivalue fields). * A regular expression that indicates how the field can take on multiple values at the same time. * If empty, the field can only take on a single value. * Otherwise, the first group is taken from each match to form the set of values. * This setting is used by the "search" and "where" commands, the summary and XML outputs of the asynchronous search API, and by the top, timeline and stats commands. * Tokenization of indexed fields (INDEXED = true) is not supported so this attribute is ignored for indexed fields. * Default to empty. INDEXED = [true false] * Indicate whether a field is indexed or not. * Set to true if the field is indexed. * Set to false for fields extracted at search time (the majority of fields). * Defaults to false. INDEXED_VALUE = [true false <sed-cmd> <simple-substitution-string>] * Set this to true if the value is in the raw text of the event. * Set this to false if the value is not in the raw text of the event. * Setting this to true expands any search for key=value into a search of value AND key=value (since value is indexed). * For advanced customization, this setting supports sed style substitution. For example, 'INDEXED_VALUE=s/foo/bar/g' would take the value of the field, replace all instances of 'foo' with 'bar,' and use that new value as the value to search in the index. * This setting also supports a simple subsitution based on looking for the literal string '<VALUE>' (including the '<' and '>' characters). For example, 'INDEXED_VALUE=source::*<VALUE>*' 100

would take a search for 'myfield=myvalue' and search for 'source::* myvalue*' in the index as a single term. * For both substitution constructs, if the resulting string starts with a '[', Splunk interprets the string as a Splunk LISPY expression. For example, 'INDEXED_VALUE=[OR <VALUE> source::*<value>]' would turn 'myfield=myvalue' into applying the LISPY expresion '[OR myvalue source::*myvalue]' (meaning it matches either 'myvalue' or 'source::*myvalue' terms). * Defaults to true. * NOTE: You only need to set indexed_value if indexed = false. fields.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains an example fields.conf. Use this file to configure dynamic field extractions. To use one or more of these configurations, copy the configuration block into fields.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles The following example can be used with the IMAP bundle (found here: http://www.splunkbase.com/addons/all/technologies/mail/addon:imap+addon.) These tokenizers result in the values of To, From and Cc treated as a list, where each list element is an email address found in the raw string of data. [To] TOKENIZER = (\w[\w\.\-]*@[\w\.\-]*\w) [From] TOKENIZER = (\w[\w\.\-]*@[\w\.\-]*\w) [Cc] TOKENIZER = (\w[\w\.\-]*@[\w\.\-]*\w) indexes.conf 다음은 indexes.conf의 사양 및 예제 파일입니다. indexes.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains all possible options for an indexes.conf file. Use this file to configure Splunk's indexes and their properties. There is an indexes.conf in $SPLUNK_HOME/etc/system/default/. To set custom configurations, place an indexes.conf in $SPLUNK_HOME/etc/system/local/. For examples, see indexes.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles CAUTION: You can drastically affect your Splunk installation by changing these settings. Consult technical support (http://www.splunk.com/page/submit_issue) if you are not sure how to configure this file. DO NOT change the attribute QueryLanguageDefinition without consulting technical support. GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the 101

value in the specific stanza takes precedence. sync = <nonnegative integer> * The index processor syncs events every <integer> number of events. * Set to 0 to disable. * Defaults to 0. * Highest legal value is 32767 defaultdatabase = <index name> * If no index is specified during search, Splunk searches the default index. * The specified index displays as the default in Splunk Manager settings. * Defaults to main. querylanguagedefinition = <path to file> * DO NOT EDIT THIS SETTING. SERIOUSLY. * The path to the search language definition file. * Defaults to $SPLUNK_HOME/etc/searchLanguage.xml. blocksignaturedatabase = <index name> & nbsp; * This is the index that stores block signatures of events. * Defaults to _blocksignature. mempoolmb = <positive integer> "auto" * Determines how much memory is given to the indexer memory pool. This restricts the number of outstanding events in the indexer at any given time. * Must be greater than 0 and has a maximum value of 1048576 (which corresponds to 1 TB) * Setting this too high can lead to splunkd memory usage going up substantially. * Setting this too low can degrade splunkd indexing performance. * Setting this to "auto" or an invalid value will cause Splunk to autotune this parameter. * Defaults to "auto". * Only set this value if you are an expert user or are advised by Splunk Support. * CARELESSNESS IN SETTING THIS MAY LEAD TO PERMANENT BRAIN DAMAGE OR LOSS OF JOB. indexthreads = <integer> "auto" * Determines the number of threads to use for indexing. * Must be at least 1 and no more than 16. * This value should not be set higher than the number of processor cores in the box. * If splunkd is also doing parsing and aggregation, the number should be set lower than the total number of processors minus two. * Setting this to "auto" or an invalid value will cause Splunk to autotune this parameter. * Defaults to "auto". * Only set this value if you are an expert user or are advised by Splunk Support. * CARELESSNESS IN SETTING THIS MAY LEAD TO PERMANENT BRAIN DAMAGE OR LOSS OF JOB. assureutf8 = true false * Verifies that all data retreived from the index is proper UTF8. * Will degrade indexing performance when enabled (set to true). * Can only be set globally, by specifying in the [default] stanza. * Defaults to false. enablerealtimesearch = true false * Enables real- time searches. * Defaults to true. suppressbannerlist = <comma-separated list of strings> * suppresses index missing warning banner messages for specified indexes * Defaults to empty maxrunningprocessgroups = <positive integer> * splunkd fires off helper child processes like splunk-optimize, recover-metadata, etc. This param limits how many child processes can be running at any given time. * This maximum applies to entire splunkd, not per index. If you have N indexes, there will be at most maxrunningprocessgroups child processes, not N*maxRunningProcessGroups * Must maintain maxrunningprocessgroupslowpriority < maxrunningprocessgroups & nbsp; * This is an advanced parameter; do NOT set unless instructed by Splunk Support * Defaults to 8 (note: up until 5.0 it defaulted to 20) * Highest legal value is 4294967295 maxrunningprocessgroupslowpriority = <positive integer> * Of the maxrunningprocessgroups (q.v.) helper child processes, at most maxrunningprocessgroupslowpriority may be low-priority (e.g. fsck) ones. * This maximum applies to entire splunkd, not per index. If you have N indexes, there will be at most 102

maxrunningprocessgroupslowpriority low-priority child processes, not N*maxRunningProcessGroupsLowPriority * Must maintain maxrunningprocessgroupslowpriority < maxrunningprocessgroups * This is an advanced parameter; do NOT set unless instructed by Splunk Support * Defaults to 1 * Highest legal value is 4294967295 bucketrebuildmemoryhint = <positive integer>[kb MB GB] "auto" * Suggestion for the bucket rebuild process on the size (bytes) tsidx file to try to make. * Larger files use more memory in rebuild, but rebuild will fail if there is not enough. * Smaller files make the rebuild take longer during the final optimize step. * Note: this value is not a hard limit on either rebuild memory usage or tsidx size. * This is an advanced parameter, do NOT set this unless instructed by Splunk Support. & nbsp; * Defaults to "auto", which varies by the amount of physical RAM on the host * less than 2GB RAM = 67108864 (64MB) tsidx * 2GB to 8GB RAM = 134217728 (128MB) tsidx * more than 8GB RAM = 268435456 (256MB) tsidx * If not "auto", then must be 16MB-1GB. * Value may be specified using a size suffix: "16777216" or "16MB" are equivalent. * Inappropriate use of this parameter will cause splunkd to not start if rebuild is required. * Highest legal value (of the numerical part) is 4294967295 serviceonlyasneeded = true false * Causes index service (housekeeping tasks) overhead to be incurred only after index activity. * Indexer module problems may be easier to diagnose when this optimization is disabled (set to false). * Defaults to true. servicesubtasktimingperiod = <positive integer> * Subtasks of indexer service task will be timed on every Nth execution, where N = value of this parameter. * Smaller values will give greater accuracy; larger values will lessen timer overhead. * Timer measurements will be found in metrics.log, marked "group=subtask_seconds, task=indexer_service" * Defaults to 30 * Highest legal value is 4294967295 maxbucketsizecacheentries = <nonnegative integer> * Controls maximum number of entries in the bucket-size cache; this number is shared across all indexes. * Defaults to 1000000 * Highest legal value is 18446744073709551615 tsidxstatshomepath = <path on server> * An absolute path that specifies where Splunk creates and reads namespace data with 'tscollect' and 'tstats' commands * If the directory does not exist, we attempt to create it * Optional. If this is unspecified, we default to the 'tsidxstats' directory under $SPLUNK_DB ************************************************ ****************************** PER INDEX OPTIONS These options may be set under an [<index>] entry. Index names must consist of only numbers, letters, periods, underscores, and hyphens. ****************************************************************************** disabled = true false * Toggles your index entry off and on. * Set to true to disable an index. * Defaults to false. deleted = true * If present, means that this index has been marked for deletion: if splunkd is running, deletion is in progress; if splunkd is stopped, deletion will re-commence on startup. * Normally absent, hence no default. & nbsp; * Do NOT manually set, clear, or modify value of this parameter. * Seriously: LEAVE THIS PARAMETER ALONE. homepath = <path on index server> * An absolute path that contains the hotdb and warmdb for the index. * Splunkd keeps a file handle open for warmdbs at all times. * May contain a volume reference (see volume section below). * CAUTION: Path MUST be writable. * Required. Splunk will not start if an index lacks a valid homepath. * Must restart splunkd after changing this parameter; index reload will not suffice. coldpath = <path on index server> 103

* An absolute path that contains the colddbs for the index. * Cold databases are opened as needed when searching. * May contain a volume reference (see volume section below). * CAUTION: Path MUST be writable. * Required. Splunk will not start if an index lacks a valid coldpath. * Must restart splunkd after changing this parameter; index reload will not suffice. thawedpath = <path on index server> * An absolute path that contains the thawed (resurrected) databases for the index. * May NOT contain a volume reference. * Required. Splunk will not start if an index lacks a valid thawedpath. * Must restart splunkd after changing this parameter; index reload will not suffice. bloomhomepath = <path on index server> * An absoluate path that contains the bloomfilter files for the index. * If not specified, it defaults to homepath. * May contain a volume reference (see volume section below). * MUST be defined in terms of a volume definition (see volume section below). * CAUTION: Path must be writable. * Must restart splunkd after changing this parameter; index reload will not suffice. createbloomfilter = true false * Control whether to create bloomfilter files for the index. & nbsp; * TRUE: bloomfilter files will be created. FALSE: not created. * Defaults to TRUE. summaryhomepath = <path on index server> * An absolute path where transparent summarization results for data in this index * should be stored. Must be different for each index and may be on any disk drive. * If not specified it defaults to homepath/../summary/ * CAUTION: Path must be writable. * May NOT contain a volume reference. * Must restart splunkd after changing this parameter; index reload will not suffice. maxbloombackfillbucketage = <nonnegative integer>[smhd] "infinite" & nbsp; * If a (warm or cold) bloomfilter-less bucket is older than this, we shall not create its blomfilter when we come across it * Defaults to 30d. * When set to 0, bloomfilters are never backfilled * When set to "infinite", bloomfilters are always backfilled * NB that if createbloomfilter=false, bloomfilters are never backfilled regardless of the value of this parameter * Highest legal value (of the numerical part) is 4294967295 enableonlinebucketrepair = true false * Controls asynchronous "online fsck" bucket repair, which runs concurrently with Splunk * When enabled, you do not have to wait until buckets are repaired, to start Splunk * When enabled, you might observe a slight performance degradation The following options can be set either per index or globally (as defaults for all indexes). Defaults set globally are overridden if set on a per-index basis. maxwarmdbcount = <integer> * The maximum number of warmdb directories. * All warm databasess are in the <homepath> for the index. * warm databases s are kept in open state. * Defaults to 300. * Highest legal value is 4294967295 maxtotaldatasizemb = <integer> * The maximum size of an index (in MB). * If an index grows larger than the maximum size, the oldest data is frozen. * This paremeter only applies to hot, warm, and cold buckets. It does not apply to thawed buckets. * Defaults to 500000. * Highest legal value is 4294967295 rotateperiodinsecs = <integer> * Controls the service period (in seconds): how often splunkd performs certain housekeeping tasks. Among these tasks are: * * Check if a new hotdb needs to be created. * * Check if there are any cold DBs that should be frozen. * & nbsp;* Check whether buckets need to be moved out of hot and cold DBs, due to respective 104

size constraints (i.e., homepath.maxdatasizemb and coldpath.maxdatasizemb) * This value becomes the default value of the rotateperiodinsecs attribute for all volumes (see rotateperiodinsecs in the Volumes section) * Defaults to 60. * Highest legal value is 2147483647 frozentimeperiodinsecs = <integer> * Number of seconds after which indexed data rolls to frozen. * If you do not specify a coldtofrozenscript, data is deleted when rolled to frozen. * IMPORTANT: Every event in the DB must be older than frozentimeperiodinsecs before it will roll. Then, the DB will be frozen the next time splunkd checks (based on rotateperiodinsecs attribute). * Defaults to 188697600 (6 years). * Highest legal value is 2147483647 warmtocoldscript = <script path> * Specifies a script to run when moving data from warm to cold. * This attribute is supported for backwards compatibility with versions older than 4.0. Migrating data across filesystems is now handled natively by splunkd. * If you specify a script here, the script becomes responsible for moving the event data, and Splunk-native data migration will not be used. * The script must accept two arguments: * First: the warm directory (bucket) to be rolled to cold. * Second: the destination in the cold path. * Searches and other activities are paused while the script is running. * Contact Splunk Support (http://www.splunk.com/page/submit_issue) if you need help configuring this setting. * The script must be in $SPLUNK_HOME/bin or a subdirectory thereof. * Defaults to empty. coldtofrozenscript = <path to program that runs script> <path to script> * Specifies the path to the archiving script itself with <path to script> * If your script requires a program to run it (e.g. python), specify that first. Otherwise just specify the script path. * Splunk ships with an example archiving script in $SPLUNK_HOME/bin called coldtofrozenexample.py * Splunk DOES NOT recommend using this example script directly. * It uses a default path, and if modified in place any changes will be overwritten on upgrade. * We recommend copying the example script to a new file in bin and modifying it for your system * Most importantly, change the default archive path to an existing directory that fits your needs. * If your new script in bin/ is named mycoldtofrozen.py, set this key to the following: coldtofrozenscript = "$SPLUNK_HOME/bin/python" "$SPLUNK_HOME/bin/myColdToFrozen.py" * By default, the example script has two possible behaviors when archiving: * For buckets created from version 4.2 and on, it will remove all files except for rawdata * To thaw: cd to the frozen bucket and type "splunk rebuild.", then copy the bucket to thawed for that index * For older-style buckets, we simply gzip all the.tsidx files * To thaw: cd to the frozen bucket and unzip the tsidx files, then copy the bucket to thawed for that index & nbsp; * The script must be in $SPLUNK_HOME/bin or a subdirectory thereof. coldtofrozendir = <path to frozen archive> * An alternative to a coldtofrozen script - simply specify a destination path for the frozen archive * Splunk will automatically put frozen buckets in this directory * Bucket freezing policy is as follows: * New style buckets (4.2 and on): removes all files but the rawdata * To thaw: run 'splunk rebuild <bucket dir>' on the bucket, then move to the thawed directory * Old style buckets (Pre-4.2): gzip all the.data and.tsidx files & nbsp;* To thaw: gunzip the zipped files and move the bucket into the thawed directory * If both coldtofrozendir and coldtofrozenscript are specified, coldtofrozendir will take precedence * Must restart splunkd after changing this parameter; index reload will not suffice. * May NOT contain a volume reference. compressrawdata = true false * This parameter is ignored. The splunkd process always compresses raw data. maxconcurrentoptimizes = <integer> * The number of concurrent optimize processes that can run against the hot DB. * This number should be increased if: * There are always many small tsidx files in the hot DB. * After rolling, there are many tsidx files in warm or cold DB. 105

* Must restart splunkd after changing this parameter; index reload will not suffice. * Highest legal value is 2147483647 maxdatasize = <integer> "auto" "auto_high_volume" * The maximum size in MB for a hot DB to reach before a roll to warm is triggered. * Specifying "auto" or "auto_high_volume" will cause Splunk to autotune this parameter (recommended). * You should use "auto_high_volume" for high volume indexes (such as the main index); otherwise, use "auto". A "high volume index" would typically be considered one that gets over 10GB of data per day. * Defaults to "auto", which sets the size to 750MB. * "auto_high_volume" sets the size to 10GB on 64-bit, and 1GB on 32-bit systems. * Although the maximum value you can set this is 1048576 MB, which corresponds to 1 TB, a reasonable number ranges anywhere from 100 to 50000. Any number outside this range should be approved by Splunk support before proceeding. * If you specify an invalid number or string, maxdatasize will be auto tuned. * NOTE: The precise size of your warm buckets may vary from maxdatasize, due to post-processing and timing issues with the rolling policy. rawfilesizebytes = <positive integer> * Deprecated in version 4.2 and later. We will ignore this value. * Rawdata chunks are no longer stored in individual files. * If you really need to optimize the new rawdata chunks (highly unlikely), edit rawchunksizebytes rawchunksizebytes = <positive integer> * Target uncompressed size in bytes for individual raw slice in the rawdata journal of the index. * Defaults to 131072 (128KB). * 0 is not a valid value. if 0 is specified, rawchunksizebytes will be set to the default value. * NOTE: rawchunksizebytes only specifies a target chunk size. The actual chunk size may be slightly larger by an amount proportional to an individual event size. * WARNING: This is an advanced parameter. Only change it if you are instructed to do so by Splunk Support. * Must restart splunkd after changing this parameter; index reload will not suffice. * Highest legal value is 18446744073709551615 minrawfilesyncsecs = <nonnegative integer> "disable" * How frequently we force a filesystem sync while compressing journal slices. During this interval, uncompressed slices are left on disk even after they are compressed. Then we force a filesystem sync of the compressed journal and remove the accumulated uncompressed files. * If 0 is specified we force a filesystem sync after every slice completes compressing * Specifying "disable" disables syncing entirely: uncompressed slices are removed as soon as compression is complete * Defaults to "disable". * Some filesystems are very inefficient at performing sync operations, so only enable this if you are sure it is needed * Must restart splunkd after changing this parameter; index reload will not suffice. * Highest legal value is 18446744073709551615 maxmemmb = <nonnegative integer> * The amount of memory to allocate for indexing. * This amount of memory will be allocated PER INDEX THREAD, or, if indexthreads is set to 0, once per index. * IMPORTANT: Calculate this number carefully. splunkd will crash if you set this number higher than the amount of memory available. * Defaults to 5. * The default is recommended for all environments. * Highest legal value is 4294967295 blocksignsize = <nonnegative integer> * Controls how many events make up a block for block signatures. * If this is set to 0, block signing is disabled for this index. * Defaults to 0. * A recommended value is 100. * Highest legal value is 2000 maxhotspansecs = <positive integer> * Upper bound of timespan of hot/warm buckets in seconds. * Defaults to 7776000 seconds (90 days). * NOTE: if you set this too small, you can get an explosion of hot/warm buckets in the filesystem. * This parameter cannot be set to less than 3600; if you set it to a lesser & nbsp; value, it will be automatically reset to 3600, which will then activate snapping behavior (see below). * This is an advanced parameter that should be set 106

with care and understanding of the characteristics of your data. * If set to 3600 (1 hour), or 86400 (1 day), becomes also the lower bound of hot bucket timespans. Further, snapping behavior (i.e. ohsnap) is activated, whereby hot bucket boundaries will be set at exactly the hour or day mark, relative to local midnight. * Highest legal value is 4294967295 maxhotidlesecs = <positive integer> * Maximum life, in seconds, of a hot bucket. * If a hot bucket exceeds maxhotidlesecs, Splunk rolls it to warm. * This setting operates independently of maxhotbuckets, which can also cause hot buckets to roll. * A value of 0 turns off the idle check (equivalent to INFINITE idle time). * Defaults to 0. * Highest legal value is 4294967295 maxhotbuckets = <positive integer> * Maximum hot buckets that can exist per index. * When maxhotbuckets is exceeded, Splunk rolls the least recently used (LRU) hot bucket to warm. * Both normal hot buckets and quarantined hot buckets count towards this total. * This setting operates independently of maxhotidlesecs, which can also cause hot buckets to roll. * Defaults to 3. * Highest legal value is 4294967295 quarantinepastsecs = <positive integer> * Events with timestamp of quarantinepastsecs older than "now" will be dropped into quarantine bucket. * Defaults to 77760000 (900 days). * This is a mechanism to prevent the main hot buckets from being polluted with fringe events. * Highest legal value is 4294967295 quarantinefuturesecs = <positive integer> * Events with timestamp of quarantinefuturesecs newer than "now" will be dropped into quarantine bucket. * Defaults to 2592000 (30 days). * This is a mechanism to prevent main hot buckets from being polluted with fringe events. * Highest legal value is 4294967295 maxmetaentries = <nonnegative integer> * Sets the maximum number of unique lines in.data files in a bucket, which may help to reduce memory consumption & nbsp; * If exceeded, a hot bucket is rolled to prevent further increase * If your buckets are rolling due to Strings.data hitting this limit, the culprit may be the 'punct' field in your data. If you do not use punct, it may be best to simply disable this (see props.conf.spec) * There is a delta between when maximum is exceeded and bucket is rolled. This means a bucket may end up with epsilon more lines than specified, but this is not a major concern unless excess is significant * If set to 0, this setting is ignored (it is treated as infinite) * Highest legal value is 4294967295 syncmeta = true false * When "true", a sync operation is called before file descriptor is closed on metadata file updates. * This functionality was introduced to improve integrity of metadata files, especially in regards to operating system crashes/machine failures. * Defaults to true. * NOTE: Do not change this parameter without the input of a Splunk support professional. * Must restart splunkd after changing this parameter; index reload will not suffice. servicemetaperiod = <nonnegative integer> * Defines how frequently metadata is synced to disk, in seconds. & nbsp; * Defaults to 25 (seconds). * You may want to set this to a higher value if the sum of your metadata file sizes is larger than many tens of megabytes, to avoid the hit on I/O in the indexing fast path. * Highest legal value is 4294967295 partialservicemetaperiod = <nonnegative integer> * Related to servicemetaperiod. If set, it enables metadata sync every <integer> seconds, but only for records where the sync can be done efficiently in-place, without requiring a full re-write of the metadata file. Records that require full re-write will be synced at servicemetaperiod. * <integer> specifies how frequently it should sync. Zero means that this 107

feature is turned off and servicemetaperiod is the only time when metadata sync happens. * If the value of partialservicemetaperiod is greater than servicemetaperiod, this setting will have no effect. * By default it is turned off (zero). * This parameter is ignored if serviceonlyasneeded = true (the default). * Highest legal value is 4294967295 throttlecheckperiod = <nonnegative integer> & nbsp;* Defines how frequently Splunk checks for index throttling condition, in seconds. * In seconds; defaults to 15 * NOTE: Do not change this parameter without the input of a Splunk Support professional. * Highest legal value is 4294967295 maxtimeunreplicatedwithacks = <nonnegative number in seconds> * Important if you have enabled acks on forwarders and have replication enabled (via Clustering) * This parameter puts an upper limit on how long events can sit unacked in a raw slice * In seconds; defaults to 60 * To disable this, you can set to 0, but this is NOT recommended!!! * NOTE: this is an advanced parameter, make sure you understand the settings on all your forwarders before changing this. This number should not exceed ack timeout configured on any forwarders, and should actually be set to at most half of the minimum value of that timeout. You can find this setting in outputs.conf readtimeout setting under tcpout stanza. * Highest legal value is 2147483647 maxtimeunreplicatednoacks = <nonnegative number in seconds> * Important only if replication is enabled for this index, otherwise ignored * This parameter puts an upper limit on how long an event can sit in raw slice. * if there are any ack''d events sharing this raw slice, this paramater will not apply (maxtimeunreplicatedwithacks will be used instead) & nbsp; * Highest legal value is 2147483647 * To disable this, you can set to 0; please be careful and understand the consequences before changing this parameter isreadonly = true false * Set to true to make an index read-only. * If true, no new events can be added to the index, but it is still searchable. * Defaults to false. * Must restart splunkd after changing this parameter; index reload will not suffice. homepath.maxdatasizemb = <nonnegative integer> * Limits the size of the hot/warm DB to the maximum specified size, in MB. * If this size is exceeded, Splunk will move buckets with the oldest value of latest time (for a given bucket) into the cold DB until the DB is below the maximum size. * If this attribute is missing or set to 0, Splunk will not constrain size of the hot/warm DB. * Defaults to 0. * Highest legal value is 4294967295 coldpath.maxdatasizemb = <nonnegative integer> * Limits the size of the cold DB to the maximum specifed size, in MB. * If this size is exceeded, Splunk will freeze buckets with the oldest value of latest time (for a given bucket) until the DB is below the maximum size. * If this attribute is missing or set to 0, Splunk will not constrain size of the cold DB. * Defaults to 0. * Highest legal value is 4294967295 disableglobalmetadata = true false * NOTE: This option was introduced in 4.3.3, but as of 5.0 it is obsolete and ignored if set. * It used to disable writing to the global metadata. In 5.0 global metadata was removed. repfactor = <nonnegative integer> "auto" * Only makes sense if this instance is a clustering slave. See server.conf spec for details on clustering configuration. * Value of 0 turns off replication for this index. * The string "auto" indicates using whatever value the master is configured with & nbsp; * Highest legal value is 4294967295 ****************************************************************************** Volume settings. This section describes settings that affect the volume- 108

optional and volume-mandatory parameters only. All volume stanzas begin with "volume:". For example: [volume:volume_name] path = /foo/bar These volume stanzas can then be referenced by individual index parameters, e.g. homepath or coldpath. To refer to a volume stanza, use the "volume:" prefix. For example, to set a cold DB to the example stanza above, in index "hiro", use: [hiro] coldpath = volume:volume_name/baz This will cause the cold DB files to be placed under /foo/bar/baz. If the volume spec is not followed by a path (e.g. "coldpath=volume:volume_name"), then the cold path would be composed by appending the index name to the volume name ("/foo/bar/hiro"). Note: thawedpath may not be defined in terms of a volume. Thawed allocations are manually controlled by Splunk administrators, typically in recovery or archival/review scenarios, and should not trigger changes in space automatically used by normal index activity. ****************************************************************************** path = <path on server> * Required. * Points to the location on the file system where all databases that use this volume will reside. You must make sure that this location does not overlap with that of any other volume or index database. maxvolumedatasizemb = <nonnegative integer> * Optional. * If set, this attribute will limit the total cumulative size of all databases that reside on this volume to the maximum size specified, in MB. Note that this it will act only on those indexes which reference this volume, not on the total size of the path set in the path attribute of this volume. * If the size is exceeded, Splunk will remove buckets with the oldest value of latest time (for a given bucket) across all indexes in the volume, until the volume is below the maximum size. This is the trim operation. Note that this can cause buckets to be chilled [moved to cold] directly from a hot DB, if those buckets happen to have the least value of latest-time (LT) across all indexes in the volume. * Highest legal value is 4294967295 rotateperiodinsecs = <nonnegative integer> * Optional. * Specifies period of trim operation for this volume. * If not set, the value of global rotateperiodinsecs attribute is inherited. * Highest legal value is 4294967295 indexes.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains an example indexes.conf. Use this file to configure indexing properties. To use one or more of these configurations, copy the configuration block into indexes.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles The following example defines a new high-volume index, called "hatch", and sets this to be the default index for both incoming data and search. Note that you may want to adjust the indexes that your roles have access to when creating indexes (in authorize.conf) defaultdatabase = hatch 109

[hatch] homepath = $SPLUNK_DB/ hatchdb/db coldpath = $SPLUNK_DB/hatchdb/colddb thawedpath = $SPLUNK_DB/hatchdb/thaweddb maxdatasize = 10000 maxhotbuckets = 10 The following example changes the default amount of space used on a per-index basis. [default] maxtotaldatasizemb = 650000 The following example changes the time data is kept around by default. It also sets an export script. NOTE: You must edit this script to set export location before running it. [default] maxwarmdbcount = 200 frozentimeperiodinsecs = 432000 rotateperiodinsecs = 30 coldtofrozenscript = "$SPLUNK_HOME/bin/python" "$SPLUNK_HOME/bin/myColdToFrozenScript.py" This example freezes buckets on the same schedule, but lets Splunk do the freezing process as opposed to a script [default] maxwarmdbcount = 200 frozentimeperiodinsecs = 432000 rotateperiodinsecs = 30 coldtofrozendir = "$SPLUNK_HOME/ myfrozenarchive" This example demonstrates the use of volumes volume definitions; prefixed with "volume:" [volume:hot1] path = /mnt/fast_disk maxvolumedatasizemb = 100000 [volume:cold1] path = /mnt/big_disk maxvolumedatasizemb not specified: no data size limitation on top of the existing ones [volume:cold2] path = /mnt/big_disk2 maxvolumedatasizemb = 1000000 index definitions [idx1] homepath = volume:hot1/idx1 coldpath = volume:cold1/idx1 thawedpath must be specified, and cannot use volume: syntax choose a location convenient for reconstitition from archive goals For many sites, this may never be used. thawedpath = $SPLUNK_DB/idx1/thaweddb [idx2] note that the specific indexes must take care to avoid collisions homepath = volume:hot1/idx2 coldpath = volume:cold2/idx2 thawedpath = $SPLUNK_DB/idx2/thaweddb [idx3] homepath = volume:hot1/idx3 coldpath = volume:cold2/idx3 thawedpath = $SPLUNK_DB/idx3/thaweddb 110

Indexes may be allocated space in effective groups by sharing volumes perhaps we only want to keep 100GB of summary data and other low-volume information [volume:small_indexes] path = /mnt/splunk_indexes maxvolumedatasizemb = 100000 and this is our main event series, allowing 50 terabytes [volume:large_indexes] path = /mnt/splunk_indexes maxvolumedatasizemb = 50000000 sumamry and rare_data together will be limited to 100GB [summary] homepath=volume:small_indexes/summary/db coldpath=volume:small_indexes/summary/colddb thawedpath=$splunk_db/summary/thaweddb low-volume indexes probably don't want a lot of hot buckets maxhotbuckets = 2 if the volume is quite low, and you have data sunset goals you may want to have smaller buckets maxdatasize = 500 [rare_data] homepath=volume: small_indexes/rare_data/db coldpath=volume:small_indexes/rare_data/colddb homepath=$splunk_db/rare_data/thaweddb maxhotbuckets = 2 main, and any other large volume indexes you add sharing large_indexes will be together be constrained to 50TB, separately from the 100GB of the small_indexes [main] homepath=volume:large_indexes/main/db coldpath=volume:large_indexes/main/colddb homepath=$splunk_db/main/thaweddb large buckets and more hot buckets are desirable for higher volume indexes, and ones where the variations in the timestream of events is hard to predict. maxdatasize = auto_high_volume maxhotbuckets = 10 This example demonstrates database size constraining In this example per-database constraint is combined with volumes. While a central volume setting makes it easy to manage data size across multiple indexes, there is a concern that bursts of data in one index may significantly displace data from others. The homepath.maxdatasizemb setting can be used to assure that no index will ever take more than certain size, therefore aleviating the concern. global settings will be inherited by all indexes: no database will exceed 1TB homepath.maxdatasizemb = 1000000 volumes [volume:caliente] path = /mnt/fast_disk maxvolumedatasizemb = 100000 [volume:frio] path = /mnt/big_disk maxvolumedatasizemb = 1000000 and this is our main event series, allowing about 50 terabytes [volume:large_indexes] path = /mnt/splunk_indexes 111

maxvolumedatasizemb = 50000000 indexes [i1] homepath = volume:caliente/i1 homepath.maxdatasizemb is inherited coldpath = volume:frio/i1 coldpath.maxdatasizemb not specified: no limit - old-style behavior thawedpath = $SPLUNK_DB/i1/thaweddb [i2] homepath = volume:caliente/i2 overrides the default maxdatasize homepath.maxdatasizemb = 1000 coldpath = volume:frio/i2 limits the cold DB's coldpath.maxdatasizemb = 10000 thawedpath = $SPLUNK_DB/i2/thaweddb [i3] homepath = /old/style/path homepath.maxdatasizemb = 1000 coldpath = volume:frio/i3 coldpath.maxdatasizemb = 10000 thawedpath = $SPLUNK_DB/i3/thaweddb main, and any other large volume indexes you add sharing large_indexes will together be constrained to 50TB, separately from the rest of the indexes [main] homepath=volume:large_indexes/main/db coldpath=volume:large_indexes/main/colddb homepath=$splunk_db/main/thaweddb large buckets and more hot buckets are desirable for higher volume indexes maxdatasize = auto_high_volume maxhotbuckets = 10 inputs.conf 다음은 inputs.conf의 사양 및 예제 파일입니다. inputs.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attributes and values you can use to configure inputs, distributed inputs such as forwarders, and file system monitoring in inputs.conf. There is an inputs.conf in $SPLUNK_HOME/etc/system/default/. To set custom configurations, place an inputs.conf in $SPLUNK_HOME/etc/system/local/. For examples, see inputs.conf.example. You must restart Splunk to enable new configurations. To learn more about configuration files (including precedence), see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. ******* 112

GENERAL SETTINGS: The following attribute/value pairs are valid for all input types (except file system change monitor, which is described in a separate section in this file). You must first enter a stanza header in square brackets, specifying the input type. See further down in this file for examples. Then, use any of the following attribute/value pairs. ******* host = <string> * Sets the host key/field to a static value for this stanza. * Primarily used to control the host field, which will be used for events coming in via this input stanza. * Detail: Sets the host key's initial value. The key is used during parsing/indexing, in particular to set the host field. It is also the host field used at search time. * As a convenience, the chosen string is prepended with 'host::'. * WARNING: Do not quote the <string> value: host=foo, not host="foo". * If set to '$decideonstartup', will be interpreted as hostname of executing machine; such interpretation will occur on each splunkd startup. This is the default. index = <string> * Sets the index to store events from this input. * Primarily used to specify the index to store events coming in via this input stanza. * Detail: Sets the index key's initial value. The key is used when selecting an index to store the events. * Defaults to "main" (or whatever you have set as your default index). source = <string> * Sets the source key/field for events from this input. * NOTE: Overriding the source key is generally not recommended. Typically, the input layer will provide a more accurate string to aid in problem analysis and investigation, accurately recording the file from which the data was retreived. Please consider use of source types, tagging, and search wildcards before overriding this value. * Detail: Sets the source key's initial value. The key is used during parsing/indexing, in particular to set the source field during indexing. It is also the source field used at search time. * As a convenience, the chosen string is prepended with 'source::'. * WARNING: Do not quote the <string> value: source=foo, not source="foo". * Defaults to the input file path. sourcetype = <string> * Sets the sourcetype key/field for events from this input. * Primarily used to explicitly declare the source type for this data, as opposed to allowing it to be determined via automated methods. This is typically important both for searchability and for applying the relevant configuration for this type of data during parsing and indexing. * Detail: Sets the sourcetype key's initial value. The key is used during parsing/indexing, in particular to set the source type field during indexing. It is also the source type field used at search time. * As a convenience, the chosen string is prepended with 'sourcetype::'. * WARNING: Do not quote the <string> value: sourcetype=foo, not sourcetype="foo". * If unset, Splunk picks a source type based on various aspects of the data. There is no hard-coded default. queue = [parsingqueue indexqueue] * Specifies where the input processor should deposit the events it reads. * Set queue to "parsingqueue" to apply props.conf and other parsing rules to your data. For more information about props.conf and rules for timestamping and linebreaking, refer to props.conf and the online documentation at http://docs.splunk.com/documentation. * Set queue to "indexqueue" to send your data directly into the index. * Defaults to parsingqueue. *********** This section contains options for routing data using inputs.conf rather than outputs.conf. Note concerning routing via inputs.conf: This is a simplified set of routing options you can use as data is coming in. For more flexible options or details on configuring required or optional settings, refer to outputs.conf.spec. _TCP_ROUTING = <tcpout_group_name>,<tcpout_group_name>,<tcpout_group_name>,... * Comma-separated list of tcpout group names. * Using this, you can selectively forward the data to specific indexer(s). 113

* Specify the tcpout group the forwarder should use when forwarding the data. The tcpout group names are defined in outputs.conf with [tcpout:<tcpout_group_name>]. * Defaults to groups specified in "defaultgroup" in [tcpout] stanza in outputs.conf. * To forward data from the "_internal" index, _TCP_ROUTING must explicitly be set to either "*" or a specific splunktcp target group. _SYSLOG_ROUTING = <syslog_group_name>,<syslog_group_name>,<syslog_group_name>,... * Comma-separated list of syslog group names. * Using this, you can selectively forward the data to specific destinations as syslog events. * Specify the syslog group to use when forwarding the data. The syslog group names are defined in outputs.conf with [syslog:<syslog_group_name>]. * Defaults to groups present in "defaultgroup" in [syslog] stanza in outputs.conf. * The destination host must be configured in outputs.conf, using "server=[<ip> <servername>]:<port>". ******* Valid input types follow, along with their input-specific attributes: ******* ******* MONITOR: ******* [monitor://<path>] * This directs Splunk to watch all files in <path>. * <path> can be an entire directory or just a single file. * You must specify the input type and then the path, so put three slashes in your path if you're starting at the root (to include the slash that goes before the root directory). Additional attributes: host_regex = <regular expression> * If specified, <regular expression> extracts host from the path to the file for each input file. * Detail: This feature examines the source key, so if source is set explicitly in the stanza, that string will be matched, not the original filename. * Specifically, the first group of the regex is used as the host. * If the regex fails to match, the default "host =" attribute is used. * If host_regex and host_segment are both set, host_regex will be ignored. * Defaults to unset. host_segment = <integer> * If specified, the "/" separated segment of the path is set as host. If host_segment=3, for example, the third segment is used. * If the value is not an integer or is less than 1, the default "host =" attribute is used. * Defaults to unset. whitelist = <regular expression> * If set, files from this path are monitored only if they match the specified regex. * Takes precedence over the deprecated _whitelist attribute, which functions the same way. blacklist = <regular expression> * If set, files from this path are NOT monitored if they match the specified regex. * Takes precedence over the deprecated _blacklist attribute, which functions the same way. Note concerning wildcards and monitor: * You can use wildcards to specify your input path for monitored input. Use "..." for recursive directory matching and "*" for wildcard matching in a single directory segment. * "..." recurses through directories. This means that /foo/.../bar will match foo/bar, foo/1/bar, foo/1/2/bar, etc. * You can use multiple "..." specifications in a single input path. For example: /foo/.../bar/... * The asterisk (*) matches anything in a single path segment; unlike "...", it does not recurse. For example, /foo/*/bar matches the files /foo/bar, /foo/1/bar, /foo/2/bar, etc. However, it does not match /foo/1/2/bar. A second example: /foo/m*r/bar matches /foo/bar, /foo/mr/bar, /foo/mir/bar, /foo/moor/bar, etc. * You can combine "*& quot; and "..." as required: foo/.../bar/* matches any file in the bar directory within the specified path. crcsalt = <string> * Use this setting to force Splunk to consume files that have matching CRCs (cyclic redundancy checks). (Splunk only performs CRC checks against the first few lines of a file. This behavior prevents Splunk from indexing the same file twice, even though you may have renamed it -- as, for example, with rolling log files. However, because the CRC is based on only the first few lines of the file, it is possible for legitimately different files to have 114

matching CRCs, particularly if they have identical headers.) * If set, <string> is added to the CRC. * If set to the literal string <SOURCE> (including the angle brackets), the full directory path to the source file is added to the CRC. This ensures that each file being monitored has a unique CRC. When crcsalt is invoked, it is usually set to <SOURCE>. * Be cautious about using this attribute with rolling log files; it could lead to the log file being re-indexed after it has rolled. * Defaults to empty. initcrclength = <integer> * This setting adjusts how much of a file Splunk reads before trying to identify whether it is a file that has already been seen. You may want to adjust this if you have many files with common headers (comment headers, long CSV headers, etc) and recurring filenames. * CAUTION: Improper use of this setting will cause data to be reindexed. You may wish to consult with Splunk Support before adjusting this value - the default is fine for most installations. * Defaults to 256 (bytes). * Must be in the range 256-1048576. ignoreolderthan = <time window> * Causes the monitored input to stop checking files for updates if their modtime has passed this threshold. This improves the speed of file tracking operations when monitoring directory hierarchies with large numbers of historical files (for example, when active log files are colocated with old files that are no longer being written to). * As a result, do not select a cutoff that could ever occur for a file you wish to index. Take downtime into account! Suggested value: 14d, which means 2 weeks * A file whose modtime falls outside this time window when seen for the first time will not be indexed at all. * Value must be: <number><unit> (e.g., 7d is one week). Valid units are d (days), m (minutes), and s (seconds). * Default: disabled. followtail = [0 1] * WARNING: Use of followtail should be considered an advanced administrative action. * Treat this setting as an 'action'. That is, bring splunk up with this setting enabled. Wait enough time for splunk to identify the related files, then disable the setting and restart splunk without it. * DO NOT leave followtail enabled in an ongoing fashion. * Can be used to force splunk to skip past all current data for a given stanza. * In more detail: this is intended to mean that if you start up splunk with a stanza configured this way, all data in the file at the time it is first encountered will not be read. Only data arriving after that first encounter time will be read. * This can be used to "skip over" data from old log files, or old portions of log files, to get started on current data right away. * If set to 1, monitoring begins at the end of the file (like tail -f). * If set to 0, Splunk will always start at the beginning of the file. * Defaults to 0. alwaysopenfile = [0 1] * Opens a file to check whether it has already been indexed. * Only useful for files that don't update modtime. * Only needed when monitoring files on Windows, mostly for IIS logs. * This flag should only be used as a last resort, as it increases load and slows down indexing. * Defaults to 0. time_before_close = <integer> * Modtime delta required before Splunk can close a file on EOF. * Tells the system not to close files that have been updated in past <integer> seconds. * Defaults to 3. recursive = [true false] * If false, Splunk will not monitor subdirectories found within a monitored directory. * Defaults to true. followsymlink = [true false] * If false, Splunk will ignore symbolic links found within a monitored directory. * Defaults to true. _whitelist =... * This setting is deprecated. It is still honored, unless "whitelist& quot; attribute also exists. _blacklist =... * This setting is deprecated. It is still honored, unless "blacklist" attribute also exists. 115

dedicatedfd =... * This setting has been removed. It is no longer needed. **************************************** BATCH ("Upload a file" in Splunk Web): **************************************** NOTE: Batch should only be used for large archives of historic data. If you want to continuously monitor a directory or index small archives, use monitor (see above). Batch reads in the file and indexes it, and then deletes the file from the Splunk instance. [batch://<path>] * One time, destructive input of files in <path>. * For continuous, non-destructive inputs of files, use monitor instead. Additional attributes: move_policy = sinkhole * IMPORTANT: This attribute/value pair is required. You *must* include "move_policy = sinkhole" when defining batch inputs. * This loads the file destructively. * Do not use the batch input type for files you do not want to consume destructively. * As long as this is set, Splunk won't keep track of indexed files. Without the "move_policy = sinkhole" setting, it won't load the files destructively and will keep a track of them. host_regex = see MONITOR, above. host_segment = see MONITOR, above. crcsalt = see MONITOR, above. IMPORTANT: The following attribute is not used by batch: source = <string> followsymlink = [true false] * Works similarly to monitor, but will not delete files after following a symlink out of the monitored directory. The following settings work identically as for [monitor::] stanzas, documented above host_regex = <regular expression> host_segment = <integer> crcsalt = <string> recursive = [true false] whitelist = <regular expression> blacklist = <regular expression> initcrclength = <integer> ******* TCP: ******* [tcp://<remote server>:<port>] * Configure Splunk to listen on a specific port. * If a connection is made from <remote server>, this stanza is used to configure the input. * If <remote server> is empty, this stanza matches all connections on the specified port. * Will generate events with source set to tcp:portnumber, for example: tcp:514 * If sourcetype is unspecified, will generate events with set sourcetype to tcp-raw. Additional attributes: connection_host = [ip dns none] * "ip" sets the host to the IP address of the system sending the data. * "dns" sets the host to the reverse DNS entry for IP address of the system sending the data. * "none" leaves the host as specified in inputs.conf, typically the splunk system hostname. * Defaults to "dns". queuesize = <integer>[kb MB GB] * Maximum size of the in-memory input queue. * Defaults to 500KB. persistentqueuesize = <integer>[kb MB GB TB] * Maximum size of the persistent queue file. * Defaults to 0 (no persistent queue). 116

* If set to some value other than 0, persistentqueuesize must be larger than the in-memory queue size (set by queuesize attribute in inputs.conf or maxsize settings in [queue] stanzas in server.conf). * Persistent queues can help prevent loss of transient data. For information on persistent queues and how the queuesize and persistentqueuesize settings interact, see the online documentation. requireheader = <bool> * Require a header be present at the beginning of every stream. * This header may be used to override indexing settings. * Defaults to false. listenonipv6 = <no yes only> * Toggle whether this listening port will listen on IPv4, IPv6, or both * If not present, the setting in the [general] stanza of server.conf will be used acceptfrom = <network_acl>... * Lists a set of networks or addresses to accept connections from. These rules are separated by commas or spaces * Each rule can be in the following forms: * 1. A single IPv4 or IPv6 address (examples: "10.1.2.3", "fe80::4a3") * 2. A CIDR block of addresses (examples: "10/8", "fe80:1234/32") * 3. A DNS name, possibly with a '*' used as a wildcard (examples: "myhost.example.com", "*.splunk.com") * 4. A single '*' which matches anything * Entries can also be prefixed with '!' to cause the rule to reject the connection. Rules are applied in order, and the first one to match is used. For example, "!10.1/16, *" will allow connections from everywhere except the 10.1.*.* network. * Defaults to "*" (accept from anywhere) rawtcpdonetimeout = <seconds> * Specifies timeout value for sending Done-key. * If a connection over this port remains idle after receiving data for specified seconds, it adds a Done-key, implying the last event has been completely received. * Defaults to 10 second. ******* Data distribution: ******* Global settings for splunktcp. Used on the receiving side for data forwarded from a forwarder. [splunktcp] route = [has_key absent_key:<key>:<queuename>;...] * Settings for the light forwarder. * Splunk sets these parameters automatically -- you DO NOT need to set them. * The property route is composed of rules delimited by ';'. * Splunk checks each incoming data payload via cooked tcp port against the route rules. * If a matching rule is found, Splunk sends the payload to the specified <queuename>. * If no matching rule is found, Splunk sends the payload to the default queue specified by any queue= for this stanza. If no queue= key is set in the stanza or globally, the events will be sent to the parsingqueue. compressed = [true false] * Specifies whether receiving compressed data. * If set to true, the forwarder port(s) should also have compression turned on; otherwise, the receiver will reject the connection. * Defaults to false. enables2sheartbeat = [true false] * This specifies the global keepalive setting for all splunktcp ports. * This option is used to detect forwarders which may have become unavailable due to network, firewall, etc., problems. * Splunk will monitor each connection for presence of heartbeat, and if the heartbeat is not seen for s2sheartbeattimeout seconds, it will close the connection. * Defaults to true (heartbeat monitoring enabled). s2sheartbeattimeout = <seconds> * This specifies the global timeout value for monitoring heartbeats. * Splunk will will close a forwarder connection if heartbeat is not seen for s2sheartbeattimeout seconds. * Defaults to 600 seconds (10 minutes). inputshutdowntimeout = <seconds> * Used during shutdown to minimize data loss when forwarders are connected to a receiver. During shutdown, the tcp input processor waits for the specified number of seconds and then 117

closes any remaining open connections. If, however, all connections close before the end of the timeout period, shutdown proceeds immediately, without waiting for the timeout. listenonipv6 = <no yes only> * Toggle whether this listening port will listen on IPv4, IPv6, or both * If not present, the setting in the [general] stanza of server.conf will be used acceptfrom = <network_acl>... * Lists a set of networks or addresses to accept connections from. These rules are separated by commas or spaces * Each rule can be in the following forms: * 1. A single IPv4 or IPv6 address (examples: "10.1.2.3", "fe80::4a3") * 2. A CIDR block of addresses (examples: "10/8", "fe80:1234/32") * 3. A DNS name, possibly with a '*' used as a wildcard (examples: "myhost.example.com", "*.splunk.com") * 4. A single '*' which matches anything * Entries can also be prefixed with '!' to cause the rule to reject the connection. Rules are applied in order, and the first one to match is used. For example, "!10.1/16, *" will allow connections from everywhere except the 10.1.*.* network. * Defaults to "*" (accept from anywhere) Forwarder-specific settings for splunktcp. [splunktcp://[< remote server>]:<port>] * This input stanza is used with Splunk instances receiving data from forwarders ("receivers"). See the topic http://docs.splunk.com/documentation/splunk/latest/deploy/aboutforwardingandreceivingdata for more information. * This is the same as TCP, except the remote server is assumed to be a Splunk instance, most likely a forwarder. * <remote server> is optional. If specified, will only listen for data from <remote server>. connection_host = [ip dns none] * For splunktcp, the host or connection_host will be used if the remote Splunk instance does not set a host, or if the host is set to "<host>::<localhost>". * "ip" sets the host to the IP address of the system sending the data. * "dns" sets the host to the reverse DNS entry for IP address of the system sending the data. * "none" leaves the host as specified in inputs.conf, typically the splunk system hostname. * Defaults to "ip". enables2sheartbeat = [true false] * This specifies the keepalive setting for the splunktcp port. * This option is used to detect forwarders which may have become unavailable due to network, firewall, etc., problems. * Splunk will monitor the connection for presence of heartbeat, and if the heartbeat is not seen for s2sheartbeattimeout seconds, it will close the connection. * This overrides the default value specified at the global [splunktcp] stanza. * Defaults to true (heartbeat monitoring enabled). s2sheartbeattimeout = <seconds> * This specifies the timeout value for monitoring heartbeats. * Splunk will will close the forwarder connection if heartbeat is not seen for s2sheartbeattimeout seconds. * This overrides the default value specified at global [splunktcp] stanza. * Defaults to 600 seconds (10 minutes). queuesize = <integer>[kb MB GB] * Maximum size of the in-memory input queue. * Defaults to 500KB. SSL settings for data distribution: [splunktcp-ssl:<port>] * Use this stanza type if you are receiving encrypted, parsed data from a forwarder. * Set <port> to the port on which the forwarder is sending the encrypted data. * Forwarder settings are set in outputs.conf on the forwarder. connection_host = [ip dns none] * For SplunkTCP, the host or connection_host will be used if the remote Splunk instance does not set a host, or if the host is set to "<host>::<localhost>". * "ip" sets the host to the IP address of the system sending the data. * "dns" sets the host to the reverse DNS entry for IP address of the system sending the data. * "none" leaves the host as specified in inputs.conf, typically the splunk system hostname. * Defaults to "ip". enables2sheartbeat = true false * See comments for [splunktcp:<port>]. 118

s2sheartbeattimeout = <seconds> * See comments for [splunktcp:<port>]. compressed = [true false] * Specifies whether receiving compressed data. * If set to true, the forwarder port must also have compression turned on. * Defaults to false. listenonipv6 = <no yes only> * Toggle whether this listening port will listen on IPv4, IPv6, or both * If not present, the setting in the [general] stanza of server.conf will be used acceptfrom = <network_acl>... * Lists a set of networks or addresses to accept connections from. These rules are separated by commas or spaces * Each rule can be in the following forms: * 1. A single IPv4 or IPv6 address (examples: "10.1.2.3", "fe80::4a3") * 2. A CIDR block of addresses (examples: "10/8", "fe80:1234/32") * 3. A DNS name, possibly with a '*' used as a wildcard (examples: "myhost.example.com", "*.splunk.com") * 4. A single '*' which matches anything * Entries can also be prefixed with '!' to cause the rule to reject the connection. Rules are applied in order, and the first one to match is used. For example, "!10.1/16, *" will allow connections from everywhere except the 10.1.*.* network. * Defaults to "*" (accept from anywhere) [tcp-ssl:<port>] * Use this stanza type if you are receiving encrypted, unparsed data from a forwarder or third-party system. * Set <port> to the port on which the forwarder/third-party system is sending unparsed, encrypted data. listenonipv6 = <no yes only> * Toggle whether this listening port will listen on IPv4, IPv6, or both * If not present, the setting in the [general] stanza of server.conf will be used acceptfrom = <network_acl>... * Lists a set of networks or addresses to accept connections from. These rules are separated by commas or spaces * Each rule can be in the following forms: * 1. A single IPv4 or IPv6 address (examples: "10.1.2.3", "fe80::4a3") * 2. A CIDR block of addresses (examples: "10/8", "fe80:1234/32") * 3. A DNS name, possibly with a '*' used as a wildcard (examples: "myhost.example.com", "*.splunk.com") * 4. A single '*' which matches anything * Entries can also be prefixed with '!' to cause the rule to reject the connection. Rules are applied in order, and the first one to match is used. For example, "!10.1/16, *" will allow connections from everywhere except the 10.1.*.* network. * Defaults to "*" (accept from anywhere) [SSL] * Set the following specifications for SSL underneath this stanza name: servercert = <path> * Full path to the server certificate. password = <string> * Server certificate password, if any. rootca = <string> * Certificate authority list (root file). requireclientcert = [true false] * Determines whether a client must authenticate. * Defaults to false. supportsslv3only = [true false] * If true, tells the inputproc to accept connections only from SSLv3 clients. * Defaults to false. ciphersuite = <cipher suite string> * If set, uses the specified cipher string for the input processors. * If not set, the default cipher string is used. * Provided by OpenSSL. This is used to ensure that the server does not accept connections using weak encryption protocols. 119

******* UDP: ******* [udp://<remote server>:& lt;port>] * Similar to TCP, except that it listens on a UDP port. * Only one stanza per port number is currently supported. * Configure Splunk to listen on a specific port. * If <remote server> is specified, the specified port will only accept data from that server. * If <remote server> is empty - [udp://<port>] - the port will accept data sent from any server. * Will generate events with source set to udp:portnumber, for example: udp:514 * If sourcetype is unspecified, will generate events with set sourcetype to udp:portnumber. Additional attributes: connection_host = [ip dns none] * "ip" sets the host to the IP address of the system sending the data. * "dns" sets the host to the reverse DNS entry for IP address of the system sending the data. * "none" leaves the host as specified in inputs.conf, typically the splunk system hostname. * Defaults to "ip". _rcvbuf = < integer> * Specifies the receive buffer for the UDP port (in bytes). * If the value is 0 or negative, it is ignored. * Defaults to 1,572,864. * Note: If the default value is too large for an OS, Splunk will try to set the value to 1572864/2. If that value also fails, Splunk will retry with 1572864/(2*2). It will continue to retry by halving the value until it succeeds. no_priority_stripping = [true false] * Setting for receiving syslog data. * If this attribute is set to true, Splunk does NOT strip the <priority> syslog field from received events. * NOTE: Do NOT include this attribute if you want to strip <priority>. * Default is false. no_appending_timestamp = [true false] * If this attribute is set to true, Splunk does NOT append a timestamp and host to received events. * NOTE: Do NOT include this attribute if you want to append timestamp and host to received events. * Default is false. queuesize = <integer>[kb MB GB] * Maximum size of the in-memory input queue. * Defaults to 500KB. persistentqueuesize = <integer>[kb MB GB TB] * Maximum size of the persistent queue file. * Defaults to 0 (no persistent queue). * If set to some value other than 0, persistentqueuesize must be larger than the in-memory queue size (set by queuesize attribute in inputs.conf or maxsize settings in [queue] stanzas in server.conf). * Persistent queues can help prevent loss of transient data. For information on persistent queues and how the queuesize and persistentqueuesize settings interact, see the online documentation. listenonipv6 = <no yes only> * Toggle whether this port will listen on IPv4, IPv6, or both * If not present, the setting in the [general] stanza of server.conf will be used acceptfrom = <network_acl>... * Lists a set of networks or addresses to accept data from. These rules are separated by commas or spaces * Each rule can be in the following forms: * 1. A single IPv4 or IPv6 address (examples: "10.1.2.3", "fe80::4a3") * 2. A CIDR block of addresses (examples: "10/8", "fe80:1234/32") * 3. A DNS name, possibly with a '*' used as a wildcard (examples: "myhost.example.com", "*.splunk.com") * 4. A single '*' which matches anything * Entries can also be prefixed with '!' to cause the rule to reject the connection. Rules are applied in order, and the first one to match is used. For example, "!10.1/16, *" will allow connections from everywhere except the 10.1.*.* network. * Defaults to "*" (accept from anywhere) ******* FIFO: 120

******* [fifo://<path>] * This directs Splunk to read from a FIFO at the specified path. queuesize = <integer>[kb MB GB] * Maximum size of the in-memory input queue. * Defaults to 500KB. persistentqueuesize = <integer>[kb MB GB TB] * Maximum size of the persistent queue file. * Defaults to 0 (no persistent queue). * If set to some value other than 0, persistentqueuesize must be larger than the in-memory queue size (set by queuesize attribute in inputs.conf or maxsize settings in [queue] stanzas in server.conf). * Persistent queues can help prevent loss of transient data. For information on persistent queues and how the queuesize and persistentqueuesize settings interact, see the online documentation. ******* Scripted Input: ******* [script://<cmd>] * Runs <cmd> at a configured interval (see below) and indexes the output. * The <cmd> must reside in one of * $SPLUNK_HOME/etc/system/bin/ * $SPLUNK_HOME/etc/ apps/$your_app/bin/ * $SPLUNK_HOME/bin/scripts/ * Script path can be an absolute path, make use of an environment variable such as $SPLUNK_HOME, or use the special pattern of an initial '.' as the first directory to indicate a location inside the current app. Note that the '.' must be followed by a platform-specific directory separator. * For example, on UNIX: [script://./bin/my_script.sh] Or on Windows: [script://.\bin\my_program.exe] This '.' pattern is strongly recommended for app developers, and necessary for operation in search head pooling environments. * Splunk on Windows ships with several Windows-only scripted inputs. Check towards the end of the inputs.conf.example for examples of the stanzas for specific Windows scripted inputs that you must add to your local inputs.conf file. * <cmd> can also be a path to a file that ends with a ".path" suffix. A file with this suffix is a special type of pointer file that points to a command to be executed. Although the pointer file is bound by the same location restrictions mentioned above, the command referenced inside it can reside anywhere on the file system. This file must contain exactly one line: the path to the command to execute, optionally followed by command line arguments. Additional empty lines and lines that begin with '' are also permitted and will be ignored. interval = [<number> <cron schedule>] * How often to execute the specified command (in seconds), or a valid cron schedule. * NOTE: when a cron schedule is specified, the script is not executed on start-up. * If specified as a number, may have a fractional component; e.g., 3.14 * Defaults to 60.0 seconds. passauth = <username> * User to run the script as. * If you provide a username, Splunk generates an auth token for that user and passes it to the script via stdin. queuesize = <integer>[kb MB GB] * Maximum size of the in-memory input queue. * Defaults to 500KB. persistentqueuesize = <integer>[kb MB GB TB] * Maximum size of the persistent queue file. * Defaults to 0 (no persistent queue). * If set to some value other than 0, persistentqueuesize must be larger than the in-memory queue size (set by queuesize attribute in inputs.conf or maxsize settings in [queue] stanzas in server.conf). * Persistent queues can help prevent loss of transient data. For information on persistent queues and how the queuesize and persistentqueuesize settings interact, see the online documentation. ******* 121

File system change monitor (fschange monitor) ******* NOTE: You cannot simultaneously watch a directory using both fschange monitor and monitor (described above). [fschange:<path>] * Monitors all add/update/deletes to this directory and its subdirectories. * NOTE: <path> is the direct path. You do not need to preface it with // like other inputs. * Sends an event for every change. Additional attributes: NOTE: fschange does not use the same attributes as other input types (described above). Use only the following attributes: index = <indexname> * The index in which to store all generated events. * Defaults to _audit, unless you do not set signedaudit (below) or set signedaudit = false, in which case events go into the default index. signedaudit = [true false] * Send cryptographically signed add/update/delete events. * If set to true, events are *always* sent to the _audit index and will *always* have the source type "audittrail". * If set to false, events are placed in the default index and the source type is whatever you specify (or "fs_notification" by default). * You must set signedaudit to false if you want to set the index. * NOTE: You must also enable auditing in audit.conf. * Defaults to false. filters = <filter1>,<filter2>,... * Each filter is applied left to right for each file or directory found during the monitor's poll cycle. * See "File System Monitoring Filters" below for help defining a filter. recurse = [true false] * If true, recurse directories within the directory specified in [fschange]. * Defaults to true. followlinks = [true false] * If true, follow symbolic links. * It is recommended that you do not set this to true; file system loops can occur. * Defaults to false. pollperiod = <integer> * Check this directory for changes every <integer> seconds. * Defaults to 3600 seconds (1 hour). hashmaxsize = <integer> * Calculate a SHA256 hash for every file that is less than or equal to <integer> bytes. * This hash is used as an additional method for detecting changes to the file/directory. * Defaults to -1 (disabled). fullevent = [true false] * Set to true to send the full event if an add or update change is detected. * Further qualified by the sendeventmaxsize attribute. * Defaults to false. sendeventmaxsize = <integer> * Only send the full event if the size of the event is less than or equal to <integer> bytes. * This limits the size of indexed file data. * Defaults to -1, which is unlimited. sourcetype = <string> * Set the source type for events from this input. * "sourcetype=" is automatically prepended to <string>. * Defaults to audittrail (if signedaudit=true) or fs_ notification (if signedaudit=false). host = <string> * Set the host for events from this input. * Defaults to whatever host sent the event. filesperdelay = <integer> * Injects a delay specified by delayinmills after processing <integer> files. * This is used to throttle file system monitoring so it doesn't consume as much CPU. 122

* Defaults to 10. delayinmills = <integer> * The delay in milliseconds to use after processing every <integer> files, as specified in filesperdelay. * This is used to throttle file system monitoring so it doesn't consume as much CPU. * Defaults to 100. ******* File system monitoring filters: ******* [filter:<filtertype>:<filtername>] * Define a filter of type <filtertype> and name it <filtername>. * <filtertype>: * Filter types are either 'blacklist' or 'whitelist.' * A whitelist filter processes all file names that match the regex list. * A blacklist filter skips all file names that match the regex list. * <filtername> * The filter name is used in the comma-separated list when defining a file system monitor. regex<integer> = <regex> * Blacklist and whitelist filters can include a set of regexes. * The name of each regex MUST be 'regex<integer>', where <integer> starts at 1 and increments. * Splunk applies each regex in numeric order: regex1=<regex> regex2=<regex>... ******* WINDOWS INPUTS: ******* * Windows platform specific input processor. * The Security, Application, and System event log inputs are enabled by default. To disable an input type, comment it out or set disabled = 1 in $SPLUNK_HOME\etc\ apps\windows\local\inputs.conf * You can configure Splunk to read other Windows event logs as well, but you must first import them to the Windows Event Viewer, and then add them to your local copy of inputs.conf (in $SPLUNK_HOME\etc\apps\windows\local\inputs.conf). Use the same format as the examples shown below and add the attribute/value pair "disabled = 0". [WinEventLog:<Log Name>] * Define a Windows Event Log to monitor. disabled = [1 0] * Enable (0) or disable (1) this input. start_from = <string> [oldest newest] * oldest - Start reading Windows Event Log chronologically from oldest to newest. * newest - Start reading Windows Event Log in reverse, from newest to oldest. Once the backlog of events is consumed, Splunk will start picking up the newest events. * 'newest' is not supported in combination with current_only = 1 (This combination does not make much sense.) * Defaults to oldest. current_only = [1 0] * If set to 1, the input will only acquire events that arrive after the input is turned on for the first time, like unix 'tail -f'. * current_only = 1 is not supported with start_from = 'newest'. (It would not really make sense.) * If set to 0, the input will first get all existing events in the log and then continue to monitor events coming in real time. * Defaults to 0 (false), gathering stored events first before monitoring live events. checkpointinterval = <seconds> * Sets how frequently the Windows Event Log input will save a checkpoint, storing the eventid of the acquired events, which allows splunk to continue monitoring at the correct event after shutdown or outage. * The default value is 5. 123

evt_resolve_ad_obj = [1 0] * Enables (1)/disables (0) the resolution of Active Directory objects like Globally Unique IDentifier (GUID) and Security IDentifier (SID) objects to their canonical names for a specific Windows event log channel. * By default, this option is enabled (1) for Security event logs, disabled for all others. * If this parameter is missing, resolution would be disabled. * Optionally, you can specify the Domain Controller name and/or DNS name of the domain to bind to, which Splunk will then use to resolve the AD objects. evt_dc_name = <string> * Optional. This parameter can be left empty. * Domain Controller Name to bind to in order to resolve AD objects. * This name can be the NetBIOS name of the domain controller or the fullyqualified DNS name of the domain controller. Either name type can, optionally, be preceded by two backslash characters. The following examples represent correctly formatted domain controller names: * "FTW-DC-01" & nbsp; * "\\FTW-DC-01" * "FTW-DC-01.splunk.com" * "\\FTW-DC-01.splunk.com" evt_dns_name = <string> * Optional. This parameter can be left empty. * Fully-qualified DNS name of the domain to bind to. *********** Splunk for Windows ships with several Windows-only scripted inputs. They are defined in the default inputs.conf. * This is a list of the Windows scripted input stanzas: [script://$splunk_home\bin\scripts\splunk-wmi.path] [script://$splunk_home\bin\scripts\splunk-regmon.path] [script://$splunk_home\bin\scripts\splunk-admon.path] * By default, some of the scripted inputs are enabled and others are disabled. * Use the "disabled=" parameter to enable/disable any of them. * Here's a short summary of the inputs: * WMI: Retrieves event logs remotely and locally. It can also gather performance data remotely, as well as receive various system notifications. * RegMon: Uses a driver to track and report any changes that occur in the local system's Registry. * ADMon: Indexes existing AD objects and listens for AD changes. inputs.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This is an example inputs.conf. Use this file to configure data inputs. To use one or more of these configurations, copy the configuration block into inputs.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles The following configuration directs Splunk to read all the files in the directory /var/log. [monitor:///var/log] The following configuration directs Splunk to read all the files under /var/log/httpd and classify them as sourcetype::access_common. When checking a file for new data, if the file's modtime is from before seven days ago, the file will no longer be checked for changes. [monitor:///var/log/httpd] sourcetype = access_common 124

ignoreolderthan = 7d The following configuration directs Splunk to read all the files under /mnt/logs. When the path is /mnt/logs/<host>/... it sets the hostname (by file) to <host>. [monitor:///mnt/logs] host_segment = 3 The following configuration directs Splunk to listen on TCP port 9997 for raw data from ANY remote server (not just a Splunk instance). The host of the data is set to the IP address of the remote server. [tcp://:9997] The following configuration directs Splunk to listen on TCP port 9995 for raw data from ANY remote server. The host of the data is set as the host name of the remote server. All data will also be assigned the sourcetype "log4j" and the source "tcp:9995". [tcp://:9995] connection_host = dns sourcetype = log4j source = tcp:9995 The following configuration directs Splunk to listen on TCP port 9995 for raw data from 10.1.1.10. All data is assigned the host "webhead-1", the sourcetype "access_common" and the the source "//10.1.1.10/var/log/apache/access.log". [tcp://10.1.1.10:9995] host = webhead-1 sourcetype = access_common source = //10.1.1.10/var/log/apache/access.log The following configuration sets a global default for data payloads sent from the light forwarder. The route parameter is an ordered set of rules that is evaluated in order for each payload of cooked data. [splunktcp] route=has_key:_utf8:indexqueue;has_key:_linebreaker:indexqueue;absent_key:_utf8:parsingqueue;absent_key:_linebreaker:parsingqueue; The following configuration directs Splunk to listen on TCP port 9996 for splunk cooked event data from ANY splunk forwarder. The host of the data is set to the host name of the remote server ONLY IF the remote data has no host set, or if it is set to "localhost". [splunktcp://:9996] connection_host = dns The following configuration directs Splunk to listen on TCP port 9998 for distributed search data from 10.1.1.100. The data is processed the same as locally indexed data. [splunktcp://10.1.1.100:9996] The following configuration directs Splunk to listen on TCP port 514 for data from syslog.corp.company.net. The data is assigned the sourcetype "syslog" and the host is set to the host name of the remote server. [tcp://syslog.corp.company.net:514] sourcetype = syslog connection_host = dns Set up SSL: [SSL] servercert=$splunk_home/etc/auth/server.pem password=password 125

rootca=$splunk_home/etc/auth/cacert.pem requireclientcert=false [splunktcp-ssl:9996] Enable Windows Registry monitoring (Windows only) This example shows how to enable Windows Registry monitoring as a scripted input. Because the Windows Registry can generate a high volume of events, Windows Registry monitoring is also affected by two other configuration files, sysmon.conf and regmon.conf: * sysmon.conf contains global settings for which event types (adds, deletes, renames, and so on) to monitor, which regular expression filters from the regmon-filters.conf file to use, and whether or not Windows registry events are monitored at all. * regmon-filters.conf contains the specific regular expressions you create to refine and filter the hive key paths you want Splunk to monitor. Splunk recommends that you refer to the documentation about Windows Registry monitoring at http://docs.splunk.com/documentation/splunk/latest/data/monitorwindowsregistrydata for more details. You must make the change shown below in inputs.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. [script://$splunk_home\bin\scripts\splunk-regmon.path] interval = 60 sourcetype = WinRegistry source = WinRegistry disabled = 0 Enable WMI input (Windows only) This example shows how to enable WMI input as a scripted input. WMI input is also affected by configurations in wmi.conf. Splunk recommends that you refer to the documentation about WMI input at http://docs.splunk.com/documentation/splunk/latest/data/monitorwmidata for more details. You must make this change in inputs.conf in $SPLUNK_HOME/etc/apps/windows/local/. You must restart Splunk to enable configurations. [script://$splunk_home\bin\scripts\splunk-wmi.path] disabled = 0 Use file system change monitor: [fschange:/etc/] fullevent=true pollperiod=60 recurse=true sendeventmaxsize=100000 index=main Monitor Windows event logs Security, getting the most recent events first, then older, and finally continuing to gather newly arriving events [WinEventLog:Security] disabled = 0 start_from = newest evt_dc_name = evt_dns_name = evt_resolve_ad_obj = 1 checkpointinterval = 5 Monitor Windows event logs ForwardedEvents, this time only gathering the events happening after first starting to monitor, going forward in time. [WinEventLog:Forwarded Events] disabled = 0 start_from = oldest current_only = 1 checkpointinterval = 5 [tcp://9994] queuesize=50kb persistentqueuesize=100mb 126

Perfmon: Windows performance monitoring examples Important: You must specify the names of objects, counters and instances exactly as they are shown in the Performance Monitor application. Splunk Web is the recommended interface to use to configure performance monitor inputs. Important: These stanzas gather performance data from the local system only. Use wmi.conf for performance monitor metrics on remote systems. Query the PhysicalDisk performance object and gather disk access data for all physical drives installed in the system. Store this data in the "perfmon" index. Note: If the interval attribute is set to 0, Splunk will reset the interval to 1. [perfmon://localphysicaldisk] interval = 0 object = PhysicalDisk counters = Disk Bytes/sec; % Disk Read Time; % Disk Write Time; % Disk Time instances = * disabled = 0 index = PerfMon Gather common memory statistics using the Memory performance object, every 5 seconds. Store the data in the "main" index. Since none of the counters specified have applicable instances, the instances attribute is not required. [perfmon://localmainmemory] interval = 5 object = Memory counters = Committed Bytes; Available Bytes; % Committed Bytes In Use disabled = 0 index = main Gather data on USB activity levels every 10 seconds. Store this data in the default index. [perfmon://usbchanges] interval = 10 object = USB counters = Usb Control Data Bytes/Sec instances = * disabled = 0 limits.conf 다음은 limits.conf의 사양 및 예제 파일입니다. limits.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attribute/value pairs for configuring limits for search commands. There is a limits.conf in $SPLUNK_HOME/etc/system/default/. To set custom configurations, place a limits.conf in $SPLUNK_HOME/etc/system/local/. For examples, see limits.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the 127

value in the specific stanza takes precedence. CAUTION: Do not alter the settings in limits.conf unless you know what you are doing. Improperly configured limits may result in splunkd crashes and/or memory overuse. * Each stanza controls different parameters of search commands. max_mem_usage_mb = <integer> * Specifies the recommended maximum estimate memory usage by internal data structures that can use disk as backing store if this limit would otherwise be exceeded. * coordinates with maxresultrows such that what is in memory satisfies at least one of these 2 constraints, except if max_mem_usage_mb is set to 0. * also acts as a cutoff for memory usage by mvexpand. * Certainly commands may use multiple such structures in conjuction with large in memory result sets and thus the true maximum search memory usage may be 4-5 times this limit depending on the sequence of commands. * defaults to 200 (MB) [searchresults] * This stanza controls search results for a variety of Splunk search commands. maxresultrows = <integer> * Configures the maximum number of events are generated by search commands which grow the size of your result set (such as multikv) or that create events. Other search commands are explicitly controlled in specific stanzas below. * This limit should not exceed 50000. Setting this limit higher than 50000 causes instability. * Defaults to 50000. tocsv_maxretry = <integer> * Maximum number of times to retry the atomic write operation. * 1 = no retries. * Defaults to 5. tocsv_retryperiod_ms = <integer> * Period of time to wait before each retry. * Defaults to 500. [subsearch] * This stanza controls subsearch results. maxout = <integer> * Maximum number of results to return from a subsearch. * This value cannot be greater than or equal to 10500. * Defaults to 100. maxtime = <integer> * Maximum number of seconds to run a subsearch before finalizing * Defaults to 60. ttl = <integer> * Time to cache a given subsearch's results, in seconds. * Do not set this below 120 seconds. * See definition in [search] ttl for more details on how the ttl is computed * Defaults to 300. [anomalousvalue] maxresultrows = <integer> * Configures the maximum number of events that can be present in memory at one time. * Defaults to searchresults::maxresultsrows (which is by default 50000). & nbsp; maxvalues = <integer> * Maximum number of distinct values for a field. * Defaults to 100000. maxvaluesize = <integer> * Maximum size in bytes of any single value (truncated to this size if larger). * Defaults to 1000. [associate] maxfields = <integer> * Maximum number of fields to analyze. 128

* Defaults to 10000. maxvalues = <integer> * Maximum number of values for any field to keep track of. * Defaults to 10000. maxvaluesize = <integer> * Maximum length of a single value to consider. * Defaults to 1000. [autoregress] maxp = <integer> * Maximum valid period for auto regression * Defaults to 10000. maxrange = <integer> * Maximum magnitude of range for p values when given a range. * Defaults to 1000. [concurrency] max_count = <integer> * Maximum number of detected concurrencies. * Defaults to 10000000 [ctable] * This stanza controls the contingency, ctable, and counttable commands. maxvalues = <integer> * Maximum number of columns/rows to generate (the maximum number of distinct values for the row field and column field). * Defaults to 1000. [correlate] maxfields = <integer> * Maximum number of fields to correlate. * Defaults to 1000. [discretize] * This stanza set attributes for bin/bucket/discretize. maxbins = <integer> * Maximum number of buckets to discretize into. * If maxbins is not specified or = 0, it defaults to searchresults::maxresultrows (which is by default 50000). [export] add_timestamp = <bool> * Add a epoch time timestamp to JSON streaming output that reflects the time the results were generated/retrieved * Defaults to false add_offset = <bool> * Add an offset/row number to JSON streaming output * Defaults to true [extern] perf_warn_limit = <integer> * Warn when external scripted command is applied to more than this many events * set to 0 for no message (message is always INFO level) * Defaults to 10000 [inputcsv] mkdir_max_retries = <integer> * Maximum number of retries for creating a tmp directory (with random name as subdir of SPLUNK_HOME/var/run/splunk) * Defaults to 100. [indexpreview] max_preview_bytes = <integer> 129

* Maximum number of bytes to read from each file during preview * Defaults to 2000000 (2 MB) max_results_perchunk = <integer> * Maximum number of results to emit per call to preview data generator * Defaults to 2500 soft_preview_queue_size = <integer> * Loosely-applied maximum on number of preview data objects held in memory * Defaults to 100 [join] subsearch_maxout = <integer> * Maximum result rows in output from subsearch to join against. * Defaults to 50000 subsearch_maxtime = <integer> * Maximum search time (in seconds) before auto-finalization of subsearch. * Defaults to 60 subsearch_timeout = <integer> * Maximum time to wait for subsearch to fully finish (in seconds). * Defaults to 120 [kmeans] maxdatapoints = <integer> * Maximum data points to do kmeans clusterings for. * Defaults to 100000000 maxkvalue = <integer> * Maximum number of clusters to attempt to solve for. * Defaults to 1000 maxkrange = <integer> * Maximum number of k values to iterate over when specifying a range. * Defaults to 100 [kv] maxcols = <integer> * When non-zero, the point at which kv should stop creating new fields. * Defaults to 512. limit = <integer> * Maximum number of keys auto kv can generate. * Defaults to 50. maxchars = <integer> * Truncate _raw to this size and then do auto KV. * Defaults to 10240 characters. max_extractor_time = <integer> * Maximum amount of CPU time, in milliseconds, that a key-value pair extractor will be allowed to * take before warning. If the extractor exceeds this execution time on any event a warning will be issued * Defaults to 1000 avg_extractor_time = <integer> * Maximum amount of CPU time, in milliseconds, that the average (over search results) execution time of * a key-value pair extractor will be allowed to take before warning. Once the average becomes larger * than this amount of time a warning will be issued * Defaults to 500 [lookup] max_memtable_bytes = <integer> * Maximum size of static lookup file to use an in-memory index for. * Defaults to 10000000 in bytes (10MB max_matches = <integer> * maximum matches for a lookup * Defaults to 1000 130

max_reverse_matches = <integer> * maximum reverse lookup matches (for search expansion) * Defaults to 50 batch_index_query = <bool> * Should non-memory file lookups (files that are too large) use batched queries to possibly improve performance? * Defaults to true batch_response_limit = <integer> * When doing batch requests, the maximum number of matches to retrieve * if more than this limit of matches would otherwise be retrieve, we will fall back to non-batch mode matching * Defaults to 5000000 [metrics] maxseries = <integer> * The number of series to include in the per_x_thruput reports in metrics.log. * Defaults to 10. interval = <integer> * Number of seconds between logging splunkd metrics to metrics.log. * Minimum of 10. * Defaults to 30. [rare] maxresultrows = <integer> * Maximum number of result rows to create. * If not specified, defaults to searchresults::maxresultrows (which is by default 50000). maxvalues = <integer> * Maximum number of distinct field vector values to keep track of. * Defaults 100000. maxvaluesize = <integer> * Maximum length of a single value to consider. * Defaults to 1000. [restapi] maxresultrows = <integer> * Maximum result rows to be returned by /events or /results getters from REST API. * Defaults to 50000. time_format_reject = <regular expression> * HTTP parameters for time_format and output_time_format which match this regex will be rejected (blacklisted). * The regex will be satisfied by a substring match anywhere in the paramater. * Intended as defense-in-depth against XSS style attacks against browser users by crafting specially encoded URLS for them to access splunkd. * If unset, all parameter strings will be accepted. * To disable this check entirely, set the value to empty. Example of disabling: time_format_reject = * Defaults to [<>!], which means that the less-than '<', greater-than '>', and exclaimation point '!' are not allowed. jobscontentmaxcount = <integer> * Maximum length of a property in the contents dictionary of an entry from /jobs getter from REST API * Value of 0 disables truncation * Defaults to 0 [search] summary_mode = [all only none] * Controls if precomputed summary are to be used if possible? * all: use summary if possible, otherwise use raw data * only: use summary if possible, otherwise do not use any data * none: never use precomputed summary data * Defaults to 'all' use_bloomfilter = <bool> * Control whether to use bloom filters to rule out buckets 131

ttl = <integer> * How long search artifacts should be stored on disk once completed, in seconds. The ttl is computed * relative to the modtime of status.csv of the job if such file exists or the modtime of the search * job's artifact directory. If a job is being actively viewed in the Splunk UI then the modtime of * status.csv is constantly updated such that the reaper does not remove the job from underneath. * Defaults to 600, which is equivalent to 10 minutes. default_save_ttl = <integer> * How long the ttl for a search artifact should be extended in response to the save control action, in second. 0 = indefinitely. * Defaults to 604800 (1 week) remote_ttl = <integer> * How long artifacts from searches run in behalf of a search head should be stored on the indexer after completion, in seconds. * Defaults to 600 (10 minutes) status_buckets = <integer> * The approximate maximum number buckets to generate and maintain in the timeline. * Defaults to 0, which means do not generate timeline information. max_bucket_bytes = <integer> * This setting has been deprecated and has no effect max_count = <integer> * The number of events that can be accessible in any given status bucket. * The last accessible event in a call that takes a base and bounds. * Defaults to 10000. max_events_per_bucket = <integer> * For searches with status_buckets>1 (i.e. Timeline), this setting will specify the maximum number of events to store per timeline bucket. * Defaults to 1000 in code. (limits.conf in default will override to 10000 for 4.3.x until 5.0 to maintain existing behavior until the next major release) truncate_report = [1 0] * Specifies whether or not to apply the max_count limit to report output. * Defaults to false (0). min_prefix_len = <integer> * The minimum length of a prefix before a * to ask the index about. * Defaults to 1. max_results_raw_size = <integer> * The largest "_raw" volume that should be read in memory. * If the total volume of _raw fields (the text of the events) exceeds this value, no more results will be returned for the search. * Defaults to 100000000, which is 100MB. cache_ttl = <integer> * The length of time to persist search cache entries (in seconds). * Defaults to 300. max_results_perchunk = <integer> * Maximum results per call to search (in dispatch), must be less than or equal to maxresultrows. * Defaults to 2500 & nbsp; min_results_perchunk = <integer> * Minimum results per call to search (in dispatch), must be less than or equal to max_results_perchunk. * Defaults to 100 max_rawsize_perchunk = <integer> * Maximum raw size of results per call to search (in dispatch). * 0 = no limit. * Defaults to 5000000 target_time_perchunk = < integer> * Target duration of a particular call to fetch search results in ms. * Defaults to 2000 long_search_threshold = <integer> 132

* Time in seconds until a search is considered "long running". * Defaults to 2 chunk_multiplier = <integer> * max_results_perchunk, min_results_perchunk, and target_time_perchunk are multiplied by this for a long running search. * Defaults to 5 min_freq = <number> * Minimum frequency of a field required for including in the /summary endpoint as a fraction (>=0 and <=1). * Defaults is 0.01 (1%) reduce_freq = <integer> * Attempt to reduce intermediate results every how many chunks (0 = never). * Defaults to 10 reduce_duty_cycle = <number> * the maximum time to spend doing reduce, as a fraction of total search time * Must be > 0.0 and < 1.0 * Defaults to 0.25 preview_duty_cycle = <number> * the maximum time to spend generating previews, as a fraction of total search time * Must be > 0.0 and < 1.0 * Defaults to 0.25 dispatch_quota_retry = <integer> * The maximum number of times to retry to dispatch a search when the quota has been reached. * Defaults to 4 dispatch_quota_sleep_ms = <integer> * Milliseconds between retrying to dispatch a search if a quota has been reached. * Retries the given number of times, with each successive wait 2x longer than the previous. * Defaults to 100 base_max_searches = <int> * A constant to add to the maximum number of searches, computed as a multiplier of the CPUs. * Defaults to 4 max_searches_per_cpu = <int> * The maximum number of concurrent historical searches per CPU. The system-wide limit of historical searches is computed as: max_hist_searches = max_searches_per_cpu x number_of_cpus + base_max_searches * Note: the maximum number of real-time searches is computed as: max_rt_searches = max_rt_search_multiplier x max_hist_searches * Defaults to 4 max_rt_search_multiplier = <decimal number> * A number by which the maximum number of historical searches is multiplied to determine the maximum * number of concurrent real-time searches * Note: the maximum number of real-time searches is computed as: max_rt_searches = max_rt_search_multiplier x max_hist_searches * Defaults to 3 max_macro_depth = <int> * Max recursion depth for macros. * Considered a search exception if macro expansion doesn't stop after this many levels. * Must be greater than or equal to 1. * Default is 100 realtime_buffer = <int> * Maximum number of accessible events to keep for real-time searches from Splunk Web. * Acts as circular buffer once this limit is reached * Must be greater than or equal to 1 * Default is 10000 stack_size = <int> * The stack size (in bytes) of the thread executing the search. * Defaults to 4194304 (4 MB) status_cache_size = <int> * The number of search job status data splunkd can cache in RAM. This cache improves performance of 133

the jobs endpoint * Defaults to 2000 timeline_freq = <timespan> or <ratio> * Minimum amount of time between timeline commits. * If specified as a number < 1 (and > 0), minimum time between commits is computed as a ratio of the amount of time that the search has been running. * defaults to 0 seconds preview_freq = <timespan> or <ratio> * Minimum amount of time between results preview updates. * If specified as a number < 1 (and > 0), minimum time between previews is computed as a ratio of the amount of time that the search has been running, or as a ratio of the length of the time window for real-time windowed searches. * Defaults to ratio of 0.05 max_combiner_memevents = <int> * Maximum size of in-memory buffer for search results combiner, in terms of number of events. * Defaults to 50000 events. replication_period_sec = <int> * The minimum amount of time in seconds between two successive bundle replications. * Defaults to 60 sync_bundle_replication = [0 1 auto] * Flag indicating whether configuration file replication blocks searches or is run asynchronously * When setting this flag to auto Splunk will choose to use asynchronous replication iff all the peers * support async bundle replication, otherwise it will fallback into sync replication. * Defaults to auto multi_threaded_setup = [0 1] * Flag indicating whether to use multiple threads when setting up distributed search to multiple peers. * Defaults to false (0) rr_min_sleep_ms = <int> * Minimum time to sleep when reading results in round-robin mode when no data is available. * Defaults to 10. rr_max_sleep_ms = <int> * Maximum time to sleep when reading results in round-robin mode when no data is available. * Defaults to 1000 rr_sleep_factor = <int> * If no data is available even after sleeping, increase the next sleep interval by this factor. * defaults to 2 fieldstats_update_freq = <number> * How often to update the field summary statistics, as a ratio to the elapsed run time so far. * Smaller values means update more frequently. 0 means as frequently as possible. * Defaults to 0 fieldstats_update_maxperiod = <int> * Maximum period for updating field summary statistics in seconds * 0 means no maximum, completely dictated by current_run_time * fieldstats_update_freq * defaults to 60 remote_timeline = [0 1] * If true, allows the timeline to be computed remotely to enable better map/reduce scalability. * defaults to true (1). remote_timeline_min_peers = <int> * Minimum search peers for enabling remote computation of timelines. * Defaults to 1 (1). remote_timeline_fetchall = [0 1] * If true, fetches all events accessible through the timeline from the remote peers before the job is considered done. * Defaults to false (0). remote_timeline_thread = [0 1] * If true, uses a separate thread to read the full events from remote peers if remote_timeline is used and remote_timeline_fetchall is set to true. (Has no effect if remote_timeline or remote_timeline_fetchall is 134

false). * Defaults to true (1). remote_timeline_max_count = <int> * Maximum number of events to be stored per timeline bucket on each search peer, * Defaults to 10000 remote_timeline_max_size_mb = <int> * Maximum size of disk that remote timeline events should take on each peer * If limit is reached, a DEBUG message is emitted (and should be visible from job inspector/messages * Defaults to 1000 remote_timeline_touchperiod = <int> * How often to touch remote timeline artifacts to keep them from being deleted by the remote peer, while a search is running. * In seconds, 0 means never. * Defaults to 300. remote_timeline_connection_timeout = <int> * Connection timeout in seconds for fetching events processed by remote peer timeliner. * Defaults to 5. remote_timeline_send_timeout = <int> * Send timeout in seconds for fetching events processed by remote peer timeliner. * Defaults to 10. remote_timeline_receive_timeout = <int> * Receive timeout in seconds for fetching events processed by remote peer timeliner. * Defaults to 10. default_allow_queue = [0 1] * Unless otherwise specified via REST api argument should an async job spawning request be queued on quota violation (if not, an http error of server too busy is returned) * Defaults to true (1). queued_job_check_freq = <int> * Frequency with which to check queued jobs to see if they can be started, in seconds * Defaults to 1. enable_history = <bool> * Enable keeping track of searches? * Defaults to true max_history_length = <int> * Max number of searches to store in history (per user/app) * Defaults to 1000 allow_inexact_metasearch = <bool> * Should a metasearch that is inexact be allow. If so, an INFO message will be added to the inexact metasearches. If not, a fatal exception will occur at search parsing time. * Defaults to false indexed_as_exact_metasearch = <bool> * Should we allow a metasearch to treat <field>=<value> the same as <field>::<value> if <field> is an indexed field. Allowing this will allow a larger set of metasearches when allow_inexact_metasearch is set to false. However, some of these searches may be inconsistent with the results of doing a normal search. * Defaults to false dispatch_dir_warning_size = <int> * The number of jobs in the dispatch directory when to issue a bulletin message warning that performance could be impacted * Defaults to 2000 allow_reuse = <bool> * Allow normally executed historical searches to be implicitly re-used for newer requests if the newer request allows it? * Defaults to true track_indextime_range = <bool> * Track the _indextime range of returned search results? * Defaults to true 135

reuse_map_maxsize = <int> * Maximum number of jobs to store in the reuse map * Defaults to 1000 use_dispatchtmp_dir = <bool> * Write temporary files to a different directory from a job's dispatch directory * Temp files would be written to $SPLUNK_HOME/var/run/splunk/dispatchtmp/<sid>/ status_period_ms = <int> * The minimum amout of time, in milliseconds, between successive status/info.csv file updates * Defaults to 1000 search_process_mode = [ auto traditional debug <debugging-command> [debugging-args...]] * Control how search processes are started * When set to "traditional", Splunk initializes each search process completely from scratch * When set to a string beginning with "debug", Splunk routes searches through the given command, allowing the user the to "plug in" debugging tools * The <debugging-command> must reside in one of * $SPLUNK_HOME/etc/system/bin/ * $SPLUNK_HOME/etc/apps/$YOUR_APP/bin/ * $SPLUNK_HOME/bin/scripts/ * Splunk will pass <debugging-args>, followed by the search command it would normally run, to <debuggingcommand> * For example, given: search_process_mode = debug $SPLUNK_HOME/bin/scripts/search-debugger.sh 5 Splunk will run a command that looks generally like: $SPLUNK_HOME/bin/scripts/search-debugger.sh 5 splunkd search --id=... --maxbuckets=... --ttl=... [...] * Defaults to "auto" fetch_remote_search_log = <bool> * If true, will attempt to fetch the search.log from every search peer at the end of the search and store in the job dispatch dir on the search head. * Defaults to true load_remote_bundles = <bool> * On a search peer, allow remote (search head) bundles to be loaded in splunkd. * Defaults to false. use_dispatchtmp_dir = <bool> * Whether to use the dispatchtmp directory for temporary search time files. * Temp files would be written to $SPLUNK_HOME/var/run/splunk/dispatchtmp/<sid>/ * In search head pooling performance can be improved by mounting disaptchtmp to the * local file system. * Defaults to true if search head pooling is enabled, false otherwise check_splunkd_period = <int> * Amount of time, in seconds, that determines how frequently the search process * (when running a real-time search) checks whether it's parent process ( splunkd) is running or not. * Defaults to 60 [realtime] Default options for indexer support of real-time searches These can all be overriden for a single search via REST API arguments queue_size = <int> * Size of queue for each real-time search (must be >0). * Defaults to 10000 blocking = [0 1] * Specifies whether the indexer should block if a queue is full. * Defaults to false max_blocking_secs = <int> * Maximum time to block if the queue is full (meaningless if blocking = false) * 0 means no limit * Default to 60 indexfilter = [0 1] * Specifies whether the indexer should prefilter events for efficiency. * Defaults to true (1). 136

default_backfill = <bool> * Specifies if windowed real-time searches should backfill events * Defaults to true list_maxsize = <int> * Maximum number of list items to emit when using the list() function stats/sistats * Defaults to 100 sparkline_maxsize = <int> * Maximum number of elements to emit for a sparkline * Defaults to value of list_maxsize setting enforce_time_order = <bool> * Specifies if real-time searches should ensure that events are sorted in ascending time order (the UI will automatically reverse the order that it display events for real-time searches so in effect the latest events will be first) * Defaults to true disk_usage_update_period = <int> * Specifies how frequently (in seconds) should the search process estimate the artifact disk usage. * Defaults to 10 [slc] maxclusters = <integer> * Maximum number of clusters to create. * Defaults to 10000. [sort] maxfiles = <integer> * Maximum files to open at once. Multiple passes are made if the number of result chunks exceeds this threshold. * Defaults to 64. [stats sistats] maxmem_check_freq = & lt;integer> * How frequently to check to see if we are exceeding the in memory data structure size limit as specified by max_mem_usage_mb, in rows * Defaults to 50000 rows maxresultrows = <integer> * Maximum number of result rows to create. * If not specified, defaults to searchresults::maxresultrows (which is by default 50000). maxvalues = <integer> * Maximum number of values for any field to keep track of. * Defaults to 0 (unlimited). maxvaluesize = <integer> * Maximum length of a single value to consider. * Defaults to 0 (unlimited). rdigest is a data structure used to compute approximate order statistics (such as median and percentiles) using sublinear space. rdigest_k = <integer> * rdigest compression factor * Lower values mean more compression * After compression, number of nodes guaranteed to be greater than or equal to 11 times k. * Defaults to 100, must be greater than or equal to 2 rdigest_maxnodes = <integer> * Maximum rdigest nodes before automatic compression is triggered. * Defaults to 1, meaning automatically configure based on k value max_stream_window = <integer> * For streamstats command, the maximum allow window size * Defaults to 10000. 137

max_valuemap_bytes = <integer> * For sistats command, the maximum encoded length of the valuemap, per result written out * If limit is exceeded, extra result rows are written out as needed. (0 = no limit per row) * Defaults to 100000. perc_method = nearest-rank interpolated * Which method to use for computing percentiles (and medians=50 percentile). * nearest-rank picks the number with 0-based rank R = floor((percentile/100)*count) * interpolated means given F = (percentile/100)*(count-1), pick ranks R1 = floor(f) and R2 = ceiling(f). Answer = (R2 * (F - R1)) + (R1 * (1 - (F - R1))) * See wikipedia percentile entries on nearest rank and "alternative methods" * Defaults to interpolated approx_dc_threshold = <integer> * When using approximate distinct count (i.e. estdc(<field>) in stats/chart/timechart), do not use approximated results if the actual number of distinct values is less than this number * Defaults to 1000 dc_digest_bits = <integer> * 2^<integer> bytes will be size of digest used for approximating distinct count. * Defaults to 10 (equivalent to 1KB) * Must be >= 8 (128B) and <= 16 (64KB) natural_sort_output = <bool> * Do a natural sort on the output of stats if output size is <= maxresultrows * Natural sort means that we sort numbers numerically and non-numbers lexicographically * Defaults to true [thruput] maxkbps = <integer> * If specified and not zero, this limits the speed through the thruput processor to the specified rate in kilobytes per second. * To control the CPU load while indexing, use this to throttle the number of events this indexer processes to the rate (in KBps) you specify. [journal_compression] threads = <integer> * Specifies the maximum number of indexer threads which will be work on compressing hot bucket journal data. * Defaults to the number of CPU threads of the host machine * This setting does not typically need to be modified. [top] maxresultrows = <integer> * Maximum number of result rows to create. * If not specified, defaults to searchresults::maxresultrows (usually 50000). maxvalues = <integer> * Maximum number of distinct field vector values to keep track of. * Defaults to 100000. maxvaluesize = <integer> * Maximum length of a single value to consider. * Defaults to 1000. [summarize] hot_bucket_min_new_events = <integer> * The minimum number of new events that need to be added to the hot bucket ( since last summarization) * before a new summarization can take place. To disable hot bucket summarization set this value to a * large positive number. * Defaults to 100000 sleep_seconds = <integer> * The amount of time to sleep between polling of summarization complete status. * Default to 5 stale_lock_seconds = <integer> * The amount of time to have elapse since the mod time of a.lock file before summarization considers * that lock file stale and removes it * Default to 600 138

max_summary_ratio = <float> * A number in the [0-1) range that indicates the maximum ratio of summary data / bucket size at which * point the summarization of that bucket, for the particual search, will be disabled. Use 0 to disable. * Defaults to 0 max_summary_size = <int> * Size of summary, in bytes, at which point we'll start applying the max_summary_ratio. Use 0 to disable. * Defaults to 0 max_time = <int& gt; * The maximum amount of time, seconds, that a summary search process is allowed to run. Use 0 to disable. * Defaults to 0 indextime_lag = <unsigned int> * The amount of lag time to give indexing to ensure that it has synced any received events to disk. Effectively, * the data that has been received in the past indextime_lag will NOT be summarized. * Do not change this value unless directed by Splunk support. * Defaults to 90 [transactions] maxopentxn = <integer> * Specifies the maximum number of not yet closed transactions to keep in the open pool before starting to evict transactions. * Defaults to 5000. maxopenevents = <integer> * Specifies the maximum number of events (which are) part of open transactions before transaction eviction starts happening, using LRU policy. * Defaults to 100000. [inputproc] max_fd = <integer> * Maximum number of file descriptors that Splunk will keep open, to capture any trailing data from files that are written to very slowly. * Defaults to 100. time_before_close = <integer> * MOVED. This setting is now configured per-input in inputs.conf. * Specifying this setting in limits.conf is DEPRECATED, but for now will override the setting for all monitor inputs. tailing_proc_speed = <integer> * REMOVED. This setting is no longer used. [scheduler] max_searches_perc = <integer> * The maximum number of searches the scheduler can run, as a percentage of the maximum number of concurrent searches, see [search] max_searches_per_cpu for how to set the system wide maximum number of searches. * Defaults to 25. auto_summary_perc = <integer> * The maximum number of concurrent searches to be allocated for auto summarization, as a percentage of the concurrent searches that the scheduler can run. Note: that user scheduled searches take precedence over auto summary searches. * Defaults to 25. max_action_results = <integer> * The maximum number of results to load when triggering an alert action. * Defaults to 10000 action_execution_threads = <integer> * Number of threads to use to execute alert actions, change this number if your alert actions take a long time to execute. * This number is capped at 10. * Defaults to 2 actions_queue_size = <integer> * The number of alert notifications to queue before the scheduler starts blocking, set to 0 for infinite size. * Defaults to 100 139

actions_queue_timeout = <integer> * The maximum amount of time, in seconds to block when the action queue size is full. * Defaults to 30 alerts_max_count = <integer> * Maximum number of unexpired alerts information to keep for the alerts manager, when this number is reached Splunk will start discarding the oldest alerts. * Defaults to 50000 alerts_expire_period = <integer> * The amount of time between expired alert removal * This period controls how frequently the alerts list is scanned, the only benefit from reducing this is better resolution in the number of alerts fired at the savedsearch level. * Change not recommended. * Defaults to 120. peristance_period = <integer> * The period (in seconds) between scheduler state persistance to disk. The scheduler currently persists the suppression and fired-unexpired alerts to disk. * This is relevant only in search head pooling mode. * Defaults to 30. max_lock_files = <int> * The number of most recent lock files to keep around. * This setting only applies in search head pooling. max_lock_file_ttl = <int> * Time (in seconds) that must pass before reaping a stale lock file. * Only applies in search head pooling. max_per_result_alerts = <int> * Maximum number of alerts to trigger for each saved search instance (or real-time results preview for RT alerts) * Only applies in non-digest mode alerting. Use 0 to disable this limit * Defaults to 500 max_per_result_alerts_time = <int> * Maximum number of time to spend triggering alerts for each saved search instance (or real-time results preview for RT alerts) * Only applies in non-digest mode alerting. Use 0 to disable this limit. * Defaults to 300 scheduled_view_timeout = <int>[s m h d] * The maximum amount of time that a scheduled view (pdf delivery) would be allowed to render * Defaults to 60m [auto_summarizer] cache_timeout = <integer> * The amount of time, in seconds, to cache auto summary details and search hash codes * Defaults to 600-10 minutes maintenance_period = <integer> * The period of time, in seconds, that the auto summarization maintenance happens * Defaults to 14400 (4 hours) allow_event_ summarization = <bool> * Whether auto summarization of searches whose remote part returns events rather than results will be allowed. * Defaults to false max_verify_buckets = <int> * When verifying buckets, stop after verifying this many buckets if no failures have been found * 0 means never * Defaults to 100 max_verify_ratio = <number> * Maximum fraction of data in each bucket to verify * Defaults to 0.1 (10%) max_verify_bucket_time = <int> * Maximum time to spend verifying each bucket, in seconds * Defaults to 15 (seconds) 140

verify_delete = <bool> * Should summaries that fail verification be automatically deleted? * Defaults to false max_verify_total_time = <int> * Maximum total time in seconds to spend doing verification, regardless if any buckets have failed or not * Defaults to 0 (no limit) max_run_stats = <int> * Maximum number of summarization run statistics to keep track and expose via REST. * Defaults to 48 [show_source] max_count = <integer> * Maximum number of events accessible by show_source. * The show source command will fail when more than this many events are in the same second as the requested event. * Defaults to 10000 max_timebefore = <timespan> * Maximum time before requested event to show. * Defaults to '1day' (86400 seconds) max_timeafter = <timespan> * Maximum time after requested event to show. * Defaults to '1day' (86400 seconds) distributed = <bool> * Controls whether we will do a distributed search for show source to get events from all servers and indexes * Turning this off results in better performance for show source, but events will only come from the initial server and index * NOTE: event signing and verification is not supported in distributed mode * Defaults to true distributed_search_limit = <unsigned int> * Sets a limit on the maximum events we will request when doing the search for distributed show source * As this is used for a larger search than the initial non-distributed show source, it is larger than max_count * Splunk will rarely return anywhere near this amount of results, as we will prune the excess results * The point is to ensure the distributed search captures the target event in an environment with many events * Defaults to 30000 [typeahead] maxcount = <integer> * Maximum number of typeahead results to find. * Defaults to 1000 use_cache = [0 1] * Specifies whether the typeahead cache will be used if use_cache is not specified in the command line or endpoint. * Defaults to true. fetch_multiplier = <integer> * A multiplying factor that determines the number of terms to fetch from the index, fetch = fetch_multiplier x count. * Defaults to 50 cache_ttl_sec = <integer> * How long the typeahead cached results are valid, in seconds. * Defaults to 300. min_prefix_length = <integer> * The minimum string prefix after which to provide typeahead. * Defaults to 1. max_concurrent_per_user = <integer> * The maximum number of concurrent typeahead searches per user. Once this maximum is reached only cached * typeahead results might be available * Defaults to 3. [typer] maxlen = <int> * In eventtyping, pay attention to first <int> characters of any attribute (such as _raw), including individual tokens. Can be overridden by supplying the typer operator with the argument maxlen (for example, " typer maxlen=300"). 141

* Defaults to 10000. [authtokens] expiration_time = <integer> * Expiration time of auth tokens in seconds. * Defaults to 3600 [sample] maxsamples = <integer> * Defaults to 10000 maxtotalsamples = <integer> * Defaults to 100000 [metadata] maxresultrows = <integer> * the maximum number of results in a single chunk fetched by the metadata command * a smaller value will require less memory on the search head in setups with large number of peers and many metadata results, though, setting this too small will decrease the search performance * default is 10000 * do not change unless instructed to do so by Splunk Support maxcount = <integer> * the total maximum number of results the metadata command will fetch from each indexer [set] maxresultrows = <integer> * the maximum number of results the set command will use from each resultset to compute the required set operation [input_channels] max_inactive = <integer> * internal setting, do not change unless instructed to do so by Splunk Support lowater_inactive = <integer> * internal setting, do not change unless instructed to do so by Splunk Support inactive_eligibility_age_seconds = <integer> * internal setting, do not change unless instructed to do so by Splunk Support [ldap] max_users_to_precache = <unsigned integer> * The maximum number of users we will attempt to precache from LDAP after reloading auth * Set this to 0 to turn off precaching allow_multiple_matching_users = <bool> * This controls whether we allow login when we find multiple entries with the same value for the username attribute * When multiple entries are found, we choose the first user DN lexicographically * Setting this to false is more secure as it does not allow any ambiguous login, but users with duplicate entries will not be able to login. * Defaults to true [spath] extraction_cutoff = <integer> * For extract-all spath extraction mode, only apply extraction to the first <integer> number of bytes * Defaults to 5000 extract_all = <boolean> * Controls whether we respect automatic field extraction when spath is invoked manually. * If true, we extract all fields regardless of settings. If false, we only extract fields used by later splunk commands. [reversedns] rdnsmaxdutycycle = <integer> * generate diagnostic WARN in splunkd.log if reverse dns lookups are taking * more than this percent of time * range 0-100 * default 10 [viewstates] enable_reaper = <boolean> 142

* Controls whether the viewstate reaper runs * Defaults to true reaper_freq = <integer> * Controls how often the viewstate reaper runs * Defaults to 86400 (1 day) reaper_soft_warn_level = <integer> * Controls what the reaper considers an acceptable number of viewstates * Defaults to 1000 ttl = <integer> * Controls the age at which a viewstate is considered eligible for reaping * Defaults to 86400 ( 1 day) [tscollect] squashcase = <boolean> * The default value of the 'squashcase' argument if not specified by the command * Defaults to false keepresults = <boolean> * The default value of the 'keepresults' argument if not specified by the command * Defaults to false tsidx_init_file_goal_mb = <unsigned int> * How large we should try to create tsidx files initially, before optimize * This is purely a heuristic, but can be used to suggest memory allocation sizes * Defaults to 500 optimize_period = <timespan string> * How often we should attempt to optimize the tsidx files created * Uses a search-like timespan string * Defaults to '15s' optimize_min_src_count = <unsigned int> * The minimum amount of candidate tsidx files in the directory before optimize will actually combine them * Defaults to 4 optimize_max_size_mb = <unsigned int> * The maximum size in megabytes of files to create with optimize * Specify 0 for no limit (may create very large tsidx files) * Defaults to 1024 [pdf] max_rows_per_table = <unsigned int> * The maximum number of rows that will be rendered for a table within integrated PDF rendering * Defaults to 1000 render_endpoint_timeout = <unsigned int> * The number of seconds after which the pdfgen render endpoint will timeout if it has not yet finished rendering the PDF output * Defaults to 3600 limits.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 CAUTION: Do not alter the settings in limits.conf unless you know what you are doing. Improperly configured limits may result in splunkd crashes and/or memory overuse. [searchresults] maxresultrows = 50000 maximum number of times to try in the atomic write operation (1 = no retries) tocsv_maxretry = 5 retry period is 1/2 second (500 milliseconds) tocsv_retryperiod_ms = 500 [subsearch] maximum number of results to return from a subsearch maxout = 100 143

maximum number of seconds to run a subsearch before finalizing maxtime = 10 time to cache a given subsearch's results ttl = 300 [anomalousvalue] maxresultrows = 50000 maximum number of distinct values for a field maxvalues = 100000 maximum size in bytes of any single value (truncated to this size if larger) maxvaluesize = 1000 [ associate] maxfields = 10000 maxvalues = 10000 maxvaluesize = 1000 for the contingency, ctable, and counttable commands [ctable] maxvalues = 1000 [correlate] maxfields = 1000 for bin/bucket/discretize [discretize] maxbins = 50000 if maxbins not specified or = 0, defaults to searchresults::maxresultrows [inputcsv] maximum number of retries for creating a tmp directory (with random name in SPLUNK_HOME/var/run/splunk) mkdir_max_retries = 100 [kmeans] maxdatapoints = 100000000 [kv] when non-zero, the point at which kv should stop creating new columns maxcols = 512 [rare] maxresultrows = 50000 maximum distinct value vectors to keep track of maxvalues = 100000 maxvaluesize = 1000 [restapi] maximum result rows to be returned by /events or /results getters from REST API maxresultrows = 50000 [search] how long searches should be stored on disk once completed ttl = 86400 the approximate maximum number of timeline buckets to maintain status_buckets = 300 the last accessible event in a call that takes a base and bounds max_count = 10000 the minimum length of a prefix before a * to ask the index about min_prefix_len = 1 the largest "_raw" volume that should be read in memory max_results_raw_size = 100000000 the length of time to persist search cache entries (in seconds) cache_ttl = 300 [slc] maximum number of clusters to create maxclusters = 10000 144

[stats] maxresultrows = 50000 maxvalues = 10000 maxvaluesize = 1000 [top] maxresultrows = 50000 maximum distinct value vectors to keep track of maxvalues = 100000 maxvaluesize = 1000 literals.conf 다음은 literals.conf의 사양 및 예제 파일입니다. literals.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains attribute/value pairs for configuring externalized strings in literals.conf. There is a literals.conf in $SPLUNK_HOME/etc/system/default/. To set custom configurations, place a literals.conf in $SPLUNK_HOME/etc/system/local/. For examples, see literals.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles For the full list of all literals that can be overridden, check out $SPLUNK_HOME/etc/system/default/literals.conf. CAUTION: - You can destroy Splunk's performance by editing literals.conf incorrectly. - Only edit the attribute values (on the right-hand side of the '='). DO NOT edit the attribute names (left-hand side of the '='). - When strings contain "%s", do not add or remove any occurrences of %s, or reorder their positions. - When strings contain HTML tags, take special care to make sure that all tags and quoted attributes are properly closed, and that all entities such as & are escaped. literals.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains an example literals.conf, which is used to configure the externalized strings in Splunk. For the full list of all literals that can be overwritten, consult the far longer list in $SPLUNK_HOME/etc/system/default/literals.conf [ui] PRO_SERVER_LOGIN_HEADER = Login to Splunk (guest/guest) INSUFFICIENT_DISK_SPACE_ERROR = The server's free disk space is too low. Indexing will temporarily pause until more 145

disk space becomes available. SERVER_RESTART_MESSAGE = This Splunk Server's configuration has been changed. The server needs to be restarted by an administrator. UNABLE_TO_CONNECT_MESSAGE = Could not connect to splunkd at %s. macros.conf 다음은 macros.conf의 사양 및 예제 파일입니다. macros.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attribute/value pairs for search language macros. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles [<STANZA_NAME>] * Each stanza represents a search macro that can be referenced in any search. * The stanza name is the name of the macro if the macro takes no arguments. Otherwise, the stanza name is the macro name appended with "(<numargs>)", where <numargs> is the number of arguments that this macro takes. * Macros can be overloaded. In other words, they can have the same name but a different number of arguments. If you have [foobar], [foobar(1)], [foobar(2)], etc., they are not the same macro. * Macros can be used in the search language by enclosing the macro name and any argument list within tick marks, for example:`foobar(arg1,arg2)` or `footer`. * Splunk does not expand macros when they are inside of quoted values, for example: "foo`bar`baz". args = <string>,<string>,... * A comma-delimited string of argument names. * Argument names can only contain alphanumeric characters, underscores '_', and hyphens '-'. * If the stanza name indicates that this macro takes no arguments, this attribute will be ignored. * This list cannot contain any repeated elements. definition = <string> * The string that the macro will expand to, with the argument substitutions made. (The exception is when iseval = true, see below.) * Arguments to be substituted must be wrapped by dollar signs ($), for example: "the last part of this string will be replaced by the value of argument foo $foo$". * Splunk replaces the $<arg>$ pattern globally in the string, even inside of quotes. validation = <string> * A validation string that is an 'eval' expression. This expression must evaluate to a boolean or a string. * Use this to verify that the macro's argument values are acceptable. * If the validation expression is boolean, validation succeeds when it returns true. If it returns false or is NULL, validation fails, and Splunk returns the error message defined by the attribute, errormsg. * If the validation expression is not boolean, Splunk expects it to return a string or NULL. If it returns NULL, validation is considered a success. Otherwise, the string returned is the error string. errormsg = <string> * The error message to be displayed if validation is a boolean expression and it does not evaluate to true. iseval = <true/false> * If true, the definition attribute is expected to be an eval expression that returns a string that represents the expansion of this macro. * Defaults to false. description = <string> * OPTIONAL. Simple english description of what the macro does. 146

macros.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 Example macros.conf macro foobar that takes no arguments can be invoked via `foobar` [foobar] the defintion of a macro can invoke another macro. nesting can be indefinite and cycles will be detected and result in an error definition = `foobar(foo=defaultfoo)` macro foobar that takes one argument, invoked via `foobar(someval)` [foobar(1)] args = foo note this is definition will include the leading and trailing quotes, i.e. something `foobar(someval)` would expand to something "foo = someval" definition = "foo = $foo$" macro that takes two arguments note that macro arguments can be named so this particular macro could be invoked equivalently as `foobar(1,2)` `foobar(foo=1,bar=2)` or `foobar(bar=2,foo=1)` [foobar(2)] args = foo, bar definition = "foo = $foo$, bar = $bar$" macro that takes one argument that does validation [foovalid(1)] args = foo definition = "foovalid = $foo$" the validation eval function takes any even number of arguments (>=2) where the first argument is a boolean expression, the 2nd a string, the third boolean, 4th a string, etc etc etc validation = validate(foo>15,"foo must be greater than 15",foo<=100,"foo must be <= 100") macro showing simple boolean validation, where if foo > bar is not true, errormsg is displayed [foovalid(2)] args = foo, bar definition = "foo = $foo$ and bar = $bar$" validation = foo > bar errormsg = foo must be greater than bar example of an eval-based definition. For example in this case `fooeval(10,20)` would get replaced by 10 + 20 [fooeval(2)] args = foo, bar definition = if (bar > 0, "$foo$ + $bar$", "$foo$ - $bar$") iseval = true multikv.conf 다음은 multikv.conf의 사양 및 예제 파일입니다. multikv.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attribute and value pairs for creating multikv rules. Multikv is the process of extracting events from table-like events, such as the output of top, ps, ls, netstat, etc. There is NO DEFAULT multikv.conf. To set custom configurations, place a multikv.conf in $SPLUNK_HOME/etc/system/local/. For examples, see multikv.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) see the documentation 147

located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles NOTE: Only configure multikv.conf if Splunk's default multikv behavior does not meet your needs. A table-like event includes a table consisting of four sections: ------------------------------------------------------- -------------------------------- Section Name Description --------------------------------------------------------------------------------------- pre optional: info/description (for example: the system summary output in top) header optional: if not defined, fields are named Column_N body required: the body of the table from which child events are constructed post optional: info/description --------------------------------------------------------------------------------------- NOTE: Each section must have a definition and a processing component. See below. [<multikv_config_name>] * Name of the stanza to use with the multikv search command, for example: '... multikv conf=<multikv_config_name& gt; rmorig=f...' * Follow this stanza name with any number of the following attribute/value pairs. Section Definition Define where each section begins and ends. <Section Name>.start = <regex> * A line matching this regex denotes the start of this section (inclusive). OR <Section Name>.start_offset = <int> * Line offset from the start of an event or the end of the previous section (inclusive). * Use this if you cannot define a regex for the start of the section. <Section Name>.member = <regex> * A line membership test. * Member if lines match the regex. <Section Name>.end = <regex> * A line matching this regex denotes the end of this section (exclusive). OR <Section Name>.linecount = <int> * Specify the number of lines in this section. * Use this if you cannot specify a regex for the end of the section. Section processing Set processing for each section. <Section Name>.ignore = [_all_ _none_ _regex_ <regex-list>] * Determines which member lines will be ignored and not processed further. <Section Name>.replace = <quoted-str> = <quoted-str>, <quoted-str> = <quoted-str>,... * List of the form: "toreplace" = "replacewith". * Can have any number of quoted string pairs. * For example: "%" = "_", "" = "_" <Section Name>.tokens = [<chopper> <tokenizer> <aligner> <token-list>] * See below for definitions of each possible token: chopper, tokenizer, aligner, token-list. <chopper> = _chop_, <int-list> * Transform each string into a list of tokens specified by <int-list>. * <int-list> is a list of (offset, length) tuples. <tokenizer> = _tokenize_ <max_tokens (int)> <delims> 148

* Tokenize the string using the delim characters. * This generates at most max_tokens number of tokens. * Set max_tokens to: * -1 for complete tokenization. * 0 to inherit from previous section (usually header). * A non-zero number for a specific token count. * If tokenization is limited by the max_tokens, the rest of the string is added onto the last token. * <delims> is a comma-separated list of delimiting chars. * Note: Splunk treats consecutive delimiters as an empty field. <aligner> = _align_, <header_string>, <side>, <max_width> * Generates tokens by extracting text aligned to the specified header fields. * header_string: a complete or partial header field value the columns are aligned with. * side: either L or R (for left or right align, respectively). * max_width: the maximum width of the extracted field. * Set max_width to -1 for automatic width. This expands the field until any of the following delimiters are found: " ", "\t" <token_list> = _token_list_ <comma-separated list> * Defines a list of static tokens in a section. * This is useful for tables with no header, for example: the output of 'ls -lah' which misses a header altogether. multikv.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains example multi key/value extraction configurations. To use one or more of these configurations, copy the configuration block into multikv.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles This example breaks up the output from top: Sample output: Processes: 56 total, 2 running, 54 sleeping... 221 threads 10:14:07... PID COMMAND %CPU TIME TH PRTS MREGS RPRVT RSHRD RSIZE VSIZE 29960 mdimport 0.0% 0:00.29 3 60 50 1.10M 2.55M 3.54M 38. 7M 29905 pickup 0.0% 0:00.01 1 16 17 164K 832K 764K 26.7M... [top_mkv] pre table starts at "Process..." and ends at line containing "PID" pre.start = "Process" pre.end = "PID" pre.ignore = _all_ specify table header location and processing header.start = "PID" header.linecount = 1 header.replace = "%" = "_", "" = "_" header.tokens = _tokenize_, -1," " table body ends at the next "Process" line (ie start of another top) tokenize and inherit the number of tokens from previous section (header) body.end = "Process" body.tokens = _tokenize_, 0, " " This example handles the output of 'ls -lah' command: 149

total 2150528 drwxr-xr-x 88 john john 2K Jan 30 07:56. drwxr-xr-x 15 john john 510B Jan 30 07:49.. -rw------- 1 john john 2K Jan 28 11:25.hiden_file drwxr-xr-x 20 john john 680B Jan 30 07:49 my_dir -r--r--r-- 1 john john 3K Jan 11 09:00 my_file.txt [ls-lah] pre.start = "total" pre.linecount = 1 the header is missing, so list the column names header.tokens = _token_list_, mode, links, user, group, size, date, name body.end = "^\s*$" body.member = "\.cpp" concatenates the date into a single unbreakable item body.replace = "(\w{3})\s+(\d{1,2})\s+(\d{2}:\d{2})" ="\1_\2_\3" ignore dirs body.ignore = _regex_ "^drwx.*", body.tokens = _tokenize_, 0, " " outputs.conf 다음은 outputs.conf의 사양 및 예제 파일입니다. outputs.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 Forwarders require outputs.conf; non-forwarding Splunk instances do not use it. It determines how the forwarder sends data to receiving Splunk instances, either indexers or other forwarders. To configure forwarding, create an outputs.conf file in $SPLUNK_HOME/etc/system/local/. For examples of its use, see outputs.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles NOTE: To learn more about forwarding, see the documentation at http://docs.splunk.com/documentation/splunk/latest/deploy/aboutforwardingandreceivingdata GLOBAL SETTINGS Use the [default] stanza to define any global settings. & nbsp; * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. TCP Output stanzas There are three levels of TCP Output stanzas: * Global: [tcpout] * Target group: [tcpout:<target_group>] * Single server: [tcpout-server://<ip address>:<port>] Settings at more specific levels override settings at higher levels. For example, an attribute set for a single server overrides the value of that attribute, if any, set at that server's target group stanza. See the online documentation on configuring forwarders for details. 150

This spec file first describes the three levels of stanzas (and any attributes unique to a particular level). It then describes the optional attributes, which can be set at any of the three levels. ----TCP Output Global Configuration ----- The global configurations specified here in the [tcpout] stanza can be overwritten in stanzas for specific target groups, as described later. Note that the defaultgroup and indexandforward attributes can only be set here, at the global level. Starting with 4.2, the [tcpout] stanza is no longer required. [tcpout] defaultgroup = <target_group>, <target_group>,... * Comma-separated list of one or more target group names, specified later in [tcpout:<target_group>] stanzas. * The forwarder sends all data to the specified groups. * If you don't want to forward data automatically, don't set this attribute. * Can be overridden by an inputs.conf _TCP_ROUTING setting, which in turn can be overridden by a props.conf/transforms.conf modifier. * Starting with 4.2, this attribute is no longer required. indexandforward = [true false] * Index all data locally, in addition to forwarding it. * This is known as an "index-and-forward" configuration. * This attribute is only available for heavy forwarders. * This attribute is available only at the top level [tcpout] stanza. It cannot be overridden in a target group. * Defaults to false. ----Target Group Configuration ----- If multiple servers are specified in a target group, the forwarder performs auto load-balancing, sending data alternately to each available server in the group. For example, assuming you have three servers (server1, server2, server3) and autolbfrequency=30, the forwarder sends all data to server1 for 30 seconds, then it sends all data to server2 for the next 30 seconds, then all data to server3 for the next 30 seconds, finally cycling back to server1. You can have as many target groups as you want. If more than one target group is specified, the forwarder sends all data to each target group. This is known as "cloning" the data. [tcpout:<target_group>] server = [<ip> <servername>]:<port>, [<ip> <servername>]:<port>,... * Required. * Takes a comma seperated list of one or more systems to send data to over a tcp socket. * Typically used to specify receiveing splunk systems, although it can be used to send data to non-splunk systems (see sendcookeddata setting). & nbsp; * For each mentioned system, the following are required: * IP or servername where one or system is listening. * Port on which syslog server is listening. ----Single server configuration ----- You can define specific configurations for individual indexers on a server-by-server basis. However, each server must also be part of a target group. [tcpout-server://<ip address>:<port>] * Optional. There is no requirement to have any tcpout-server stanzas. ----TCPOUT ATTRIBUTES---- These attributes are optional and can appear in any of the three stanza levels. [tcpout<any of above>] ----General Settings---- sendcookeddata = [true false] * If true, events are cooked (have been processed by Splunk). 151

* If false, events are raw and untouched prior to sending. * Set to false if you are sending to a third-party system. * Defaults to true. heartbeatfrequency = <integer> * How often (in seconds) to send a heartbeat packet to the receiving server. * Heartbeats are only sent if sendcookeddata=true. * Defaults to 30 seconds. blockoncloning = [true false] * If true, TcpOutputProcessor blocks till at least one of the cloned group gets events. This will not drop events when all the cloned groups are down. * If false, TcpOutputProcessor will drop events when all the cloned groups are down and queues for the cloned groups are full. When at least one of the cloned groups is up and queues are not full, the events are not dropped. * Defaults to true. compressed = [true false] * Applies to non-ssl forwarding only. For SSL useclientsslcompression setting is used. * If true, forwarder sends compressed data. * If set to true, the receiver port must also have compression turned on (in its inputs.conf file). * Defaults to false. ----Queue Settings---- maxqueuesize = [<integer> <integer>[kb MB GB]] * This attribute sets the maximum size of the forwarder's output queue. It also sets the maximum size of the wait queue to 3x this value, if you have enabled indexer acknowledgment (useack=true), as described later. * Although the wait queue and the output queues are both configured by this attribute, they are separate queues. * The setting determines the maximum size of the queue's in-memory (RAM) buffer. * If specified as a lone integer (for example, maxqueuesize=100), maxqueuesize indicates the maximum number of queued events (for parsed data) or blocks of data (for unparsed data). A block of data is approximately 64KB. For nonparsing forwarders, such as universal forwarders, that send unparsed data, maxqueuesize is the maximum number of data blocks. For heavy forwarders sending parsed data, maxqueuesize is the maximum number of events. Since events are typically much shorter than data blocks, the memory consumed by the queue on a parsing forwarder will likely be much smaller than on a non-parsing forwarder, if you use this version of the setting. * If specified as an integer followed by KB, MB, or GB (for example, maxqueuesize=100mb), maxqueuesize indicates the maximum RAM allocated to the queue buffer. * Defaults to 500KB (which means a maximum size of 500KB for the output queue and 1500KB for the wait queue, if any). * If indexer acknowledgment is used(useack=true), you should set the maxqueuesize to 6MB to ensure that the forwarder does not get blocked while waiting for acknowledgement from an indexer. dropeventsonqueuefull = <integer> * If set to a positive number, wait <integer> seconds before throwing out all new events until the output queue has space. * Setting this to -1 or 0 will cause the output queue to block when it gets full, causing further blocking up the processing chain. * If any target group's queue is blocked, no more data will reach any other target group. * Using auto load-balancing is the best way to minimize this condition, because, in that case, multiple receivers must be down (or jammed up) before queue blocking can occur. * Defaults to -1 (do not drop events). * DO NOT SET THIS VALUE TO A POSITIVE INTEGER IF YOU ARE MONITORING FILES! dropclonedeventsonqueuefull = <integer> * If set to a positive number, do not block completely, but wait up to < integer> seconds to queue events to a group. If it cannot enqueue to a group for more than <integer> seconds, begin dropping events for the group. It makes sure that at least one group in the cloning configuration will get events. It blocks if event cannot be delivered to any of the cloned groups. * If set to -1, the TcpOutputProcessor will make sure that each group will get all of the events. If one of the groups is down, then Splunk will block everything. * Defaults to 5. 152

----Backoff Settings When Unable To Send Events to Indexer---- The settings in this section determine forwarding behavior when there are repeated failures in sending events to an indexer ("sending failures"). maxfailuresperinterval = <integer> * Specifies the maximum number failures allowed per interval before backoff takes place. The interval is defined below. * Defaults to 2. secsinfailureinterval = <integer> * Number of seconds in an interval. If the number of write failures exceeds maxfailuresperinterval in the specified secsinfailureinterval seconds, the forwarder sleeps for backoffonfailure seconds. * Defaults to 1. maxconnectionsperindexer = <integer> * Maximum number of allowed connections per indexer. In presence of failures, the max number of connection attempt per indexer at any point in time. * Defaults to 2. connectiontimeout = <integer> * Time out period if connection establishment does not finish in <integer> seconds. * Defaults to 20 seconds. readtimeout = <integer> * Time out period if read from socket does not finish in <integer> seconds. * This timeout is used to read acknowledgment when indexer acknowledgment is used (useack=true). * Defaults to 300 seconds. writetimeout = <integer> * Time out period if write on socket does not finish in <integer> seconds. * Defaults to 300 seconds. dnsresolutioninterval = <integer> * Specifies base time interval in seconds at which indexer dns names will be resolved to ip address. This is used to compute runtime dnsresolutioninterval as follows: runtime interval = dnsresolutioninterval + (number of indexers in server settings - 1)*30. DNS resolution interval is extended by 30 second for each additional indexer in server setting. * Defaults to 300 seconds. forcetimebasedautolb = [true false] * Will force existing streams to switch to newly elected indexer every AutoLB cycle. * Defaults to false ----Index Filter Settings. These attributes are only applicable under the global [tcpout] stanza. This filter does not work if it is created under any other stanza. forwardedindex.<n>.whitelist = <regex> forwardedindex.<n>.blacklist = <regex> * These filters determine which events get forwarded, based on the indexes they belong to. * This is an ordered list of whitelists and blacklists, which together decide if events should be forwarded to an index. * The order is determined by <n>. <n> must start at 0 and continue with positive integers, in sequence. There cannot be any gaps in the sequence. (For example, forwardedindex.0.whitelist, forwardedindex.1.blacklist, forwardedindex.2.whitelist,...). * The filters can start from either whitelist or blacklist. They are tested from forwardedindex.0 to forwardedindex.<max>. * You should not normally need to change these filters from their default settings in $SPLUNK_HOME/system/default/outputs.conf. * Filtered out events are not indexed if local indexing is not enabled. forwardedindex.filter.disable = [true false] * If true, disables index filtering. Events for all indexes are then forwarded. * Defaults to false. ---- Automatic Load-Balancing autolb = true * Automatic load balancing is the only way to forward data. Round-robin method is not supported anymore. * Defaults to true. autolbfrequency = <seconds> 153

* Every autolbfrequency seconds, a new indexer is selected randomly from the list of indexers provided in the server attribute of the target group stanza. * Defaults to 30 (seconds). ----SSL Settings---- To set up SSL on the forwarder, set the following attribute/value pairs. If you want to use SSL for authentication, add a stanza for each receiver that must be certified. sslpassword = <password> * The password associated with the CAcert. * The default Splunk CAcert uses the password "password". * There is no default value. sslcertpath = <path> * If specified, this connection will use SSL. * This is the path to the client certificate. * There is no default value. sslrootcapath = <path> * The path to the root certificate authority file (optional). * There is no default value. sslverifyservercert = [true false] * If true, you must make sure that the server you are connecting to is a valid one (authenticated). * Both the common name and the alternate name of the server are then checked for a match. * Defaults to false. sslcommonnametocheck = <string> * Check the common name of the server's certificate against this name. * If there is no match, assume that Splunk is not authenticated against this server. * You must specify this setting if sslverifyservercert is true. sslaltnametocheck = <string> * Check the alternate name of the server's certificate against this name. * If there is no match, assume that Splunk is not authenticated against this server. * You must specify this setting if sslverifyservercert is true. useclientsslcompression = [ true false] * Enables compression on SSL. * Defaults to value of useclientsslcompression from [sslconfig] stanza in server.conf. ----Indexer Acknowledgment ---- Indexer acknowledgment ensures that forwarded data is reliably delivered to the receiver. If the receiver is an indexer, it indicates that the indexer has received the data, indexed it, and written it to the file system. If the receiver is an intermediate forwarder, it indicates that the intermediate forwarder has successfully forwarded the data to the terminating indexer and has received acknowledgment from that indexer. Important: Indexer acknowledgment is a complex feature that requires careful planning. Before using it, read the online topic describing it in the Distributed Deployment manual. useack = [true false] * True - Forwarder expects acknowledgment of successful delivery from receiver. * False - Forwarder does not expect acknowledgment from receiver. * Defaults to false. * This attribute can be set at the [tcpout] or [tcpout:<target_group>] stanza levels. You cannot set it for individual servers at the [tcpout-server:...] stanza level. ----Syslog output---- The syslog output processor is not available for universal or light forwarders. The following configuration is used to send output using syslog: [syslog] defaultgroup = <target_group>, <target_group>,... 154

[syslog:<target_group>] ----REQUIRED SETTINGS---- Required settings for a syslog output group: server = [<ip> <servername>]:<port> * IP or servername where syslog server is running. * Port on which server is listening. You must specify the port. Syslog, by default, uses 514. ----OPTIONAL SETTINGS---- Optional settings for syslog output: type = [tcp udp] * Protocol used. * Default is udp. priority = <priority_value> * The priority_value should specified as "<integer>" (an integer surrounded by angle brackets). For example, specify a priority of 34 like this: <34> * The integer must be one to three digits in length. * The value you enter will appear in the syslog header. * Mimics the number passed via syslog interface call, documented via man syslog. * The integer can be computed as (<facility> * 8) + <severity>. For example, if <facility> is 4 (security/authorization messages) and <severity> is 2 (critical conditions), the priority will be 34 = (4 * 8) + 2. Set the attribute to: <34> * The table of facility and severity (and their values) can be referenced in RFC3164, eg http://www.ietf.org/rfc/rfc3164.txt section 4.1.1 * Defaults to <13>, or a facility of "user" or typically unspecified application, and severity of "Notice". * The table is reproduced briefly here, some of these are archaic. Facility: 0 kernel messages 1 user-level messages 2 mail system 3 system daemons 4 security/authorization messages 5 messages generated internally by syslogd 6 line printer subsystem 7 network news subsystem 8 UUCP subsystem 9 clock daemon 10 security/authorization messages 11 FTP daemon 12 NTP subsystem 13 log audit & nbsp; 14 log alert 15 clock daemon 16 local use 0 (local0) 17 local use 1 (local1) 18 local use 2 (local2) 19 local use 3 (local3) 20 local use 4 (local4) 21 local use 5 (local5) 22 local use 6 (local6) 23 local use 7 (local7) Severity: 0 Emergency: system is unusable 1 Alert: action must be taken immediately 2 Critical: critical conditions 3 Error: error conditions 4 Warning: warning conditions 5 Notice: normal but significant condition 6 Informational: informational messages 7 Debug: debug-level messages syslogsourcetype = <string> * Specifies an additional rule for handling data, in addition to that provided by the 'syslog' source type. * This string is used as a substring match against the sourcetype key. For example, if the string is set to 'syslog', then all source types containing the string 'syslog' will receive this special treatment. 155

* To match a source type explicitly, use the pattern "sourcetype::sourcetype_name". * Example: syslogsourcetype = sourcetype::apache_common * Data which is 'syslog' or matches this setting is assumed to already be in syslog format. * Data which does not match the rules has a header, potentially a timestamp, and a hostname added to the front of the event. This is how Splunk causes arbitrary log data to match syslog expectations. * Defaults to unset. timestampformat = <format> * If specified, the formatted timestamps are added to the start of events forwarded to syslog. * As above, this logic is only applied when the data is not syslog, or the syslogsourcetype. * The format is a strftime-style timestamp formatting string. This is the same implementation used in the 'eval' search command, splunk logging, and other places in splunkd. * For example: %b %e %H:%M:%S * %b - Abbreviated month name (Jan, Feb,...) * %e - Day of month * %H - Hour * %M - Minute * %s - Second * For a more exhaustive list of the formatting specifiers, refer to the online documentation. * Note that the string is not quoted. * Defaults to unset, which means that no timestamp will be inserted into the front of events. ---- Routing Data to Syslog Server ----- To route data to syslog server: 1) Decide which events to route to which servers. 2) Edit the props.conf, transforms.conf, and outputs.conf files on the forwarders. Edit $SPLUNK_HOME/etc/system/local/props.conf and set a TRANSFORMS-routing attribute as shown here: [<spec>] TRANSFORMS-routing=<unique_stanza_name> * <spec> can be: * <sourcetype>, the source type of an event * host::<host>, where <host> is the host for an event * source::<source>, where <source> is the source for an event * Use the <unique_stanza_name> when creating your entry in transforms.conf. Edit $SPLUNK_HOME/etc/system/local/transforms.conf and set rules to match your props.conf stanza: [<unique_stanza_name>] & nbsp;regex=<your_regex> DEST_KEY=_SYSLOG_ROUTING FORMAT=<unique_group_name> * <unique_stanza_name> must match the name you created in props.conf. * Enter the regex rules in <your_regex> to determine which events get conditionally routed. * DEST_KEY should be set to _SYSLOG_ROUTING to send events via SYSLOG. * Set FORMAT to <unique_group_name>. This should match the syslog group name you create in outputs.conf. ----IndexAndForward Processor----- The IndexAndForward processor determines the default behavior for indexing data on full Splunk. It has the "index" property, which determines whether indexing occurs. When Splunk is not configured as a forwarder, "index" is set to "true". That is, the Splunk instance indexes data by default. When Splunk is configured as a forwarder, the processor turns "index" to "false". That is, the Splunk instance does not index data by default. The IndexAndForward processor has no effect on the universal forwarder, which can never index data. If the [tcpout] stanza configures the indexandforward attribute, the value of that attribute overrides the default value of "index". However, if you set "index" in the [indexandforward] stanza, described below, it supersedes any value set in [tcpout]. 156

[indexandforward] index = [true false] * If set to true, data is indexed. * If set to false, data is not indexed. * Default depends on whether the Splunk instance is configured as a forwarder, modified by any value configured for the indexandforward attribute in [tcpout]. selectiveindexing = [true false] * When index is 'true', all events are indexed. Setting selectiveindexing to 'true' allows you to index only specific events that has key '_INDEX_ AND_FORWARD_ROUTING' set. * '_INDEX_AND_FORWARD_ROUTING' can be set in inputs.conf as: [<input_stanza>] _INDEX_AND_FORWARD_ROUTING = local * Defaults to false. outputs.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains an example outputs.conf. Use this file to configure forwarding in a distributed set up. To use one or more of these configurations, copy the configuration block into outputs.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles Specify a target group for an IP:PORT which consists of a single receiver. This is the simplest possible configuration; it sends data to the host at 10.1.1.197 on port 9997. [tcpout:group1] server=10.1.1.197:9997 Specify a target group for a hostname which consists of a single receiver. [tcpout:group2] server=myhost. Splunk.com:9997 Specify a target group made up of two receivers. In this case, the data will be distributed using AutoLB between these two receivers. You can specify as many receivers as you wish here. You can combine host name and IP if you wish. NOTE: Do not use this configuration with SplunkLightForwarder. [tcpout:group3] server=myhost.splunk.com:9997,10.1.1.197:6666 You can override any of the global configuration values on a per-target group basis. All target groups that do not override a global config will inherit the global config. Send every event to a receiver at foo.splunk.com:9997 with a maximum queue size of 100,500 events. [tcpout:group4] server=foo.splunk.com:9997 heartbeatfrequency=45 maxqueuesize=100500 Clone events to groups indexer1 and indexer2. Also, index all this data locally as well. [tcpout] 157

indexandforward=true [tcpout:indexer1] server=y.y.y.y:9997 [tcpout:indexer2] server=x.x.x.x:6666 Clone events between two data balanced groups. [tcpout:indexer1] server=a.a.a.a:1111, B.B.B.B:2222 [tcpout:indexer2] server=c.c.c.c:3333, D.D.D.D:4444 Syslout output configuration This example sends only events generated by the splunk daemon to a remote syslog host: [syslog:syslog-out1] disabled = false server = X.X.X.X:9099 type = tcp priority = <34> timestampformat = %b %e %H:%M:%S New in 4.0: Auto Load Balancing This example balances output between two indexers running on 1.2.3.4:4433 and 1.2.4.5:4433. To achive this you'd create a DNS entry for splunklb pointing to the two IP addresses of your indexers: $ORIGIN example.com. splunklb A 1.2.3.4 splunklb A 1.2.3.5 [tcpout] defaultgroup = lb [tcpout: lb] server = splunklb.example.com:4433 autolb = true Alternatively, you can autolb sans DNS: [tcpout] defaultgroup = lb [tcpout:lb] server = 1.2.3.4:4433, 1.2.3.5:4433 autolb = true Compression This example sends compressed events to the remote indexer. NOTE: Compression can be enabled TCP or SSL outputs only. The receiver input port should also have compression enabled. [tcpout] server = splunkserver.example.com:4433 compressed = true SSL This example sends events to an indexer via SSL using splunk's self signed cert: 158

[tcpout] server = splunkserver.example.com:4433 sslpassword = password sslcertpath = $SPLUNK_HOME/etc/auth/server.pem sslrootcapath = $SPLUNK_HOME/etc/auth/ca.pem The following example shows how to route events to syslog server This is similar to tcpout routing, but DEST_KEY is set to _SYSLOG_ROUTING 1. Edit $SPLUNK_HOME/etc/system/local/props.conf and set a TRANSFORMS-routing attribute: [default] TRANSFORMS-routing=errorRouting [syslog] TRANSFORMS-routing=syslogRouting 2. Edit $SPLUNK_HOME/etc/system/local/transforms.conf and set errorrouting and syslogrouting rules: [errorrouting] REGEX=error DEST_KEY=_SYSLOG_ROUTING FORMAT=errorGroup [syslogrouting] REGEX=. DEST_KEY=_SYSLOG_ROUTING FORMAT=syslogGroup 3. Edit $SPLUNK_HOME/etc/system/local/outputs.conf and set which syslog outputs go to with servers or groups: [syslog] defaultgroup=everythingelsegroup [syslog:sysloggroup] server = 10.1.1.197:9997 [syslog:errorgroup] server=10.1.1.200:9999 [syslog:everythingelsegroup] server=10.1.1.250:6666 Perform selective indexing and forwarding With a heavy forwarder only, you can index and store data locally, as well as forward the data onwards to a receiving indexer. There are two ways to do this: 1. In outputs.conf: [tcpout] defaultgroup = indexers [indexandforward] index=true selectiveindexing=true [tcpout:indexers] server = 10.1.1.197:9997, 10.1.1.200:9997 2. In inputs.conf, Add _INDEX_AND_FORWARD_ROUTING for any data that you want index locally, and _TCP_ROUTING=<target_group> for data to be forwarded. [monitor:///var/log/messages/] _INDEX_AND_FORWARD_ROUTING=local [monitor:///var/log/httpd/] _TCP_ROUTING=indexers pdf_server.conf 159

다음은 pdf_server.conf의 사양 및 예제 파일입니다. pdf_server.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attributes and values you can use to configure Splunk's pdf server. There is a pdf_server.conf in $SPLUNK_HOME/etc/system/default/. To set custom configurations, place a pdf_server.conf in $SPLUNK_HOME/etc/system/local/. For examples, see pdf_server.conf.example. You must restart the pdf server to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. [settings] * Set general Splunk Web configuration options under this stanza name. * Follow this stanza name with any number of the following attribute/value pairs. * If you do not specify an entry for each attribute, Splunk will use the default value. startwebserver = [0 1] * Set whether or not to start the server. & nbsp; * 0 disables Splunk Web, 1 enables it. * Defaults to 1. httpport = <port_number> * Must be present for the server to start. * If omitted or 0 the server will NOT start an http listener. * If using SSL, set to the HTTPS port number. * Defaults to 9000. enablesplunkwebssl = [True False] * Toggle between http or https. * Set to true to enable https and SSL. * Defaults to False. privkeypath = /certs/privkey.pem cacertpath = /certs/cert. pem * Specify paths and names for Web SSL certs. * Path is relative to $SPLUNK_HOME/share/splunk. supportsslv3only = [True False] * Allow only SSLv3 connections if true. * NOTE: Enabling this may cause some browsers problems. root_endpoint = <URI_prefix_string> * Defines the root URI path on which the appserver will listen. * Default setting is '/'. * For example: if you want to proxy the splunk UI at http://splunk:8000/splunkui, then set root_endpoint = /splunkui static_endpoint = <URI_prefix_string> * Path to static content. * The path here is automatically appended to root_endpoint defined above. * Default is /static. static_dir = <relative_filesystem_path> * The directory that actually holds the static content. * This can be an absolute URL if you want to put it elsewhere. * Default is share/splunk/search_mrsparkle/exposed. enable_gzip = [True False] 160

* Determines if web server applies gzip compression to responses. * Defaults to True. cherrypy HTTP server config server.thread_pool = <integer> * Specifies the numbers of threads the app server is allowed to maintain. * Defaults to 10. server.socket_host = <ip_address> * Host values may be any IPv4 or IPv6 address, or any valid hostname. * The string 'localhost' is a synonym for '127.0.0.1' (or '::1', if your hosts file prefers IPv6). The string '0.0.0.0' is a special IPv4 entry meaning "any active interface" (INADDR_ANY), and '::' is the similar IN6ADDR_ANY for IPv6. * The empty string or None are not allowed. * Defaults to 0.0.0.0 log.access_file = <filename> * Specifies the HTTP access log filename. * Stored in default Splunk /var/log directory. * Defaults to pdf_access.log log.error_file = <filename> * Specifies the HTTP error log filename. * Stored in default Splunk /var/log directory. * Defaults to pdf_service.log log.screen = [True False] * Indicates if runtime output is displayed inside an interactive tty. * Defaults to True request.show_tracebacks = [True False] * Indicates if an exception traceback is displayed to the user on fatal exceptions. * Defaults to True engine. autoreload_on = [True False] * Indicates if the app server will auto-restart if it detects a python file has changed. * Defaults to False tools.sessions.on = True * Indicates if user session support is enabled. * Should always be True tools.sessions.timeout = <integer> * Specifies the number of minutes of inactivity before a user session expires. * Defaults to 60 response.timeout = <integer> * Specifies the number of seconds to wait for the server to complete a response. * Some requests such as uploading large files can take a long time. * Defaults to 7200 tools.sessions.storage_type = [file] tools.sessions.storage_path = <filepath> * Specifies the session information storage mechanisms. * Comment out these two lines to use RAM based sessions instead. * Use an absolute path to store sessions outside of the Splunk directory tree. * Defaults to storage_type=file, storage_path=var/run/splunk tools.decode.on = [True False] * Indicates if all strings that come into CherryPy controller methods are decoded as unicode (assumes UTF-8 encoding). * WARNING: Disabling this will likely break the application, as all incoming strings are assumed to be unicode. * Defaults to True tools.encode.on = [True False] * Encodes all controller method response strings into UTF-8 str objects in Python. 161

* WARNING: Disabling this will likely cause high byte character encoding to fail. * Defaults to True tools.encode.encoding = <codec> * Force all outgoing characters to be encoded into UTF-8. * This only works with tools.encode.on set to True. * By setting this to utf-8, CherryPy's default behavior of observing the Accept-Charset header is overwritten and forces utf-8 output. Only change this if you know a particular browser installation must receive some other character encoding (Latin-1, iso-8859-1, etc.). * WARNING: Change this at your own risk. * Defaults to utf-8 pid_path = <filepath> * Specifies the path to the PID file. * Defaults to var/run/splunk/splunkweb.pid. firefox_cmdline = <cmdline> * Specifies additional arguments to pass to Firefox. * This should normally not be set. max_queue = <integer> * Specifies the maximum size of the backlog of pending report requests. * Once the backlog is reached the server will return an error on receiving additional requests. * Defaults to 10. max_concurrent = <integer> * Specifies the maximum number of copies of Firefox that the report server will use concurrently to render reports. * Increase only if the host machine has multiple cores and plenty of spare memory. * Defaults to 2. Xvfb = <path> * Pathname to the Xvfb program. * Defaults to searching the PATH. xauth = <path> * Pathname to the xauth program. * Defaults to searching the PATH. mcookie = <path> * Pathname to the mcookie program. * Defaults to searching the PATH. appserver_ipaddr = <ip_networks> * If set, the PDF server will only query Splunk app servers on IP addresses within the IP networks specified here. * Networks can be specified as a prefix (10.1.0.0/16) or using a netmask (10.1.0.0/255.255.0.0). * IPv6 addresses are also supported. * Individual IP addresses can also be listed (1.2.3.4). * Multiple networks should be comma separated. * Defaults to accepting any IP address. client_ipaddr = <ip_networks> * If set, the PDF server will only accept requests from hosts whose IP address falls within the IP networks specified here. * Generally this setting should match the appserver_ipaddr setting. * Format matches appserver_ipaddr. * Defaults to accepting any IP address. screenshot_enabled = [True False] * If enabled allows screenshots of the X server to be taken for debugging purposes. * Enabling this is a potential security hole as anyone on an IP address matching client_ipaddr will be able to see reports in progress. * Defaults to False. pdf_server.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 162

This is an example pdf_server.conf. Use this file to configure pdf server process settings. To use one or more of these configurations, copy the configuration block into pdf_server.conf in $SPLUNK_HOME/etc/system/local/. You must restart the pdf server to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles This stanza heading must precede any changes. [settings] Change the default port number: httpport = 12900 Lock down access to the IP address of specific appservers that will utilize the pdf server appserver_ipaddr = 192.168.3.0/24,192.168.2.2 client_ipaddr = 192.168.3.0/24,192.168.2.2 perfmon.conf 다음은 perfmon.conf의 사양 및 예제 파일입니다. perfmon.conf.spec Copyright (C) 2005-2011 Splunk Inc. All Rights Reserved. Version 4.3.4 This file contains possible attribute/value pairs for configuring Splunk's Windows Performance Monitor. There is a perfmon.conf in $SPLUNK_HOME\etc\system\default\. To set custom configurations, place a perfmon.conf in $SPLUNK_HOME\etc\system\local\. For examples, see perfmon.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles ----PERFMON SETTINGS----- Each [Perfmon:] stanza represents an individually configured performance monitoring input. The value of "$NAME" will match what was specified in Splunk Web. Splunk recommends that you use the Manager interface to configure performance monitor inputs because it is easy to mistype the values for Performance Monitor objects, counters and instances. Note: perfmon.conf is for local systems ONLY. When defining performance monitor inputs for remote machines, use wmi.conf. [PERFMON:{NAME}] object = <string> * This is a valid Performance Monitor object as defined within Performance Monitor (for example, "Process," "Server," "PhysicalDisk.") * You can only specify a single valid Performance Monitor object per input. * This attribute is required, and the input will not run if the attribute is not present. * There is no default. counters = <semicolon-separated strings> * This can be a single counter, or multiple valid Performance Monitor counters. * This attribute is required, and the input will not run if the attribute is not present. 163

* '*' is equivalent to all available counters for a given Performance Monitor object. * There is no default. instances = <semicolon-separated strings> * This can be a single instance, or multiple valid Performance Monitor instances. * '*' is equivalent to all available instances for a given Performance Monitor counter. * If applicable instances are available for a counter and this attribute is not present, then all available instances are specified (this is the same as setting 'instances = *'). * If there are no applicable instances for a counter, then this attribute can be safely omitted. * There is no default. interval = <integer> * How often, in seconds, to poll for new data. * This attribute is required, and the input will not run if the attribute is not present. * The recommended setting depends on the Performance Monitor object, counter(s) and instance(s) you are defining in the input, and how much performance data you require for the input. Objects with numerous instantaneous or per-second counters, such as "Memory," "Processor" and "PhysicalDisk" should have shorter interval times specified (anywhere from 1-3 seconds). Less volatile counters such as "Terminal Services," "Paging File" and "Print Queue" can have longer times configured. * There is no default. disabled = [0 1] * Specifies whether or not the input is enabled. * 1 to disable the input, 0 to enable it. * Defaults to 0 (enabled). index = <string> * Specifies the index that this input should send the data to. * This attribute is optional. * If no value is present, defaults to the default index. perfmon.conf.example Copyright (C) 2005-2011 Splunk Inc. All Rights Reserved. Version 4.3.4 This is an example perfmon.conf. These settings are used to configure Splunk's Windows performance monitor scripted input. Refer to perfmon.conf.spec and the documentation at splunk.com for more information about this file. To use one or more of these configurations, copy the configuration block into perfmon.conf in $SPLUNK_HOME\etc\system\local\. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles Important: You must specify the names of objects, counters and instances exactly as they are shown in the Performance Monitor application. Splunk Web is the recommended interface to use to configure performance monitor inputs. Important: These stanzas gather performance data from the local system only. Use wmi.conf for performance monitor metrics on remote systems. Query the PhysicalDisk performance object and gather disk access data for all physical drives installed in the system. Store this data in the "perfmon" index. Note: If the interval attribute is set to 0, Splunk will reset the interval to 1. [PERFMON:LocalPhysicalDisk] interval = 0 164

object = PhysicalDisk counters = Disk Bytes/sec; % Disk Read Time; % Disk Write Time; % Disk Time instances = * disabled = 0 index = PerfMon Gather common memory statistics using the Memory performance object, every 5 seconds. Store the data in the "main" index. Since none of the counters specified have applicable instances, the instances attribute is not required. [PERFMON:LocalMainMemory] interval = 5 object = Memory counters = Committed Bytes; Available Bytes; % Committed Bytes In Use disabled = 0 index = main Gather data on USB activity levels every 10 seconds. Store this data in the default index. [PERFMON:USBChanges] interval = 10 object = USB counters = Usb Control Data Bytes/Sec instances = * disabled = 0 procmon-filters.conf 다음은 procmon-filters.conf의 사양 및 예제 파일입니다. procmon-filters.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 *** DEPRECATED *** This file contains potential attribute/value pairs to use when configuring Windows registry monitoring. The procmon-filters.conf file contains the regular expressions you create to refine and filter the processes you want Splunk to monitor. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles find out if this file is still being used. [<stanza name>] * Name of the filter being defined. proc = <string> * Regex specifying process image that you want Splunk to monitor. type = <string> & nbsp; * Regex specifying the type(s) of process event that you want Splunk to monitor. hive = <string> * Not used in this contexted, but should always have value ".*" procmon-filters.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains example registry monitor filters. To create your own filter, use the information in procmon-filters.conf.spec. To use one or more of these configurations, copy the configuration block into procmon-filters.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. 165

To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles [default] hive =.* [not-splunk-optimize] proc = (?<!splunk-optimize.exe)$ type = create exit image props.conf 다음은 props.conf의 사양 및 예제 파일입니다. props.conf.spec This file contains possible attribute/value pairs for configuring Splunk's processing properties via props.conf. Props.conf is commonly used for: * Configuring linebreaking for multiline events. * Setting up character set encoding. * Allowing processing of binary files. * Configuring timestamp recognition. * Configuring event segmentation. * Overriding Splunk's automated host and source type matching. You can use props.conf to: * Configure advanced (regex-based) host and source type overrides. * Override source type matching for data from a particular source. * Set up rule-based source type recognition. * Rename source types. * Anonymizing certain types of sensitive incoming data, such as credit card or social security numbers, using sed scripts. * Routing specific events to a particular index, when you have multiple indexes. * Creating new index-time field extractions, including header-based field extractions. NOTE: We do not recommend adding to the set of fields that are extracted at index time unless it is absolutely necessary because there are negative performance implications. * Defining new search-time field extractions. You can define basic search-time field extractions entirely through props.conf. But a transforms.conf component is required if you need to create search-time field extractions that involve one or more of the following: * Reuse of the same field-extracting regular expression across multiple sources, source types, or hosts. * Application of more than one regex to the same source, source type, or host. * Delimiter-based field extractions (they involve field-value pairs that are separated by commas, colons, semicolons, bars, or something similar). * Extraction of multiple values for the same field (multivalued field extraction). * Extraction of fields with names that begin with numbers or underscores. * Setting up lookup tables that look up fields from external sources. * Creating field aliases. NOTE: Several of the above actions involve a corresponding transforms.conf configuration. You can find more information on these topics by searching the Splunk documentation (http://docs.splunk.com/documentation/splunk). There is a props.conf in $SPLUNK_HOME/etc/system/default/. To set custom configurations, place a props.conf in $SPLUNK_HOME/etc/ system/local/. For help, see props.conf.example. You can enable configurations changes made to props.conf by typing the following search string in Splunk Web: extract reload=t To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles 166

For more information about using props.conf in conjunction with distributed Splunk deployments, see the Distributed Deployment Manual. GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same & nbsp; attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. [<spec>] * This stanza enables properties for a given <spec>. * A props.conf file can contain multiple stanzas for any number of different <spec>. * Follow this stanza name with any number of the following attribute/value pairs, as appropriate for what you want to do. * If you do not set an attribute for a given <spec>, the default is used. <spec> can be: 1. <sourcetype>, the source type of an event. 2. host::<host>, where <host> is the host, or host-matching pattern, for an event. 3. source::<source>, where <source> is the source, or source-matching pattern, for an event. 4. rule::<rulename>, where <rulename> is a unique name of a source type classification rule. 5. delayedrule::<rulename>, where <rulename> is a unique name of a delayed source type classification rule. These are only considered as a last resort before generating a new source type based on the source seen. **[<spec>] stanza precedence:** For settings that are specified in multiple categories of matching [<spec>] stanzas, [host::<host>] settings override [<sourcetype>] settings. Additionally, [source::<source>] settings override both [host::<host>] and [<sourcetype>] settings. **Considerations for Windows file paths:** When you specify Windows-based file paths as part of a [source::<source>] stanza, you must escape any backslashes contained within the specified file path. Example: [source::c:\\path_to\\file.txt] **[<spec>] stanza patterns:** When setting a [<spec>] stanza, you can use the following regex-type syntax:... recurses through directories until the match is met. * matches anything but / 0 or more times. is equivalent to 'or' ( ) are used to limit scope of. Example: [source::...(?<!tar.)(gz tgz)] **[source::<source>] and [host::<host>] stanza match language:** Match expressions must match the entire name, not just a substring. If you are familiar with regular expressions, match expressions are based on a full implementation of PCRE with the translation of..., * and. Thus. matches a period, * matches non-directory separators, and... matches any number of any characters. For more information see the wildcards section at: http://docs.splunk.com/documentation/splunk/latest/data/specifyinputpathswithwildcards **[<spec>] stanza pattern collisions:** Suppose the source of a given input matches multiple [ source::<source>] patterns. If the [<spec>] stanzas for these patterns each supply distinct settings, Splunk applies all of these settings. However, suppose two [<spec>] stanzas supply the same setting. In this case, Splunk chooses the value to apply based on the ASCII order of the patterns in question. 167

For example, take this source: source::az and the following colliding patterns: [source::...a...] sourcetype = a [source::...z...] sourcetype = z In this case, the settings provided by the pattern [source::...a...] take precedence over those provided by [source::...z...], and sourcetype ends up with "a" as its value. To override this default ASCII ordering, use the priority key: [source::...a...] sourcetype = a priority = 5 [source::...z...] sourcetype = z priority = 10 Assigning a higher priority to the second stanza causes sourcetype to have the value "z". **Case-sensitivity for [<spec>] stanza matching:** By default, [source::<source>] and [<sourcetype>] stanzas match in a case-sensitive manner, while [host::<host>] stanzas match in a case-insensitive manner. This is a convenient default, given that DNS names are case-insensitive. To force a [host::<host>] stanza to match in a case-sensitive manner use the "(?-i)" option in its pattern. For example: [host::foo] FIELDALIAS-a = a AS one [host::(?-i)bar] FIELDALIAS-b = b AS two The first stanza will actually apply to events with host values of "FOO" or "Foo". The second stanza, on the other hand, will not apply to events with host values of "BAR" or "Bar". **Building the final [<spec>] stanza:** The final [<spec>] stanza is built by layering together (1) literal-matching stanzas (stanzas which match the string literally) and (2) any regex-matching stanzas, according to the value of the priority field. If not specified, the default value of the priority key is: * 0 for pattern-matching stanzas. * 100 for literal-matching stanzas. NOTE: Setting the priority key to a value greater than 100 causes the pattern-matched [<spec>] stanzas to override the values of the literal-matching [<spec>] stanzas. The priority key can also be used to resolve collisions between [<sourcetype>] patterns and [host::<host>] patterns. However, be aware that the priority key does *not* affect precedence across <spec> types. For example, [<spec>] stanzas with [source::<source>] patterns take priority over stanzas with [host::<host>] and [<sourcetype>] patterns, regardless of their respective priority key values. ****************************************************************************** The possible attributes/value pairs for props.conf, and their default values, are: 168

****************************************************************************** International characters and character encoding. CHARSET = <string> * When set, Splunk assumes the input from the given [<spec>] is in the specified encoding. * Can only be used as the basis of [<sourcetype>] or [source::<spec>], not [host::<spec>]. * A list of valid encodings can be retrieved using the command "iconv -l" on most *nix systems. * If an invalid encoding is specified, a warning is logged during initial configuration and further input from that [<spec>] is discarded. * If the source encoding is valid, but some characters from the [<spec>] are not valid in the specified encoding, then the characters are escaped as hex (for example, "\xf3"). * When set to "AUTO", Splunk attempts to automatically determine the character encoding and convert text from that encoding to UTF-8. * For a complete list of the character sets Splunk automatically detects, see the online documentation. * Defaults to ASCII. ****************************************************************************** Line breaking ****************************************************************************** Use the following attributes to define the length of a line. TRUNCATE = <non-negative integer> * Change the default maximum line length (in bytes). * Although this is in bytes, line length is rounded down when this would otherwise land mid-character for multi-byte characters. * Set to 0 if you never want truncation (very long lines are, however, often a sign of garbage data). * Defaults to 10000 bytes. LINE_BREAKER = <regular expression> * Specifies a regex that determines how the raw text stream is broken into initial events, before line merging takes place. (See the SHOULD_LINEMERGE attribute, below) * Defaults to ([\r\n]+), meaning data is broken into an event for each line, delimited by any number of carriage return or newline characters. * The regex must contain a capturing group -- a pair of parentheses which defines an identified subcomponent of the match. * Wherever the regex matches, Splunk considers the start of the first capturing group to be the end of the previous event, and considers the end of the first capturing group to be the start of the next event. * The contents of the first capturing group are discarded, and will not be present in any event. You are telling Splunk that this text comes between lines. * NOTE: You get a significant boost to processing speed when you use LINE_BREAKER to delimit multiline events (as opposed to using SHOULD_LINEMERGE to reassemble individual lines into multiline events). * When using LINE_BREAKER to delimit events, SHOULD_LINEMERGE should be set to false, to ensure no further combination of delimited events occurs. * Using LINE_BREAKER to delimit events is discussed in more detail in the web documentation at the following url: http://docs.splunk.com/documentation/splunk/latest/data/indexmulti-lineevents ** Special considerations for LINE_BREAKER with branched expressions & nbsp;** When using LINE_BREAKER with completely independent patterns seperated by pipes, some special issues come into play. EG. LINE_BREAKER = pattern1 pattern2 pattern3 Note, this is not about all forms of alternation, eg there is nothing particular special about example: LINE_BREAKER = ([\r\n])+(one two three) where the top level remains a single expression. A caution: Relying on these rules is NOT encouraged. Simpler is better, in both regular expressions and the complexity of the behavior they rely on. If possible, it is strongly recommended that you reconstruct your regex to have a leftmost capturing group that always matches. It may be useful to use non-capturing groups if you need to express a group 169

before the text to disacard. EG. LINE_BREAKER = (?:one two)(\[r\n]+) * This will match the text one, or two, followed by any amount of newlines or carriage returns. The one-or-two group is non-capturing via the?: prefix and will be skipped by LINE_BREAKER. * A branched expression can match without the first capturing group matching, so the line breaker behavior becomes more complex. Rules: 1: If the first capturing group is part of a match, it is considered the linebreak, as normal. 2: If the first capturing group is not part of a match, the leftmost capturing group which is part of a match will be considered the linebreak. 3: If no capturing group is part of the match, the linebreaker will assume that the linebreak is a zero-length break immediately preceeding the match. Example 1: LINE_BREAKER = end(\n)begin end2(\n) begin2 begin3 * A line ending with 'end' followed a line beginning with 'begin' would match the first branch, and the first capturing group would have a match according to rule 1. That particular newline would become a break between lines. * A line ending with 'end2' followed by a line beginning with 'begin2' would match the second branch and the second capturing group would have a match. That second capturing group would become the linebreak according to rule 2, and the associated newline would become a break between lines. * The text 'begin3' anywhere in the file at all would match the third branch, and there would be no capturing group with a match. A linebreak would be assumed immediately prior to the text 'begin3' so a linebreak would be inserted prior to this text in accordance with rule 3. This means that a linebreak will occur before the text 'begin3' at any point in the text, whether a linebreak character exists or not. Example 2: Example 1 would probably be better written as follows. This is not equivalent for all possible files, but for most real files would be equivalent. LINE_BREAKER = end2?(\n)begin(2 3)? LINE_BREAKER_LOOKBEHIND = <integer> * When there is leftover data from a previous raw chunk, LINE_BREAKER_LOOKBEHIND indicates the number of bytes before the end of the raw chunk (with the next chunk concatenated) that Splunk applies the LINE_BREAKER regex. You may want to increase this value from its default if you are dealing with especially large or multiline events. * Defaults to 100 (bytes). Use the following attributes to specify how multiline events are handled. SHOULD_LINEMERGE = [true false] * When set to true, Splunk combines several lines of data into a single multiline event, based on the following configuration attributes. * Defaults to true. When SHOULD_LINEMERGE is set to true, use the following attributes to define how Splunk builds multiline events. BREAK_ONLY_BEFORE_DATE = [true false] * When set to true, Splunk creates a new event only if it encounters a new line with a date. * Note, when using DATETIME_CONFIG = CURRENT or NONE, this setting is not meaningful, as timestamps are not identified. * Defaults to true. BREAK_ONLY_BEFORE = <regular expression> * When set, Splunk creates a new event only if it encounters a new line that matches the regular expression. * Defaults to empty. MUST_BREAK_AFTER = <regular expression> * When set and the regular expression matches the current line, Splunk creates a new event for 170

the next input line. * Splunk may still break before the current line if another rule matches. * Defaults to empty. MUST_NOT_BREAK_AFTER = <regular expression> * When set and the current line matches the regular expression, Splunk does not break on any subsequent lines until the MUST_BREAK_AFTER expression matches. * Defaults to empty. MUST_NOT_BREAK_BEFORE = <regular expression> * When set and the current line matches the regular expression, Splunk does not break the last event before the current line. * Defaults to empty. MAX_EVENTS = <integer> * Specifies the maximum number of input lines to add to any event. * Splunk breaks after the specified number of lines are read. * Defaults to 256 (lines). ****************************************************************************** Timestamp extraction configuration ****************************************************************************** DATETIME_CONFIG = <filename relative to $SPLUNK_HOME> * Specifies which file configures the timestamp extractor, which identifies timestamps from the event text. * This configuration may also be set to "NONE" to prevent the timestamp extractor from running or "CURRENT" to assign the current system time to each event. * "CURRENT" will set the time of the event to the time that the event was merged from lines, or worded differently, the time it passed through the aggregator processor. * "NONE" will leave the event time set to whatever time was selected by the input layer * For data sent by splunk forwarders over the splunk protocol, the input layer will be the time that was selected on the forwarder by its input behavior (as below). * For file-based inputs (monitor, batch) the time chosen will be the modification timestamp on the file being read. * For other inputs, the time chosen will be the current system time when the event is read from the pipe/socket/etc. * Both "CURRENT" and "NONE" explicitly disable the per-text timestamp identification, so the default event boundary detection (BREAK_ONLY_BEFORE_DATE = true) is likely to not work as desired. When using these settings, use SHOULD_LINEMERGE and/or the BREAK_ONLY_*, MUST_BREAK_* settings to control event merging. * Defaults to /etc/datetime.xml (for example, $SPLUNK_HOME/etc/datetime.xml). TIME_PREFIX = <regular expression> * If set, splunk scans the event text for a match for this regex in event text before attempting to extract a timestamp. * The timestamping algorithm only looks for a timestamp in the text following the end of the first regex match. * For example, if TIME_PREFIX is set to "abc123", only text following the first occurrence of the text abc123 will be used for timestamp extraction. * If the TIME_PREFIX cannot be found in the event text, timestamp extraction will not occur. * Defaults to empty. MAX_TIMESTAMP_LOOKAHEAD = <integer> * Specifies how far (in characters) into an event Splunk should look for a timestamp. * This constraint to timestamp extraction is applied from the point of the TIME_PREFIX-set location. * For example, if TIME_PREFIX positions a location 11 characters into the event, and MAX_TIMESTAMP_LOOKAHEAD is set to 10, timestamp extraction will be constrained to characters 11 through 20. * If set to 0, or -1, the length constraint for timestamp recognition is effectively disabled. This can have negative performance implications which scale with the length of input lines (or with event size when LINE_BREAKER is redefined for event splitting). * Defaults to 150 (characters). TIME_FORMAT = <strptime-style format> * Specifies a strptime format string to extract the date. * strptime is an industry standard for designating time formats. * For more information on strptime, see "Configure timestamp recognition" in the online documentation. * TIME_FORMAT starts reading after the TIME_PREFIX. If both are specified, the TIME_PREFIX 171

regex must match up to and including the character before the TIME_FORMAT date. * For good results, the <strptime-style format> should describe the day of the year and the time of day. * Defaults to empty. TZ = <timezone identifier> * The algorithm for determining the time zone for a particular event is as follows: * If the event has a timezone in its raw text (for example, UTC, -08:00), use that. * If TZ is set to a valid timezone string, use that. * Otherwise, use the timezone of the system that is running splunkd. * Defaults to empty. MAX_DAYS_AGO = <integer> * Specifies the maximum number of days past, from the current date, that an extracted date can be valid. * For example, if MAX_DAYS_AGO = 10, Splunk ignores dates that are older than 10 days ago. * Defaults to 2000 (days), maximum 10951. * IMPORTANT: If your data is older than 2000 days, increase this setting. MAX_DAYS_HENCE = <integer> * Specifies the maximum number of days in the future from the current date that an extracted date can be valid. * For example, if MAX_DAYS_HENCE = 3, dates that are more than 3 days in the future are ignored. * The default value includes dates from one day in the future. * If your servers have the wrong date set or are in a timezone that is one day ahead, increase this value to at least 3. * Defaults to 2 (days), maximum 10950. * IMPORTANT:False positives are less likely with a tighter window, change with caution. MAX_DIFF_SECS_AGO = <integer> * If the event's timestamp is more than <integer> seconds BEFORE the previous timestamp, only accept the event if it has the same exact time format as the majority of timestamps from the source. * IMPORTANT: If your timestamps are wildly out of order, consider increasing this value. * Note: if the events contain time but not date (date determined another way, such as from a filename) this check will only consider the hour. (No one second granularity for this purpose.) * Defaults to 3600 (one hour), maximum 2147483646. MAX_DIFF_SECS_HENCE = <integer> * If the event's timestamp is more than <integer> seconds AFTER the previous timestamp, only accept the event if it has the same exact time format as the majority of timestamps from the source. * IMPORTANT: If your timestamps are wildly out of order, or you have logs that are written less than once a week, consider increasing this value. * Defaults to 604800 (one week), maximum 2147483646. ****************************************************************************** Field extraction configuration ****************************************************************************** NOTE: If this is your first time configuring field extractions in props.conf, review the following information first. There are three different "field extraction types" that you can use to configure field extractions: TRANSFORMS, REPORT, and EXTRACT. They differ in two significant ways: 1) whether they create indexed fields (fields extracted at index time) or extracted fields (fields extracted at search time), and 2), whether they include a reference to an additional component called a "field transform," which you define separately in transforms.conf. **Field extraction configuration: index time versus search time** Use the TRANSFORMS field extraction type to create index-time field extractions. Use the REPORT or EXTRACT field extraction types to create search-time field extractions. NOTE: Index-time field extractions have performance implications. Creating additions to Splunk's default set of indexed fields is ONLY recommended in specific circumstances. Whenever possible, extract fields only at search time. There are times when you may find that you need to change or add to your set of indexed fields. For example, you may have situations where certain search-time field extractions are noticeably impacting search performance. This can happen when the value of a search-time extracted field exists outside of the field more often than not. For example, if you commonly search a large event set with the expression company_id=1 but the value 1 occurs in many 172

events that do *not* have company_id=1, you may want to add company_id to the list of fields extracted by Splunk at index time. This is because at search time, Splunk will want to check each instance of the value 1 to see if it matches company_id, and that kind of thing slows down performance when you have Splunk searching a large set of data. Conversely, if you commonly search a large event set with expressions like company_id!=1 or NOT company_id=1, and the field company_ id nearly *always* takes on the value 1, you may want to add company_id to the list of fields extracted by Splunk at index time. For more information about index-time field extraction, search the documentation for "index-time extraction." For more information about search-time field extraction, search the online documentation for "search-time extraction." **Field extraction configuration: field transforms vs. "inline" (props.conf only) configs** The TRANSFORMS and REPORT field extraction types reference an additional component called a field transform, which you define separately in transforms.conf. Field transforms contain a field-extracting regular exprexsion and other attributes that govern the way that the transform extracts fields. Field transforms are always created in conjunction with field extraction stanzas in props.conf; they do not stand alone. The EXTRACT field extraction type is considered to be " inline," which means that it does not reference a field transform. It contains the regular expression that Splunk uses to extract fields at search time. You can use EXTRACT to define a field extraction entirely within props.conf--no transforms.conf component is required. **Search-time field extractions: Why use REPORT if EXTRACT will do?** It's a good question. And much of the time, EXTRACT is all you need for search-time field extraction. But when you build search-time field extractions, there are specific cases that require the use of REPORT and the field transform that it references. Use REPORT if you want to: * Reuse the same field-extracting regular expression across multiple sources, source types, or hosts. If you find yourself using the same regex to extract fields across several different sources, source types, and hosts, set it up as a transform, and then reference it in REPORT extractions in those stanzas. If you need to update the regex you only have to do it in one place. Handy! * Apply more than one field-extracting regular expression to the same source, source type, or host. This can be necessary in cases where the field or fields that you want to extract from a particular source, source type, or host appear in two or more very different event patterns. * Use a regular expression to extract fields from the values of another field (also & nbsp; referred to as a "source key"). * Set up delimiter-based field extractions. Useful if your event data presents field-value pairs (or just field values) separated by delimiters such as commas, spaces, bars, and so on. * Configure extractions for multivalue fields. You can have Splunk append additional values to a field as it finds them in the event data. * Extract fields with names beginning with numbers or underscores. Ordinarily, Splunk's key cleaning functionality removes leading numeric characters and underscores from field names. If you need to keep them, configure your field transform to turn key cleaning off. * Manage formatting of extracted fields, in cases where you are extracting multiple fields, or are extracting both the field name and field value. **Precedence rules for TRANSFORMS, REPORT, and EXTRACT field extraction types** * For each field extraction, Splunk takes the configuration from the highest precedence configuration stanza (see precedence rules at the beginning of this file). * If a particular field extraction is specified for a source and a source type, the field extraction for source wins out. * Similarly, if a particular field extraction is specified in../local/ for a <spec>, it overrides that field extraction in../default/. TRANSFORMS-<name> = <transform_stanza_name>, <transform_stanza_name2>,... * Used for creating indexed fields (index-time field extractions). * <name> is any unique name you want to give to your stanza to identify its namespace. * <transform_stanza_name> is the name of your stanza from transforms.conf. * Use a comma-separated list to apply multiple transform stanzas to a single TRANSFORMS extraction. Splunk applies them in the list order. For example, this sequence ensures that 173

the [yellow] transform stanza gets applied first, then [blue], and then [red]: [source::color_logs] TRANSFORM-colorchange = yellow, blue, red REPORT-<name> = <transform_stanza_name>, <transform_stanza_name2>,... * Used for creating extracted fields (search-time field extractions) that reference one or more transforms.conf stanzas. * <name> is any unique name you want to give to your stanza to identify its namespace. * <transform_stanza_name> is the name of your stanza from transforms.conf. * Use a comma-separated list to apply multiple transform stanzas to a single REPORT extraction. Splunk applies them in the list order. For example, this sequence insures that the [yellow] transform stanza gets applied first, then [blue], and then [red]: [source::color_logs] REPORT-colorchange = yellow, blue, red EXTRACT-<name> = [<regex> <regex> in <src_field>] * Used to create extracted fields (search-time field extractions) that do not reference transforms.conf stanzas. * Performs a regex-based field extraction from the value of the source field. * The <regex> is required to have named capturing groups. When the <regex> matches, the named capturing groups and their values are added to the event. * Use '<regex> in <src_field>' to match the regex against the values of a specific field. Otherwise it just matches against _raw (all raw event data). * NOTE: <src_field> can only contain alphanumeric characters (a-z, A-Z, and 0-9). * If your regex needs to end with 'in <string>' where <string> is *not* a field name, change the regex to end with '[i]n <string>' to ensure that Splunk doesn't try to match <string> to a field name. KV_MODE = [none auto multi json xml] * Used for search-time field extractions only. * Specifies the field/value extraction mode for the data. * Set KV_MODE to one of the following: * none: if you want no field/value extraction to take place. & nbsp; * auto: extracts field/value pairs separated by equal signs. * multi: invokes the multikv search command to expand a tabular event into multiple events. * xml : automatically extracts fields from XML data. * json: automatically extracts fields from JSON data. * Setting to 'none' can ensure that one or more user-created regexes are not overridden by automatic field/value extraction for a particular host, source, or source type, and also increases search performance. * Defaults to auto. * The 'xml' and 'json' modes will not extract any fields when used on data that isn't of the correct format (JSON or XML). CHECK_FOR_HEADER = [true false] * Used for index-time field extractions only. * Set to true to enable header-based field extraction for a file. * If the file has a list of columns and each event contains a field value (without field name), Splunk picks a suitable header line to use to for extracting field names. * Can only be used on the basis of sourcetype, or source::<spec>, not host::<spec>. * If the file has a list of columns and each event contains a field value (without a field name), Splunk picks a suitable header line to use for field extraction. * Can only be used on the basis of [<sourcetype>] or [source::<spec>], not [host::<spec>]. * Disabled when LEARN_SOURCETYPE = false. * Will cause the indexed source type to have an appended numeral; for example, sourcetype-2, sourcetype-3, and so on. * The field names are stored in etc/apps/learned/local/props.conf. * Because of this, this feature will not work in most environments where the data is forwarded. * Defaults to false. SEDCMD-<name> = <sed script> * Only used at index time. * Commonly used to anonymize incoming data at index time, such as credit card or social security numbers. For more information, search the online documentation for "anonymize data." * Used to specify a sed script which Splunk applies to the _raw field. * A sed script is a space-separated list of sed commands. Currently the following subset of sed commands is supported: * replace (s) and character substitution (y). * Syntax: * replace - s/regex/replacement/flags 174

* regex is a perl regular expression (optionally containing capturing groups). * replacement is a string to replace the regex match. Use \n for backreferences, where "n" is a single digit. * flags can be either: g to replace all matches, or a number to replace a specified match. * substitute - y/string1/string2/ * substitutes the string1[i] with string2[i] LOOKUP-<name> = $TRANSFORM (<match_field> (AS <match_field_in_event>)?)+ (OUTPUT OUTPUTNEW (<output_field> (AS <output_field_in_event>)? )+ )? * At search time, identifies a specific lookup table and describes how that lookup table should be applied to events. * <match_field> specifies a field in the lookup table to match on. * By default Splunk looks for a field with that same name in the event to match with (if <match_field_in_event> is not provided) * You must provide at least one match field. Multiple match fields are allowed. * <output_field> specifies a field in the lookup entry to copy into each matching event, where it will be in the field <output_field_in_event>. * If you do not specify an <output_field_in_event> value, Splunk uses <output_field>. * A list of output fields is not required. * If they are not provided, all fields in the lookup table except for the match fields ( and the timestamp field if it is specified) will be output for each matching event. * If the output field list starts with the keyword "OUTPUTNEW" instead of "OUTPUT", then each outputfield is only written out if it did not previous exist. Otherwise, the output fields are always overridden. Any event that has all of the <match_field> values but no matching entry in the lookup table clears all of the output fields. NOTE that OUTPUTNEW behavior has changed since 4.1.x (where *none* of the output fields were written to if *any* of the output fields previously existed) * The LOOKUP- prefix is actually case-insensitive. Acceptable variants include: LOOKUP_<name> = [...] LOOKUP<name> = [...] lookup_<name> = [...] lookup<name> = [...] FIELDALIAS-<class> = (<orig_field_name> AS <new_field_name>)+ * Use this to apply aliases to a field. The original field is not removed. This just means that the original field can be searched on using any of its aliases. * You can create multiple aliases for the same field. * <orig_field_name> is the original name of the field. * <new_field_name> is the alias to assign to the field. * You can include multiple field alias renames in the same stanza. * Field aliasing is performed at search time, after field extraction, but before lookups. This means that: * Any field extracted at search time can be aliased. * You can specify a lookup based on a field alias. EVAL-<fieldname> = <eval statement> * Use this to automatically run the <eval statement> and assign the value of the output to <fieldname>. This feature is referred to as 'calculated fields'. * When multiple EVAL-* statements are specified, they behave as if they are run in parallel, rather than in any particular sequence. This means that if you have e.g. EVAL-x=y*2, EVAL-y=100, x will be assigned the original value of y * 2, not the value of y after it is set to 100. * All field calculations will done after field aliasing but before lookups. This means you can lookup based on the value of a calculated field ****************************************************************************** Binary file configuration ****************************************************************************** NO_BINARY_CHECK = [true false] * When set to true, Splunk processes binary files. * Can only be used on the basis of [<sourcetype>], or [source::<source>], not [host::<host>]. * Defaults to false (binary files are ignored). ****************************************************************************** Segmentation configuration ****************************************************************************** SEGMENTATION = <segmenter> * Specifies the segmenter from segmenters.conf to use at index time for the host, source, or sourcetype specified by <spec> in the stanza heading. 175

* Defaults to indexing. SEGMENTATION-<segment selection> = <segmenter> * Specifies that Splunk Web should use the specific segmenter (from segmenters.conf) for the given <segment selection> choice. * Default <segment selection> choices are: all, inner, outer, raw. For more information see the Admin Manual. * Do not change the set of default <segment selection> choices, unless you have some overriding reason for doing so. In order for a changed set of <segment selection> choices to appear in Splunk Web, you will need to edit the Splunk Web UI. ****************************************************************************** File checksum configuration ****************************************************************************** CHECK_METHOD = [endpoint_md5 entire_md5 modtime] * Set CHECK_METHOD endpoint_md5 to have Splunk checksum of the first and last 256 bytes of a file. When it finds matches, Splunk lists the file as already indexed and indexes only new data, or ignores it if there is no new data. * Set CHECK_METHOD = entire_md5 to use the checksum of the entire file. * Set CHECK_METHOD = modtime to check only the modification time of the file. * Settings other than endpoint_md5 cause Splunk to index the entire file for each detected change. * Defaults to endpoint_md5. * Important: this option is only valid for [source::<source>] stanzas. initcrclength = <integer> * See documentation in inputs.conf.spec. * IMPORTANT: In props.conf, this option is only valid for [source::<source>] stanzas. ****************************************************************************** Small file settings ****************************************************************************** PREFIX_SOURCETYPE = [true false] * NOTE: this attribute is only relevant to the "[too_small]" sourcetype. * Determines the source types that are given to files smaller than 100 lines, and are therefore not classifiable. * PREFIX_SOURCETYPE = false sets the source type to "too_small." * PREFIX_SOURCETYPE = true sets the source type to "<sourcename>-too_small", where "<sourcename>" is a cleaned up version of the filename. * The advantage of PREFIX_SOURCETYPE = true is that not all small files are classified as the same source type, and wildcard searching is often effective. * For example, a Splunk search of "sourcetype=access*" will retrieve "access" files as well as "access-too_small" files. * Defaults to true. ****************************************************************************** Sourcetype configuration ****************************************************************************** sourcetype = <string> * Can only be set for a [source::...] stanza. * Anything from that <source> is assigned the specified source type. * Defaults to empty. The following attribute/value pairs can only be set for a stanza that begins with [<sourcetype>]: rename = <string> * Renames [<sourcetype>] as <string> * With renaming, you can search for the [<sourcetype>] with sourcetype=<string> * To search for the original source type without renaming it, use the field _sourcetype. * Data from a a renamed sourcetype will only use the search-time configuration for the target sourcetype. Field extractions (REPORTS/EXTRAXCT) for this stanza sourcetype will be ignored. * Defaults to empty. invalid_cause = <string> * Can only be set for a [<sourcetype>] stanza. * Splunk does not index any data with invalid_cause set. * Set <string> to "archive" to send the file to the archive processor (specified in 176

unarchive_cmd). * Set to any other string to throw an error in the splunkd.log if you are running Splunklogger in debug mode. * Defaults to empty. is_valid = [true false] * Automatically set by invalid_cause. * DO NOT SET THIS. * Defaults to true. unarchive_cmd = <string> * Only called if invalid_cause is set to "archive". * This field is only valid on [source::<source>] stanzas. * <string> specifies the shell command to run to extract an archived source. * Must be a shell command that takes input on stdin and produces output on stdout. * Use _auto for Splunk's automatic handling of archive files (tar, tar.gz, tgz, tbz, tbz2, zip) * Defaults to empty. unarchive_sourcetype = <string> * Sets the source type of the contents of the matching archive file. Use this field instead of the sourcetype field to set the source type of archive files that have the following extensions: gz, bz, bz2, Z. * If this field is empty (for a matching archive file props lookup) Splunk strips off the archive file's extension (.gz, bz etc) and lookup another stanza to attempt to determine the sourcetype. * Defaults to empty. LEARN_SOURCETYPE = [true false] * Determines whether learning of known or unknown sourcetypes is enabled. * For known sourcetypes, refer to LEARN_MODEL. * For unknown sourcetypes, refer to the rule:: and delayedrule:: configuration (see below). * Setting this field to false disables CHECK_FOR_HEADER as well (see above). * Defaults to true. LEARN_MODEL = [true false] * For known source types, the file classifier adds a model file to the learned directory. * To disable this behavior for diverse source types (such as sourcecode, where there is no good exemplar to make a sourcetype) set LEARN_MODEL = false. * Defaults to false. maxdist = <integer> * Determines how different a source type model may be from the current file. * The larger the maxdist value, the more forgiving Splunk will be with differences. * For example, if the value is very small (for example, 10), then files of the specified sourcetype should not vary much. * A larger value indicates that files of the given source type can vary quite a bit. * If you're finding that a source type model is matching too broadly, reduce its maxdist value by about 100 and try again. If you're finding that a source type model is being too restrictive, increase its maxdist value by about 100 and try again. * Defaults to 300. rule:: and delayedrule:: configuration MORE_THAN<optional_unique_value>_<number> = <regular expression> (empty) LESS_THAN<optional_unique_value>_<number> = <regular expression> (empty) An example: [rule::bar_some] sourcetype = source_with_lots_of_bars if more than 80% of lines have "----", but fewer than 70% have "" declare this a "source_with_lots_of_bars" MORE_THAN_80 = ---- LESS_THAN_70 = A rule can have many MORE_THAN and LESS_THAN patterns, and all are required for the rule to match. ****************************************************************************** Annotation Processor configured ****************************************************************************** 177

ANNOTATE_PUNCT = [true false] * Determines whether to index a special token starting with "punct::" * The "punct::" key contains punctuation in the text of the event. It can be useful for finding similar events * If it is not useful for your dataset, or if it ends up taking too much space in your index it is safe to disable it * Defaults to true. ****************************************************************************** Header Processor configuration ****************************************************************************** HEADER_MODE = <empty> always firstline none * Determines whether to use the inline ***SPLUNK*** directive to rewrite index-time fields. * If "always", any line with ***SPLUNK*** can be used to rewrite index-time fields. * If "firstline", only the first line can be used to rewrite index-time fields. * If "none", the string ***SPLUNK*** is treated as normal data. * If <empty>, scripted inputs take the value "always" and file inputs take the value "none". * Defaults to <empty>. ****************************************************************************** Internal settings ****************************************************************************** NOT YOURS. DO NOT SET. _actions = <string> * Internal field used for user-interface control of objects. * Defaults to "new,edit,delete". pulldown_type = <bool> * Internal field used for user-interface control of source types. * Defaults to empty. given_type = <string> * Internal field used by the CHECK_FOR_HEADER feature to remember the original sourcetype. * Default to unset. props.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 The following are example props.conf configurations. Configure properties for your data. To use one or more of these configurations, copy the configuration block into props.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles Line merging settings The following example linemerges source data into multi-line events for apache_error sourcetype. [apache_error] SHOULD_LINEMERGE = True Settings for tuning The following example limits the amount of characters indexed per event from host::small_events. [host::small_ events] 178

TRUNCATE = 256 The following example turns off DATETIME_CONFIG (which can speed up indexing) from any path that ends in /mylogs/*.log. In addition, the default splunk behavior of finding event boundaries via per-event timestamps can't work with NONE, so we disable SHOULD_LINEMERGE, essentially declaring that all events in this file are single-line. [source::.../mylogs/*.log] DATETIME_CONFIG = NONE SHOULD_LINEMERGE = false Timestamp extraction configuration The following example sets Eastern Time Zone if host matches nyc*. [host::nyc*] TZ = US/Eastern The following example uses a custom datetime.xml that has been created and placed in a custom app directory. This sets all events coming in from hosts starting with dharma to use this custom file. [host::dharma*] DATETIME_CONFIG = <etc/apps/custom_time/datetime.xml> Transform configuration The following example creates a search field for host::foo if tied to a stanza in transforms.conf. [host::foo] TRANSFORMS-foo=foobar The following example creates an extracted field for sourcetype access_combined if tied to a stanza in transforms.conf. [eventtype::my_custom_eventtype] REPORT-baz = foobaz The following stanza extracts an ip address from _raw [my_sourcetype] EXTRACT-extract_ip = (?<ip>\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}) The following example shows how to configure lookup tables [my_lookuptype] LOOKUP-foo = mylookuptable userid AS myuserid OUTPUT username AS myusername The following shows how to specify field aliases FIELDALIAS-foo = user AS myuser id AS myid Sourcetype configuration The following example sets a sourcetype for the file web_access.log for a unix path. [source::.../web_access.log] sourcetype = splunk_web_access The following example sets a sourcetype for the Windows file iis6.log. Note: Backslashes within Windows file 179

paths must be escaped. [source::...\\iis\\iis6.log] sourcetype = iis_access The following example untars syslog events. [syslog] invalid_cause = archive unarchive_cmd = gzip -cd - The following example learns a custom sourcetype and limits the range between different examples with a smaller than default maxdist. [custom_sourcetype] LEARN_MODEL = true maxdist = 30 rule:: and delayedrule:: configuration The following examples create sourectype rules for custom sourcetypes with regex. [rule::bar_some] sourcetype = source_with_lots_of_bars MORE_THAN_80 = ---- [delayedrule::baz_some] sourcetype = my_sourcetype LESS_ THAN_70 = File configuration Binary file configuration The following example eats binary files from the sourcetype "imported_records". [imported_records] NO_BINARY_CHECK = true File checksum configuration The following example checks the entirety of every file in the web_access dir rather than skipping files that appear to be the same. [source::.../web_access/*] CHECK_METHOD = entire_md5 pubsub.conf 다음은 pubsub.conf의 사양 및 예제 파일입니다. pubsub.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attributes and values for configuring a client of the PubSub system (broker). To set custom configurations, place a pubsub.conf in $SPLUNK_HOME/etc/system/local/. For examples, see pubsub.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS 180

Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. ****************************************************************** Configure the physical location where deploymentserver is running. This configuration is used by the clients of the pubsub system. ****************************************************************** [pubsub-server:deploymentserver] disabled = <false or true> * defaults to 'false' targeturi = <IP:Port or hostname:port or "direct"> * specify either the url of a remote server in case the broker is remote, or just the keyword "direct" when broker is in-process. & nbsp;* It is usually a good idea to co-locate the broker and the Deployment Server on the same Splunk. In such a configuration, all * deployment clients would have targeturi set to deploymentserver:port. ****************************************************************** The following section is only relevant to Splunk developers. ****************************************************************** This "direct" configuration is always available, and cannot be overridden. [pubsub-server:direct] disabled = false targeturi = direct [pubsub-server:<logicalname>] * It is possible for any Splunk to be a broker. If you have multiple brokers, assign a logicalname that is used by the clients to refer to it. disabled = <false or true> * defaults to 'false' targeturi = <IP:Port or hostname:port or "direct"> & nbsp;* The Uri of a Splunk that is being used as a broker. * The keyword "direct" implies that the client is running on the same Splunk instance as the broker. pubsub.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 [pubsub-server:deploymentserver] disabled=false targeturi=somehost:8089 [pubsub-server:internalbroker] disabled=false targeturi=direct regmon-filters.conf 다음은 regmon-filters.conf의 사양 및 예제 파일입니다. regmon-filters.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains potential attribute/value pairs to use when 181

configuring Windows Registry monitoring. The regmon-filters.conf file contains the regular expressions you create to refine and filter the registry key paths you want Splunk to monitor. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. [<stanza name>] * The name of the filter being defined. proc = <regular expression> * If set, is matched against the process name which performed the Registry access. * Events generated by processes that do not match the regular expression are filtered out. * Events generated by processes that match the regular expression are passed through. * There is no default. hive = <regular expression> * If set, is matched against the registry key which was accessed. * Events generated by processes that do not match the regular expression are filtered out. * Events generated by processes that match the regular expression are passed through. * There is no default. type = <string> * A regular expression that specifies the type(s) of Registry event(s) that you want Splunk to monitor. * There is no default. baseline = [0 1] * Specifies whether or not to establish a baseline value for the Registry keys that this filter defines. * 1 to establish a baseline, 0 not to establish one. * Defaults to 0 (do not establish a baseline). baseline_interval = <integer> * Splunk will only ever take a registry baseline only on registry monitoring startup. * On startup, a baseline will be taken if registry monitoring was not running for baseline_interval seconds. For example, if splunk was down for some days, or if registry monitoring was disabled for some days. * Defaults to 86400 (1 day). disabled = [0 1] * Specifies whether the input is enabled or not. * 1 to disable the input, 0 to enable it. * Defaults to 0 (enabled). index = <string> * Specifies the index that this input should send the data to. * This attribute is optional. * If no value is present, defaults to the default index. regmon-filters.conf.example 182

Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains example filters for use by the Splunk Registry monitor scripted input. To use one or more of these configurations, copy the configuration block into regmon-filters.conf in $SPLUNK_HOME/etc/search/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles The following are examples of Registry monitor filters. To create your own filter, modify the values by following the specification outlined in regmon-filters.conf.spec. [default] disabled = 1 baseline = 0 baseline_interval = 86400 Monitor all registry keys under the HKEY_CURRENT_USER Registry hive for "set," " create," "delete," and "rename" events created by all processes. Store the events in the "regmon" splunk index [User keys] proc = c:\\.* hive = HKU\\.* type = set create delete rename index = regmon restmap.conf 다음은 restmap.conf의 사양 및 예제 파일입니다. restmap.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attribute and value pairs for creating new Representational State Transfer (REST) endpoints. There is a restmap.conf in $SPLUNK_HOME/etc/system/default/. To set custom configurations, place a restmap.conf in $SPLUNK_HOME/etc/system/local/. For help, see restmap.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles NOTE: You must register every REST endpoint via this file to make it available. Global stanza [global] * This stanza sets global configurations for all REST endpoints. * Follow this stanza name with any number of the following attribute/value pairs. allowgetauth=[true false] * Allow user/password to be passed as a GET parameter to endpoint services/auth/login. * Setting this to true, while convenient, may result in user/password getting logged as cleartext in Splunk's logs *and* any proxy servers in between. * Defaults to false. pythonhandlerpath=<path> * Path to 'main' python script handler. * Used by the script handler to determine where the actual 'main' script is located. * Typically, you should not need to change this. * Defaults to $SPLUNK_HOME/bin/rest_handler.py. 183

Applicable to all REST stanzas Stanza definitions below may supply additional information for these. [<rest endpoint name>:<endpoint description string>] match=<path> * Specify the URI that calls the handler. * For example if match=/foo, then https://$server:$port/services/foo calls this handler. * NOTE: You must start your path with a /. requireauthentication=[true false] * This optional attribute determines if this endpoint requires authentication. * Defaults to 'true'. capability=<capabilityname> capability.<post delete get put>=<capabilityname> * Depending on the HTTP method, check capabilities on the authenticated session user. * If you use 'capability.post delete get put,' then the associated method is checked against the authenticated user's role. * If you just use 'capability,' then all calls get checked against this capability (regardless of the HTTP method). Per-endpoint stanza Specify a handler and other handler-specific settings. The handler is responsible for implementing arbitrary namespace underneath each REST endpoint. [script:<uniquename>] * NOTE: The uniquename must be different for each handler. * Call the specified handler when executing this endpoint. * The following attribute/value pairs support the script handler. scripttype=python * Tell the system what type of script to execute when using this endpoint. * Defaults to python. * Python is currently the only option for scripttype. handler=<script>.<classname> * The name and class name of the file to execute. * The file *must* live in an application's bin subdirectory. * For example, $SPLUNK_HOME/etc/apps/<APPNAME>/bin/TestHandler.py has a class called MyHandler (which, in the case of python must be derived from a base class called 'splunk.rest.baseresthandler'). The tag/value pair for this is: "handler=testhandler.myhandler". xsl=<path to XSL transform file> * Optional. * Perform an optional XSL transform on data returned from the handler. * Only use this if the data is XML. script=<path to a script executable> * Optional. * Execute a script which is *not* derived from 'splunk.rest.baseresthandler'. * Put the path to that script here. * This is rarely used. * Do not use this unless you know what you are doing. output_modes=<csv list> * Specifies which output formats can be requested from this endpoint. * Valid values are: json, xml. * Defaults to xml. 'admin' The built-in handler for the Extensible Administration Interface. Exposes the listed EAI handlers at the given URL. 184

[admin:<uniquename>] match=<partial URL> * URL which, when accessed, will display the handlers listed below. members=<csv list> * List of handlers to expose at this URL. * See https://localhost:8089/services/admin for a list of all possible handlers. 'admin_ external' Register Python handlers for the Extensible Administration Interface. Handler will be exposed via its "uniquename". [admin_external:<uniquename>] handlertype=<script type> * Currently only the value 'python' is valid. handlerfile=<unique filename> * Script to execute. * For bin/myawesomeapphandler.py, specify only myawesomeapphandler.py. handleractions=<comma separated list> * List of EAI actions supported by this handler. * Valid values are: create, edit, list, delete, _reload. Validation stanzas Add stanzas using the following definition to add arg validation to the appropriate EAI handlers. [validation:<handler-name>] <field> = <validation-rule> * <field> is the name of the field whose value would be validated when an object is being saved. * <validation-rule> is an eval expression using the validate() function to evaluate arg correctness and return an error message. If you use a boolean returning function, a generic message is displayed. * <handler-name> is the name of the REST endpoint which this stanza applies to handler-name is what is used to access the handler via /servicesns/<user>/<app/admin/<handler-name>. * For example: * action.email.sendresult = validate( isbool('action.email.sendresults'), "'action.email.sendresults' must be a boolean value"). * NOTE: use ' or $ to enclose field names that contain non alphanumeric characters. 'eai' Settings to alter the behavior of EAI handlers in various ways. These should not need to be edited by users. [eai:<eai handler name>] showindirsvc = [true false] * Whether configurations managed by this handler should be enumerated via the & nbsp; directory service, used by SplunkWeb's "All Configurations" management page. Defaults to false. desc = <human readable string> * Allows for renaming the configuration type of these objects when enumerated via the directory service. Miscellaneous The un-described parameters in these stanzas all operate according to the descriptions listed under "script:", above. These should not need to be edited by users - they are here only to quiet down the configuration checker. 185

[input:...] dynamic = [true false] * If set to true, listen on the socket for data. * If false, data is contained within the request body. * Defaults to false. [peerupload:...] path = <directory path> * Path to search through to find configuration bundles from search peers. untar = [true false] * Whether or not a file should be untarred once the transfer is complete. restmap.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains example REST endpoint configurations. To use one or more of these configurations, copy the configuration block into restmap.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles The following are default REST configurations. To create your own endpoints, modify the values by following the spec outlined in restmap.conf.spec. ///////////////////////////////////////////////////////////////////////////// global settings ///////////////////////////////////////////////////////////////////////////// [global] indicates if auths are allowed via GET params allowgetauth=false The default handler (assuming that we have PYTHONPATH set) pythonhandlerpath=$splunk_home/bin/rest_handler.py ///////////////////////////////////////////////////////////////////////////// internal C++ handlers NOTE: These are internal Splunk-created endpoints. 3rd party developers can only use script or search can be used as handlers. (Please see restmap.conf.spec for help with configurations.) ///////////////////////////////////////////////////////////////////////////// [SBA:sba] match=/properties capability=get_property_map [asyncsearch:asyncsearch] match=/search capability=search savedsearches.conf 다음은 savedsearches.conf의 사양 및 예제 파일입니다. savedsearches.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 186

This file contains possible attribute/value pairs for saved search entries in savedsearches.conf. You can configure saved searches by creating your own savedsearches.conf. There is a default savedsearches.conf in $SPLUNK_HOME/etc/system/default. To set custom configurations, place a savedsearches.conf in $SPLUNK_HOME/etc/system/local/. For examples, see savedsearches.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. & nbsp; * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. ******* The possible attribute/value pairs for savedsearches.conf are: ******* [<stanza name>] * Create a unique stanza name for each saved search. * Follow the stanza name with any number of the following attribute/value pairs. * If you do not specify an attribute, Splunk uses the default. disabled = [0 1] * Disable your search by setting to 1. * If set to 1, this saved search is not visible in Splunk Web. * Defaults to 0. search = <string> * Actual search terms of the saved search. * For example, search = index::sampledata http NOT 500. * Your search can include macro searches for substitution. * To learn more about creating a macro search, search the documentation for "macro search." * Defaults to empty string. ******* Scheduling options ******* enablesched = [0 1] * Set this to 1 to run your search on a schedule. * Defaults to 0. cron_schedule = <cron string> * The cron schedule used to execute this search. * For example: */5 * * * * causes the search to execute every 5 minutes. * Cron lets you use standard cron notation to define your scheduled search interval. In particular, cron can accept this type of notation: 00,20,40 * * * *, which runs the search every hour at hh:00, hh:20, hh:40. Along the same lines, a cron of 03,23, 43 * * * * runs the search every hour at hh:03, hh:23, hh:43. * Splunk recommends that you schedule your searches so that they are staggered over time. This reduces system load. Running all of them every 20 minutes (*/20) means they would all launch at hh:00 (20, 40) and might slow your system every 20 minutes. * Defaults to empty string. schedule = <cron-style string> * This field is DEPRECATED. * Antequated pre-4.0 scheduling strings. Use cron_schedule instead. * Slightly incompatable Cron-like schedule. The behavior for '/' is splunk-specific. * For this antequated key, the expression */n is handled as "divide by n" (instead of standard POSIX cron's "every n"). * For example: */6 for posix cron means: every six minutes. For this specific setting, this means "for every sixth of an hour" which results in running every ten minutes. * Defaults to empty string. max_concurrent = <int> 187

* The maximum number of concurrent instances of this search the scheduler is allowed to run. * Defaults to 1. realtime_schedule = [0 1] * Controls the way the scheduler computes the next execution time of a scheduled search. * If this value is set to 1, the scheduler bases its determination of the next scheduled search execution time on the current time. * If this value is set to 0, the scheduler bases its determination of the next scheduled search on the last search execution time. This is called continuous scheduling. * If set to 1, the scheduler might skip some execution periods to make sure that the scheduler is executing the searches running over the most recent time range. * If set to 0, the scheduler never skips scheduled execution periods. However, the execution & nbsp; of the saved search might fall behind depending on the scheduler's load. Use continuous scheduling whenever you enable the summary index option. * The scheduler tries to execute searches that have realtime_schedule set to 1 before it executes searches that have continuous scheduling (realtime_schedule = 0). * Defaults to 1 ******* Notification options ******* counttype = number of events number of hosts number of sources always * Set the type of count for alerting. * Used with relation and quantity (below). * NOTE: If you specify "always," do not set relation or quantity (below). * Defaults to always. relation = greater than less than equal to not equal to drops by rises by * Specifies how to compare against counttype. * Defaults to empty string. quantity = <integer> * Specifies a value for the counttype and relation, to determine the condition under which an alert is triggered by a saved search. * You can think of it as a sentence constructed like this: <counttype> <relation> <quantity>. * For example, "number of events [is] greater than 10" sends an alert when the count of events is larger than by 10. * For example, "number of events drops by 10%" sends an alert when the count of events drops by 10%. * Defaults to an empty string. alert_condition = <search string> * Contains a conditional search that is evaluated against the results of the saved search. Alerts are triggered if the specified search yields a non-empty search result list. * NOTE: If you specify an alert_condition, do not set counttype, relation, or quantity. * Defaults to an empty string. ******* generic action settings. For a comprehensive list of actions and their arguments, refer to alert_actions.conf. ******* action.<action_name> = 0 1 * Indicates whether the action is enabled or disabled for a particular saved search. * The action_name can be: email populate_lookup script summary_index * For more about your defined alert actions see alert_actions.conf. * Defaults to an empty string. action.<action_name>.<parameter> = <value> * Overrides an action's parameter (defined in alert_actions.conf) with a new <value> for this saved search only. * Defaults to an empty string. ****** Settings for email action ****** action.email = 0 1 188

* Enables or disables the email action. * Defaults to 0. action.email.to = <email list> * REQUIRED. This setting is not defined in alert_actions.conf. * Set a comma-delimited list of recipient email addresses. * Defaults to empty string. action.email.from = <email address> * Set an email address to use as the sender's address. * Defaults to splunk@<localhost> (or whatever is set in alert_actions.conf). action.email.subject = <string> * Set the subject of the email delivered to recipients. * Defaults to SplunkAlert-<savedsearchname> (or whatever is set in alert_actions.conf). action.email.mailserver = <string> * Set the address of the MTA server to be used to send the emails. * Defaults to <LOCALHOST> (or whatever is set in alert_actions.conf). ****** Settings for script action ****** action.script = 0 1 * Enables or disables the script action. * 1 to enable, 0 to disable. * Defaults to 0 action.script.filename = <script filename> * The filename of the shell script to execute. * The script should be located in: $SPLUNK_HOME/bin/scripts/ * Defaults to empty string. ** ***** Settings for summary index action ******* action.summary_index = 0 1 * Enables or disables the summary index action. * Defaults to 0. action.summary_index._name = <index> * Specifies the name of the summary index where the results of the scheduled search are saved. * Defaults to summary. action.summary_index.inline = <bool> * Determines whether to execute the summary indexing action as part of the scheduled search. * NOTE: This option is considered only if the summary index action is enabled and is always executed (in other words, if counttype = always). * Defaults to true. action.summary_index.<field> = <string> * Specifies a field/value pair to add to every event that gets summary indexed by this search. * You can define multiple field/value pairs for a single summary index search. ******* Settings for lookup table population parameters ******* action.populate_lookup = 0 1 * Enables or disables the lookup population action. * Defaults to 0. action.populate_lookup.dest = <string> * Can be one of the following two options: * A lookup name from transforms.conf. * A path to a lookup.csv file that Splunk should copy the search results to, relative to $SPLUNK_HOME. 189

* NOTE: This path must point to a.csv file in either of the following directories: * etc/ system/lookups/ * etc/apps/<app-name>/lookups * NOTE: the destination directories of the above files must already exist * Defaults to empty string. run_on_startup = true false * Toggles whether this search runs when Splunk starts or any edit that changes search related args happen * (which includes: search and dispatch.* args). * If set to true the search is ran as soon as possible during startup or after edit * otherwise the search is ran at the next scheduled time. * We recommend that you set run_on_startup to true for scheduled searches that populate lookup * tables or generate artifacts used by dashboards. * Defaults to false. & nbsp; ******* dispatch search options ******* dispatch.ttl = <integer>[p] * Indicates the time to live (in seconds) for the artifacts of the scheduled search, if no actions are triggered. * If the integer is followed by the letter 'p' Splunk interprets the ttl as a multiple of the scheduled search's execution period (e.g. if the search is scheduled to run hourly and ttl is set to 2p the ttl of the artifacts will be set to 2 hours). * If an action is triggered Splunk changes the ttl to that action's ttl. If multiple actions are triggered, Splunk applies the largest action ttl to the artifacts. To set the action's ttl, refer to alert_actions.conf.spec. * For more info on search's ttl please see limits.conf.spec [search] ttl * Defaults to 2p (that is, 2 x the period of the scheduled search). dispatch.buckets = <integer> * The maximum number of timeline buckets. * Defaults to 0. dispatch.max_count = <integer> * The maximum number of results before finalizing the search. * Defaults to 500000. dispatch.max_time = <integer> * Indicates the maximum amount of time (in seconds) before finalizing the search. * Defaults to 0. dispatch.lookups = 1 0 * Enables or disables lookups for this search. * Defaults to 1. dispatch.earliest_time = <time-str> * Specifies the earliest time for this search. Can be a relative or absolute time. * If this value is an absolute time, use the dispatch.time_format to format the value. * Defaults to empty string. dispatch.latest_time = <time-str> * Specifies the latest time for this saved search. Can be a relative or absolute time. * If this value is an absolute time, use the dispatch.time_format to format the value. * Defaults to empty string. dispatch.time_format = <time format str> * Defines the time format that Splunk uses to specify the earliest and latest time. * Defaults to %FT%T.%Q%:z dispatch.spawn_process = 1 0 * Specifies whether Splunk spawns a new search process when this saved search is executed. * Default is 1. dispatch.reduce_freq = <int> * Specifies how frequently Splunk should run the MapReduce reduce phase on accumulated map values. * Defaults to 10. dispatch.rt_backfill = <bool> * Specifies whether to do real-time window backfilling for scheduled real time searches 190

* Defaults to false. restart_on_searchpeer_add = 1 0 * Specifies whether to restart a real-time search managed by the scheduler when a search peer becomes available for this saved search. * NOTE: The peer can be a newly added peer or a peer that has been down and has become available. * Defaults to 1. ******* auto summarization options ******* auto_ summarize = <bool> * Whether the scheduler should ensure that the data for this search is automatically summarized * Defaults to false. auto_summarize.command = <string> * A search template to be used to construct the auto summarization for this search. * DO NOT change unles you know what you're doing auto_summarize.timespan = <time-specifier> (, <time-specifier>)* * Comma delimite list of time ranges that each summarized chunk should span. This comprises the list * of available granularity levels for which summaries would be available. For example a timechart over * the last month whose granuality is at the day level should set this to 1d. If you're going to need the * same data summarized at the hour level because you need to have weekly charts then use: 1h,1d auto_summarize.cron_schedule = <cron-string> * Cron schedule to be used to probe/generate the summaries for this search auto_ summarize.dispatch.<arg-name> = <string> * Any dispatch.* options that need to be overriden when running the summary search. auto_summarize.suspend_period = <time-specifier> * Amount of time to suspend summarization of this search if the summarization is deemed unhelpful * Defaults to 24h auto_summarize.max_summary_size = <unsigned int> * The minimum summary size when to start testing it's helpfulness * Defaults to 52428800 (5MB) auto_summarize.max_summary_ratio = <positive float> * The maximum ratio of summary_size/bucket_size when to stop summarization and deem it unhelpful for a bucket * NOTE: the test is only performed if the summary size is larger than auto_summarize.max_summary_size * Defaults to: 0.1 auto_summarize.max_disabled_buckets = <unsigned int> * The maximum number of buckets with the suspended summarization before the summarization search is completely * stopped and the summarization of the search is suspended for auto_summarize.suspend_period * Defaults to: 2 auto_summarize.max_time = <unsigned in> * The maximum amount of time that the summary search is allowed to run. Note that this is an approximate time * and the summarize search will be stopped at clean bucket boundaries. * Defaults to: 3600 ******* alert suppression/severity/expiration/tracking settings ******* alert.suppress = 0 1 * Specifies whether alert suppression is enabled for this scheduled search. * Defaults to 0. alert.suppress.period = <time-specifier> * Sets the suppression period. Use [number][time-unit] to specify a time. * For example: 60 = 60 seconds, 1m = 1 minute, 1h = 60 minutes = 1 hour etc * Honored if and only if alert.suppress = 1 * Defaults to empty string. alert.suppress.fields = <comma-delimited-field-list> * List of fields to use when suppressing per-result alerts. This field *must* be specified * if the digest mode is disabled and suppression is enabled. 191

* Defaults to empty string. alert.severity = <int> * Sets the alert severity level. * Valid values are: 1-debug, 2-info, 3-warn, 4-error, 5-severe, 6-fatal * Defaults to 3. alert.expires = <time-specifier> * Sets the period of time to show the alert in the dashboard. Use [number][time-unit] to specify a time. * For example: 60 = 60 seconds, 1m = 1 minute, 1h = 60 minutes = 1 hour etc * Defaults to 24h. alert.digest_mode = true false * Specifies whether Splunk applies the alert actions to the entire result set or on each * individual result. * Defaults to true. alert.track = true false auto * Specifies whether to track the actions triggered by this scheduled search. * auto - determine whether to track or not based on the tracking setting of each action, * do not track scheduled searches that always trigger actions. * true - force alert tracking. * false - disable alert tracking for this search. * Defaults to auto. ******* UI-specific settings ******* displayview =<string> * Defines the default UI view name (not label) in which to load the results. * Accessibility is subject to the user having sufficient permissions. * Defaults to empty string. vsid = <string> * Defines the viewstate id associated with the UI view listed in 'displayview'. * Must match up to a stanza in viewstates.conf. * Defaults to empty string. is_visible = true false * Specifies whether this saved search should be listed in the visible saved search list. * Defaults to true. description = <string> * Human-readable description of this saved search. * Defaults to empty string. request.ui_dispatch_app = <string& gt; * Specifies a field used by Splunk UI to denote the app this search should be dispatched in. * Defaults to empty string. request.ui_dispatch_view = <string> * Specifies a field used by Splunk UI to denote the view this search should be displayed in. * Defaults to empty string. ******* deprecated settings ******* sendresults = <bool> * use action.email.sendresult action_rss = <bool> * use action.rss action_email = <string> * use action.email and action.email.to role = <string> * see saved search permissions userid = <string> 192

* see saved search permissions query = <string> * use search nextrun = <int> * not used anymore, the scheduler maintains this info internally qualifiedsearch = <string> * not used anymore, Splunk computes this value during runtime savedsearches.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains example saved searches and alerts. To use one or more of these configurations, copy the configuration block into savedsearches.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles The following searches are example searches. To create your own search, modify the values by following the spec outlined in savedsearches.conf.spec. [Daily indexing volume by server] search = index=_internal todaysbytesindexed LicenseManager-Audit NOT source=*web_service.log NOT source=*web_access.log eval Daily _Indexing_Volume_in_MBs = todaysbytesindexed/1024/1024 timechart avg(daily_ Indexing_Volume_in_MBs) by host dispatch.earliest_time = -7d [Errors in the last 24 hours] search = error OR failed OR severe OR ( sourcetype=access_* ( 404 OR 500 OR 503 ) ) dispatch.earliest_time = -1d [Errors in the last hour] search = error OR failed OR severe OR ( sourcetype=access_* ( 404 OR 500 OR 503 ) ) dispatch.earliest_time = -1h [KB indexed per hour last 24 hours] search = index=_internal metrics group=per_index_thruput NOT debug NOT sourcetype=splunk_web_access timechart fixedrange=t span=1h sum(kb) rename sum(kb) as totalkb dispatch.earliest_time = -1d [Messages by minute last 3 hours] search = index=_internal eps "group=per_source_thruput" NOT filetracker eval events=eps*kb/kbps timechart fixedrange=t span=1m s um(events) by series dispatch.earliest_time = -3h [Splunk errors last 24 hours] search = index=_internal " error " NOT debug source=*/splunkd.log* dispatch. earliest_time = -24h searchbnf.conf 다음은 searchbnf.conf의 사양 및 예제 파일입니다. searchbnf.conf.spec 193

Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contain descriptions of stanzas and attribute/value pairs for configuring search-assistant via searchbnf.conf There is a searchbnf.conf in $SPLUNK_HOME/etc/system/default/. It should not be modified. If your application has its own custom python search commands, your application can include its own searchbnf.conf to describe the commands to the search-assistant. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. [<search-commandname>-command] * This stanza enables properties for a given <search-command>. * A searchbnf.conf file can contain multiple stanzas for any number of commands. * Follow this stanza name with any number of the following attribute/value pairs. * If you do not set an attribute for a given <spec>, the default & nbsp; is used. The default values are empty. * An example stanza name might be "geocode-command", for a "geocode" command. * Search command stanzas can refer to definitions defined in others stanzas, and they do not require "-command", appended to them. For example: [geocode-command] syntax = geocode <geocode-option>*... [geocode-option] syntax = (maxcount=<int>) (maxhops=<int>)... ****************************************************************************** The possible attributes/value pairs for searchbnf. conf ****************************************************************************** SYNTAX = <string> * Describes the syntax of the search command. See the head of searchbnf.conf for details. * Required SIMPLESYNTAX = <string> * Optional simpler version of the syntax to make it easier to understand at the expense of completeness. Typically it removes rarely used options or alternate ways of saying the same thing. * For example, a search command might accept values such as "m min mins minute minutes", but that would unnecessarily clutter the syntax description for the user. In this can, the simplesyntax can just pick the one (e.g., "minute"). ALIAS = <commands list> * Alternative names for the search command. This further cleans up the syntax so the user does not have to know that 'savedsearch' can also be called by 'macro' or 'savedsplunk'. DESCRIPTION = <string> * Detailed text description of search command. Description can continue on the next line if the line ends in 194

"\" * Required SHORTDESC = <string> * A short description of the search command. The full DESCRIPTION may take up too much screen real-estate for the search assistant. * Required EXAMPLE = <string> COMMENT = <string> * 'example' should list out a helpful example of using the search command, and 'comment' should describe that example. * 'example' and 'comment' can be appended with matching indexes to allow multiple examples and corresponding comments. * For example: example2 = geocode maxcount=4 command2 = run geocode on up to four values example3 = geocode maxcount=-1 comment3 = run geocode on all values USAGE = public private deprecated * Determines if a command is public, private, depreciated. The search assistant only operates on public commands. * Required TAGS = <tags list> * List of tags that describe this search command. Used to find commands when the use enters a synonym (e.g. "graph" -> "chart") RELATED = <commands list> * List of related commands to help user when using one command to learn about others. ****************************************************************************** Optional attributes primarily used internally at Splunk ****************************************************************************** maintainer, appears-in, note, supports-multivalue, appears-in searchbnf.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 The following are example stanzas for searchbnf.conf configurations. selfjoin [selfjoin-command] syntax = selfjoin (<selfjoin-options>)* <field-list> shortdesc = Join results with itself. description = Join results with itself. Must specify at least one field to join on. usage = public example1 = selfjoin id comment1 = Joins results with itself on 'id' field. related = join tags = join combine unite [selfjoin-options] syntax = overwrite=<bool> max=<int> keepsingle=<int> description = The selfjoin joins each result with other results that\ have the same value for the join fields. 'overwrite' controls if\ fields from these 'other' results should overwrite fields of the\ result used as the basis for the join (default=true). max indicates\ the maximum number of 'other' results each main result can join with.\ (default = 1, 0 means no limit). 'keepsingle' controls whether or not\ 195

results with a unique value for the join fields (and thus no other\ results to join with) should be retained. (default = false) segmenters.conf 다음은 segmenters.conf의 사양 및 예제 파일입니다. segmenters.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attribute/value pairs for configuring segmentation of events in segementers.conf. There is a default segmenters.conf in $SPLUNK_HOME/etc/system/default. To set custom configurations, place a segmenters.conf in $SPLUNK_HOME/etc/system/local/. For examples, see segmenters.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. [<SegmenterName>] * Name your stanza. * Follow this stanza name with any number of the following attribute/value pairs. * If you don't specify an attribute/value pair, Splunk will use the default. MAJOR = <space separated list of breaking characters> * Set major breakers. * Major breakers are words, phrases or terms in your data that are surrounded by set breaking characters. * By default, major breakers are set to most characters and blank spaces. * Typically, major breakers are single characters. * Default is [ ] < > ( ) { }! ;, ' " * \n \r \s \t &? + %21 %26 %2526 %3B %7C %20 %2B %3D -- %2520 %5D %5B %3A %0A %2C %28 %29 * Please note: \s represents a space; \n, a newline; \r, a carriage return; and \t, a tab. MINOR = <space separated list of strings> * Set minor breakers. * In addition to the segments specified by the major breakers, for each minor breaker found, & nbsp; Splunk indexes the token from the last major breaker to the current minor breaker and from the last minor breaker to the current minor breaker. * Default is / : = @. - $ % \\ _ INTERMEDIATE_MAJORS = true false * Set this to "true" if you want an IP address to appear in typeahead as a, a.b, a.b.c, a.b.c.d * The typical performance hit by setting to "true" is 30%. * Default is "false". FILTER = <regular expression> * If set, segmentation will only take place if the regular expression matches. * Furthermore, segmentation will only take place on the first group of the matching regex. * Default is empty. LOOKAHEAD = <integer> * Set how far into a given event (in characters) Splunk segments. * LOOKAHEAD applied after any FILTER rules. * To disable segmentation, set to 0. * Defaults to -1 (read the whole event). MINOR_LEN = <integer> 196

* Specify how long a minor token can be. * Longer minor tokens are discarded without prejudice. * Defaults to -1. MAJOR_LEN = <integer> * Specify how long a major token can be. & nbsp; * Longer major tokens are discarded without prejudice. * Defaults to -1. MINOR_COUNT = <integer> * Specify how many minor segments to create per event. * After the specified number of minor tokens have been created, later ones are discarded without prejudice. * Defaults to -1. MAJOR_COUNT = <integer> * Specify how many major segments are created per event. * After the specified number of major segments have been created, later ones are discarded without prejudice. * Default to -1. segmenters.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 The following are examples of segmentation configurations. To use one or more of these configurations, copy the configuration block into segmenters.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles Example of a segmenter that doesn't index the date as segments in syslog data: [syslog] FILTER = ^.*?\d\d:\d\d:\d\d\s+\s+\s+(.*)$ Example of a segmenter that only indexes the first 256b of events: [limited-reach] LOOKAHEAD = 256 Example of a segmenter that only indexes the first line of an event: [first-line] FILTER = ^(.*?)(\n $) Turn segmentation off completely: [no-segmentation] LOOKAHEAD = 0 server.conf 다음은 server.conf의 사양 및 예제 파일입니다. server.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains the set of attributes and values you can use to configure server options 197

in server.conf. There is a server.conf in $SPLUNK_HOME/etc/system/default/. To set custom configurations, place a server.conf in $SPLUNK_HOME/etc/system/local/. For examples, see server.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. General Server Configuration [general] servername = <ascii string> * The name used to identify this Splunk instance for features such as distributed search. * Defaults to <hostname>-<user running splunk>. * May not be an empty string * May contain environment variables * After any environment variables have been expanded, the server name (if not an IPv6 address) can only contain letters, numbers, underscores, dots, and dashes; and it must start with a letter, number, or an underscore. sessiontimeout = <time range string> * The amount of time before a user session times out, expressed as a search-like time range * Examples include '24h' (24 hours), '3d' (3 days), '7200s' (7200 seconds, or two hours) * Defaults to '1h' (1 hour) trustedip = <ip address> * All logins from this IP address are trusted, meaning password is no longer required * Only set this if you are using Single Sign On (SSO) allowremotelogin = <always never requiresetpassword> & nbsp; * Controls remote management by restricting general login. Note that this does not apply to trusted SSO logins from trustedip. * If 'always', enables authentication so that all remote login attempts are allowed. * If 'never', only local logins to splunkd will be allowed. Note that this will still allow remote management through splunkweb if splunkweb is on the same server. * If 'requiresetpassword' (default): * In the free license, remote login is disabled. * In the pro license, remote login is only disabled for the admin user that has not changed their default password. pass4symmkey = <password string> * This is prepended to the splunk symmetric key to generate the final key which is used to sign all traffic between master/slave licenser listenonipv6 = <no yes only> * By default, splunkd will listen for incoming connections (both REST and TCP inputs) using IPv4 only * To enable IPv6 support in splunkd, set this to 'yes'. splunkd will simultaneously listen for connections on both IPv4 and IPv6 * To disable IPv4 entirely, set this to 'only', which will cause splunkd to exclusively accept connections over IPv6. You will probably also need to change mgmthostport in web.conf (use '[::1]' instead of '127.0.0.1') * Note that any setting of SPLUNK_BINDIP in your environment or splunk-launch.conf will override this value. In that case splunkd will listen on the exact address specified. connectusingipversion = <auto 4-first 6-first 4-only 6-only> * When making outbound TCP connections (for forwarding eventdata, making distributed search requests, etc) this controls whether the connections will be made via IPv4 or IPv6. 198

* If a host is available over both IPv4 and IPv6 and this is set to '4-first' then we will connect over IPv4 first and fallback to IPv6 if the connection fails * If it is set to '6-first' then splunkd will try IPv6 first and fallback to IPv4 on failure * If this is set to '4-only' then splunkd will only attempt to make connections over IPv4 * Likewise, if this is set to '6-only' will only attempt to connect to the IPv6 address * The default value of 'auto' will select a reasonable value based on listenonipv6's setting If that value is set to 'no' it will act like '4-only'. If it is set to 'yes' it will act like '6-first' and if it is set to 'only' it will act like '6-only' * Note that connections to literal addresses are unaffected by this. For example, if a forwarder is configured to connect to "10.1.2.3" the connection will be made over IPv4 regardless of this setting guid = <globally unique identifier for this instance> usehttpservercompression = <bool> * Whether Splunkd's HTTP server should support gzip content encoding. For more info on how * content encoding works see http://www.w3.org/protocols/rfc2616/rfc2616-sec14.html (section 14.3) usehttpclientcompression = <bool> < on-http on-https> * Whether gzip compression should be supported when Splunkd acts as a client (including distributed searches). Note that * in order for the content to be compressed the HTTP server that the client is connecting to should also support compression. * If the connection is being made over https and useclientsslcompression=true (see below) then setting this * option to true would result in double compression work without much compression gain. It is recommended that this * value be set to on-http or (true and set useclientsslcompression=false). SSL Configuration details [sslconfig] * Set SSL for communications on Splunk's back-end under this stanza name. * NOTE: To set SSL (eg HTTPS) for Splunk Web and the browser, use web.conf. * Follow this stanza name with any number of the following attribute/value pairs. * If you do not specify an entry for each attribute, Splunk will use the default value. enablesplunkdssl = [true false] * Enables/disables SSL on the splunkd management port (8089). * Defaults to true. useclientsslcompression = [true false] * Turns on HTTP client compression. * Server-side compression is turned on by default; setting this on the client side enables * compression between server and client. * Enabling this potentially gives you much faster distributed searches across multiple Splunk instances. * Defaults to true. usesplunkdclientsslcompression = [true false] * Controls whether SSL compression would be used when splunkd is acting as an HTTP client, * usually during certificate exchange, bundle replication, remote calls etc. * NOTE: this setting is effective if and only if useclientsslcompression is set to true * NOTE: splunkd is not involved in data transfer in distributed search, the search in a separate process is. * Defaults to false supportsslv3only = [true false] * If true, tells the HTTP server to only accept connections * from SSLv3 clients. * Default is false. sslverifyservercert = [true false] * Used by distributed search: When making a search request to another server in the search cluster. * Used by distributed deployment clients: When polling a deployment server. * If true, make sure that the server that is being connected to is a valid one (authenticated). Both the common name and the alternate name & nbsp; of the server are then checked for a match if they are specified in this configuration file. * Default is false 199

sslcommonnametocheck = <commonname> * The common name to check when 'sslverifyservercert' is set to true * This feature does not work with the deployment server and client communication over SSL. * Optional. Defaults to no common name checking. sslaltnametocheck = <alternatename> * The alternate name to check when 'sslverifyservercert' is set to true * This feature does not work with the deployment server and client communication over SSL. * Optional. Defaults to no alternate name checking requireclientcert = [true false] * Requires that any HTTPS client that connects to splunkds internal HTTPS server has a certificate that was signed by our certificate authority. * Used by distributed search: Splunk indexing instances must be authenticated to connect to another splunk indexing instance. * Used by distributed deployment: The deployment server requires that deployment clients are authenticated before allowing them to poll for new configurations/applications. * If true, a client can connect ONLY if a certificate created by our certificate authority was used on that client. * Default is false ciphersuite = <cipher suite string> * If set, uses the specified cipher string for the HTTP server. If not set, uses the default cipher string provided by OpenSSL. This is used to ensure that the server does not accept connections using weak encryption protocols. sslkeysfile = <filename> * Server certificate file. * Certificates are auto-generated by splunkd upon starting Splunk. * You may replace the default cert with your own PEM format file. * Certs are stored in capath (see below). * Default is server.pem. sslkeysfilepassword = <password> * Server certificate password. * Default is password. cacertfile = <filename> * Public key of the signing authority. * Default is cacert.pem. capath = <path> * path where all these certs are stored. * Default is $SPLUNK_HOME/etc/auth. certcreatescript = <script name> & nbsp; * Creation script for generating certs on startup of Splunk. Splunkd HTTP server configuration [httpserver] * Set stand-alone HTTP settings for Splunk under this stanza name. * Follow this stanza name with any number of the following attribute/value pairs. * If you do not specify an entry for each attribute, Splunk uses the default value. atomfeedstylesheet = <string> * Defines the stylesheet relative URL to apply to default Atom feeds. * Set to 'none' to stop writing out xsl-stylesheet directive. * Defaults to /static/atom.xsl. max-age = <int> * Set the maximum time (in seconds) to cache a static asset served off of the '/static' directory. * This value is passed along in the 'Cache-Control' HTTP header. * Defaults to 3600. follow-symlinks = [true false] * Toggle whether static file handler (serving the '/static' directory) follow filesystem 200

symlinks when serving files. * Defaults to false. disabledefaultport = [true false] * If true, turns off listening on the splunkd management port (8089 by default) & nbsp; * Default value is 'false'. acceptfrom = <network_acl>... * Lists a set of networks or addresses to accept data from. These rules are separated by commas or spaces * Each rule can be in the following forms: * 1. A single IPv4 or IPv6 address (examples: "10.1.2.3", "fe80::4a3") * 2. A CIDR block of addresses (examples: "10/8", "fe80:1234/32") * 3. A DNS name, possibly with a '*' used as a wildcard (examples: "myhost.example.com", "*.splunk.com") * 4. A single '*' which matches anything * Entries can also be prefixed with '!' to cause the rule to reject the connection. Rules are applied in order, and the first one to match is & nbsp; used. For example, "!10.1/16, *" will allow connections from everywhere except the 10.1.*.* network. * Defaults to "*" (accept from anywhere) streaminwritetimeout = <int> * When uploading data to http server, if http server is unable to write data to * receiver for configured streaminwritetimeout seconds, it aborts write operation. * Defaults to 5 second. max_content_length = <int> * Measured in bytes * HTTP requests over this size will rejected. * Exists to avoid allocating an unreasonable amount of memory from web requests * Defaulted to 838860800 or 800MB * In environments where indexers have enormous amounts of RAM, this number can be reasonably increased to handle large quantities of bundle data. Splunkd HTTPServer listener configuration [httpserverlistener:<ip>:<port>] * Enable the splunkd http server to listen on a network interface (NIC) specified by <ip> and a port number specified by <port>. If you leave <ip> blank (but still include the ':'), splunkd will listen on the kernel picked NIC using port <port>. ssl = [true false] * Toggle whether this listening ip:port will use SSL or not. * Default value is 'true'. listenonipv6 = <no yes only> * Toggle whether this listening ip:port will listen on IPv4, IPv6, or both * If not present, the setting in the [general] stanza will be used acceptfrom = <network_acl>... * Lists a set of networks or addresses to accept data from. These rules are separated by commas or spaces * Each rule can be in the following forms: * 1. A single IPv4 or IPv6 address (examples: "10.1.2. 3", "fe80::4a3") * 2. A CIDR block of addresses (examples: "10/8", "fe80:1234/32") * 3. A DNS name, possibly with a '*' used as a wildcard (examples: "myhost.example.com", "*.splunk.com") * 4. A single '*' which matches anything * Entries can also be prefixed with '!' to cause the rule to reject the connection. Rules are applied in order, and the first one to match is used. For example, "!10.1/16, *" will allow connections from everywhere except the 10.1.*.* network. * Defaults to the setting in the [httpserver] stanza above Static file handler MIME-type map [mimetype-extension-map] * Map filename extensions to MIME type for files served from the static file handler under this stanza name. 201

<file-extension> = <MIME-type> * Instructs the HTTP static file server to mark any files ending in 'file-extension' with a header of 'Content-Type: <MIME-type>'. * Defaults to: [mimetype-extension-map] gif = image/gif htm = text/html jpg = image/jpg & nbsp; png = image/png txt = text/plain xml = text/xml xsl = text/xml Remote applications configuration (e.g. SplunkBase) [applicationsmanagement] * Set remote applications settings for Splunk under this stanza name. * Follow this stanza name with any number of the following attribute/value pairs. * If you do not specify an entry for each attribute, Splunk uses the default value. allowinternetaccess = <bool> * Allow Splunk to access the remote applications repository. url = <URL> * Applications repository. * Defaults to https://splunkbase.splunk.com/api/apps loginurl = <URL> * Applications repository login. * Defaults to https://splunkbase.splunk.com/api/account:login/ detailsurl = <URL> * Base URL for application information, keyed off of app ID. * Defaults to https://splunkbase.splunk.com/apps/id useragent = <splunk-version>-<splunk-build-num>-<platform> * User-agent string to use when contacting applications repository. * <platform> includes information like operating system and CPU architecture. updatehost = <URL> * Host section of URL to check for app updates, e.g. https://splunkbase.splunk.com updatepath = <URL> * Path section of URL to check for app updates, e.g. /api/apps:resolve/checkforupgrade updatetimeout = <time range string> * The minimum amount of time Splunk will wait between checks for app updates * Examples include '24h' (24 hours), '3d' (3 days), '7200s' (7200 seconds, or two hours) * Defaults to '24h' Misc. configuration [scripts] initialnumberofscriptprocesses = <num> * The number of pre-forked script processes that are launched when the system comes up. These scripts are reused when script REST endpoints *and* search scripts are executed. The idea is to eliminate the performance overhead of launching the script interpreter every time it is invoked. These processes are put in a pool. If the pool is completely busy when a script gets invoked, a new processes is fired up to handle the new invocation - but it disappears when that invocation is finished. Disk usage settings (for the indexer, not for Splunk log files) 202

[diskusage] minfreespace = <num> * Specified in megabytes. * The default setting is 2000 (approx 2GB) * Specifies a safe amount of space that must exist for splunkd to continue operating. * Note that this affects search and indexing * This is how the searching is affected: * For search: * Before attempting to launch a search, splunk will require this amount of free space on the filesystem where the dispatch directory is stored, $SPLUNK_HOME/var/run/splunk/dispatch * Applied similarly to the search quota values in authorize.conf and limits.conf. * For indexing: * Periodically, the indexer will check space on all partitions that contain splunk indexes as specified by indexes.conf. Indexing & nbsp; will be paused and a ui banner + splunkd warning posted to indicate need to clear more disk space. pollingfrequency = <num> * After every pollingfrequency events indexed, the disk usage is checked. * The default frequency is every 100000 events. pollingtimerfrequency = <num> * After every pollingtimerfrequency seconds, the disk usage is checked * The default value is 10 seconds Queue settings [queue] maxsize = [<integer> <integer>[kb MB GB]] * Specifies default capacity of a queue. * If specified as a lone integer (for example, maxsize=1000), maxsize indicates the maximum number of events allowed in the queue. * If specified as an integer followed by KB, MB, or GB (for example, maxsize=100mb), it indicates the maximum RAM allocated for queue. * The default is 500KB. [queue=<queuename>] maxsize = [<integer> <integer>[kb MB GB]] * Specifies the capacity of a queue. It overrides the default capacity specified in [queue]. * If specified as a lone integer (for example, maxsize=1000), maxsize indicates the maximum number of events allowed in the queue. * If specified as an integer followed by KB, MB, or GB (for example, maxsize=100mb), it indicates the maximum RAM allocated for queue. * The default is inherited from maxsize value specified in [queue] PubSub server settings for the http endpoint. [pubsubsvr-http] disabled = [true false] * If disabled, then http endpoint is not registered. Set this value to 'false' to expose PubSub server on http. * Defaults to 'true' stateintervalinsecs = <seconds> * The number of seconds before a connection is flushed due to inactivity. The connection is not closed, only messages for that connection are flushed. * Defaults to 300 seconds (5 minutes). General file input settings. 203

[fileinput] outputqueue = <queue name> * The queue that input methods should send their data to. Most users will not need to change this value. * Defaults to parsingqueue. Settings controlling the behavior of 'splunk diag', the dignostic tool [diag] EXCLUDE-<class> = <glob expression> * Specifies a glob / shell pattern to be excluded from diags generated on this instance. * Example: */etc/secret_app/local/*.conf License manager settings for configuring the license pool(s) [license] master_uri = [self <uri>] * An example of <uri>: <scheme>://<hostname>:<port> active_group = Enterprise Trial Forwarder Free these timeouts only matter if you have a master_uri set to remote master connection_timeout = 30 & nbsp; * Maximum time (in seconds) to wait before connection to master times out send_timeout = 30 * Maximum time (in seconds) to wait before sending data to master times out receive_timeout = 30 * Maximum time (in seconds) to wait before receiving data from master times out squash_threshold = 1000 * Advanced setting. Periodically the indexer must report to license manager the data indexed broken down by source,sourcetype,host. If the number of distinct source,sourcetype/host tuples grows over the squash_threshold, we squash the host/source values and only report a breakdown by sourcetype. This is to prevent explosions in memory + license_usage.log lines. Set this with care or after consulting a Splunk Support engineer, it is an advanced parameter. [lmpool:auto_generated_pool_forwarder] * This is the auto generated pool for the forwarder stack description = <textual description of this license pool> quota = MAX <maximum amount allowed by this license> * MAX indicates the total capacity of the license. You may have only 1 pool with MAX size in a stack * The quota can also be specified as a specific size eg. 20MB, 1GB etc slaves = * <slave list> * An asterix(*) indicates that any slave can connect to this pool * You can also specifiy a comma separated slave guid list stack_id = forwarder * the stack to which this pool belongs [lmpool:auto_generated_pool_free] * This is the auto generated pool for the free stack * field descriptions are the same as that for the "lmpool:auto_ generated_pool_forwarder" [lmpool:auto_generated_pool_enterprise] * This is the auto generated pool for the enterprise stack * field descriptions are the same as that for the "lmpool:auto_generated_pool_forwarder" [lmpool:auto_generated_pool_fixed-sourcetype_<sha256 hash of srctypes>] * This is the auto generated pool for the enterprise fixed srctype stack * field descriptions are the same as that for the "lmpool:auto_generated_pool_forwarder" [lmpool:auto_generated_pool_download_trial] * This is the auto generated pool for the download trial stack * field descriptions are the same as that for the "lmpool:auto_generated_pool_forwarder" 204

Search head pooling configuration [pooling] state = [enabled disabled] * Enables or disables search head pooling. * Defaults to disabled. storage = <path to shared storage> * All members of a search head pool must have access to shared storage. * Splunk will store configurations and search artifacts here. * On *NIX, this should be an NFS mount. * On Windows, this should be a UNC path to a Samba/CIFS share. lock.timeout = <time range string> * Timeout for acquiring file-based locks on configuration files. * Splunk will wait up to this amount of time before aborting a configuration write. * Defaults to '10s' (10 seconds). lock.logging = [true false] * When acquiring a file-based lock, log information into the locked file. * This information typically includes: * Which host is acquiring the lock * What that host intends to do while holding the lock * There is no maximum filesize or rolling policy for this logging. If you enable this setting, you must periodically truncate the locked file yourself to prevent unbounded growth. * The information logged to the locked file is intended for debugging purposes only. Splunk makes no guarantees regarding the contents of the file. It may, for example, write padding NULs to the file or truncate the file at any time. * Defaults to false. poll.interval.rebuild = <time range string> * Rebuild or refresh in-memory configuration data structures at most this often. * Defaults to '1s' (1 second). poll.interval.check = <time range string> * Check on-disk configuration files for changes at most this often. * Defaults to '30s' (30 seconds). poll.blacklist.<name> = <regex> * Do not check configuration files for changes if they match this regular expression. * Example: Do not check vim swap files for changes --.swp$ High availability clustering configuration [clustering] mode = [master slave searchhead disabled] * Sets operational mode for this cluster node. * Only one master may exist per cluster. * Defaults to disabled. master_uri = [<uri> clustermaster:stanzaname1, clustermaster:stanzaname2] * Only valid for mode=slave or searchhead * uri of the cluster master that this slave or searchhead should connect to. * An example of <uri>: <scheme>://<hostname>:<port> * Only for mode=searchhead - If the searchhead is a part of multiple clusters, * the master uris can be specified by a comma separated list. pass4symmkey = <string> * Secret shared among the nodes in the cluster to prevent any arbitrary node from connecting to the cluster. If a slave or searchhead is not configured with the same secret as the master, it will not be able to communicate with the master. * Not set by default. * If it is not set in the clustering stanza, the key will be looked in 205

the general stanza cxn_timeout = <seconds> * Lowlevel timeout for establishing connection between cluster nodes. * Defaults to 60s. send_timeout = <secomds> * Lowlevel timeout for sending data between cluster nodes. * Defaults to 60s. rcv_timeout = <seconds> * Lowlevel timeout for receiving data between cluster nodes. * Defaults to 60s. rep_cxn_timeout = <seconds& gt; * Lowlevel timeout for establishing connection for replicating data. * Defaults to 5s. rep_send_timeout = <secomds> * Lowlevel timeout for sending replication slice data between cluster nodes. * This is a soft timeout. When this timeout is triggered on source peer, it tries to determine if target is still alive. If it is still alive, it reset the timeout for another rep_send_timeout interval and continues. If target has failed or cumulative timeout has exceeded rep_max_send_timeout, replication fails. * Defaults to 5s. rep_rcv_timeout = <seconds> * Lowlevel timeout for receiving acknowledgement data from peers. * This is a soft timeout. When this timeout is triggered on source peer, it tries to determine if target is still alive. If it is still alive, it reset the timeout for another rep_send_timeout interval and continues. If target has failed or cumulative timeout has exceeded rep_max_rcv_timeout, replication fails. * Defaults to 10s. rep_max_send_timeout = <seconds> * Maximum send timeout for sending replication slice data between cluster nodes. * On rep_send_timeout source peer determines if total send timeout has exceeded rep_max_send_timeout. If so, replication fails. * If cumulative rep_send_timeout exceeds rep_max_send_timeout, replication fails. * Defaults to 600s. rep_max_rcv_timeout = <seconds> * Maximum cumulative receive timeout for receiving acknowledgement data from peers. * On rep_rcv_timeout source peer determines if total receive timeout has exceeded rep_max_rcv_timeout. If so, replication fails. * Defaults to 600s. replication_factor = <positive integer> * Only valid for mode=master. * Determines how many copies of rawdata are created in the cluster. Set this to N, where N is how many peers you have. * Must be greater than 0. * Defaults to 3 search_factor = <positive integer> * Only valid for mode=master * Determines how many buckets will have index structures pre-built. & nbsp; * Must be less than or equal to replication_factor and greater than 0. * Defaults to 2. heartbeat_timeout = <positive integer> * Only valid for mode=master * Determines when the master considers a slave down. Once a slave is down, the master will initiate fixup steps to replicate buckets from the dead slave to its peers. * Defaults to 60s. restart_timeout = <positive integer> * Only valid for mode=master * This is the amount of time the master waits for a peer to come 206

back when the peer is restarted (to avoid the overhead of trying to fixup the buckets that were on the peer). * Note that currently this only works if the peer is restarted vi the UI. * Defaults to 600s. quiet_period = <positive integer> * Only valid for mode=master * This determines the amount of time for which the master is quiet right after it starts. During this period the master does not initiate any action but is instead waiting for the slaves to register themselves. At the end of this time period, it builds its view of the cluster based on the registered information and starts normal processing. * Defaults to 60s. generation_poll_interval = <positive integer> * Only valid if mode=master or mode=searchhead * Determines how often the searchhead polls the master for generation information. * Defaults to 60s. max_peer_build_load = <integer> * This is the maximum number of concurrent tasks to make buckets searchable that can be assigned to a peer. * Defaults to 5. max_peer_rep_load = <integer> * This is the maximum number of concurrent non-streaming replications that a peer can take part in as a target. * Defaults to 5. searchable_targets = <bool> * Only valid for mode=master * Tells the master to make some replication targets searchable even while the replication is going on. This only affects hot bucket replication for now. * Defaults to true register_replication_address = <ip or fully qualified machine/domain name> * Only valid for mode=slave * This is the address on which a slave will be available for accepting replication data. This is useful in the cases where a slave host machine has multiple interaces and only one of them can be reached by another splunkd instance register_forwarder_address = <ip or fully qualified machine/domain name> * Only valid for mode=slave * This is the address on which a slave will be available for accepting data from forwarder.this is useful in the cases where a splunk host machine has multiple interaces and only one of them can be reached by another splunkd instance. ` register_search_address = <ip or fully qualified machine/domain name> * Only valid for mode=slave * This is the address on which a slave will be available as search head. This is useful in the cases where a splunk host machine has multiple interaces and only one of them can be reached by another splunkd instance. heartbeat_period = <non-zero positive integer> * Only valid for mode=slave * Controls the frequency the slave attempts to send heartbeats enables2sheartbeat = [true false] * Only valid for mode=slave * Splunk will monitor each replication connection for presence of heartbeat, and if the heartbeat is not seen for s2sheartbeattimeout seconds, it will close the connection. * Defaults to true. s2sheartbeattimeout = <seconds> * This specifies the global timeout value for monitoring heartbeats on replication connections. * Splunk will will close a replication connection if heartbeat is not seen for s2sheartbeattimeout seconds. 207

* Defaults to 120 seconds (2 minutes). Replication source sends heartbeat every 30 second. [clustermaster:stanza1] * Only valid for mode=searchhead when the searchhead is a part of multiple clusters. master_uri = <uri> * Only valid for mode=searchhead when present in this stanza. * uri of the cluster master that this searchhead should connect to. pass4symmkey = <string> * Secret shared among the nodes in the cluster to prevent any arbitrary node from connecting to the cluster. If a searchhead is not configured with the same secret as the master, it will not be able to communicate with the master. * Not set by default. * If it is not present here, the key in the clustering stanza will be used. If it is not present in the clustering stanza, the value in the general stanza will be used. [replication_port://<port>] Configure Splunk to listen on a given TCP port for replicated data from another cluster member. If mode=slave is set in the [clustering] stanza at least one replication_port must be configured and not disabled. disabled = <bool> * Set to true to disable this replication port stanza. * Defaults to false. listenonipv6 = <no yes only> * Toggle whether this listening port will listen on IPv4, IPv6, or both. * If not present, the setting in the [general] stanza will be used. acceptfrom = <network_acl>... * Lists a set of networks or addresses to accept connections from. These rules are separated by commas or spaces * Each rule can be in the following forms: * 1. A single IPv4 or IPv6 address (examples: "10.1.2.3", "fe80::4a3") * 2. A CIDR block of addresses (examples: "10/8", "fe80:1234/32") * 3. A DNS name, possibly with a '*' used as a wildcard (examples: "myhost.example.com", "*.splunk.com") * 4. A single '*' which matches anything * Entries can also be prefixed with '!' to cause the rule to reject the connection. Rules are applied in order, and the first one to match is used. For example, "!10.1/16, *" will allow connections from everywhere except the 10.1.*.* network. * Defaults to "*" (accept replication data from anywhere) [replication_port-ssl://<port>] * This configuration is same as replication_port stanza above but uses SSL. disabled = <bool> * Set to true to disable this replication port stanza. * Defaults to false. listenonipv6 = <no yes only> * Toggle whether this listening port will listen on IPv4, IPv6, or both. * If not present, the setting in the [general] stanza will be used. acceptfrom = <network_acl>... * This setting is same as setting in replication_port stanza defined above. servercert = <path> * Full path to file containing private key and server certificate. * There is no default value. password = <string> * Server certificate password, if any. * There is no default value. rootca = <string> * The path to the file containing the SSL certificate for root certifying authority. * The file may also contain root and intermediate certificates, if required. * There is no default value. 208

ciphersuite = <cipher suite string> * If set, uses the specified cipher string for the SSL connection. * If not set, uses the default cipher string. * provided by OpenSSL. This is used to ensure that the server does not accept connections using weak encryption protocols. supportsslv3only = [true false] * If true, it only accept connections from SSLv3 clients. * Default is false. compressed = [true false] * If true, it enables compression on SSL. * Default is true. requireclientcert = [true false] * Requires that any peer that connects to replication port has a certificate that can be validated by certificate authority specified in rootca. * Default is false. server.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains an example server.conf. Use this file to configure SSL and HTTP server options. To use one or more of these configurations, copy the configuration block into server.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles Allow users 8 hours before they time out [general] sessiontimeout=8h pass4symmkey = changeme Listen on IPv6 in addition to IPv4... listenonipv6 = yes...but make all outgoing TCP connections on IPv4 exclusively connectusingipversion = 4-only Turn on SSL: [sslconfig] enablesplunkdssl = true useclientsslcompression = true sslkeysfile = server.pem sslkeysfilepassword = password cacertfile = cacert.pem capath = $SPLUNK_HOME/etc/auth certcreatescript = genmyservercert.sh SSO Example This example trusts all logins from the splunk web server and localhost Note that a proxy to the splunk web server should exist to enforce authentication [general] trustedip = 127.0.0.1 Set this node to be a cluster master. [clustering] mode = master replication_factor = 3 209

pass4symmkey = somesecret search_factor = 2 Set this node to be a slave to cluster master "SplunkMaster01" on port 8089. [clustering] mode = slave master_uri = https://splunkmaster01.example.com:8089 pass4symmkey = somesecret Set this node to be a searchhead to cluster master "SplunkMaster01" on port 8089. [clustering] mode = searchhead master_uri = https://splunkmaster01.example.com:8089 pass4symmkey = somesecret Set this node to be a searchhead to multiple cluster masters - "SplunkMaster01" with pass4symmkey set to 'somesecret and "SplunkMaster02" with no pass4symkey set here. [clustering] mode = searchhead master_uri = clustermaster:east, clustermaster:west [clustermaster:east] master_uri=https://splunkmaster01.example.com:8089 pass4symmkey=somesecret [clustermaster:west] master_uri=https://splunkmaster02.example.com:8089 serverclass.conf 다음은 serverclass.conf의 사양 및 예제 파일입니다. serverclass.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attributes and values for defining server classes to which deployment clients can belong. These attributes and values specify what content a given server class member will receive from the deployment server. To define server classes for this deployment server to use when deploying content to deployment clients, place a serverclass.conf in $SPLUNK_HOME/etc/system/local/. For examples, see serverclass.conf.example. You must restart Splunk for changes to this file to take effect. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. *************************************************************************** Configure the server classes that are used by a deployment server instance. 210

Server classes are essentially categories. They use filters to control what clients they apply to, contain a set of applications, and may define deployment server behavior for the management of those applications. The filters can be based on dns name, ip address, build number of client machines, platform, and so-called clientname tag strings. If a target machine matches the filter, then the apps and configuration content that make up the server class will be deployed to it. Property inheritance Stanzas in serverclass.conf go from general to more specific, in the following order: [serverclass] -> [serverclass:<name>] -> [serverclass:<scname>:app:<appname>] Some properties defined at a general level (say [serverclass]) can be overridden by the more specific stanzas as it applies to them. All inheritable properties are marked as such. *************************************************************************** Global stanza that defines properties for all server classes. [global] repositorylocation = <path> * The repository of applications on the server machine. & nbsp; * Can be overridden at the serverclass level. * Defaults to $SPLUNK_HOME/etc/deployment-apps targetrepositorylocation = <path> * The location on the deployment client to install the apps and configuration content defined for this server class. * If this value is unset, or set emptyr the repositorylocation path is used. * Useful only for complex (for example, tiered) deployment strategies. * Defaults to $SPLUNK_HOME/etc/apps, the live configuration directory for a Splunk instance. tmpfolder = <path> * Working folder used by deployment server. * Defaults to $SPLUNK_HOME/var/run/tmp continuematching = true false * Controls how configuration is layered across classes and server-specific settings. * If true, configuration lookups continue matching server classes, beyond the first match. * If false, only the first match will be used. * A serverclass can override this property and stop the matching. * Matching is done in the order that server classes are defined. * Can be overridden at the serverclass level. * Defaults to true endpoint = <URL template string> * The endpoint from which content can be downloaded by a deployment client. The deployment client knows how to substitute the values of the variables in the URL. * Any custom URL can also be supplied here as long as it uses the specified variables. * This attribute does not need to be specified unless you have very specific need, for example: to acquire deployment application files from a third-party httpd, for extremely large environments. * Can be overridden at the serverclass level. * Defaults to $deploymentserveruri$/services/streams/deployment?name=$serverclassname$:$appname$ filtertype = whitelist blacklist * The whitelist setting indicates a filtering strategy that pulls in a subset: * Items are not considered to match the stanza by default. * Items that match any whitelist entry, and do not match any blacklist entry are considered to match the stanza. * Items that match any blacklist entry are not considered to match the stanza, regardless of whitelist. * The blacklist setting indicates a filtering strategy that rules out a subset: * Items are considered to match the stanza by default. & nbsp; * Items that match any blacklist entry, and do not match any whitelist entry are considered to not match the stanza. * Items that match any whitelist entry are considered to match the stanza. * More briefly: * whitelist: default no-match -> whitelists enable -> blacklists disable * blacklist: default match -> blacklists disable-> whitelists enable * Can be overridden at the serverclass level, and the serverclass:app level. * Defaults to whitelist whitelist.<n> = <clientname> <ip address> <hostname> 211

blacklist.<n> = <clientname> <ip address> <hostname> * 'n' is a number starting at 0, and increasing by 1. Stop looking at the filter when 'n' breaks. * The value of this attribute is matched against several things in order: * Any clientname specified by the client in its deploymentclient.conf file * The ip address of the connected client * The hostname of the connected client as provided by reverse DNS lookup * The hostname of the client as provided by the client * All of these can be used with wildcards. * will match any sequence of characters. For example: * Match an network range: 10.1.1.* * Match a domain: *.splunk.com * These patterns are PCRE regular expressions with the additional mappings: & nbsp; * '.' is mapped to '\.' * '*' is mapped to '.*' * Can be overridden at the serverclass level, and the serverclass:app level. * There are no whitelist or blacklist entries by default. Note: Overriding one type of filter (whitelist/blacklist) causes the other to the overridden too. It is important to note that if you are overriding the whitelist, the blacklist will not be inherited from the parent - you must provide one in the stanza. Example of when filtertype is whitelist whitelist.0=*.splunk.com blacklist.0=printer.splunk.com blacklist.1=scanner.splunk.com This will cause all hosts in splunk.com, except 'printer' and 'scanner' to match this server class. Example of when filtertype is blacklist blacklist.0=* whitelist.0=*.web.splunk.com whitelist.1=*.linux.splunk. com This will cause only the 'web' and 'linux' hosts to match the server class. No other hosts will match. client machinetypes can also be used to match clients. This setting lets you use the hardware type of the deployment client as a filter. This filter will be used only if a client could not be matched using the whitelist/blacklist filter. The value for machinetypes is a specific string that is designated by the hardware platform itself. The method for finding this string on the client itself will vary by platform, but if the deployment client is already connected to the deployment server, you can determine what this string is by using this Splunk CLI command on the deployment server: <code>./splunk list deploy-clients</code> This will return a value for <code>utsname</code> that you can use to specify <code>machinetypes</code>. machinetypes = <comma separated list> * This setting is deprecated. Please use machinetypesfilter instead. * For legacy purposes, if used, it will continue to work. * Not used unless specified. * Match any of the machine types in the comma-delimited list. * Commonly used machine types: linux-x86_64, windows-intel, linux-i686, freebsd-i386, darwin-i386, sunos-sun4u * This filter is used in boolean OR logic with white/blacklist filters. Clients which match the white/blacklist are included, and clients which match the machinetypes filter are included. This means a system which matches either rule will be considered to match. * In other words, the match is a union of the matches for the white/blacklist and the & nbsp; matches for machinetypes. * Be sure to include the 's' at the end of "machinetypes" * This filter can be overridden at the serverclass and serverclass:app levels. * This value is unset by default. machinetypesfilter = <comma separated list> * Not used unless specified. * Matches any of the machine types in the comma-delimited list. * Commonly used machine types: linux-x86_64, windows-intel, linux-i686, freebsd-i386, darwin-i386, sunos-sun4u * This filter is used in in boolean AND logic with white/blacklist filters. Only clients which match the white/blacklist AND which match this maachinetypesfilter will be included. * In other words, the match is an intersection of the matches for the white/blacklist and the matches for MachineTypesFilter. * This filter can be overridden at the serverclass and serverclass:app levels. * This filter is unset by default. * If both the machinetypes and machinetypesfilter attributes are specified, machinetypes is ignored. 212

restartsplunkweb = True False * If True, restart SplunkWeb on the client when a member app or directly configured app is updated. * Can be overridden at the serverclass level, and the serverclass:app level. * Defaults to False restartsplunkd = True False * If True, restart splunkd on the client when a member app or directly configured app is updated. * Can be overridden at the serverclass level, and the serverclass:app level. * Defaults to False stateonclient = enabled disabled noop * For enabled, set the application state to enabled on the client, regardless of state on the deployment server. * For disable, set the application state to disabled on the client, regardless of state on the deployment server. * For noop, the state on the client will be the same as on the deployment server. * Can be overridden at the serverclass level, and the serverclass:app level. * Defaults to enabled. [serverclass:<serverclassname>] * This stanza defines a server class. A serverclass is a collection of applications. * serverclassname is a unique name that is assigned to this serverclass. * A serverclass can override all inheritable properties from the [serverclass] stanza. NOTE: the following keys listed below are all described in detail in the [global] section above, but can be used with serverclass stanza to override the global setting continuematching = true false endpoint = <URL template string> filtertype = whitelist blacklist whitelist.<n> = <clientname> <ip address> <hostname> blacklist.<n> = <clientname> <ip address> <hostname> machinetypes = <comma separated list> machinetypesfilter = <comma separated list> restartsplunkweb = True False restartsplunkd = True False stateonclient = enabled disabled noop repositorylocation = <path> [serverclass:<server class name>:app:<app name>] * This stanza adds an application that exists in repositorylocation to the server class. * server class name - the server class to which this content should be added. * app name can be '*' or the name of an app: * The value '*' refers to all content in the repositorylocation, adding it to this serverclass. '*' stanzas cannot be mixed with named stanzas. * Other values 'someappname' explicitly adds the app/configuration content to a server class. Typically apps are named by the folders that contain them. * Important note on matching: A server class must be matched before content belonging to the server class will be matched by the system. appfile=<file name> * In cases where an appname is different from the file or directory name, you can use this parameter to specify the file name. Supported formats are: app directories,.tar or.tgz files. serverclass.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 Example 1 Matches all clients and includes all apps in the server class [global] whitelist.0=* whitelist matches all clients. [serverclass:allapps] [serverclass:allapps:app:*] a server class that encapsulates all apps in the repositorylocation 213

Example 2 Assign server classes based on dns names. [global] [serverclass:appsforops] whitelist.0=*.ops.yourcompany.com [serverclass:appsforops:app:unix] [serverclass:appsforops:app:splunklightforwarder] [serverclass:appsfordesktops] filtertype=blacklist blacklist everybody except the Windows desktop machines. blacklist.0=* whitelist.0=*.desktops.yourcompany.com [serverclass:appsfordesktops:splunkdesktop] Example 3 Deploy server class based on machine types [global] [serverclass: AppsByMachineType] Ensure this server class is matched by all clients. It is IMPORTANT to have a general filter here, and a more specific filter at the app level. An app is matched _only_ if the server class it is contained in was successfully matched! whitelist.0=* [serverclass:appsbymachinetype:app:splunkdesktop] Deploy this app only to Windows boxes. machinetypesfilter=windows-* [serverclass:appsbymachinetype:app:unix] Deploy this app only to unix boxes - 32/64 bit. machinetypesfilter=linux-i686, linux-x86_64 serverclass.seed.xml.conf 다음은 serverclass.seed.xml.conf의 사양 및 예제 파일입니다. serverclass.seed.xml.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 <!-- This configuration is used by deploymentclient to seed a Splunk installation with applications, at startup time. This file should be located in the workingdir folder defined by deploymentclient.conf. An interesting fact - the DS -> DC communication on the wire also uses this XML format. --> <?xml version="1.0"?> <deployment name="somename"> <!-- The endpoint from which all apps can be downloaded. This value can be overriden by serviceclass or ap declarations below. In addition, deploymentclient.conf can control how this property is used by deploymentclient - see deploymentclient.conf.spec. --> <endpoint>$deploymentserveruri$/services/streams/deployment? name=$serviceclassname$:$appname$</endpoint> <!-- The location on the deploymentclient where all applications will be installed. This value can be overriden by serviceclass or app declarations below. 214

In addition, deploymentclient.conf can control how this property is used by deploymentclient - see deploymentclient.conf.spec. --> <repositorylocation>$splunk_home/etc/apps</repositorylocation> <serviceclass name="serviceclassname"> <!-- The order in which this service class is processed. --> <order>n</order> & nbsp; <!-- DeploymentClients can also override these values using serverrepositorylocationpolicy and serverendpointpolicy. --> <repositorylocation>$splunk_home/etc/myapps</repositorylocation> <endpoint>splunk.com/spacecake/$serviceclassname$/$appname$.tgz</endpoint> <!-- Please See serverclass.conf.spec for how these properties are used. --> <continuematching>true</continuematching> <restartsplunkweb>false</restartsplunkweb> <restartsplunkd>false</restartsplunkd> <stateonclient>enabled</stateonclient> <app name="appname1"> <!-- Applications can override the endpoint property. --> <endpoint>splunk.com/spacecake/$appname$</endpoint> </app> <app name="appname2"/> </serviceclass> </deployment> serverclass.seed.xml.conf.example <?xml version="1.0" encoding="utf-8"?> <deployment name="root"> <serverclass name="spacecake_apps"> <app name="app_0"> <repositorylocation>$splunk_home/etc/myapps</repositorylocation> <!-- Download app_0 from the given location --> <endpoint>splunk.com/spacecake/apps/app_0.tgz</endpoint> </app> <app name="app_1"> <repositorylocation>$splunk_home/etc/myapps</repositorylocation> <!-- Download app_1 from the given location --> <endpoint>splunk.com/spacecake/apps/app_1.tgz</endpoint> & nbsp; </app> </serverclass> <serverclass name="foobar_apps"> <!-- construct url for each location based on the scheme below and download each app --> <endpoint>foobar.com:5556/services/streams/deployment?name=$serverclassname$_$appname$.bundle</endpoint> <app name="app_0"/> <app name="app_1"/> <app name="app_2"/> </serverclass> <serverclass name="local_apps"> <endpoint>foo</endpoint> <app name="app_0"> <!-- app present in local filesystem --> <endpoint>file:/home/johndoe/splunk/ds/service_class_2_app_0.bundle& lt;/endpoint> </app> <app name="app_1"> <!-- app present in local filesystem --> <endpoint>file:/home/johndoe/splunk/ds/service_class_2_app_1.bundle</endpoint> 215

</app> <app name="app_2"> <!-- app present in local filesystem --> <endpoint>file:/home/johndoe/splunk/ds/service_class_2_app_2.bundle</endpoint> </app> </serverclass> </deployment> setup.xml.conf 다음은 setup.xml.conf의 사양 및 예제 파일입니다. setup.xml.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 <!-- This file describes the setup XML config and provides some examples. setup.xml provides a Setup Screen that you provide to users to specify configurations for an app. The Setup Screen is available when the user first runs the app or from the Splunk Manager: Splunk > Manager > Apps > Actions > Set up Place setup.xml in the app's default directory: $SPLUNK_HOME/etc/apps/<app>/default/setup.xml The basic unit of work is an <input>, which is targeted to a triplet (endpoint, entity, field) and other information used to model the data. For example data type, validation information, name/label, etc. The (endpoint, entity, field attributes) identifies an object where the input is read/written to, for example: endpoint=saved/searches entity=mysavedsearch field=cron_schedule The endpoint/entities addressing is relative to the app being configured. Endpoint/entity can be inherited from the outer blocks (see below how blocks work). Inputs are grouped together within a <block> element: (1) blocks provide an iteration concept when the referenced REST entity is a regex (2) blocks allow you to group similar configuration items (3) blocks can contain <text> elements to provide descriptive text to the user. (4) blocks can be used to create a new entry rather than edit an already existing one, set the entity name to "_new". NOTE: make sure to add the required field 'name' as an input. (5) blocks cannot be nested See examples below. Block Node attributes: endpoint - The REST endpoint relative to "https://hostname:port/servicesns/nobody/<app- name>/" of entities/object the block/input addresses. Generally, an endpoint maps to a Splunk configuration file. entity - An object at the endpoint. Generally, this maps to a stanza name in a configuration file. NOTE: entity names should be URI encoded. mode - (bulk iter) used if the entity attribute is a regular expression: 216

o iter - (default value for mode) Iterate over all matching entities and provide a separate input field for each. o bulk - Update all matching entities with the same value. NOTE: splunk interprets '*' as the regex '.*' eai_search - a search to filter entities returned by an endpoint. If not specified the following search is used: eai:acl.app="" OR eai:acl.app="<current-app>" This search matches only objects defined in the app which the setup page is being used for. NOTE: if objects from another app are allowed to be configured, any changes to those objects will be stored in the current app. enabled - (true false in-windows in-unix) whether this block is enabled or not o true - (default) this block is enabled o false - block disabled o in-windows - block is enabled only in windows installations o in-unix - block is enabled in non-windows installations Input Node Attributes: endpoint - see description above (inherited from block) entity - see description above (inherited from block) field & nbsp; - <string> the field which is being configured old_style_disable - <bool> whether to perform entity disabling by submiting the edited entity with the following field set: disabled=1. (This is only relevant for inputs whose field=disabled enabled). Defaults to false. Nodes within an <input> element can display the name of the entity and field values within the entity on the setup screen. Specify $name$ to display the name of the entity. Use $<field_name>$ to specify the value of a specified field. --> <setup> <block title="basic stuff" endpoint="saved/searches/" entity="foobar"> & lt;text> some description here </text> <input field="is_scheduled"> <label>enable Schedule for $name$</label> <!-- this will be rendered as "Enable Schedule for foobar" --> <type>bool</type> </input> <input field="cron_scheduled"> <label>cron Schedule</label> <type>text</type> </input> <input field="actions"> <label>select Active Actions</label> <type>list</type> </input> & nbsp; <!-- bulk update --> <input entity="*" field="is_scheduled" mode="bulk"> <label>enable Schedule For All</label> <type>bool</type> </input> </block> <!-- iterative update in this block --> <block title="configure search" endpoint="saved/eventypes/" entity="*" mode="iter"> <input field="search"> <label>$name$ search</label> <type>string</type> </input> <input field="disabled"> & nbsp; <label>disable $name$</label> <type>bool</type> 217

</input> </block> <block title="create a new eventtype" endpoint="saved/eventtypes/" entity="_new"> <input target="name"> <label>name</label> <type>text</type> </input> <input target="search"> <label>search</label> <type>text</type> </input> </block> <block title="add Account Info" endpoint="admin/passwords" entity="_new"> <input field="name"> <label>username</label> <type>text</type> </input> <input field="password"> <label>password</label> <type>password</type> </input> </block> <!-- example config for "Windows setup" --> <block title="collect local event logs" endpoint="admin/win-eventlogs/" eai_search="" > <text> Splunk for Windows needs at least your local event logs to demonstrate how to search them. You can always add more event logs after the initial setup in Splunk Manager. </text> <input entity="system" field="enabled" old_style_disable="true"> <label>enable $name$</label> <type>bool</type> </input> <input entity="security" field="enabled" old_style_disable="true"> <label>enable $name$</label> <type>bool</type> </input> <input entity="application" field="enabled" old_style_disable="true"> & nbsp; <label>enable $name$</label> <type>bool</type> </input> </block> <block title="monitor Windows update logs" endpoint="data/inputs/monitor"> <text> If you monitor the Windows update flat-file log, Splunk for Windows can show your patch history. You can also monitor other logs if you have them, such as IIS or DHCP logs, from Data Inputs in Splunk Manager </text> <input entity="%24windir%5cwindowsupdate.log" field="enabled"> <label>enable $name$</label> <type>bool</type> & lt;/input> </block> </setup> setup.xml.conf.example No example source-classifier.conf 다음은 source-classifier.conf의 사양 및 예제 파일입니다. 218

source-classifier.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains all possible options for configuring settings for the file classifier in source-classifier.conf. There is a source-classifier.conf in $SPLUNK_HOME/etc/system/default/ To set custom configurations, place a source-classifier.conf in $SPLUNK_HOME/etc/system/local/. For examples, see source-classifier.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles ignored_model_keywords = <space-separated list of terms> * Terms to ignore when generating a sourcetype model. * To prevent sourcetype "bundles/learned/*-model.xml" files from containing sensitive terms (e.g. "bobslaptop") that occur very frequently in your data files, add those terms to ignored_model_keywords. ignored_filename_keywords = <space-separated list of terms> * Terms to ignore when comparing a new sourcename against a known sourcename, for the purpose of classifying a source. source-classifier.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains an example source-classifier.conf. Use this file to configure classification of sources into sourcetypes. To use one or more of these configurations, copy the configuration block into source-classifier.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles terms to ignore when generating sourcetype model to prevent model from containing servernames, ignored_model_keywords = sun mon tue tues wed thurs fri sat sunday monday tuesday wednesday thursday friday saturday jan feb mar apr may jun jul aug sep oct nov dec january february march april may june july august september october november december 2003 2004 2005 2006 2007 2008 2009 am pm ut utc gmt cet cest cetdst met mest metdst mez mesz eet eest eetdst wet west wetdst msk msd ist jst kst hkt ast adt est edt cst cdt mst mdt pst pdt cast cadt east eadt wast wadt terms to ignore when comparing a sourcename against a known sourcename ignored_filename_keywords = log logs com common event events little main message messages queue server splunk sourcetypes.conf 다음은 sourcetypes.conf의 사양 및 예제 파일입니다. sourcetypes.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 NOTE: sourcetypes.conf is a machine-generated file that stores the document models used by the file classifier for creating source types. Generally, you should not edit sourcetypes.conf, as most attributes are machine generated. However, there are two attributes which you can change. There is a sourcetypes.conf in $SPLUNK_HOME/etc/system/default/ To set custom 219

configurations, place a sourcetypes..conf in $SPLUNK_HOME/etc/system/local/. For examples, see sourcetypes.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. _sourcetype = <value> * Specifies the sourcetype for the model. * Change this to change the model's sourcetype. * Future sources that match the model will receive a sourcetype of this new name. _source = <value> * Specifies the source (filename) for the model. sourcetypes.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains an example sourcetypes.conf. Use this file to configure sourcetype models. NOTE: sourcetypes.conf is a machine-generated file that stores the document models used by the file classifier for creating source types. Generally, you should not edit sourcetypes.conf, as most attributes are machine generated. However, there are two attributes which you can change. To use one or more of these configurations, copy the configuration block into sourcetypes.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles This is an example of a machine-generated sourcetype models for a fictitious sourcetype cadcamlog. [/Users/bob/logs/bnf.x5_Thu_Dec_13_15:59:06_2007_171714722] _source = /Users/bob/logs/bnf.x5 _sourcetype = cadcamlog L----------- = 0.096899 L-t<_EQ> = 0.016473 splunk-launch.conf 다음은 splunk-launch.conf의 사양 및 예제 파일입니다. splunk-launch.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 splunk-launch.conf contains values used during splunk startup time, by the splunk command and by windows services. Note, this conf file is different from most splunk conf files. There is only one in the whole system, located at $SPLUNK_HOME/etc/splunk-launch.conf 220

Any files in etc/apps/... or etc/users/... will be ignored. Lines beginning with a are considered comments and are ignored. ******* Environment variables Primarily, this file simply sets environment variables to be used by Splunk programs. These environment variables are the same type of system environment variables that can be set, on unix, using: bourne shells: $ export ENV_VAR=value c-shells: % setenv ENV_ VAR value or at a windows command prompt: C:\> SET ENV_VAR=value ******* <environment_variable>=<value> * Any desired environment variable can be set to any value. Whitespace is trimmed from around both the key and value. * Environment variables set here will be available to all splunk processes, barring operating system limitations. ******* Specific Splunk environment settings These settings are primarily treated as environment variables, though some have some additional logic (defaulting). There is no need to explicitly set any of these values in typical environments. ******* SPLUNK_HOME=<pathname> * The comment in the auto-generated splunk-launch.conf is informational, not a live setting, and does not need to be uncommented. * Fully qualified path to the Splunk install directory. * If unset, Splunk automatically determines the location of SPLUNK_HOME based on the location of splunk-launch.conf * Specifically, the parent of the directory containing splunk-launch.conf * Defaults to unset. SPLUNK_DB=<pathname> * The comment in the auto-generated splunk-launch.conf is informational, not a live setting, and does not need to be uncommented. * Fully qualified path to the directory containing the splunk index directories. * Primarily used by paths expressed in indexes.conf * The comment in the autogenerated splunk-launch.conf is informational, not a live setting, and does not need to be uncommented. * If unset, becomes $SPLUNK_HOME/var/lib/splunk (unix) or $SPLUNK_HOME\var\lib\splunk (windows) * Defaults to unset. SPLUNK_BINDIP=<ip address> * Specifies an interface that splunkd and splunkweb should bind to, as opposed to binding to the default for the local operating system. * If unset, Splunk makes no specific request operating system when binding to ports/opening a listening socket. This means it effectively binds to '*' or an unspecified bind. The exact result of this is contolled by operating system behavior and configuration. * NOTE: When using this setting you must update mgmthostport in web.conf to match, or the command line and splunkweb will not know how to reach splunkd. * For splunkd, this sets both the management port and the receiving ports (from forwarders). * Typically useful for a host with multiple IP addresses, either to enable access or restrict access, though firewalling is typically a superior choice 221

for restriction. * Overrides the Splunkweb-specific setting in web.conf of server.socket_host for historical reasons. That setting is preferred when SplunkWeb's behavior is the concern. * Defaults to unset. SPLUNK_IGNORE_SELINUX=true * If unset (not present), then Splunk on Linux will abort startup if it detects it is running in an SELinux environment. This is because in shipping/distribution-provided SELinux environments, Splunk will not be permitted to work, and Splunk will not be able to identify clearly why. * This setting is useful in environments where you have configured SELinux to enable Splunk to work. * If set to any value, Splunk will launch, despite the presence of SELinux. * Defaults to unset. ******* Service/server names. These settings are considered internal, and altering them is not supported. On windows, they influence the expected name of the service; on unix they influence the reported name of the appropriate server or daemon process. ******* SPLUNK_SERVER_NAME=<name> * Names the splunkd server/service. * Defaults to splunkd (unix), or Splunkd (windows). SPLUNK_WEB_NAME=<name> * Names the python app server / web server/service. * Defaults to splunkweb (unix), or Splunkweb (windows). splunk-launch.conf.example No example sysmon.conf 다음은 sysmon.conf의 사양 및 예제 파일입니다. sysmon.conf.spec Copyright (C) 2005-2011 Splunk Inc. All Rights Reserved. Version 4.2.5 This file contains possible attribute/value pairs for configuring Registry monitoring on a Windows system, including global settings for which event types (adds, deletes, renames, and so on) to monitor, which regular expression filters from the filter rules file (normally regmon-filters.conf) to use, and whether or not Windows Registry events are monitored at all. This file is used in conjunction with regmon-filters.conf, or a file that you reference in the "filter_file_name" attribute below. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles [<stanza name>] * Defaults to [RegistryMonitor] * Follow this stanza name with the following attribute/value pairs. filter_file_name = <string> * This attribute references the name of the file where filters for this monitor are stored. * For example, setting this attribute to "hklm_filters" will cause 222

splunk-regmon.exe to look in "hklm_filters.conf" for filter rules for this input. * Splunk-regmon.exe will read the contents of regmon-filters.conf if this attribute is not present. event_types = <string> * A regular expression string that specifies the type(s) of Registry events to monitor. * Regular expressions specified in this attribute can begin with one or more of the following strings: set, create, delete, rename, open, close, query. * When specifying multiple event type strings for this attribute, the individual event type elements must be separated by the pipe character (& quot; "). inclusive = [0 1] * Specifies whether the rules specified in the filter rules file are inclusive (a white list) or exclusive (a black list). * This attribute is required, and splunk-regmon.exe will not run for this input if the attribute is not present. * Set to 1 to specify that filter rules specified in the filter rules file are inclusive (white list), and 0 to specify that those rules are exclusive (black list). * There is no default. disabled = [0 1] * Specifies whether the input is enabled or not. * Set to 1 to disable the input, and 0 to enable it. * Defaults to 0 (enabled). proc_name = <string> * This attribute is no longer used. sysmon.conf.example Copyright (C) 2005-2011 Splunk Inc. All Rights Reserved. Version 4.2.5 This file contains an example configuration for monitoring changes to the Windows registry. Refer to sysmon.conf.spec for details. The following is an example of a registry monitor filter and process monitor filter. To create your own filters, modify the values using the information in regmon-filters.conf.spec. To use one or more of these configurations, copy the configuration block into sysmon-filters.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles Define the filter rules file as "regmon-filters.conf" and define the available event types "set", "create& quot;, "delete", and "rename". The filter rules specified in "regmon-filters.conf" are exclusive (black list), which means that the regular expressions in that file will be filtered if they match. [RegistryMonitor] filter_file_name = regmon-filters event_types = set.* create.* delete.* rename.* inclusive = 0 disabled = 0 Define the filter rules file as "procmon-filters.conf" and define the available event types "create", "exit" and "image". The filter rules specified in "procmon-filters.conf" are exclusive (black list), which means that the regular expressions in that file will be filtered if they match. [ProcessMonitor] filter_file_name = procmon-filters event_types = create.* exit.* image.* inclusive = 0 disabled = 1 223

tags.conf 다음은 tags.conf의 사양 및 예제 파일입니다. tags.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attribute/value pairs for configuring tags. Set any number of tags for indexed or extracted fields. There is no tags.conf in $SPLUNK_HOME/etc/system/default/. To set custom configurations, place a tags.conf in $SPLUNK_HOME/etc/system/local/. For help, see tags.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles [<fieldname>=<value>] * The field name and value to which the tags in the stanza apply ( eg host=localhost ). * A tags.conf file can contain multiple stanzas. It is recommended that the value be URL encoded to avoid & nbsp; * config file parsing errors especially if the field value contains the following characters: \n, =, [] * Each stanza can refer to only one field=value <tag1> = <enabled disabled> <tag2> = <enabled disabled> <tag3> = <enabled disabled> * Set whether each <tag> for this specific <fieldname><value> is enabled or disabled. * While you can have multiple tags in a stanza (meaning that multiple tags are assigned to the same field/value combination), only one tag is allowed per stanza line. In other words, you can't have a list of tags on one line of the stanza. * WARNING: Do not quote the <tag> value: foo=enabled, not "foo"=enabled. tags.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This is an example tags.conf. Use this file to create regexes and rules for transforms. Use this file in tandem with props.conf. To use one or more of these configurations, copy the configuration block into transforms.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles This first example presents a situation where the field is "host" and the three hostnames for which tags are being defined are "hostswitch," "emailbox," and "devmachine." Each hostname has two tags applied to it, one per line. Note also that the "building1" tag has been applied to two hostname values (emailbox and devmachine). [host=hostswitch] pci = enabled cardholder-dest = enabled [host=emailbox] email = enabled building1 = enabled [host=devmachine] development = enabled building1 = enabled [src_ip=192.168.1.1] 224

firewall = enabled [seekptr=1cb58000] EOF = enabled NOT_EOF = disabled tenants.conf The following are the spec and example files for tenants.conf. tenants.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 Use tenants.conf to redirect incoming requests from deployment clients to another deployment server or servers. This is typically used for offloading load on your splunkd's HTTP server. This is not a typical configuration for deployment server. There is no default tenants.conf *There is no need to create/edit tenants.conf* unless you have worked with Splunk Professional Services to design a custom deployment that includes explicit involvement of tenants.conf. To set custom configurations, place a pubsub.conf in $SPLUNK_HOME/etc/system/local/. For examples, see pubsub.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. *************************************************************************** Configure tenants (DeploymentServer instances) within the same Splunk server. Multiple instances of deployment servers can be configured withing the same Splunk instance using this configuration file. If this file is missing, a default DeploymentServer for tenant='default'is configured by the system, if there exists serverclass.conf or default-serverclass.conf. It is possible to redirect deployment clients to the appropriate instance of deployment server by using a whitelist/blacklist mechanism, similar to the one in serverclass.conf. How does it all work? A DeploymentClient does a handshake with TenantService to determine which DeploymentServer it should be talking to. The TenantService will use this configuration to redirect a client to the appropriate deployment server (represented by phonehometopic). How is multi-tenant configuration stored? Server class configuration for each tenant should be made available in: <tenantname>-serverclass.conf Configuration for the 'default' tenant can also be in 'serverclass.conf' - note the missing tenantname prefix. ************* ************************************************************** [tenant:<tenantname>] filtertype = <whitelist or blacklist> * defaults to whitelist whitelist.<n> = <ipaddress or hostname or clientname> blacklist.<n> = <ipaddress of hostname of clientname> * 'n' is a number starting at 0, and increasing by 1. Stop looking at the filter when 'n' breaks. 225

* ipaddress of deployment client. Can also use wildcards as 10.1.1.* * hostname of deployment client. Can also use wildcards as *.splunk.com. * clientname- a logical or 'tag' name that can be assigned to each deployment client in deploymentclient.conf. clientname takes precedence (over ip/hostname) when matching a client to a filter. Internal. phonehometopic=deploymentserver/phonehome/$tenantname$ * some unique suffix. Default is to use the tenant name. Make sure this value is unique. * Override this value only when you wish to script and roll your own deployment server. tenants.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 Define two tenants - dept1 and dept2. DS Configuration for dept1 will be in a matching dept1-serverclass.conf DS Configuration for dept2 will be in a matching dept2-serverclass.conf [tenant:dept1] whitelist.0=*.dept1.splunk.com [tenant:dept2] whitelist.0=*.dept2.splunk.com times.conf The following are the spec and example files for times.conf. times.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attribute/value pairs for creating custom time ranges. To set custom configurations, place a times.conf in $SPLUNK_HOME/etc/system/local/. For help, see times.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. [<timerange_name>] * The token to be used when accessing time ranges via the API or command line * A times.conf file can contain multiple stanzas. label = <string> * The textual description used by the UI to reference this time range * Required header_label = <string> * The textual description used by the UI when displaying search results in this time range. * Optional. If omitted, the <timerange_name> is used instead. earliest_time = <relative_time_identifier> * The relative time identifier string that represents the earliest event to to return, inclusive. * Optional. If omitted, no earliest time bound is used. 226

latest_time = <relative_time_identifier> * The relative time identifier string that represents the latest event to to return, exclusive. * Optional. If omitted, no latest time bound is used. NOTE: events that occur in the future (relative to the server timezone) may be returned. order = <integer> * The key on which all custom time ranges are sorted, ascending. * The default time range selector in the UI will merge and sort all time ranges according to the 'order' key, and then alphabetically. * Optional. Default value is 0. sub_menu = <submenu name> * if present, the time range is to be shown in the given submenu instead of in the main menu. * the value for this key must be the label key of an existing stanza name, and that stanza name must have an is_sub_menu = True key * Optional. If omitted the given time option will display in the main menu. is_sub_menu = <boolean> * If True, the given item is only the 'opener' element for a submenu. * stanzas containing this key can still be assigned an order value to set the placement within the main menu, but can not themselves have latest_time nor earliest_time keys. times.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This is an example times.conf. Use this file to create custom time ranges that can be used while interacting with the search system. To use one or more of these configurations, copy the configuration block into times.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles Note: These are examples. Replace the values with your own customizations. The stanza name is an alphanumeric string (no spaces) that uniquely identifies a time range. [this_business_week] Define the label used in the time range control label = This business week Define the label to be used in display headers. If omitted the 'label' key will be used with the first letter lowercased. header_label = during this business week earliest_time = +1d@w1 latest_time = +6d@w6 Define the ordering sequence of this time range. All time ranges are sorted numerically, ascending. If the time range is in a sub menu and not in the main menu, this will determine the position within the sub menu. order = 110 a time range that only has a bound on the earliest time [last_3_hours] label = Last 3 hours header_label = in the last 3 hours earliest_time = -3h order = 30 227

two time ranges that should appear in a sub menu instead of in the main menu. the order values here determine relative ordering within the submenu. [yesterday] label = Yesterday earliest_time = -1d@d latest_time = @d order = 10 sub_menu = Other options [day_before_yesterday] label = Day before yesterday header_label = from the day before yesterday earliest_time = -2d@d latest_time = -1d@d order = 20 sub_menu = Other options The sub menu item that should contain the previous two time ranges. the order key here determines the submenu opener's placement within the main menu. [other] label = Other options order = 202 transactiontypes.conf The following are the spec and example files for transactiontypes.conf. transactiontypes.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains all possible attributes and value pairs for a transactiontypes.conf file. Use this file to configure transaction searches and their properties. There is a transactiontypes.conf in $SPLUNK_HOME/etc/system/default/. To set custom configurations, place a transactiontypes.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. [<TRANSACTIONTYPE>] * Create any number of transaction types, each represented by a stanza name and any number of the following attribute/value pairs. * Use the stanza name, [<TRANSACTIONTYPE>], to search for the transaction in Splunk Web. * If you do not specify an entry for each of the following attributes, Splunk uses the default value. maxspan = [<integer> s m h d] * Set the maximum time span for the transaction. * Can be in seconds, minutes, hours or days, -1 for unlimited * For example: 5s, 6m, 12h or 30d. * Defaults to: maxspan=-1 maxpause = [<integer> s m h d] * Set the maximum pause between the events in a transaction. 228

* Can be in seconds, minutes, hours or days, -1 for unlimited. * For example: 5s, 6m, 12h or 30d. * Defaults to: maxpause=-1 maxevents = <integer> * The maximum number of events in a transaction. If the value is a negative integer then this constraint is disabled. * Defaults to: maxevents=1000 fields = <comma-separated list of fields> * If set, each event must have the same field(s) to be considered part of the same transaction. * For example: fields=host,cookie * Defaults to: "" startswith=<transam-filter-string> * A search or eval filtering expression which if satisfied by an event marks the beginning of a new transaction * For example: * startswith="login" * startswith=(username=foobar) * startswith=eval(speed_field < max_speed_field) * startswith=eval(speed_field < max_speed_field/12) * Defaults to: "" endswith=<transam-filter-string> * A search or eval filtering expression which if satisfied by an event marks the end of a transaction * For example: * endswith="logout" * endswith=(username=foobar) * endswith=eval(speed_field > max_speed_field) * endswith=eval(speed_field > max_speed_field/12) * Defaults to: "" * For startswith/endswith <transam-filter-string> is defined as * syntax: "<search-expression>" (<quoted-search-expression>) eval(<eval-expression>) * description = Where: * <search-expression> is a valid search expression that does not contain quotes * <quoted-search-expression> is a valid search expression that contains quotes * <eval-expression> is a valid eval expression that evaluates to a boolean * Examples * search expression: (name="foo bar") * search expression: "user=mildred" * search expression: ("search literal") * eval bool expression: eval(distance/time < max_speed) * connected=<bool> * Relevant iff fields is not empty. Controls whether an event that is not inconsistent and not consistent * with the fields of a transaction, opens a new transaction (connected=t) or is added to the transaction. * An event can be not inconsistent and not consistent if it contains fields required by the transaction * but none of these fields has been instantiated in the transaction (by a previous event addition). * Defaults to: connected=t memory constraint options maxopentxn=<int> * Specifies the maximum number of not yet closed transactions to keep in the open pool before starting * to evict transactions, using LRU policy. * Defautls to: the default value of this field is read from the transactions stanza in limits.conf maxopenevents=<int> * Specifies the maximum number of events (which are) part of open transactions before transaction * eviction starts happening, using LRU policy. * Defaults to: the default value of this field is read from the transactions stanza in limits.conf keepevicted=<bool> * Whether to output evicted transactions. Evicted transactions can be distinguished from non-evicted * transactions by checking the value of the 'evicted' field, which is set to '1' for evicted transactions 229

* Defaults to: keepevicted=false multivalue rendering options mvlist=<bool> <field-list> * Field controlling whether the multivalued fields of the transaction are (1) a list of the original * events ordered in arrival order or (2) a set of unique field values ordered lexigraphically. If a * comma/space delimited list of fields is provided only those fields are rendered as lists * Defaults to: mvlist=f delim=<string> * A string used to delimit the original event values in the transaction event fields. * Defaults to: delim=" " nullstr=<string> * The string value to use when rendering missing field values as part of mv fields in a transactions. * This option applies only to fields that are rendered as lists. * Defaults to: nullstr=null values only used by the searchtxn search command search=<string> * A search string used to more efficiently seed transactions of this type. * The value should be as specific as possible, to limit the number of * events that must be retrieved to find transactions. * Example: sourcetype="sendmaill_sendmail" * Defaults to "*" (all events) transactiontypes.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This is an example transactiontypes.conf. Use this file as a template to configure transactions types. To use one or more of these configurations, copy the configuration block into transactiontypes.conf in $SPLUNK_HOME/etc/system/local/. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles [default] maxspan = 5m maxpause = 2s match = closest [purchase] maxspan = 10m maxpause = 5m fields = userid transforms.conf The following are the spec and example files for transforms.conf. transforms.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains attributes and values that you can use to configure data transformations. and event signing in transforms.conf. Transforms.conf is commonly used for: * Configuring regex-based host and source type overrides. * Anonymizing certain types of sensitive incoming data, such as credit card or social security numbers. * Routing specific events to a particular index, when you have multiple indexes. * Creating new index-time field extractions. NOTE: We do not recommend adding to the set of fields that are extracted at index time unless it is absolutely necessary because there 230

are negative performance implications. * Creating advanced search-time field extractions that involve one or more of the following: & nbsp; * Reuse of the same field-extracting regular expression across multiple sources, source types, or hosts. * Application of more than one regex to the same source, source type, or host. * Using a regex to extract one or more values from the values of another field. * Delimiter-based field extractions (they involve field-value pairs that are separated by commas, colons, semicolons, bars, or something similar). * Extraction of multiple values for the same field (multivalued field extraction). * Extraction of fields with names that begin with numbers or underscores. * NOTE: Less complex search-time field extractions can be set up entirely in props.conf. * Setting up lookup tables that look up fields from external sources. All of the above actions require corresponding settings in props.conf. You can find more information on these topics by searching the Splunk documentation (http://docs.splunk.com/documentation) There is a transforms.conf file in $SPLUNK_HOME/etc/system/default/. To set custom configurations, place a transforms.conf $SPLUNK_HOME/etc/system/local/. For examples, see the transforms.conf.example file. You can enable configurations changes made to transforms.conf by typing the following search string in Splunk Web: extract reload=t To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. [<unique_transform_stanza_name>] * Name your stanza. Use this name when you configure field extractions, lookup tables, and event routing in props.conf. For example, if you are setting up an advanced search-time field extraction, in props.conf you would add REPORT-<value> = <unique_transform_stanza_name> under the [<spec>] stanza that corresponds with a stanza you've created in transforms.conf. * Follow this stanza name with any number of the following attribute/value pairs, as appropriate for what you intend to do with the transform. * If you do not specify an entry for each attribute, Splunk uses the default value. REGEX = <regular expression> * Enter a regular expression to operate on your data. * NOTE: This attribute is valid for both index-time and search-time field extraction. & nbsp;* REGEX is required for all search-time transforms unless you are setting up a delimiter-based field extraction, in which case you use DELIMS (see the DELIMS attribute description, below). * REGEX is required for all index-time transforms. * REGEX and the FORMAT attribute: * Name-capturing groups in the REGEX are extracted directly to fields. This means that you do not need to specify the FORMAT attribute for simple field extraction cases (see the description of FORMAT, below). * If the REGEX extracts both the field name and its corresponding field value, you can use & nbsp; the following special capturing groups if you want to skip specifying the mapping in FORMAT: _KEY_<string>, _VAL_<string>. * For example, the following are equivalent: * Using FORMAT: * REGEX = ([a-z]+)=([a-z]+) * FORMAT = $1::$2 * Without using FORMAT & nbsp; * REGEX = (?<_KEY_1>[a-z]+)=(?<_VAL_1>[a-z]+) * When using either of the above formats, in a search-time extraction, the regex will continue to match against the source text, extracting as many 231

fields as can be identified in the source text. * Defaults to an empty string. FORMAT = <string> * NOTE: This option is valid for both index-time and search-time field extraction. However, FORMAT behaves differently depending on whether the extraction is performed at index time or search time. * This attribute specifies the format of the event, including any field names or values you want to add. * FORMAT for index-time extractions: * Use $n (for example $1, $2, etc) to specify the output of each REGEX match. * If REGEX does not have n groups, the matching fails. * The special identifier $0 represents what was in the DEST_KEY before the REGEX was performed. * At index time only, you can use FORMAT to create concatenated fields: * FORMAT = ipaddress::$1.$2.$3.$4 * When you create concatenated fields with FORMAT, "$" is the only special character. It is treated as a prefix for regex-capturing groups only if it is followed by a number and only & nbsp; if the number applies to an existing capturing group. So if REGEX has only one capturing group and its value is "bar", then: * "FORMAT = foo$1" yields "foobar" * "FORMAT = foo$bar" yields "foo$bar" * "FORMAT = foo$1234" yields "foo$1234" * "FORMAT = foo$1\$2" yields "foobar\$2" * At index-time, FORMAT defaults to <stanza-name>::$1 * FORMAT for search-time extractions: & nbsp; * The format of this field as used during search time extractions is as follows: * FORMAT = <field-name>::<field-value>( <field-name>::<field-value>)* * where: * field-name = [<string> $<extracting-group-number>] * field-value = [<string> $<extracting-group-number>] * Search-time extraction examples: & nbsp; * 1. FORMAT = first::$1 second::$2 third::other-value * 2. FORMAT = $1::$2 * If the key-name of a FORMAT setting is varying, for example $1 in the example 2 just above, then the regex will continue to match against the source key to extract as many matches as are present in the text. * NOTE: You cannot create concatenated fields with FORMAT at search time. That functionality is only available at index time. * At search-time, FORMAT defaults to an empty string. LOOKAHEAD = <integer> * NOTE: This option is only valid for index-time field extractions. * Optional. Specifies how many characters to search into an event. * Defaults to 4096. You may want to increase this value if you have event line lengths that exceed 4096 characters (before linebreaking). WRITE_META = [true false] * NOTE: This attribute is only valid for index-time field extractions. * Automatically writes REGEX to metadata. * Required for all index-time field extractions except for those where DEST_KEY = meta (see the description of the DEST_KEY attribute, below) * Use instead of DEST_KEY = meta. * Defaults to false. DEST_KEY = <KEY> * NOTE: This attribute is only valid for index-time field extractions. * Specifies where Splunk stores the expanded FORMAT results in accordance with the REGEX match. * Required for index-time field extractions where WRITE_META = false or is not set. * For index-time extractions, DEST_KEY can be set to a number of values mentioned in the KEYS section at the bottom of this file. * If DEST_KEY = _meta (not recommended) you should also add $0 to the start of your FORMAT attribute. $0 represents the DEST_KEY value before Splunk performs the REGEX (in other words, _meta). * The $0 value is in no way derived *from* the REGEX match. (It does not represent a captured group.) * KEY names are case-sensitive, and should be used exactly as they appear in the KEYs list at the bottom of this file. (For example, you would say DEST_KEY = MetaData:Host, *not* DEST_KEY = metadata:host.) DEFAULT_VALUE = <string> * NOTE: This attribute is only valid for index-time field extractions. * Optional. Splunk writes the DEFAULT_VALUE to DEST_KEY if the REGEX fails. 232

* Defaults to empty. SOURCE_KEY = <string> * NOTE: This attribute is valid for both index-time and search-time field extractions. * Optional. Defines the KEY that Splunk applies the REGEX to. * For search time extractions, you can use this attribute to extract one or more values from the values of another field. You can use any field that is available at the time of the execution of this field extraction. * For index-time extractions use the KEYs described at the bottom of this file. * KEYs are case-sensitive, and should be used exactly as they appear in the KEYs list at the bottom of this file. (For example, you would say SOURCE_KEY = MetaData:Host, *not* SOURCE_KEY = metadata:host.) * SOURCE_KEY is typically used in conjunction with REPEAT_MATCH in index-time field transforms. * Defaults to _raw, which means it is applied to the raw, unprocessed text of all events. REPEAT_MATCH = [true false] * NOTE: This attribute is only valid for index-time field extractions. * Optional. When set to true Splunk runs the REGEX multiple times on the SOURCE_KEY. * REPEAT_MATCH starts wherever the last match stopped, and continues until no more matches are found. Useful for situations where an unknown number of REGEX matches are expected per event. * Defaults to false. DELIMS = <quoted string list> * NOTE: This attribute is only valid for search-time field extractions. * IMPORTANT: If a value may contain an embedded unescaped double quote character, such as "foo"bar", use REGEX, not DELIMS. An escaped double quote (\") is ok. * Optional. Used in place of REGEX when dealing with delimiter-based field extractions, where field values (or field/value pairs) are separated by delimiters such as colons, spaces, line breaks, and so on. * Sets delimiter characters, first to separate data into field/value pairs, and then to separate field from value. * Each individual character in the delimiter string is used as a delimiter to split the event. * Delimiters must be quoted with " " (use \ to escape). * When the event contains full delimiter-separated field/value pairs, you enter two sets of quoted characters for DELIMS: * The first set of quoted delimiters extracts the field/value pairs. * The second set of quoted delimiters separates the field name from its corresponding value. * When the event only contains delimiter-separated values (no field names) you use just one set of quoted delimiters to separate the field values. Then you use the FIELDS attribute to apply field names to the extracted values (see FIELDS, below). * Alternately, Splunk reads even tokens as field names and odd tokens as field values. * Splunk consumes consecutive delimiter characters unless you specify a list of field names. * The following example of DELIMS usage applies to an event where field/value pairs are seperated by ' ' symbols and the field names are separated from their corresponding values by '=' symbols: [pipe_eq] & nbsp; DELIMS = " ", "=" * Defaults to "". FIELDS = <quoted string list> * NOTE: This attribute is only valid for search-time field extractions. * Used in conjunction with DELIMS when you are performing delimiter-based field extraction and only have field values to extract. * FIELDS enables you to provide field names for the extracted field values, in list format according to the order in which the values are extracted. * NOTE: If field names contain spaces or commas they must be quoted with " " (to escape, use \). * The following example is a delimiter-based field extraction where three field values appear in an event. They are separated by a comma and then a space. [commalist] & nbsp; DELIMS = ", " FIELDS = field1, field2, field3 * Defaults to "". MV_ADD = [true false] * NOTE: This attribute is only valid for search-time field extractions. * Optional. Controls what the extractor does when it finds a field which already exists. * If set to true, the extractor makes the field a multivalued field and appends the * newly found value, otherwise the newly found value is discarded. 233

* Defaults to false CLEAN_KEYS = [true false] * NOTE: This attribute is only valid for search-time field extractions. * Optional. Controls whether Splunk "cleans" the keys (field names) it extracts at search time. "Key cleaning" is the practice of replacing any non-alphanumeric characters (characters other than those falling between the a-z, A-Z, or 0-9 ranges) in field names with underscores, as well as the stripping of leading underscores and 0-9 characters from field names. * Add CLEAN_KEYS = false to your transform if you need to extract field names that include non-alphanumeric characters, or which begin with underscores or 0-9 characters. * Defaults to true. KEEP_EMPTY_VALS = [true false] * NOTE: This attribute is only valid for search-time field extractions. * Optional. Controls whether Splunk keeps field/value pairs when the value is an empty string. * This option does not apply to field/value pairs that are generated by Splunk's autokv extraction. Autokv ignores field/value pairs with empty values. * Defaults to false. CAN_OPTIMIZE = [true false] * NOTE: This attribute is only valid for search-time field extractions. * Optional. Controls whether Splunk can optimize this extraction out (another way of saying the extraction is disabled). * You might use this if you're running searches under a Search Mode setting that disables field discovery--it ensures that Splunk *always* discovers specific fields. * Splunk only disables an extraction if it can determine that none of the fields identified by the extraction will ever be needed for the successful evaluation of a search. * NOTE: This option should be rarely set to false. * Defaults to true. ******* Lookup tables ******* NOTE: Lookup tables are used ONLY during search time filename = <string> * Name of static lookup file. * File should be in $SPLUNK_HOME/etc/<app_name>/lookups/ for some <app_name>, or in $SPLUNK_HOME/etc/system/lookups/ * If file is in multiple 'lookups' directories, no layering is done. * Standard conf file precedence is used to disambiguate. * Defaults to empty string. max_matches = <integer> * The maximum number of possible matches for each input lookup value. * If the lookup is non-temporal (not time-bounded, meaning the time_field attribute is not specified), Splunk uses the first <integer> entries, in file order. * If the lookup is temporal, Splunk uses the first <integer> entries in descending time order. In other words, up <max_matches> lookup entries will be allowed to match, and if more than this many the ones nearest to the lookup value will be used. * Default = 100 if the lookup is not temporal, default = 1 if it is temporal. min_matches = <integer> * Minimum number of possible matches for each input lookup value. * Default = 0 for both temporal and non-temporal lookups, which means that Splunk outputs nothing if it cannot find any matches. * However, if min_matches > 0, and Splunk get less than min_matches, then Splunk provides & nbsp; the default_match value provided (see below). default_match = <string> * If min_matches > 0 and Splunk has less than min_matches for any given input, it provides this default_match value one or more times until the min_matches threshold is reached. * Defaults to empty string. case_sensitive_match = <bool> * If set to false, case insensitive matching will be performed for all fields in a lookup table * Defaults to true (case sensitive matching) match_type = <string> * A comma and space-delimited list of <match_type>(<field_name>) specification to allow for 234

non-exact matching * The avaiable match_type values are WILDCARD, CIDR, and EXACT. EXACT is the default and does not need to be specified. Only fields that should use WILDCARD or CIDR matching should be specified in this list external_ cmd = <string> * Provides the command and arguments to invoke to perform a lookup. Use this for external (or "scripted") lookups, where you interface with with an external script rather than a lookup table. * This string is parsed like a shell command. * The first argument is expected to be a python script located in $SPLUNK_HOME/etc/<app_name>/bin (or../etc/searchscripts). * Presence of this field indicates that the lookup is external and command based. * Defaults to empty string. fields_list = <string> * A comma- and space-delimited list of all fields that are supported by the external command. external_type = python * Type of external command. * Currently, only python is supported. * Defaults to python. time_field = <string> * Used for temporal (time bounded) lookups. Specifies the name of the field in the lookup table that represents the timestamp. * Defaults to an empty string, meaning that lookups are not temporal by default. time_format = <string> * For temporal lookups this specifies the 'strptime' format of the timestamp field. * You can include subseconds but Splunk will ignore them. * Defaults to %s.%q or seconds from unix epoch in UTC an optional milliseconds. max_offset_secs = <integer> * For temporal lookups, this is the maximum time (in seconds) that the event timestamp can be later than the lookup entry time for a match to occur. * Default is 2000000000 (no maximum, effectively). min_offset_secs = <integer> * For temporal lookups, this is the minimum time (in seconds) that the event timestamp can be later than the lookup entry timestamp for a match to occur. * Defaults to 0. batch_index_query = <bool> * For large file based lookups, this determines whether queries can be grouped to improve search performance. * Default is unspecified here, but defaults to true (at global level in limits.conf) allow_caching = <bool> * Allow output from lookup scripts to be cached * Default is true ******* KEYS: ******* * NOTE: Keys are case-sensitive. Use the following keys exactly as they appear. queue : Specify which queue to send the event to (can be parsingqueue, nullqueue, indexqueue). _raw : The raw text of the event. _done : If set to any string, this represents the last event in a stream. _meta : A space-separated list of metadata for an event. _time : The timestamp of the event, in seconds since 1/1/1970 UTC. MetaData:FinalType : The event type of the event. MetaData:Host : The host associated with the event. & nbsp; The value must be prefixed by "host::" _MetaData:Index : The index where the event should be stored. MetaData:Source : The source associated with the event. The value must be prefixed by "source::" 235

MetaData:Sourcetype : The sourcetype of the event. The value must be prefixed by "sourcetype::" _TCP_ROUTING : Comma separated list of tcpout group names (from outputs.conf) Defaults to groups present in 'defaultgroup' for [tcpout]. * NOTE: Any KEY (field name) prefixed by '_' is not indexed by Splunk, in general. transforms.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This is an example transforms.conf. Use this file to create regexes and rules for transforms. Use this file in tandem with props.conf. To use one or more of these configurations, copy the configuration block into transforms.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles Note: These are examples. Replace the values with your own customizations. Indexed field: [netscreen-error] REGEX = device_id=\[w+\](?<err_code>[^:]+) FORMAT = err_code::$1 WRITE_META = true Override host: [hostoverride] DEST_KEY = MetaData:Host REGEX = \s(\w*) $ FORMAT = host::$1 Extracted fields: [netscreen-error-field] REGEX = device_id=\[w+\](?<err_code>[^:]+) FORMAT = err_code::$1 Static lookup table [mylookuptable] filename = mytable.csv one to one lookup guarantees that we output a single lookup value for each input value, if no match exists, we use the value of "default_match", which by default is "NONE" [mylook] filename = mytable.csv max_matches = 1 min_matches = 1 default_match = nothing external command lookup table [myexternaltable] external_cmd = testadapter.py blah fields_list = foo bar Temporal based static lookup table [staticwtime] 236

filename = mytable.csv time_field = timestamp time_format = %d/%m/%y %H:%M:%S Mask sensitive data: [session-anonymizer] REGEX = (?m)^(.*)sessionid=\w+(\w{4}[&"].*)$ FORMAT = $1SessionId=$2 DEST_KEY = _raw Route to an alternate index: [AppRedirect] REGEX = Application DEST_KEY = _MetaData:Index FORMAT = Verbose Extract comma-delimited values into fields: [extract_csv] DELIMS = "," FIELDS = "field1", "field2", "field3" This example assigns the extracted values from _raw to field1, field2 and field3 (in order of extraction). If more than three values are extracted the values without a matching field name are ignored. [pipe_eq] DELIMS = " ", "=" The above example extracts key-value pairs which are separated by ' ' while the key is delimited from value by '='. [multiple_delims] DELIMS = " ;", "=:" The above example extracts key-value pairs which are separated by ' ' or ';'. while the key is delimited from value by '=' or ':'. user-seed.conf The following are the spec and example files for user-seed.conf. user-seed.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 Specification for user-seed.conf. Allows configuration of Splunk's initial username and password. Currently, only one user can be configured with user-seed.conf. To override the default username and password, place user-seed.conf in $SPLUNK_HOME/etc/system/default. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles [user_info] USERNAME = <string> * Username you want to associate with a password. * Default is Admin. PASSWORD = <string> * Password you wish to set for that user. * Default is changeme. user-seed.conf.example 237

Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This is an example user-seed.conf. Use this file to create an initial login. NOTE: To change the default start up login and password, this file must be in $SPLUNK_HOME/etc/system/default/ prior to starting Splunk for the first time. To use this configuration, copy the configuration block into user-seed.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles [user_info] USERNAME = admin PASSWORD = myowndefaultpass web.conf The following are the spec and example files for web.conf. web.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attributes and values you can use to configure Splunk's web interface. There is a web.conf in $SPLUNK_HOME/etc/system/default/. To set custom configurations, place a web.conf in $SPLUNK_HOME/etc/system/local/. For examples, see web.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles [settings] * Set general SplunkWeb configuration options under this stanza name. * Follow this stanza name with any number of the following attribute/value pairs. * If you do not specify an entry for each attribute, Splunk will use the default value. startwebserver = [0 1] * Set whether or not to start SplunkWeb. * 0 disables SplunkWeb, 1 enables it. * Defaults to 1. httpport = <port_number> * Must be present for SplunkWeb to start. * If omitted or 0 the server will NOT start an http listener. * If using SSL, set to the HTTPS port number. * Defaults to 8000. mgmthostport = <IP:port> * Location of splunkd. * Don't include http[s]:// -- just the IP address. * Defaults to 127.0.0.1:8089. enablesplunkwebssl = [True False] * Toggle between http or https. * Set to true to enable https and SSL. * Defaults to False. privkeypath = etc/auth/splunkweb/privkey.pem * The path to the file containing the web server's SSL certificate's private key * Relative paths are interpreted as relative to $SPLUNK_HOME * Relative paths may not refer outside of $SPLUNK_HOME (eg. no../somewhere) * An absolute path can also be specified to an external key & nbsp; * See also enablesplunkwebssl and cacertpath 238

cacertpath = etc/auth/splunkweb/cert.pem * The path to the file containing the SSL certificate for the splunk web server * The file may also contain root and intermediate certificates, if required They should be listed sequentially in the order: [ Server's SSL certificate ] [ One or more intermediate certificates, if required ] [ Root certificate, if required ] * Relative paths are interpreted as relative to $SPLUNK_HOME * Relative paths may not refer outside of $SPLUNK_HOME (eg. no../somewhere) * An absolute path can also be specified to an external certificate * See also enablesplunkwebssl and privkeypath serviceformposturl = http://headlamp. Splunk.com/event/add userregistrationurl = https://www.splunk.com/index.php/pre_reg?destination=prod_reg updatecheckerbaseurl = http://quickdraw.splunk.com/js/ docscheckerbaseurl = http://quickdraw.splunk.com/help * These are various Splunk.com urls that are configurable. * Setting updatecheckerbaseurl to 0 will stop the SplunkWeb from pinging Splunk.com for new versions of itself. enable_insecure_login = [True False] * Indicates if the GET-based /account/insecurelogin endpoint is enabled * Provides an alternate GET-based authentication mechanism * If True, the /account/insecurelogin?username=username&password=passwd is available * If False, only the main /account/login endpoint is available * Defaults to False login_content = <content_string> & nbsp; * Add custom content to the login page * Supports any text including html supportsslv3only = [True False] * Allow only SSLv3 connections if true * NOTE: Enabling this may cause some browsers problems ciphersuite = <cipher suite string> * If set, uses the specified cipher string for the HTTP server. * If not set, uses the default cipher string provided by OpenSSL. This is used to ensure that the server does not accept connections using weak encryption protocols. root_endpoint = <URI_prefix_string> * defines the root URI path on which the appserver will listen * default setting is '/' * Ex: if you want to proxy the splunk UI at http://splunk:8000/splunkui, then set root_ endpoint = /splunkui static_endpoint = <URI_prefix_string> * path to static content * The path here is automatically appended to root_endpoint defined above * default is /static static_dir = <relative_filesystem_path> * The directory that actually holds the static content * This can be an absolute url if you want to put it elsewhere * Default is share/splunk/search_mrsparkle/exposed rss_endpoint = <URI_prefix_string> * path to static rss content * The path here is automatically appended to root_endpoint defined above * default is /rss tools.staticdir.generate_indexes = [1 0] * Indicates if the webserver will serve a directory listing for static directories * Defaults to 0 (false) template_dir = <relative_ filesystem_path> * base path to mako templates * Defaults to share/splunk/search_mrsparkle/templates module_dir = <relative_filesystem_path> * base path to UI module assets * Defaults to share/splunk/search_mrsparkle/modules 239

enable_gzip = [True False] * Determines if webserver applies gzip compression to responses * Defaults to True use_future_expires = [True False] * Determines if the Expires header of /static files is set to a far-future date * Defaults to True flash_major_version = <integer> flash_minor_version = <integer> flash_revision_version = <integer> * Specifies the minimum Flash plugin version requirements * Flash support, broken into three parts. * We currently require a min baseline of Shockwave Flash 9.0 r124 enable_proxy_write = [True False] * Indicates if the /splunkd proxy endpoint allows POST operations * If True, both GET and POST operations are proxied through to splunkd * If False, only GET operations are proxied through to splunkd * Setting this to False will prevent many client-side packages (such as the Splunk JavaScript SDK) from working correctly * Defaults to True js_logger_mode = [None Firebug Server] * JavaScript Logger mode * Available modes: None, Firebug, Server * Mode None: Does not log anything * Mode Firebug: Use firebug by default if it exists or defer to the older less promiscuous version of firebug lite * Mode Server: Log to a defined server endpoint * See js/logger.js Splunk. Logger.Mode for mode implementation details and if you would like to author your own * Defaults to Firebug js_logger_mode_server_end_point = <URI_relative_path> * Specifies the server endpoint to post javascript log messages * Used when js_logger_mode = Server * Defaults to util/log/js js_logger_mode_server_poll_buffer = <integer> * Specifieds the interval in milliseconds to check, post and cleanse the javascript log buffer * Defaults to 1000 js_logger_mode_server_max_buffer = <integer> * Specifies the maximum size threshold to post and cleanse the javascript log buffer * Defaults to 100 ui_inactivity_timeout = <integer> * Specifies the length of time lapsed (in minutes) for notification when there is no user interface clicking, mouseover, scrolling or resizing. * Notifies client side pollers to stop, resulting in sessions expiring at the tools.sessions.timeout value. * If less than 1, results in no timeout notification ever being triggered (Sessions will stay alive for as long as the browser is open). * Defaults to 60 minutes js_no_cache = [True False] * Toggle js cache control * Defaults to False enable_autocomplete_login = [True False] * Indictes if the main login page allows browsers to autocomplete the username * If True, browsers may display an autocomplete drop down in the username field * If False, browsers are instructed not to show autocomplete drop down in the username field * Defaults to True minify_js = [True False] * indicates whether the static JS files for modules are consolidated and minified * enabling improves client-side performance by reducing the number of HTTP requests and the size of HTTP responses minify_css = [True False] * indicates whether the static CSS files for modules are consolidated and minified 240

* enabling improves client-side performance by reducing the number of HTTP requests and the size of HTTP responses trap_module_exceptions = [True False] * Toggle whether the JS for individual modules is wrapped in a try/catch * If True, syntax errors in individual modules will not cause the UI to hang, * other than when using the module in question * Set this to False when developing apps. jschart_test_mode = [True False] * Toggle whether JSChart module runs in Test Mode * If True, JSChart module attaches HTML classes to chart elements for introspection * This will negatively impact performance, so should be disabled unless actively in use. max_view_cache_size = <integer> * Specifies the maximum number of views to cache in the appserver. * Defaults to 300. version_label_format = <printf_string> * internal config * used to override the version reported by the UI to *.splunk.com resources * defaults to: %s SSO remoteuser = <http_header_string> * Remote user HTTP header sent by the authenticating proxy server. * This header should be set to the authenticated user. * Defaults to 'REMOTE_USER'. * Caution: There is a potential security concern regarding Splunk's treatment of HTTP headers. * Your proxy provides the selected username as an HTTP header as specified above. * If the browser or other http agent were to specify the value of this header, probably any proxy would overwrite it, or in the case that the username cannot be determined, refuse to pass along the request or set it blank. * However, Splunk (cherrypy) will normalize headers containing the dash, and the underscore to the same value. For example USER-NAME and USER_NAME will be treated as the same in SplunkWeb. * This means that if the browser provides REMOTE-USER and splunk accepts REMOTE_USER, theoretically the browser could dictate the username. & nbsp; * In practice, however, in all our testing, the proxy adds its headers last, which causes them to take precedence, making the problem moot. SSOMode = [permissive strict] * Allows SSO to behave in either permissive or strict mode. * Permissive: Users may login to splunkweb using a valid splunk account * even if they are coming from a non trusted IP. * Strict: All requests to splunkweb will be restricted to those originating * from a trusted IP except those to endpoints not requiring authentication. * Defaults to "strict" trustedip = <ip_address> Trusted IP. This is the IP address of the authenticating proxy. Splunkweb verifies it is receiving data from the proxy host for all SSO requests. & nbsp; Uncomment and set to a valid IP address to enable SSO. Disabled by default. Normal value is '127.0.0.1' testing_endpoint = <relative_uri_path> * Specifies the root URI path on which to serve splunkweb unit and * integration testing resources. * Development only setting * Defaults to '/testing' testing_dir = <relative_file_path> * Specifies the path relative to $SPLUNK_HOME that contains the testing * files to be served at endpoint defined by 'testing_endpoint'. * Development only setting * Defaults to 'share/splunk/testing' 241

cherrypy HTTP server config server.thread_pool = <integer> * Specifies the minimum number of threads the appserver is allowed to maintain * Defaults to 50 server.thread_pool_max = <integer> * Specifies the maximum number of threads the appserver is allowed to maintain * Defaults to -1 (unlimited) server.thread_pool_min_spare = <integer> * Specifies the minimum number of spare threads the appserver keeps idle * Defaults to 15 server.thread_pool_max_spare = <integer> * Specifies the maximum number of spare threads the appserver keeps idle * Defaults to 30 server.socket_host = <ip_address> * Host values may be any IPv4 or IPv6 address, or any valid hostname. * The string 'localhost' is a synonym for '127.0.0.1' (or '::1', if * your hosts file prefers IPv6). The string '0.0.0.0' is a special * IPv4 entry meaning "any active interface& quot; (INADDR_ANY), and '::' * is the similar IN6ADDR_ANY for IPv6. * Defaults to 0.0.0.0 if listenonipv6 is set to no, else :: listenonipv6 = <no yes only> * By default, splunkweb will listen for incoming connections using IPv4 only * To enable IPv6 support in splunkweb, set this to "yes". Splunkweb will simultaneously listen for connections on both IPv4 and IPv6 * To disable IPv4 entirely, set this to "only", which will cause splunkweb to exclusively accept connections over IPv6. * You will also want to set server.socket_host (use "::" instead of "0.0.0.0") if you wish to listen on an IPv6 address max_upload_ size = <integer> * Specifies the hard maximum size of uploaded files in MB * Defaults to 500 log.access_file = <filename> * Specifies the HTTP access log filename * Stored in default Splunk /var/log directory * Defaults to web_access.log log.access_maxsize = <integer> * Specifies the maximum size the web_access.log file should be allowed to grow to (in bytes) * Comment out or set to 0 for unlimited file size * File will be rotated to web_access.log.0 after max file size is reached * See log.access_maxfiles to limit the number of backup files created * Defaults to unlimited file size log.access_maxfiles = <integer> * Specifies the maximum number of backup files to keep after the web_ access.log file has reached its maximum size * Warning: setting this to very high numbers (eg. 10000) may impact performance during log rotations * Defaults to 5 if access_maxsize is set log.error_maxsize = <integer> * Specifies the maximum size the web_service.log file should be allowed to grow to (in bytes) * Comment out or set to 0 for unlimited file size * File will be rotated to web_service.log.0 after max file size is reached * See log.error_maxfiles to limit the number of backup files created * Defaults to unlimited file size log.error_maxfiles = <integer> * Specifies the maximum number of backup files to keep after the web_service.log file has reached its maximum size * Warning: setting this to very high numbers (eg. 10000) may impact performance during log rotations 242

* Defaults to 5 if access_maxsize is set log.screen = [True False] * Indicates if runtime output is displayed inside an interactive tty * Defaults to True request.show_tracebacks = [True False] * Indicates if a an exception traceback is displayed to the user on fatal exceptions * Defaults to True engine.autoreload_on = [True False] * Indicates if the appserver will auto-restart if it detects a python file has changed * Defaults to False tools.sessions.on = True * Indicates if user session support is enabled * Should always be True tools.sessions.timeout = <integer> * Specifies the number of minutes of inactivity before a user session is expired & nbsp; * The countdown is effectively reset by browser activity minute until ui_inactivity_timeout inactivity timeout is reached. * Use a value of 2 or higher, as a value of 1 will race with the browser refresh, producing unpredictable behavior. (Low values aren't very useful though except for testing.) * Defaults to 60 tools.sessions.restart_persist = [True False] * If set to False then the session cookie will be deleted from the browser when the browser quits * Defaults to True - Sessions persist across browser restarts (assuming the tools.sessions.timeout limit hasn't been reached) tools.sessions.httponly = [True False] * If set to True then the session cookie will be made unavailable to running javascript scripts, increasing session security * Defaults to True tools.sessions.secure = [True False] * If set to True and Splunkweb is configured to server requests using HTTPS (see the enablesplunkwebssl setting) then the browser will only transmit the session cookie over HTTPS connections, increasing session security * Defaults to True response.timeout = <integer> * Specifies the number of seconds to wait for the server to complete a response * Some requests such as uploading large files can take a long time * Defaults to 7200 tools.sessions.storage_type = [file] tools.sessions.storage_path = <filepath> * Specifies the session information storage mechahims * Comment out the next two lines to use RAM based sessions instead * Use an absolute path to store sessions outside of the splunk tree * Defaults to storage_type=file, storage_path=var/run/splunk tools.decode.on = [True False] * Indicates if all strings that come into Cherrpy controller methods are decoded as unicode (assumes UTF-8 encoding). * WARNING: Disabling this will likely break the application, as all incoming strings are assumed * to be unicode. * Defaults to True tools.encode.on = [True False] * Encodes all controller method response strings into UTF-8 str objects in Python. * WARNING: Disabling this will likely cause high byte character encoding to fail. * Defaults to True tools.encode.encoding = <codec> & nbsp; * Force all outgoing characters to be encoded into UTF-8. * This only works with tools.encode.on set to True. * By setting this to utf-8, Cherrypy's default behavior of observing the Accept-Charset header 243

* is overwritten and forces utf-8 output. Only change this if you know a particular browser * installation must receive some other character encoding (Latin-1 iso-8859-1, etc) * WARNING: Change this at your own risk. * Defaults to utf08 tools.proxy.on = [True False] * Used for running Apache as a proxy for Splunk UI, typically for SSO configuration. See http://tools.cherrypy.org/wiki/behindapache for more information. * For Apache 1.x proxies only. Set this attribute to "true". This configuration instructs CherryPy (the Splunk Web HTTP server) to look for an incoming X-Forwarded-Host header and to use the value of that header to construct canonical redirect URLs that include the proper host name. For more information, refer to the CherryPy documentation on running behind an Apache proxy. This setting is only necessary for Apache 1.1 proxies. For all other proxies, the setting must be "false", which is the default. * Defaults to False pid_path = <filepath> * Specifies the path to the PID file * Equals precisely and only var/run/splunk/splunkweb.pid * NOTE: Do not change this parameter. enabled_decomposers = <intention> [, <intention>]... * Added in Splunk 4.2 as a short term workaround measure for apps which happen to still require search decomposition, which is deprecated with 4.2. * Search decomposition will be entirely removed in a future release. * Comma separated list of allowed intentions. & nbsp; * Modifies search decomposition, which is a splunk-web internal behavior. * Can be controlled on a per-app basis. * If set to the empty string, no search decomposition occurs, which causes some usability problems with report builder. * The current possible values are: addcommand, stats, addterm, addtermgt, addtermlt, setfields, excludefields, audit, sort, plot * Default is 'plot', leaving only the plot intention enabled. SSO Configuration trustedip = <ip_address> * Set this to the IP address of the authenticating proxy or proxies. Specify a single address or a commaseparated list of addresses; IP ranges and netmask notation are not supported. * Required for SSO to work remoteuser = <remote_user_header> * Sets the remote user header. Most proxies forward the authenticated username in an HTTP header called REMOTE_USER. However, some may use a different header, such as REMOTE-USER (with a hyphen instead of an underscore). If the proxy you are using does not use REMOTE_USER, specify the HTTP header that Splunk Web should look for. * Defaults to REMOTE_USER SSOMode = [permissive strict] * Specifies the SSO mode for Splunk Web. The value is either "permissive" or "strict". Permissive mode honors incoming requests from IPs not specified in the trustedip setting but refuses to use SSO authentication if it receives requests from these unsupported IPs. Strict mode completely shuts down all requests unless they originate from an IP address specified in the trustedip setting. * Defaults to "strict" custom cherrypy endpoints [endpoint:<python_module_name>] * registers a custom python CherryPy endpoint * the expected file must be located at: $SPLUNK_HOME/etc/apps/<APP_NAME>/appserver/controllers/<PYTHON_NODULE_NAME>.py * this module's methods will be exposed at /custom/<app_name>/<python_nodule_name>/<method_name> web.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 244

This is an example web.conf. Use this file to configure data web settings. To use one or more of these configurations, copy the configuration block into web.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles This stanza heading must precede any changes. [settings] Change the default port number: httpport = 12800 Turn on SSL: enablesplunkwebssl = true absolute paths may be used here. privkeypath = /home/user/certs/myprivatekey.pem cacertpath = /home/user/certs/mycacert.pem NOTE: non-absolute paths are relative to $SPLUNK_HOME wmi.conf The following are the spec and example files for wmi.conf. wmi.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attribute/value pairs for configuring Windows Management Instrumentation (WMI) access from Splunk. There is a wmi.conf in $SPLUNK_HOME\etc\system\default\. To set custom configurations, place a wmi.conf in $SPLUNK_HOME\etc\system\local\. For examples, see wmi.conf.example. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles ----GLOBAL SETTINGS----- [settings] * The settings stanza specifies various runtime parameters. * The entire stanza and every parameter within it is optional. * If the stanza is missing, Splunk assumes system defaults. initial_backoff = <integer> * How long, in seconds, to wait before retrying the connection to the WMI provider after the first connection error. * If connection errors continue, the wait time doubles until it reaches the integer specified in max_backoff. * Defaults to 5. max_backoff = <integer> * The maximum time, in seconds, to attempt to reconnect to the WMI provider. * Defaults to 20. max_retries_at_max_backoff = <integer> * Once max_backoff is reached, tells Splunk how many times to attempt to reconnect to the WMI provider. * Splunk will try to reconnect every max_backoff seconds. * If reconnection fails after max_retries, give up forever (until restart). 245

* Defaults to 2. checkpoint_sync_interval = <integer> * The minimum wait time, in seconds, for state data (event log checkpoint) to be written to disk. * Defaults to 2. ----INPUT-SPECIFIC SETTINGS----- [WMI:$NAME] * There are two types of WMI stanzas: * Event log: for pulling event logs. You must set the event_log_file attribute. * WQL: for issuing raw Windows Query Language (WQL) requests. You must set the wql attribute. * Do not use both the event_log_file or the wql attributes. Use one or the other. server = <comma-separated strings> * A comma-separated list of servers from which to get data. * If not present, defaults to the local machine. interval = <integer> * How often, in seconds, to poll for new data. * This attribute is required, and the input will not run if the attribute is not present. * There is no default. disabled = [0 1] * Specifies whether the input is enabled or not. * 1 to disable the input, 0 to enable it. * Defaults to 0 (enabled). hostname = <host> * All results generated by this stanza will appear to have arrived from the string specified here. * This attribute is optional. * If it is not present, the input will detect the host automatically. current_only = [0 1] * Changes the characteristics and interaction of WMI-based event collections. * When current_only is set to 1: * For event log stanzas, this will only capture events that occur while Splunk is running. * For WQL stanzas, event notification queries are expected. The queried class must support sending events. Failure to supply the correct event notification query structure will cause & nbsp; WMI to return a syntax error. * An example event notification query that watches for process creation: * SELECT * FROM InstanceCreationEvent WITHIN 1 WHERE TargetInstance ISA 'Win32_Process'. * When current_only is set to 0: * For event log stanzas, all the events from the checkpoint are gathered. If there is no checkpoint, all events starting from the oldest events are retrieved. * For WQL stanzas, the query is executed and results are retrieved. The query is a non-notification query. * For example * Select * Win32_Process where caption = "explorer.exe" * Defaults to 0. index = <string> * Specifies the index that this input should send the data to. * This attribute is optional. * When defined, & quot;index=" is automatically prepended to <string>. * Defaults to "index=main" (or whatever you have set as your default index). Event log-specific attributes: 246

event_log_file = <Application, System, etc> * Tells Splunk to expect event log data for this stanza, and specifies the event log channels you want Splunk to monitor. * Use this instead of WQL to specify sources. * Specify one or more event log channels to poll. Multiple event log channels must be separated by commas. * There is no default. disable_hostname_normalization = [0 1] * If set to true, hostname normalization is disabled * If absent or set to false, the hostname for 'localhost' will be converted to %COMPUTERNAME%. * 'localhost' refers to the following list of strings: localhost, 127.0.0.1, ::1, the name of the DNS domain for the local computer, * the fully qualified DNS name, the NetBIOS name, the DNS host name of the local computer WQL-specific attributes: wql = <string> * Tells Splunk to expect data from a WMI provider for this stanza, and specifies the WQL query you want Splunk to make to gather that data. * Use this if you are not using the event_log_file attribute. * Ensure that your WQL queries are syntactically and structurally correct when using this option. * For example, SELECT * FROM Win32_PerfFormattedData_PerfProc_Process WHERE Name = "splunkd". * If you wish to use event notification queries, you must also set the "current_only" attribute to 1 within the stanza, and your query must be appropriately structured for event notification (meaning it must contain one or more of the GROUP, WITHIN or HAVING clauses.) * For example, SELECT * FROM InstanceCreationEvent WITHIN 1 WHERE TargetInstance ISA 'Win32_Process' * There is no default. namespace = <string> * The namespace where the WMI provider resides. * The namespace spec can either be relative (root\cimv2) or absolute (\\server\root\cimv2). * If the server attribute is present, you cannot specify an absolute namespace. * Defaults to root\cimv2. wmi.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This is an example wmi.conf. These settings are used to control inputs from WMI providers. Refer to wmi.conf.spec and the documentation at splunk.com for more information about this file. To use one or more of these configurations, copy the configuration block into wmi.conf in $SPLUNK_HOME\etc\system\local\. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles This stanza specifies runtime parameters. [settings] initial_backoff = 5 max_backoff = 20 max_retries_at_max_backoff = 2 checkpoint_sync_interval = 2 Pull events from the Application, System and Security event logs from the 247

local system every 10 seconds. Store the events in the "wmi_eventlog" Splunk index. [WMI:LocalApplication] interval = 10 event_log_file = Application disabled = 0 index = wmi_eventlog [WMI:LocalSystem] interval = 10 event_log_file = System disabled = 0 index = wmi_eventlog [WMI:LocalSecurity] interval = 10 event_log_file = Security disabled = 0 index = wmi_eventlog Gather disk and memory performance metrics from the local system every second. Store event in the "wmi_perfmon" Splunk index. [WMI:LocalPhysicalDisk] interval = 1 wql = select Name, DiskBytesPerSec, PercentDiskReadTime, PercentDiskWriteTime, PercentDiskTime from Win32_PerfFormattedData_PerfDisk_PhysicalDisk disabled = 0 index = wmi_perfmon [WMI:LocalMainMemory] interval = 10 wql = select CommittedBytes, AvailableBytes, PercentCommittedBytesInUse, Caption from Win32_PerfFormattedData_PerfOS_ Memory disabled = 0 index = wmi_perfmon Collect all process-related performance metrics for the splunkd process, every second. Store those events in the "wmi_perfmon" index. [WMI:LocalSplunkdProcess] interval = 1 wql = select * from Win32_PerfFormattedData_PerfProc_Process where Name = "splunkd" disabled = 0 index = wmi_perfmon Listen from three event log channels, capturing log events that occur only while Splunk is running, every 10 seconds. Gather data from three remote servers srv1, srv2 and srv3. [WMI:TailApplicationLogs] interval = 10 event_log_file = Application, Security, System server = srv1, srv2, srv3 disabled = 0 current_only = 1 Listen for process-creation events on a remote machine, once a second. [WMI:ProcessCreation] interval = 1 server = remote-machine wql = select * from InstanceCreationEvent within 1 where TargetInstance isa ' Win32_Process' disabled = 0 current_only = 1 Receive events whenever someone connects or removes a USB device on the computer, once a second. [WMI:USBChanges] interval = 1 wql = select * from InstanceOperationEvent within 1 where TargetInstance ISA 'Win32_PnPEntity' and 248

TargetInstance.Description='USB Mass Storage Device' disabled = 0 current_only = 1 workflow_actions.conf The following are the spec and example files for workflow_actions.conf. workflow_actions.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This file contains possible attribute/value pairs for configuring workflow actions in Splunk. There is a workflow_actions.conf in $SPLUNK_HOME/etc/apps/search/default/. To set custom configurations, place a workflow_actions.conf in either $SPLUNK_HOME/etc/system/local/ or add a workflow_actions.conf file to your app's local/ directory. For examples, see workflow_actions.conf.example. You must restart Splunk to enable configurations, unless editing them through the Splunk manager. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. General required settings: These apply to all workflow action types. type = <string> * The type of the workflow action. * If not set, Splunk skips this workflow action. label = <string> * The label to display in the workflow action menu. * If not set, Splunk skips this workflow action. General optional settings: These settings are not required but are available for all workflow actions. fields = <comma or space separated list> * The fields required to be present on the event in order for the workflow action to be applied. * When "display_location" is set to "both" or "field_menu", the workflow action will be applied to the menu's corresponding to the specified fields. * If fields is undefined or set to *, the workflow action is applied to all field menus. * If the * character is used in a field name, it is assumed to act as a "globber". For example host* would match the fields hostname, hostip, etc. * Acceptable values are any valid field name, any field name including the * character, or * (e.g. *_ip). * Defaults to * eventtypes = <comma or space separated list> * The eventtypes required to be present on the event in order for the workflow action to be applied. * Acceptable values are any valid eventtype name, or any eventtype name plus the * character (e.g. host*). display_location = <string> * Dictates whether to display the workflow action in the event menu, the field menus or in both locations. * Accepts field_menu, event_menu, or both. * Defaults to both. disabled = [True False] 249

* Dictates whether the workflow action is currently disabled * Defaults to False Using field names to insert values into workflow action settings Several settings detailed below allow for the substitution of field values using a special variable syntax, where the field's name is enclosed in dollar signs. For example, $_raw$, $hostip$, etc. The settings, label, link.uri, link.postargs, and search.search_string all accept the value of any valid field to be substituted into the final string. For example, you might construct a Google search using an error message field called error_msg like so: link.uri = http://www.google.com/search?q=$error_msg$. Some special variables exist to make constructing the settings simpler. $@field_name$ * Allows for the name of the current field being clicked on to be used in a field action. * Useful when constructing searches or links that apply to all fields. * NOT AVAILABLE FOR EVENT MENUS $@field_value$ * Allows for the value of the current field being clicked on to be used in a field action. * Useful when constructing searches or links that apply to all fields. * NOT AVAILABLE FOR EVENT MENUS $@sid$ * The sid of the current search job. $@offset$ * The offset of the event being clicked on in the list of search events. $@namespace$ * The name of the application from which the search was run. $@latest_time$ * The latest time the event occurred. This is used to disambiguate similar events from one another. It is not often available for all fields. Field action types Link type: Allows for the construction of GET and POST requests via links to external resources. link.uri = <string& gt; * The URI for the resource to link to. * Accepts field values in the form $<field name>$, (e.g $_raw$). * All inserted values are URI encoded. * Required link.target = <string> * Determines if clicking the link opens a new window, or redirects the current window to the resource defined in link.uri. * Accepts: "blank" (opens a new window), "self" (opens in the same window) * Defaults to "blank" link.method = <string> * Determines if clicking the link should generate a GET request or a POST request to the resource defined in link.uri. * Accepts: "get" or "post". * Defaults to "get". link.postargs.<int>.<key/value> = <value> * Only available when link.method = post. 250

* Defined as a list of key / value pairs like such that foo=bar becomes: link.postargs.1.key = "foo" link.postargs.1.value = "bar& quot; * Allows for a conf compatible method of defining multiple identical keys (e.g.): link.postargs.1.key = "foo" link.postargs.1.value = "bar" link.postargs.2.key = "foo" link.postargs.2.value = "boo"... * All values are html form encoded appropriately. Search type: Allows for the construction of a new search to run in a specified view. search.search_string = <string> * The search string to construct. * Accepts field values in the form $<field name>$, (e.g. $_raw$). * Does NOT attempt to determine if the inserted field values may brake quoting or other search language escaping. * Required search.app = <string> * The name of the Splunk application in which to perform the constructed search. * By default this is set to the current app. search.view = <string> * The name of the view in which to preform the constructed search. * By default this is set to the current view. search.target = <string> * Accepts: blank, self. * Works in the same way as link.target. See link.target for more info. search.earliest = <time> * Accepts absolute and Splunk relative times (e.g. -10h). * Determines the earliest time to search from. search.latest = <time> * Accepts absolute and Splunk relative times (e.g. -10h). * Determines the latest time to search to. search.preserve_timerange = <boolean> * Ignored if either the search.earliest or search.latest values are set. * When true, the time range from the original search which produced the events list will be used. * Defaults to false. workflow_actions.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This is an example workflow_actions.conf. These settings are used to create workflow actions accessible in an event viewer. Refer to workflow_actions.conf.spec and the documentation at splunk.com for more information about this file. To use one or more of these configurations, copy the configuration block into workflow_actions.conf in $SPLUNK_HOME/etc/system/local/, or into your application's local/ folder. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles These are the default workflow actions and make extensive use of the special parameters: $@namespace$, $@sid$, etc. [show_source] type=link fields = _cd, source, host, index display_location = event_menu label = Show Source 251

link.uri = /app/$@namespace$/show_source?sid=$@sid$&offset=$@offset$&latest_time=$@latest_time$ [ifx] type = link display_location = event_menu label = Extract Fields link.uri = /ifx?sid=$@sid$&offset=$@offset$&namespace=$@namespace$ [etb] type = link display_location = event_menu label = Build Eventtype link.uri = /etb?sid=$@sid$&offset=$@offset$&namespace=$@namespace$ This is an example workflow action which will be displayed in a specific field menu (clientip). [whois] display_location = field_menu fields = clientip label = Whois: $clientip$ link.method = get link.target = blank link.uri = http://ws.arin.net/whois/?queryinput=$clientip$ type = link This is an example field action which will allow a user to search every field value in Google. [Google] display_location = field_menu fields = * label = Google $@field_name$ link.method = get link.uri = http://www.google.com/search?q=$@field_value$ type = link This is an example post link that will send its field name and field value to a fictional bug tracking system. [Create JIRA issue] display_location = field_menu fields = error_msg label = Create JIRA issue for $error_class$ link.method = post link.postargs.1.key = error link.postargs.1.value = $error_msg$ link.target = blank link.uri = http://127.0.0.1:8000/jira/issue/create type = link This is an example search workflow action that will be displayed in an event's menu, but requires the field "controller" to exist in the event in order for the workflow action to be available for that event. [Controller req over time] display_location = event_menu fields = controller label = Requests over last day for $controller$ search.earliest = -3d search.search_string = sourcetype=rails_app controller=$controller$ timechart span=1h count search.target = blank search.view = charting type = search viewstates.conf The following are the spec and example files for viewstates.conf. viewstates.conf.spec Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 252

This file explains how to format viewstates. To use this configuration, copy the configuration block into viewstates.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk to enable configurations. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles GLOBAL SETTINGS Use the [default] stanza to define any global settings. * You can also define global settings outside of any stanza, at the top of the file. * Each conf file should have at most one default stanza. If there are multiple default stanzas, attributes are combined. In the case of multiple definitions of the same & nbsp; attribute, the last definition in the file wins. * If an attribute is defined at both the global level and in a specific stanza, the value in the specific stanza takes precedence. [<view_name>:<viewstate_id>] * Auto-generated persistence stanza label that corresponds to UI views * The <view_name> is the URI name (not label) of the view to persist * if <view_name> = "*", then this viewstate is considered to be 'global' * The <viewstate_id> is the unique identifier assigned to this set of parameters * <viewstate_id> = '_current' is a reserved name for normal view 'sticky state' * <viewstate_id> = '_empty' is a reserved name for no persistence, i.e., all defaults <module_id>.< setting_name> = <string> * The <module_id> is the runtime id of the UI module requesting persistence * The <setting_name> is the setting designated by <module_id> to persist viewstates.conf.example Copyright (C) 2005-2012 Splunk Inc. All Rights Reserved. Version 5.0 This is an example viewstates.conf. To learn more about configuration files (including precedence) please see the documentation located at http://docs.splunk.com/documentation/splunk/latest/admin/aboutconfigurationfiles [charting:g3b5fa7l] ChartTypeFormatter_0_7_0.default = area Count_0_6_0.count = 10 LegendFormatter_0_13_0.default = right LineMarkerFormatter_0_10_0.default = false NullValueFormatter_0_12_0.default = gaps [*:g3jck9ey] Count_0_7_1.count = 20 DataOverlay_0_12_0.dataOverlayMode = none DataOverlay_1_13_0.dataOverlayMode = none FieldPicker_0_6_1.fields = host sourcetype source date_hour date_mday date_minute date_month FieldPicker_0_6_1.sidebarDisplay = True FlashTimeline_0_5_0.annotationSearch = search index=twink FlashTimeline_0_5_0.enableAnnotations = true FlashTimeline_0_5_0.minimized = false MaxLines_0_13_0.maxLines = 10 RowNumbers_0_12_0.displayRowNumbers = true RowNumbers_1_11_0.displayRowNumbers = true RowNumbers_2_12_0.displayRowNumbers = true Segmentation_0_14_0.segmentation = full SoftWrap_0_11_0.enable = true [dashboard:_current] TimeRangePicker_0_1_0.selected = All time 253