我已经使用了stackdriver记录了很长时间了,现在我也想利用错误报告。如果可能的话,我宁愿使用日志文件的日志记录机制和刮擦异常(出于各种原因),而不是使用error_reporting库。话虽如此,该文件非常令人困惑。例如,文档说:https://cloud.google.com/error-reporting/docs/setup/compute-engine-engine#log_exceptions
首先,安装流利的木材 - 佩斯库:
sudo pip安装google-cloud-error-retporting-upgrade
这使我相信Google-cloud-error报告是一个叉子或与fluent-logger-python相关的叉子,但是当我初始化Google-cloud-eror-eror-error报告时,它直接调用了GCE Metadata Server而不是而不是连接到当地的fluentd。这两个无关的软件包还是文档是错误的还是误导性的?如果我将JSON格式的异常发送到Fluentd或由Fluentd监视的日志文件,将会出错了解它们?
感谢您的任何澄清
文档是错误的。
tl; dr您必须输出看起来像https://cloud.google.com/error-reporting/docs/formatting-error-messages
这是我的解决方案:
#Parse raw log entries to expose severity field so that
#StackDriver log viewer can properly categorize (and so we can filter)
<source>
@type tail
path /var/log/conductor
pos_file /var/log/td-agent/conductor.pos
format multiline
format_firstline /d{4}-d{2}-d{2} d{2}:d{2}:d{2}/
format1 /^(?<message>(?<time>d{4}-d{2}-d{2} d{2}:d{2}:d{2}),d*s*[a-zA-Z_]*s*(?<severity>[A-Z]*).*)/
read_from_head true
multiline_flush_interval 3s
tag conductor.app
</source>
#Add hostname field
<filter conductor.app>
@type record_transformer
<record>
hostname ${hostname}
</record>
</filter>
#Filter and tag log entries of severity ERROR or CRITICAL
<match conductor.app>
@type rewrite_tag_filter
rewriterule1 severity ERROR|CRITICAL conductor.err
rewriterule2 severity .+ conductor.info
</match>
#Process entries with tracebacks differently than those without
<match conductor.err>
@type rewrite_tag_filter
rewriterule1 message .*Traceback conductor.err.traceback
rewriterule2 message .+ conductor.err.message
</match>
#Parse out the traceback
<match conductor.err.traceback>
@type parser
key_name message
format multiline
format1 /^(?<message>(?<time>d{4}-d{2}-d{2} d{2}:d{2}:d{2}),d*s*(?<log>[a-zA-Z_]*)s*(?<severity>[A-Z]*).*(?
<traceback>Traceback .*))/
tag conductor.err.traceback.report
</match>
#Format traceback reports
<filter conductor.err.traceback.report>
@type record_transformer
<record>
serviceContext {
"service": "${record["log"]}"
}
message ${record["traceback"]}
</record>
remove_keys traceback
</filter>
#Process errors that don't have tracebacks
<match conductor.err.message>
@type parser
key_name message
format multiline
format1 /^(?<message>(?<time>d{4}-d{2}-d{2} d{2}:d{2}:d{2}),d*s*(?<log>[a-zA-Z_]*)s*(?<severity>[A-Z]*):s*(?<report>.*))/
tag conductor.err.message.report
</match>
#For errors without tracebacks we have to stub out some fields that
#error reporting requires, but we don't have
<filter conductor.err.message.report>
@type record_transformer
<record>
serviceContext {
"service": "${record["log"]}"
}
message ${record["report"]}
reportLocation {
"filePath": "None",
"lineNumber": 0,
"functionName": "None"
}
</record>
</filter>
#Send to StackDriver logging!
<match conductor.**>
@type google_cloud
buffer_chunk_limit 2M
flush_interval 5s
max_retry_wait 300
disable_retry_limit
num_threads 8
</match>
您可以在此处关注该教程:https://cloud.google.com/run/docs/logging#writing#writing_struct_logs
您可以使用Python创建一个dict并将其记录到堆叠式驱动器 - 它将与跟踪相关。它应该看起来像这样(来自教程):
# Build structured log messages as an object.
global_log_fields = {}
# Add log correlation to nest all log messages
# beneath request log in Log Viewer.
trace_header = request.headers.get('X-Cloud-Trace-Context')
if trace_header and PROJECT:
trace = trace_header.split('/')
global_log_fields['logging.googleapis.com/trace'] = (
f"projects/{PROJECT}/traces/{trace[0]}")
# Complete a structured log entry.
entry = dict(severity='NOTICE',
message='This is the default display field.',
# Log viewer accesses 'component' as jsonPayload.component'.
component='arbitrary-property',
**global_log_fields)
print(json.dumps(entry))
有关错误报告的更多信息:https://cloud.google.com/run/docs/error-reporting