Skip to content

Commit 1ce5eee

Browse files
committed
Corrected typos
1 parent c5750ae commit 1ce5eee

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

logging/Azure_log_analytics_workspaces.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
If you use Microsoft Azure and want to use Azure Monitor *instead* of OpenSearch
66
to explore, filter, and report on log messages from a SAS Viya environment, you
77
can deploy the alternate logging solution described in this document. This solution
8-
uses acombination of Fluent Bit and an Azure Log Analytics workspace to handle log
8+
uses a combination of Fluent Bit and an Azure Log Analytics workspace to handle log
99
messages so that they can be accessed by Azure Monitor. Please note that the
1010
development work in this solution has been limited, and is primarily a proof of
1111
concept.
@@ -79,7 +79,7 @@ To remove all logging components for this solution, issue this command:
7979
/logging/bin/remove_logging_azmonitor.sh
8080
```
8181
By default, this script does not delete the namespace, but it does delete configmaps and secrets that were created by the deployment script. If you would like to delete the namespace as part
82-
of this script's execution, set the evnironment variable `LOG_DELETE_NAMESPACE_ON_REMOVE` to
82+
of this script's execution, set the environment variable `LOG_DELETE_NAMESPACE_ON_REMOVE` to
8383
*'true'* prior to running the script.
8484
8585
## Using Connection Information From a Kubernetes Secret

0 commit comments

Comments
 (0)