From a0df1f91bcd6965bb1b46f8ca4e2b51d062b9448 Mon Sep 17 00:00:00 2001 From: arturlazarenkoemnify Date: Mon, 19 Sep 2022 12:55:29 +0200 Subject: [PATCH 1/2] added dashboard link --- emnify/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/emnify/README.md b/emnify/README.md index e99ccd2a3f..8744531376 100644 --- a/emnify/README.md +++ b/emnify/README.md @@ -15,7 +15,7 @@ For more information read the [Forecast monitor][4] and [Anomaly monitor][5] doc ### Dashboard -You can pick a period to filter data displayed. +You can pick a period in [dashboard][6] to filter data displayed. ## Support @@ -26,3 +26,4 @@ Need help? Contact [Emnify support][3]. [3]: https://support.emnify.com/hc/en-us [4]: https://docs.datadoghq.com/monitors/create/types/forecasts/?tab=linear [5]: https://docs.datadoghq.com/monitors/create/types/anomaly/ +[6]: https://app.datadoghq.com/dashboard/lists?q=emnify \ No newline at end of file From 062841b1d325c3e3f60c2571bc2c3e5a7a0028d3 Mon Sep 17 00:00:00 2001 From: arturlazarenkoemnify Date: Tue, 20 Sep 2022 15:27:08 +0200 Subject: [PATCH 2/2] fix: comments fix --- emnify/README.md | 4 ++-- emnify/manifest.json | 4 ++-- emnify/metadata.csv | 8 ++++---- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/emnify/README.md b/emnify/README.md index 8744531376..979e548031 100644 --- a/emnify/README.md +++ b/emnify/README.md @@ -5,11 +5,11 @@ connected and secure. Use the Datadog-EMnify integration to collect metrics and data usage from IoT EMnify devices. ## Setup -Follow the [integration guide][2] to configure streaming of usage data, using the **Integration steps** and **Verifying the integration** sections. +Follow the [Emnify integration guide][2] to configure streaming of usage data, using the **Integration steps** and **Verifying the integration** sections. ### Monitors -Everybody has different usage patterns so in order for monitors to reflect your specific case you must +Everybody has different usage patterns, so in order for monitors to reflect your specific case you must define workload-based boundaries and sensitivity. For more information read the [Forecast monitor][4] and [Anomaly monitor][5] documentation. diff --git a/emnify/manifest.json b/emnify/manifest.json index 01e0fc22b3..7bee771c7a 100644 --- a/emnify/manifest.json +++ b/emnify/manifest.json @@ -13,7 +13,7 @@ "media": [ { "media_type": "image", - "caption": "All-in-one Dashboard enables you to observe organisation consumption and analyze usage patterns of your devices inventory.", + "caption": "All-in-one Dashboard enables you to observe organization consumption and analyze usage patterns of your devices inventory.", "image_url": "images/data_usage_dashboard.png" }, { @@ -60,7 +60,7 @@ }, "metrics": { "prefix": "emnify.", - "check": "endpoint.volume", + "check": "emnify.endpoint.volume", "metadata_path": "metadata.csv" } }, diff --git a/emnify/metadata.csv b/emnify/metadata.csv index f690f0fa4a..b2d0e4519b 100644 --- a/emnify/metadata.csv +++ b/emnify/metadata.csv @@ -1,4 +1,4 @@ -metric_name,metric_type,interval,unit_name,per_unit_name,description,orientation,integration,short_name,curated_metric -endpoint.volume,count,,byte,,Total Volume,"","",volume, -endpoint.volume_rx,count,,byte,,Data Received,,,volume_rx -endpoint.volume_tx,count,,byte,,Data Transmitted,,,volume_tx +metric_name,metric_type,interval,unit_name,per_unit_name,description,orientation,integration,short_name,curated_metric,integration,orientation +emnify.endpoint.volume,count,,byte,,Total Volume,"","",volume,emnify,0 +emnify.endpoint.volume_rx,count,,byte,,Data Received,,,volume_rx,emnify,0 +emnify.endpoint.volume_tx,count,,byte,,Data Transmitted,,,volume_tx,emnify,0 \ No newline at end of file