Lightbend Console can monitor any time series which is present in its Prometheus instance. It has built in monitors for the metrics provided by Lightbend Telemetry for Reactive Platform apps built using Akka, Lagom, and Play.

To enable metrics in:

  • Applications built with Lightbend technology—Lightbend Telemetry, a commercial offering, will automatically set up metrics. Use the Lightbend Telemetry documentation as a guide to instrument your own project.

  • Other applications—Lightbend Console can monitor other applications that are available for Prometheus to scrape. To export preconfigured metrics from your application you can use one of the many available prometheus exporters. For custom metrics, you will need to use one of the Prometheus client libraries.

Benefits from using Lightbend Telemetry

The cinnamon library for Lightbend Telemetry can be included unobtrusively in a Reactive application. Lightbend Telemetry metrics enable developers and operations to respond quickly to problems, track down unexpected behavior—and even tune the system. As a result, you can deploy your applications to production with confidence.

Lightbend Telemetry offers deep insight into applications built on the Lightbend technology stack and includes:

  • Visibility and dashboards for Akka actors, clustering, streams, remoting, Akka HTTP, Play, and Lagom.
  • Multiple options for external data integration including JMX, StatsD, Prometheus, DataDog, New Relic, and more.
  • Custom API to correlate business and application metrics with system and cluster information.

For the full list of supported metrics and events, see the Lightbend Telemetry documentation.

Development monitoring modes

Lightbend Console can help you monitor applications deployed into a Kubernetes, Minikube, or Minishift cluster, or run locally on the same machine as a cluster. Testing complex scenarios with an application cluster that more closely mirrors production lowers risk at deployment time. Local monitoring enables nimble iteration during development. The two modes provide different capabilities:

  • The default mode of monitoring applications deployed into a cluster enables Lightbend Console’s full spectrum of monitoring capabilities, including graph dashboards and health monitors. Through Kubernetes, this also provides the opportunity to “chaos test” application behavior such as node failover or cluster partitions.

  • When scraping metrics from a local application process directly, without the application being deployed into the cluster, the Console will not monitor the application since nothing is technically deployed. However, Graphana displays application metrics. This mode offers a convenient way to quickly make changes to the application and see results without spending the time to build, publish, and deploy the application.

The following diagram shows clustered and local application deployment.

Metrics from Deployed and Local applications