The project is in a healthy, maintained state
This filter plugin filters fluentd records in gcp to the configured LogicMonitor account.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

>= 1.0.0

Runtime

>= 1, < 2
 Project Readme

lm-filter-gcp-fluentd

This filter plugin is provided for mapping the logs coming from GCP pubsub to '_lm.resourceId' which is used for sending GCP logs to LM https://www.logicmonitor.com/support/lm-logs/setting-up-gcp-logs-ingestion. The plugin maps the following services to '_lm.resourceId' in LM :

  • Google Compute Engine
  • Google Cloud Functions
  • Google Cloud SQL
  • Google Audit Logs
  • Google Cloud Composer
  • Google Cloud Run

LogicMonitor properties

Property Description
metadata_keys Array of keys to be added as metadata. Filter will look for these keys in fluentd record and extract those if exist. in case of nested json, whole sub json would be added. default ["severity", "logName", "labels", "resource.type", "resource.labels", "httpRequest"] . few keys will be renamed as part of metadata standardization in Logicmonitor : {"trace" => "trace_id", "spanId" => "span_id","resource.type" => "_type"}
use_default_severity When true, and log record does not have severity, log_level=DEFAULT would be added to log. default false.
lm_tenant_id tenant id to be added as event metadata. This will be added directly into metadata as _lm.tenantId