[skywalking] branch endpoint-length updated: Set endpointNameMaxLength in the application.yml

[wu...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

wusheng pushed a commit to branch endpoint-length
in repository https://gitbox.apache.org/repos/asf/skywalking.git


The following commit(s) were added to refs/heads/endpoint-length by this push:
     new f0033d9  Set endpointNameMaxLength in the application.yml
f0033d9 is described below

commit f0033d904cc651f3fc74f60cabca56a73230bcae
Author: Wu Sheng <wu...@foxmail.com>
AuthorDate: Mon Mar 30 23:17:43 2020 +0800

    Set endpointNameMaxLength in the application.yml
---
 dist-material/application.yml                                  | 4 +++-
 oap-server/server-bootstrap/src/main/resources/application.yml | 4 +++-
 2 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/dist-material/application.yml b/dist-material/application.yml
index f715df9..5e38bfc 100644
--- a/dist-material/application.yml
+++ b/dist-material/application.yml
@@ -85,7 +85,9 @@ core:
     # and it will cause more load for memory, network of OAP and storage.
     # But, being activated, user could see the name in the storage entities, which make users easier to use 3rd party tool, such as Kibana->ES, to query the data by themselves.
     activeExtraModelColumns: ${SW_CORE_ACTIVE_EXTRA_MODEL_COLUMNS:false}
-
+    # The max length of the endpoint name.
+    # In the current practice, we don't recommend the length over 190.
+    endpointNameMaxLength: ${SW_CORE_ENDPOINT_NAME_MAX_LENGTH:150}
 storage:
   selector: ${SW_STORAGE:h2}
   elasticsearch:
diff --git a/oap-server/server-bootstrap/src/main/resources/application.yml b/oap-server/server-bootstrap/src/main/resources/application.yml
index 7c79625..c794452 100755
--- a/oap-server/server-bootstrap/src/main/resources/application.yml
+++ b/oap-server/server-bootstrap/src/main/resources/application.yml
@@ -84,7 +84,9 @@ core:
     # and it will cause more load for memory, network of OAP and storage.
     # But, being activated, user could see the name in the storage entities, which make users easier to use 3rd party tool, such as Kibana->ES, to query the data by themselves.
     activeExtraModelColumns: ${SW_CORE_ACTIVE_EXTRA_MODEL_COLUMNS:false}
-
+    # The max length of the endpoint name.
+    # In the current practice, we don't recommend the length over 190.
+    endpointNameMaxLength: ${SW_CORE_ENDPOINT_NAME_MAX_LENGTH:150}
 storage:
   selector: ${SW_STORAGE:h2}
   elasticsearch: