Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

前端错误的收集、记录 #14

Open
Justineo opened this issue Apr 22, 2014 · 14 comments
Open

前端错误的收集、记录 #14

Justineo opened this issue Apr 22, 2014 · 14 comments

Comments

@Justineo
Copy link
Member

业务端系统在运行时报错的信息目前没有任何记录,可以考虑增强一下这方面的控制。

@otakustay
Copy link
Member

推荐er-track,现在支持的东西看这里,有啥需要可以提我们做通用的

@Justineo
Copy link
Member Author

OK,我先看看~

@leeight
Copy link
Member

leeight commented Apr 24, 2014

数据发送到哪里去的?我感觉希望是一个独立的组件/服务,可以实时的看到线上的error log记录

@otakustay
Copy link
Member

管家想用node架一个,不过还要和OP、RD等沟通

@Justineo
Copy link
Member Author

error log 可以像 AdInsight 一样在 JPAAS 上搭一个环境来记录,这个我们搭了自己看看就行了吧~

@leeight
Copy link
Member

leeight commented Apr 24, 2014

管家想用node架一个,不过还要和OP、RD等沟通

直接扔到jpaas上就好了,有啥要沟通的

@leeight
Copy link
Member

leeight commented Apr 24, 2014

给edp弄个issue记录一下吧,我抽空搭建一个去

@ksky521
Copy link

ksky521 commented Apr 26, 2014

webfe那边不是有解决方案吗?

@leeight
Copy link
Member

leeight commented Apr 26, 2014

没听说过,发来看看?

@ksky521
Copy link

ksky521 commented Apr 28, 2014

@otakustay
Copy link
Member

你们的方案都好重型……

ECOM的SPA程序大概有如下特点:

  1. 异常大部分被Promise吃掉了,普通的异常监控没用,甚至callstack都可能要特殊处理
  2. SPA系统不能监控页面打开时的性能,要监控每个controller的性能
  3. 点击事件等的监控必须按controller切分,全局监控完全没效果

因此注定只有自定主事件(其它统计)有用了……

我本来想的就是放个服务器,把发过来的数据以N小时(可配)为维度写到文件里,以天为单位建文件夹,事后再处理这些数据的,突然间就被你们讨论得如此高大上了……

@leeight
Copy link
Member

leeight commented Apr 28, 2014

我本来想的就是放个服务器,把发过来的数据以N小时(可配)为维度写到文件里,以天为单位建文件夹,事后再处理这些数据的,突然间就被你们讨论得如此高大上了……

那就这么来吧

@leeight
Copy link
Member

leeight commented Apr 28, 2014

简单来说可以这样子
jpaas上面放一个nginx,日志写入mfs(配置一下按照分钟级别分割),然后开发机定时任务读取mfs的日志,自定义任务处理,生成danshboard,结束。

@otakustay
Copy link
Member

嗯,把记录和处理分开,处理有很多事要做呢,比如把用户的访问路径转成可视化的图之类的,用crontab跑就行了

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants