We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
描述您遇到的bug CMDB日志查询的ciName和ciTypeName没有内容
如何重现
预期行为 CMDB日志查询的ciName和ciTypeName显示相应的内容
截图
附加
The text was updated successfully, but these errors were encountered:
cmdb日志只记录调用参数里有的信息,调用参数里缺失的信息是不会去query数据库的(AOP切面功能应尽量不影响主服务线程的性能)。这个逻辑之前跟@chaneyliu 讨论过,当时的结论是先这么做;如果现在重新检讨,那么解决这个问题有两个方案: A,在日志功能里根据ciTypeId去查一次db,获取ciTypeName,缺点是会让正常的业务流程多一步DB操作 B,修改接口,让接口多接收一个ciTypeName的参数,然后让调用者传过来,缺点是api的提供方(cmdb)和使用方(wecube)都需要同步改。
Sorry, something went wrong.
先这样处理就可以。
跟超哥同步过,解决方案如下:
#144 don't popular fields without log data for now
9e87b09
Merge pull request #249 from WeBankPartners/144_clean_up_unused_field…
7eed274
…s_of_log #144 don't popular fields without log data for now
jordanzhangsz
No branches or pull requests
描述您遇到的bug
CMDB日志查询的ciName和ciTypeName没有内容
如何重现
预期行为
CMDB日志查询的ciName和ciTypeName显示相应的内容
截图
![image](https://user-images.githubusercontent.com/17095701/64493599-a70b6980-d2b4-11e9-9b45-13828e353f96.png)
附加
The text was updated successfully, but these errors were encountered: