Skip to content

Commit

Permalink
fix(sweep): copy edits
Browse files Browse the repository at this point in the history
  • Loading branch information
bradleycamacho committed May 16, 2022
1 parent 4a00461 commit bdfd383
Showing 1 changed file with 2 additions and 2 deletions.
Expand Up @@ -8,15 +8,15 @@ metaDescription: Monitoring and troubleshooting the health of your ktranslate co

While running the **ktranslate** Docker container for New Relic network performance monitoring, you can monitor the health of the container to proactively detect potential issues.

The **ktranslate** container image has the `-tee_logs=true` and `-metrics=jchf` settings available during runtime, which allow it to send health metrics to us directly. These are enabled by default when installing network performance monitoring via the New Relic guided install. We recommend you to set them up when installing network performance monitoring manually.
The **ktranslate** container image has the `-tee_logs=true` and `-metrics=jchf` settings available during runtime, which allow it to send health metrics directly to New Relic. These are enabled by default when installing network performance monitoring via the New Relic guided install. We recommend you to set them up when installing network performance monitoring manually.

## Logs from ktranslate [#logs]

<Callout variant="tip">
If you want to check the logs locally from the Docker host, run `docker logs $CONTAINER_NAME`. For example, `docker logs ktranslate-snmp`.
</Callout>

The `-tee_logs=true` option sends logs to to us when polling devices. To see them, do the following:
The `-tee_logs=true` option sends logs to New Relic when polling devices. To see them, do the following:

1. Go to [one.newrelic.com](https://one.newrelic.com/) > **Logs**.
2. In **Find logs where**, enter `collector.name:"ktranslate"` and click **Query logs**.
Expand Down

0 comments on commit bdfd383

Please sign in to comment.