https://github.com/logicmonitor/lm-logs-fluentd-gcp-filter
Fluentd plugin providing resource mapping for GCP to forward logs to LM
https://github.com/logicmonitor/lm-logs-fluentd-gcp-filter
Last synced: 5 months ago
JSON representation
Fluentd plugin providing resource mapping for GCP to forward logs to LM
- Host: GitHub
- URL: https://github.com/logicmonitor/lm-logs-fluentd-gcp-filter
- Owner: logicmonitor
- License: apache-2.0
- Created: 2021-04-28T08:06:20.000Z (about 5 years ago)
- Default Branch: master
- Last Pushed: 2024-11-14T15:38:05.000Z (over 1 year ago)
- Last Synced: 2025-12-11T01:16:59.904Z (6 months ago)
- Language: Ruby
- Homepage:
- Size: 48.8 KB
- Stars: 0
- Watchers: 4
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this 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` |