Minor doc fixes

GSA-TTS · Dec 20, 2023 · 20f6aaa · 20f6aaa
1 parent 2a2cf2a
commit 20f6aaa
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/README.md b/README.md
@@ -60,7 +60,7 @@ Current Supported Tags:
 7. If you are using an egress proxy, set the PROXYROUTE variable and restage the app.
     ```sh
     cf set-env fluentbit-drain PROXYROUTE 'https://user:[email protected]:61443'
-    cf restage fluentbit-drain
+    cf restart fluentbit-drain
     ```
 
 At this point you should have a running app, but nothing is sending logs to it.

diff --git a/TROUBLESHOOTING.md b/TROUBLESHOOTING.md
@@ -47,7 +47,8 @@ The `newrelic` plugin will log errors if it cannot connect to New Relic because
 New Relic has *Logs* in two places in its UI. There is a global *Logs* section, which is where you should look first. The URL of this view will start with https://one.newrelic.com/logger (in fact, if you are logged in, that URL should take you there) and the heading will be something like _All logs_. There is another, very similar looking, logs view in the *APM & Services* section under each entity New Relic knows about.
 
 Each APM & Service instance that New Relic classifies as a "service" will have its own individual logs that are available when navigating to a specific service. When navigating to the "Global Logs Inbox" as specified above, you will see all logs from all services. To filter on specific logs that are coming from `cg-logshipper` you can add a column of `newrelic.source`, or, run a query with the following: `newrelic.source:"api.logs"`. Logshipper will have a source of `newrelic.source:"api.logs"`, where application logs will have a source of `newrelic.source:"logs.APM"`.
-Which helped highlight that New Relic was in fact, receiving logs from the `cg-logshipper` application, along with adding a column of `newrelic.source`. If you plan to have the logshipper deployed in multiple environments, it may also be beneficial to add a column of `tags.space_name` so that when all instances of logshipper, as well as application instances are putting logs into the inbox, it is easier to see which environments are, in fact, sending logs to new relic.
+
+If you plan to have the logshipper deployed in multiple environments, it may also be beneficial to add a column of `tags.space_name` so that when all instances of logshipper, as well as application instances are putting logs into the inbox, it is easier to see which environments are, in fact, sending logs to New Relic.
 
 ![image](https://github.com/GSA-TTS/cg-logshipper/assets/130377221/a832b1f9-02df-41c2-a0c4-8f3f9558f67e)