Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

SPM lets you extend standard performance metrics reports.  SPM exposes APIs and provides libraries that let you send custom metrics (any numerical data, not just performance metrics) into SPM and graph it along other reports.

 

NOTE:

  • To be able to use Custom Metrics, you need Sematext account. If you don't already have it, you can create it here, it's free, no credit card needed. After you have Sematext account,

...

  • create an SPM App to which Custom Metrics will be sent.
  • If you have already

...

  • created some SPM

...

  • Apps under your account in the past, you can

...

  • send Custom Metrics to any of them.
  • If you just registered, you can create SPM

...

  • Apps by following the steps

...

  • after Sematext account registration, or by clicking directly here.

Terminology

  • A "metric" is a distinct triple of (metric name, filter1 name, filter2 name).  Some examples:
    • ("cpuIdle", server="server1", null) vs. ("cpuIdle", null, server="server1") – these are 2 distinct metrics
    • ("cpuSteal", server="server1", null) vs. ("cpuIdle", server="server1", null) – these are 2 distinct metrics
    • ("diskRead", server="server1", device="/dev/xxx") vs. ("diskRead", server="server1", device="/dev/yyy") – this is the same 1 metric with two different values for filter2 named "device"
    • ("diskWrite", server="server1", device="/dev/xxx") vs. ("diskWrite", server="server1", device="/dev/yyy") – this is the same 1 metric with two different values for filter2 named "device"
    • ("diskRead", server="server1", device="/dev/xxx") vs. ("diskWrite", server="server1", device="/dev/xxx") – these are 2 distinct metrics

...