Subject to Customer’s compliance with this Agreement, including Customer’s timely payment of all License Fees, Splunk grants to Customer a nonexclusive, worldwide, nontransferable, nonsublicensable license during the applicable Term to install and use the Purchased Software within the Licensed Capacity solely for Customer’s Internal Business Purposes.Ģ.2 Evaluation Software. Capitalized terms used but not otherwise defined in this Agreement have the meanings set forth in Exhibit A.Ģ.1 Purchased Software. and “Customer” refers to the company, government, or other entity on whose behalf you have entered into this Agreement or, if there is no such entity, you as an individual.ġ. WITHOUT LIMITING THE FOREGOING, YOU (AND YOUR ENTITY, IF ANY) ACKNOWLEDGE THAT BY SUBMITTING AN ORDER FOR THE SPLUNK SOFTWARE, YOU (AND YOUR ENTITY (IF ANY)) HAVE AGREED TO BE BOUND BY THIS AGREEMENT.Īs used in this Agreement, “Splunk,” refers to Splunk Inc., a Delaware corporation, with its principal place of business at 270 Brannan Street, San Francisco, California 94107, U.S.A. BY DOWNLOADING AND/OR INSTALLING SPLUNK SOFTWARE: (A) YOU ARE INDICATING THAT YOU HAVE READ AND UNDERSTAND THIS AGREEMENT, AND AGREE TO BE LEGALLY BOUND BY IT ON BEHALF OF THE COMPANY, GOVERNMENT, OR OTHER ENTITY FOR WHICH YOU ARE ACTING (FOR EXAMPLE, AS AN EMPLOYEE OR GOVERNMENT OFFICIAL) OR, IF THERE IS NO COMPANY, GOVERNMENT OR OTHER ENTITY FOR WHICH YOU ARE ACTING, ON BEHALF OF YOURSELF AS AN INDIVIDUAL AND (B) YOU REPRESENT AND WARRANT THAT YOU HAVE THE AUTHORITY TO ACT ON BEHALF OF AND BIND SUCH COMPANY, GOVERNMENT OR OTHER ENTITY (IF ANY). To learn about Splunk software license management, see Allocate license volume.THIS SPLUNK SOFTWARE LICENSE AGREEMENT ( “AGREEMENT”) GOVERNS THE LICENSING, INSTALLATION AND USE OF SPLUNK SOFTWARE. There are multiple types of Splunk software licenses available, see Types of Splunk licenses. See Resource Usage: CPU Usage in the Monitoring Splunk Enterprise manual. To check the vCPU count in your deployment, use the Resource Usage: CPU Usage dashboards in the Monitoring Console, and filter the report for the search head and indexer roles. The total vCPU count across all Splunk Enterprise search heads and indexers count towards the vCPU licensed capacity. Splunk software uses the CPU's reported by the OS as the total vCPU's for each measured node. The term vCPU is commonly used when provisioning resources in virtualized environments and in cloud infrastructure allocations but each implementation of vCPU is unique. A vCPU can represent a physical core, a logical core created through the use of hyper-threading or simultaneous multithreading, or a shared logical CPU provided through virtualization. How vCPU is calculated for infrastructure licensingįor Splunk software, a vCPU is any logical CPU core as reported by the host operating system. The indexing volume is measured daily from midnight to midnight using the system clock on the license manager. License warnings occur when you exceed the indexing volume allowed for your license. What happens if I exceed my license volume? The use of summary indexing and metric rollup summaries do not count against your license volume quota. The Splunk software troubleshooting and internal communications logs that are indexed into the internal indexes such as _internal and _introspection do not count against your license volume quota. Metrics data draws from the same license quota as event data. Metric events less than 150 bytes are recorded as event size in bytes plus 18 bytes, up to a maximum of 150 bytes. Metric events that exceed 150 bytes are recorded as only 150 bytes. However, the per-event size measurement is capped at 150 bytes. When ingesting metrics data, each metric event is measured by volume like event data. Because the data is measured at the indexing pipeline, data that is filtered and dropped prior to indexing does not count against the license volume quota. It is not based on the amount of compressed data that is written to disk. When ingesting event data, the measured data volume is based on the raw data that is placed into the indexing pipeline. Part of the indexing process is to measure the volume of data being ingested, and report that volume to the license manager for license volume tracking. When data is sent to the Splunk platform, that data is indexed and stored on disk.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |