From 638e3c91a13c7cc5e3319c94224b60c82b19df8c Mon Sep 17 00:00:00 2001 From: Oleksii Borisenko Date: Wed, 8 Sep 2021 23:35:44 +0300 Subject: [PATCH] Change link to YAML validator (with https) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 525b257..3259ffe 100644 --- a/README.md +++ b/README.md @@ -24,7 +24,7 @@ Elasticsearch's HTTP module should be enabled since this extension collects metr Please place the extension in the "monitors" directory of your Machine Agent installation directory. Do not place the extension in the "extensions" directory of your Machine Agent installation directory. ## Configuration -Note : Please make sure not to use tab (\t) while editing yaml files. You can validate the yaml file using a [yaml validator](http://yamllint.com) +Note : Please make sure not to use tab (\t) while editing yaml files. You can validate the yaml file using a [yaml validator](https://jsonformatter.org/yaml-validator) Configure the extension by editing the config.yml file in `/monitors/ElasticsearchMonitor/`. The metricPrefix of the extension has to be configured as specified [here](https://community.appdynamics.com/t5/Knowledge-Base/How-do-I-troubleshoot-missing-custom-metrics-or-extensions/ta-p/28695#Configuring%20an%20Extension). Please make sure that the right metricPrefix is chosen based on your machine agent deployment, otherwise this could lead to metrics not being visible in the controller. ###config.yml