You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2020/03/04 04:37:33 UTC

[GitHub] [skywalking] wu-sheng commented on a change in pull request #4439: Support name column(s) in the storage for 3rd party integration, like Kibana. Default OFF

wu-sheng commented on a change in pull request #4439: Support name column(s) in the storage for 3rd party integration, like Kibana. Default OFF
URL: https://github.com/apache/skywalking/pull/4439#discussion_r387445087
 
 

 ##########
 File path: docs/en/setup/backend/backend-setup.md
 ##########
 @@ -115,3 +115,15 @@ which format process is timezone related.
   
 In default, SkyWalking OAP backend choose the OS default timezone.
 If you want to override it, please follow Java and OS documents to do so.
+
+#### How to query the storage directly from 3rd party tool?
+SkyWalking provides browser UI, CLI and GraphQL ways to support extensions. But some users may have the idea to query data 
+directly from the storage. Such as in ElasticSearch case, Kibana is a great tool to do this.
+
+In default, due to reduce memory, network and storage space usages, SkyWalking saves id(s) only in the entity and metadata saved in the
+*_inventory entities only. But these tools usually don't support nested query, or don't work conveniently. In this special case,
 
 Review comment:
   No, it isn't. How to force it back in the markdown?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services