From 56a90151bd6fd04ddb58d7a20f35e9dce6cb9087 Mon Sep 17 00:00:00 2001 From: Ginger Collison Date: Fri, 5 Feb 2021 14:54:13 -0600 Subject: [PATCH] update based on RI changes to README --- jetstream/monitoring/monitoring.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/jetstream/monitoring/monitoring.md b/jetstream/monitoring/monitoring.md index 39add46..f95e510 100644 --- a/jetstream/monitoring/monitoring.md +++ b/jetstream/monitoring/monitoring.md @@ -8,7 +8,7 @@ Typically, NATS is monitored via HTTP endpoints like `/varz`, we do not at this JetStream publish a number of advisories that can inform operations about health and state of the Streams. These advisories are published to normal NATS subjects below `$JS.EVENT.ADVISORY.>` and one can store these advisories in JetStream Streams if desired. -The command `nats event --js-advsiroy` can view all these events on your console. The Golang package [jsm.go](https://github.com/nats-io/jsm.go) can consume and render these events and have data types for each of these events. +The command `nats event --js-advisory` can view all these events on your console. The Golang package [jsm.go](https://github.com/nats-io/jsm.go) can consume and render these events and have data types for each of these events. All these events have JSON Schemas that describe them, schemas can be viewed on the CLI using the `nats schema show ` command.