Merge pull request #1082 from lucperkins/lperkins/issue-750-sample-term

Add "sample" term to glossary

content/docs/concepts/jobs_instances.md

@@ -29,8 +29,8 @@ depends on the `honor_labels` configuration option. See the
 [scrape configuration documentation](/docs/operating/configuration/#%3Cscrape_config%3E)
 for more information.
 
-For each instance scrape, Prometheus stores a sample in the following
-time series:
+For each instance scrape, Prometheus stores a [sample](/docs/introduction/glossary#sample) in
+the following time series:
 
 * `up{job="<job-name>", instance="<instance-id>"}`: `1` if the instance is
    healthy, i.e. reachable, or `0` if the scrape failed.

content/docs/introduction/glossary.md

@@ -108,6 +108,12 @@ write into a format the other system can understand.
 
 A remote write endpoint is what Prometheus talks to when doing a remote write.
 
+### Sample
+
+A sample is a single value at a point in time in a time series.
+
+In Prometheus, each sample consists of a float64 representing some metric and a millisecond-precision timestamp.
+
 ### Silence
 
 A silence in the Alertmanager prevents alerts, with labels matching the silence, from
@@ -116,3 +122,4 @@ being included in notifications.
 ### Target
 
 A target is the definition of an object to scrape. For example, what labels to apply, any authentication required to connect, or other information that defines how the scrape will occur.
+