Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update telemetry docs #29

Merged
merged 7 commits into from
Oct 27, 2021
Merged

Update telemetry docs #29

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
acc1da8
Fix spelling on link
ronaktruss Oct 21, 2021
92c7746
Update link formatting to follow standard md rules
ronaktruss Oct 25, 2021
600f2e4
Add page about viewing telemetry logs
ronaktruss Oct 25, 2021
c3b9836
Merge branch 'main' of https://github.com/transcom/mymove-docs into r…
ronaktruss Oct 26, 2021
97d1003
Add images and depth to instructions for better clarity
ronaktruss Oct 27, 2021
14c4d8f
Reorganize structure and add troubleshooting section
ronaktruss Oct 27, 2021
99f3bd2
Fix typo and move bug to Jira
ronaktruss Oct 27, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Fix typo and move bug to Jira
  • Loading branch information
@ronaktruss
ronaktruss committed Oct 27, 2021
commit 99f3bd274f8fcdfb6e365e138529910525e06586
4 changes: 2 additions & 2 deletions docs/tools/telemetry/running-telemetry-locally.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Running telemetry locally

Because we are using open telemetry, we can use one telemetry system
in production (AWS) and another one locally. More information on why open telemetry was chose is available in this [ADR](https://github.com/transcom/mymove/blob/6feaa5b79cfd20276dd670babdbf0b31351a2fb4/docs/adr/0061-use-opentelemetry-for-distributed-tracing.md).
in production (AWS) and another one locally. More information on why open telemetry was chosen is available in this [ADR](https://github.com/transcom/mymove/blob/6feaa5b79cfd20276dd670babdbf0b31351a2fb4/docs/adr/0061-use-opentelemetry-for-distributed-tracing.md).

Running the elastic search offering locally turns out to be easy.

Expand Down Expand Up @@ -29,7 +29,7 @@ Running the elastic search offering locally turns out to be easy.

![Services Dashboard](../../../static/img/telemetry/services-dashboard.png)

Note: Services are all named unknown_service_milmove_gin and all local transactions besides logging in and logging out are called server-no-tls. This behavior is no ideal and should be looked into. Utilizing local urls such as `officelocal:3000` may be the cause of the lack of semantic naming.
Note: Services are all named `unknown_service_milmove_gin` and all local transactions besides logging in and logging out are called `server-no-tls`. This is a known [bug](https://dp3.atlassian.net/browse/MB-9926).

## Troubleshooting

Expand Down