Skip to content

Typo "Azure Monitor/Application Insights"→"Azure Monitor Application … #35

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

Open
hyoshioka0128 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Typo "Azure Monitor/Application Insights"→"Azure Monitor Application … #35

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -331,7 +331,7 @@ If we need to shut down the solution and start it up later, see below for the pr

# Monitoring

Currently automated Azure dashboards aren't built when deploying the solution; however, outside of regular host metrics like CPU/Memory, some key metrics will be important to monitor in Azure Monitor/Application Insights such as:
Currently automated Azure dashboards aren't built when deploying the solution; however, outside of regular host metrics like CPU/Memory, some key metrics will be important to monitor in Azure Monitor Application Insights such as:

- `SSPlayerConnected` – The most key metric to know when a user connected (use Count)
- `SSPlayerDisconnected` – When a user disconnects from the Signaling Server (use Count)
Expand Down