Skip to content

Commit ae7edcc

Browse files
Merge pull request #115 from loggregator/add-core-counting
add core counting information
2 parents 789e42f + 3e110d1 commit ae7edcc

File tree

2 files changed

+40
-0
lines changed

2 files changed

+40
-0
lines changed

core-counting.html.md.erb

+39
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
---
2+
title: Core Counting
3+
owner: TAS Observability
4+
---
5+
6+
7+
This topic explains how to configure your tile to take advantage of Ops
8+
Manager's ability to count physical and virtual cores. This option is available
9+
starting in Ops Manager versions v3.0.10+LTS-T and v2.10.58.
10+
11+
Warning: In the following paragraph we refer to SKU. This is not technically a
12+
VMware SKU. We use the concept because some tiles share a license, e.g. TAS, TASW,
13+
and IST. A core can run all three of these products at the same
14+
time with a single core license without being double counted.
15+
16+
Tile developers can add monit jobs named `SKU-<SKU_NAME>` to their VMs to let
17+
Ops Manager know to count all of that VM's cores as part of a SKU. VMs with the
18+
same SKU will be counted together. If no matching monit jobs are present, no
19+
cores will be counted for those VMs. For example: if you wanted to create and
20+
specify a SKU of the name `TEST`, you must define a monit job with the name
21+
`SKU-TEST`. A simpler way for VMware tile developers to define such a monit job
22+
for linux and windows VMs is to use the internal count-cores-indicator-release.
23+
24+
When workloads are being run on vSphere, if multiple VMs are being run on the
25+
same host, the total counted cores of a given SKU will never be more then the
26+
number of physical cores on that host. On other infrastructures Ops Manager
27+
uses the values returned by the kernel for number of cores and threads per
28+
core.
29+
30+
The Bosh Director counts all the relevant cores once per hour and stores up to
31+
2MB of historic measurements. Click the "Download Core Consumption Data" button on Ops
32+
Manager, or curl the `/api/v0/download_core_consumption` API endpoint
33+
to retrieve a CSV of all the measurements. Each row in the CSV is formatted as
34+
follows:
35+
36+
```
37+
timestamp, product identifier/SKU, physical core count, virtual core count
38+
```
39+

toc.md.erb

+1
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,7 @@
2626
* [Securing service credentials with runtime CredHub](/docs-tiledev/ssi-creds-tiledev.html)
2727
* [How to integrate services with Cloud Foundry's logging system](/docs-tiledev/nozzle.html)
2828
* [Syslog: migrating existing configuration](/docs-tiledev/migrating-syslog-configuration.html)
29+
* [Core Counting](/docs-tiledev/core-counting.html)
2930
* [**Service brokers**](/docs-tiledev/service-broker-index.html)
3031
* [Service broker resources](/docs-tiledev/service-brokers.html)
3132
* [Example service brokers](/docs-services/examples.html)

0 commit comments

Comments
 (0)