我如何查看Fabric Composer的日志 [英] How do I see the logs for Fabric Composer

查看:133
本文介绍了我如何查看Fabric Composer的日志的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我想查看由Fabric Composer生成的运行时日志和客户端日志,但是找不到它们.您能否提供有关如何访问日志的指南?.

I would like to view the runtime and client logs generated by Fabric Composer but cannot find them. Can you please provide guidance on how to access the logs?.

推荐答案

运行时日志

如果运行docker ps -a,应该会看到3个正在运行的Docker容器. docker容器之一将是chaincode容器(Composer运行时在其中执行您的逻辑).

Runtime Logs

If you run docker ps -a you should see 3 running docker containers. One of the docker containers will be the chaincode container (where the Composer runtime is executing your logic).

它的生成名称类似于:dev-vp0-4968dea9e3a69670235d9283859801ab5df6f18398f15711d6f5426123955f9f

It has a generated name something like: dev-vp0-4968dea9e3a69670235d9283859801ab5df6f18398f15711d6f5426123955f9f

查找其容器ID,然后运行docker logs <container id> 您可以使用docker logs -f

Look for its container id, and then run docker logs <container id> You can follow the logs using docker logs -f

如果您使用的是Mac,还可以使用Kitematic GUI查看日志. Fabric Composer日志条目标记有[Concerto](旧的代号)

If you are on the Mac you can also view the logs using the Kitematic GUI. Fabric Composer log entries are tagged with [Concerto] (the old codename)

客户端API(用Node编写)也可以生成日志.设置DEBUG环境变量以启用调试.例如(对于Linux和Mac):

The client-side APIs (written in Node) can also generate logs. Set the DEBUG environment variable to enable debugging. E.g (for Linux and Mac):

export DEBUG=composer:*

INFO和更高级别的日志消息将发送到stdout.所有日志还将记录到./logs文件夹下的磁盘中.

INFO and higher log messages will be sent to stdout by default. All logs will also be logged to disk under a ./logs folder.

请在此处查看文档: https://fabric-composer.github.io/problems/diagnostics.html

Please see the docs here: https://fabric-composer.github.io/problems/diagnostics.html

这篇关于我如何查看Fabric Composer的日志的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆