Versions Compared

Key

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

...

They will then emit their metrics and you can retrieve them (along with system metrics) via the Metrics Explorer in the CDAP UI or via the CDAP’s CDAP Microservices v3. The names given to the metrics (such as names.longnames and names.bytes as in the example below) should be composed only of alphanumeric characters.

...

  • System wide In cdap-site.xml (system wide) to control whether app containers emit metrics

  • Per Run Using the config system.metrics.enabled as program argument to override the system-wide setting per program run.

  • Program Preference Using the system.metrics.enabled permanently for a program by setting a preference.

  • Scoping Additionally for program types that have sub-components (such as MapReduce and Spark programs), a prefix can be added to system.metrics.enabled to limit the scope of the arguments. 

Using Metrics Explorer

...

Flow Control

A flow control mechanism in CDAP prevents you from submitting too many requests, which can cause stuck or failed pipeline runs. This mechanism applies to start (Launch) requests for the following pipelines and jobs in all editions of CDAP, versions 6.6 and later:

...