Skip to content

M
message-call-service
Commit 8361d500 by Sxy
Options

feat: 日志配置

parent 3781bc86
Showing with 54 additions and 243 deletions
README.md
#### 实现功能 #### 实现功能
* 消息请求失败重试 * 消息请求失败重试
* 消息请求延时发送 * 消息请求延时发送
* 全链路日志
#### 启动 #### 启动
...@@ -89,3 +90,9 @@ method : post ...@@ -89,3 +90,9 @@ method : post
} }
``` ```
#### filebeat 读取 日志
```
./filebeat -e -c {自定义}/filebeat.yml
```
app.js
...@@ -11,7 +11,7 @@ import moment from "moment" ...@@ -11,7 +11,7 @@ import moment from "moment"
import rabbmitmqUtil from "./utils/rabbitmq" import rabbmitmqUtil from "./utils/rabbitmq"
rabbmitmqUtil.initQueue() rabbmitmqUtil.initQueue()
import correlation from './middleware/correlation' import correlation from './middleware/correlation'
import { createNamespace } from 'cls-hooked' import { createNamespace, getNamespace } from 'cls-hooked'
const logNameSpace = createNamespace('logger') const logNameSpace = createNamespace('logger')
...@@ -47,6 +47,8 @@ app.use(correlation(logNameSpace)); ...@@ -47,6 +47,8 @@ app.use(correlation(logNameSpace));
app.use(async (ctx, next) => { app.use(async (ctx, next) => {
const start = new Date() const start = new Date()
await next() await next()
const logNameSpace = getNamespace('logger');
ctx.response.body.requestId = logNameSpace.get("requestId")
logger.info({ logger.info({
request: ctx.request, request: ctx.request,
response: ctx.body, response: ctx.body,
......
fields.yml 0 → 100644
# WARNING! Do not edit this file directly, it was generated by the ECS project,
# based on ECS version 1.9.0.
# Please visit https://github.com/elastic/ecs to suggest changes to ECS fields.
- key: ecs
title: ECS
description: ECS Fields.
fields:
- name: timestamp
level: core
required: true
type: date
description: 'Date/time when the event originated.
This is the date/time extracted from the event, typically representing when
the event was generated by the source.
If the event source has no original timestamp, this value is typically populated
by the first time the event was received by the pipeline.
Required field for all events.'
example: '2016-05-23T08:05:34.853Z'
- name: level
level: core
type: keyword
- name: serverName
level: core
type: keyword
- name: requestId
level: core
type: keyword
- name: message
level: core
type: keyword
\ No newline at end of file
filebeat.yml
###################### Filebeat Configuration Example #########################
# This file is an example configuration file highlighting only the most common
# options. The filebeat.reference.yml file from the same directory contains all the
# supported options with more comments. You can use it as a reference.
#
# You can find the full configuration reference here:
# https://www.elastic.co/guide/en/beats/filebeat/index.html
# For more available modules and options, please see the filebeat.reference.yml sample
# configuration file.
# ============================== Filebeat inputs ===============================
filebeat.inputs: filebeat.inputs:
# Each - is an input. Most options can be set at the input level, so
# you can use different inputs for various configurations.
# Below are the input specific configurations.
- type: log - type: log
# Change to true to enable this input configuration. # Change to true to enable this input configuration.
...@@ -26,70 +8,7 @@ filebeat.inputs: ...@@ -26,70 +8,7 @@ filebeat.inputs:
# Paths that should be crawled and fetched. Glob based paths. # Paths that should be crawled and fetched. Glob based paths.
paths: paths:
- /Users/shaoxingye/Documents/WORK/ownerproject/message-call-service/logs/*.log - /Users/shaoxingye/Documents/WORK/ownerproject/message-call-service/logs/*.log
#- c:\programdata\elasticsearch\logs\*
# Exclude lines. A list of regular expressions to match. It drops the lines that are
# matching any regular expression from the list.
#exclude_lines: ['^DBG']
# Include lines. A list of regular expressions to match. It exports the lines that are
# matching any regular expression from the list.
#include_lines: ['^ERR', '^WARN']
# Exclude files. A list of regular expressions to match. Filebeat drops the files that
# are matching any regular expression from the list. By default, no files are dropped.
#exclude_files: ['.gz$']
# Optional additional fields. These fields can be freely picked
# to add additional information to the crawled log files for filtering
#fields:
# level: debug
# review: 1
### Multiline options
# Multiline can be used for log messages spanning multiple lines. This is common
# for Java Stack Traces or C-Line Continuation
# The regexp Pattern that has to be matched. The example pattern matches all lines starting with [
#multiline.pattern: ^\[
# Defines if the pattern set under pattern should be negated or not. Default is false.
#multiline.negate: false
# Match can be set to "after" or "before". It is used to define if lines should be append to a pattern
# that was (not) matched before or after or as long as a pattern is not matched based on negate.
# Note: After is the equivalent to previous and before is the equivalent to to next in Logstash
#multiline.match: after
# filestream is an experimental input. It is going to replace log input in the future.
# - type: filestream
# Change to true to enable this input configuration.
# enabled: false
# Paths that should be crawled and fetched. Glob based paths.
# paths:
# - /var/log/*.log
#- c:\programdata\elasticsearch\logs\*
# Exclude lines. A list of regular expressions to match. It drops the lines that are
# matching any regular expression from the list.
#exclude_lines: ['^DBG']
# Include lines. A list of regular expressions to match. It exports the lines that are
# matching any regular expression from the list.
#include_lines: ['^ERR', '^WARN']
# Exclude files. A list of regular expressions to match. Filebeat drops the files that
# are matching any regular expression from the list. By default, no files are dropped.
#prospector.scanner.exclude_files: ['.gz$']
# Optional additional fields. These fields can be freely picked
# to add additional information to the crawled log files for filtering
#fields:
# level: debug
# review: 1
# ============================== Filebeat modules ============================== # ============================== Filebeat modules ==============================
...@@ -100,177 +19,35 @@ filebeat.config.modules: ...@@ -100,177 +19,35 @@ filebeat.config.modules:
# Set to true to enable config reloading # Set to true to enable config reloading
reload.enabled: false reload.enabled: false
# Period on which files under path should be checked for changes
#reload.period: 10s
# ======================= Elasticsearch template setting =======================
setup.template.settings:
index.number_of_shards: 0
#index.codec: best_compression
#_source.enabled: false
# ================================== General ===================================
# The name of the shipper that publishes the network data. It can be used to group
# all the transactions sent by a single shipper in the web interface.
#name:
# The tags of the shipper are included in their own field with each
# transaction published.
#tags: ["service-X", "web-tier"]
# Optional fields that you can specify to add additional information to the #==================== Elasticsearch template setting ==========================
# output. setup.ilm.enabled: false
#fields: setup.template.name: "logs"
# env: staging setup.template.fields: "/Users/shaoxingye/Documents/WORK/ownerproject/message-call-service/fields.yml"
setup.template.overwrite: true
setup.template.enabled: false
# ================================= Dashboards =================================
# These settings control loading the sample dashboards to the Kibana index. Loading
# the dashboards is disabled by default and can be enabled either by setting the
# options here or by using the `setup` command.
#setup.dashboards.enabled: false
# The URL from where to download the dashboards archive. By default this URL
# has a value which is computed based on the Beat name and version. For released
# versions, this URL points to the dashboard archive on the artifacts.elastic.co
# website.
#setup.dashboards.url:
# =================================== Kibana ===================================
# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
# setup.kibana:
# Kibana Host
# Scheme and port can be left out and will be set to the default (http and 5601)
# In case you specify and additional path, the scheme is required: http://localhost:5601/path
# IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
#host: "localhost:5601"
# Kibana Space ID
# ID of the Kibana Space into which the dashboards should be loaded. By default,
# the Default Space will be used.
#space.id:
# =============================== Elastic Cloud ================================
# These settings simplify using Filebeat with the Elastic Cloud (https://cloud.elastic.co/).
# The cloud.id setting overwrites the `output.elasticsearch.hosts` and
# `setup.kibana.host` options.
# You can find the `cloud.id` in the Elastic Cloud web UI.
#cloud.id:
# The cloud.auth setting overwrites the `output.elasticsearch.username` and
# `output.elasticsearch.password` settings. The format is `<user>:<pass>`.
#cloud.auth:
# ================================== Outputs ===================================
# Configure what output to use when sending the data collected by the beat.
# ---------------------------- Elasticsearch Output ---------------------------- # ---------------------------- Elasticsearch Output ----------------------------
output.elasticsearch: output.elasticsearch:
# Array of hosts to connect to. # Array of hosts to connect to.
hosts: ["192.168.18.102:9200"] hosts: ["192.168.18.102:9200"]
index: "logs-message-call-service-%{+yyyy.MM.dd}"
# Protocol - either `http` (default) or `https`. setup.kibana:
#protocol: "https" host: "192.168.18.102:5601"
# Authentication credentials - either API key or username/password.
#api_key: "id:api_key"
# username: "elastic"
# password: "3NdwvM7sxl0gKYOrzg16"
# ------------------------------ Logstash Output -------------------------------
#output.logstash:
# The Logstash hosts
#hosts: ["localhost:5044"]
# Optional SSL. By default is off.
# List of root certificates for HTTPS server verifications
#ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
# Certificate for SSL client authentication
#ssl.certificate: "/etc/pki/client/cert.pem"
# Client Certificate Key
#ssl.key: "/etc/pki/client/cert.key"
# ================================= Processors ================================= # ================================= Processors =================================
processors: processors:
# - add_host_metadata:
# when.not.contains.tags: forwarded
# - add_cloud_metadata: ~
# - add_docker_metadata: ~
# - add_kubernetes_metadata: ~
- decode_json_fields: - decode_json_fields:
fields: ['message'] #要进行解析的字段 fields: ['message'] #要进行解析的字段
target: "" #json内容解析到指定的字段，如果为空（“”），则解析到顶级结构下 target: "" #json内容解析到指定的字段，如果为空（“”），则解析到顶级结构下
overwrite_keys: false #如果解析出的json结构中某个字段在原始的event（在filebeat中传输的一条数据为一个event）中也存在，是否覆盖event中该字段的值，默认值:false overwrite_keys: false #如果解析出的json结构中某个字段在原始的event（在filebeat中传输的一条数据为一个event）中也存在，是否覆盖event中该字段的值，默认值:false
process_array: false #数组是否解码，默认值:false process_array: false #数组是否解码，默认值:false
max_depth: 1 #解码深度，默认值：1 max_depth: 1 #解码深度，默认值：1
# ================================== Logging ===================================
# Sets log level. The default log level is info.
# Available log levels are: error, warning, info, debug
#logging.level: debug
# At debug level, you can selectively enable logging only for some components.
# To enable all selectors use ["*"]. Examples of other selectors are "beat",
# "publisher", "service".
#logging.selectors: ["*"]
# ============================= X-Pack Monitoring ==============================
# Filebeat can export internal metrics to a central Elasticsearch monitoring
# cluster. This requires xpack monitoring to be enabled in Elasticsearch. The
# reporting is disabled by default.
# Set to true to enable the monitoring reporter.
#monitoring.enabled: false
# Sets the UUID of the Elasticsearch cluster under which monitoring data for this
# Filebeat instance will appear in the Stack Monitoring UI. If output.elasticsearch
# is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.
#monitoring.cluster_uuid:
# Uncomment to send the metrics to Elasticsearch. Most settings from the
# Elasticsearch output are accepted here as well.
# Note that the settings should point to your Elasticsearch *monitoring* cluster.
# Any setting that is not set is automatically inherited from the Elasticsearch
# output configuration, so if you have the Elasticsearch output configured such
# that it is pointing to your Elasticsearch monitoring cluster, you can simply
# uncomment the following line.
#monitoring.elasticsearch:
# ============================== Instrumentation ===============================
# Instrumentation support for the filebeat.
#instrumentation:
# Set to true to enable instrumentation of filebeat.
#enabled: false
# Environment in which filebeat is running on (eg: staging, production, etc.)
#environment: ""
# APM Server hosts to report instrumentation results to.
#hosts:
# - http://localhost:8200
# API Key for the APM Server(s).
# If api_key is set then secret_token will be ignored.
#api_key:
# Secret token for the APM Server(s).
#secret_token:
# ================================= Migration ==================================
# This allows to enable 6.7 migration aliases
#migration.6_to_7.enabled: true
utils/system.js
import { getNamespace } from 'cls-hooked';
export const ok = (data) => { export const ok = (data) => {
const logNameSpace = getNamespace('logger');
return { return {
code: 0, code: 0,
success: true, success: true,
message: null, message: null,
data, data,
requestId: logNameSpace.get("requestId"),
} }
} }
export const error = (msg = "未知错误", code = -1) => { export const error = (msg = "未知错误", code = -1) => {
const logNameSpace = getNamespace('logger');
return { return {
code, code,
success: false, success: false,
message: msg, message: msg,
data: null, data: null,
requestId: logNameSpace.get("requestId"),
} }
} }
\ No newline at end of file
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment