This is just a time format, I can't see why it is a blocker to any integration. Someone used to tell me, they use Kibana to show the data, I don't know how, because I don't use Kibana mostly.
Also, the tool like Kibana, are you sure they don't have the time field format capability? For myself, this is NOT a good enough reason to request the changes which are huge and will break many things. And most importantly, we are hard to afford the workloads. Both of them are not our primary UI, even aren't our secondary UI. Sheng Wu 吴晟 Twitter, wusheng1108 刘 嘉鹏 <[email protected]> 于2020年6月10日周三 下午3:20写道： > But this solution limits the possibility of combining other open source > products with skywalking > > 2020年6月10日 14:38，Sheng Wu <[email protected]<mailto: > [email protected]>> 写道： > > Because it indicates the precision of the metrics data, and easier to read > and debug, less TZ related concern in query implementation. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > 刘 嘉鹏 <[email protected]<mailto:[email protected]>> 于2020年6月10日周三 > 下午2:31写道： > > Hi,all: > Question: what is the benefit of the time_bucket? > For example: the cpm day metrics contains the following time_bucket: > 1. 20200531 > 2. 2020053102 > 3. 202005310101 > the time_bucket is only works on skywalking, why not replace him with > the universal timestamp with a type? > for example : > 1. 1590854400 and type 1 replace 20200531 > the advantage is skywalking metrics can use other display tools to > display,for example: kibana and grafana > Evan.Liu > > >
