TCDN服务端日志说明
日志文件存储于 TCDN服务端的 /mnt/tcdn/logs/ 路径下
开放API接口
TCDN服务端开放API接口来读取最新日志,可以根据日志文件名及指定最后读取多少行,来读取某个日志文件的最新记录。API文档参考: http://doc.zvo.cn/tcdn/20241107/admin.log.log.json.html
以下是相关日志文件的说明
cacheRefresh_yyyy-MM-dd.log
/mnt/tcdn/logs/cacheRefresh_yyyy-MM-dd.log 为 TCDN系统自带的缓存刷新能力进行自动化刷新翻译缓存时的执行日志。
这个文件是以天来进行存储的,每天都会创建一个日志文件,比如:
cacheRefresh_2024-12-03.log
cacheRefresh_2024-12-04.log
这个文件中每行都是以json格式存储的,同时每行也是一个执行动作。
这个文件中的内容如:
{"sourceUrl":"http://qiye1.wang.market/1101.html","targetLanguage":"korean","result":"success","thread":"thread 2","index":32,"allNumberUrl":43,"time":"14:59:00"}
{"sourceUrl":"http://qiye1.wang.market/1057.html","targetLanguage":"persian","result":"success","thread":"thread 3","index":34,"allNumberUrl":43,"time":"14:59:00"}
{"sourceUrl":"http://qiye1.wang.market/1099.html","targetLanguage":"afrikaans","result":"success","thread":"thread 1","index":33,"allNumberUrl":43,"time":"14:59:01"}
{"sourceUrl":"http://qiye1.wang.market/1101.html","targetLanguage":"tajik","result":"success","thread":"thread 2","index":32,"allNumberUrl":43,"time":"14:59:03"}
{"sourceUrl":"http://qiye1.wang.market/1057.html","targetLanguage":"bhojpuri","result":"success","thread":"thread 3","index":34,"allNumberUrl":43,"time":"14:59:04"}
{"sourceUrl":"http://qiye1.wang.market/1099.html","targetLanguage":"indonesian","result":"success","thread":"thread 1","index":33,"allNumberUrl":43,"time":"14:59:05"}
它是按照时间来排序的,执行完一个动作后就会把这个动作追加到这个文件的末尾。 也就是文件的末尾最后一个日志,是最后一次的动作。
有关每行中的字段及内容说明:
- sourceUrl 当前执行的源站url页面
- targetLanguage 翻译为的目标语言
- result 翻译结果,如果为 success 则是执行成功; 如果失败或别的情况这里是相关描述
- thread 线程的名字,执行这个动作是有哪个线程来执行的
- allNumberUrl 共有多少url,也就是TCDN自动刷新功能扫描扫出来的所有url数量,待进行翻译的URL数量
- index 执行进度,当前执行到总数 allNumberUrl 中的第几个了,是 allNumberUrl 中顺序执行的第几个。 比如 allNumberUrl 是10 ,这里是1,那么就证明是刚开始执行,刚执行到第一个。当 index 跟 allNumberUrl 相等时,那便是执行到最后了,执行完这个那便是执行结束了。
tcdn.log
/mnt/tcdn/logs/tcdn.log 为 tcdn 本身运行的日志,一些运行输出都会输出到这里面。
另外每次tcdn启动时,会自动将这个日志文件清空,重新记录。
htmlTranslate_yyyy-MM-dd.log
所有调用html翻译接口的日志记录
示例:
{"result":1,"serverNode":"loc.7812ec6d28ec","size":72314,"to":"chinese_simplified","time":"2025-04-13 14:15:31","url":"https://xxx.com/","exeTime":10553}
{"result":1,"serverNode":"loc.3a03932ce7a9","size":33064,"to":"chinese_simplified","time":"2025-04-13 14:16:11","url":"https://xxx.com/company-introduction","exeTime":5539}
{"result":1,"serverNode":"loc.b082ee024591","size":33879,"to":"chinese_simplified","time":"2025-04-13 14:17:04","url":"https://xxx.com/contact-us","exeTime":4905}
- result 执行结果,1是成功, 不为1或者result不存在则是失败
- serverNode 调用html翻译接口进行翻译时,是有哪个具体的集群节点提供的翻译
- size 传入的 html 参数内容的字符数,字符长度。注意,这个是传入的html的整个值的内容字符数。
- to 当前是翻译为什么语种
- time 翻译时间
- url 进行翻译的源站页面 url
- exeTime 如果执行成功(result为1),这里是执行的耗时,单位是毫秒
- exception 如果执行失败(result不为1),这里是执行失败的原因
jsParse_yyyy-MM-dd.log
所有调用 JS引擎接口执行的日志记录
示例:
{"result":1,"serverNode":"loc.a266238cd47c","size":72898,"time":"2025-05-13 14:15:29","url":"https://abc.com/","exeTime":553}
{"result":1,"serverNode":"loc.a266238cd47c","size":33019,"time":"2025-05-13 14:16:09","url":"https://abc.com/company-introduction","exeTime":1871}
{"result":1,"serverNode":"loc.245978e82ea1","size":33767,"time":"2025-05-13 14:17:02","url":"https://abc.com/contact-us","exeTime":601}
- result 执行结果,1是成功, 不为1或者result不存在则是失败
- serverNode 调用html翻译接口进行翻译时,是有哪个具体的集群节点提供的翻译
- size 传入的 html 参数内容的字符数,字符长度。注意,这个是传入的html的整个值的内容字符数。
- time 执行的时间
- url 进行操作的源站页面 url
- exeTime 如果执行成功(result为1),这里是执行的耗时,单位是毫秒
- exception 如果执行失败(result不为1),这里是执行失败的原因