PHPackages dpc-sdp/tide\_logs - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. dpc-sdp/tide\_logs ActiveDrupal-module dpc-sdp/tide\_logs ================== Log forwarder for SumoLogic OTel collector. 2.0.1(1y ago)033.5k↓24.2%[1 PRs](https://github.com/dpc-sdp/tide_logs/pulls)1GPL-2.0-or-laterPHP Since Aug 15Pushed 3mo ago8 watchersCompare [ Source](https://github.com/dpc-sdp/tide_logs)[ Packagist](https://packagist.org/packages/dpc-sdp/tide_logs)[ RSS](/packages/dpc-sdp-tide-logs/feed)WikiDiscussions main Synced 1mo ago READMEChangelog (3)Dependencies (1)Versions (5)Used By (1) Tide Logs ========= [](#tide-logs) Provides a SumoLogic handler for Monolog. Requirements ------------ [](#requirements) - [Lagoon logs](https://drupal.org/project/lagoon_logs) There is also a soft dependency on the following modules - [admin audit trail](https://drupal.org/project/admin_audit_trail) - auditable events are sent to the Drupal logs Activation ---------- [](#activation) 1. The module requires a working [Sumo Logic OTEL Collector](https://github.com/SumoLogic/sumologic-otel-collector) to which it can send logs. 1. A helm chart has been created [here](https://github.com/dpc-sdp/sdp-helm-charts/tree/master/charts/sumologic-otel-collector) for easy installation on Kubernetes clusters. 2. To test locally, in a test project: 1. Create a file at `.docker/sumologic-otel/config.yaml` with the following content: ``` extensions: sumologic: # Get from https://service.au.sumologic.com/ui/#/security/installation-tokens install_token: # Highly recommend adding a unique suffix, otherwise you might run into conflicts with other collector instances. collector_name: SDP Syslog - OTEL - clobber: true receivers: udplog: listen_address: "0.0.0.0:514" attributes: source_name: "foobar/otel/test" operators: - type: json_parser - type: metadata id: metadata/source_host if: '"source_host" in $$body' attributes: source_host: 'EXPR($$body.source_host)' - type: metadata id: metadata/source_category if: '"source_category" in $$body' attributes: source_category: 'EXPR($$body.source_category)' processors: {} exporters: logging: loglevel: debug sumologic: auth: authenticator: sumologic source_category: "%{source_category}" source_name: "%{source_name}" source_host: "%{source_host}" metadata_attributes: - source.* service: extensions: [sumologic] pipelines: logs: receivers: [udplog] exporters: [sumologic] ``` 2. Add a service to `docker-compose.yml` as follows: ``` sumo-otel: image: "public.ecr.aws/sumologic/sumologic-otel-collector:${SUMO_OTEL_RELEASE_VERSION:-0.47.0-sumo-0}" volumes: - .docker/sumologic-otel:/etc/otel ports: - 514 networks: - amazeeio-network - default labels: lagoon.type: none ``` 3. Running `ahoy up` will register the instance with Sumo Logic; it's now ready to start collecting logs. Run `docker-compose logs -f sumo-otel` to make sure there were no errors. The last line should be something like ``` Everything is ready. Begin running and processing data. ``` 2. Enable the Tide Logs module. Go to `/admin/config/development/tide_logs` and ensure `UDPlog host` and `UDPlog port` correspond to the service's name and the port in the `config.yaml` respectively, if running with docker-compose. The module's default is `udp://logger.default.svc:5514` (see the default config [here](config/install/tide_logs.settings.yml)). 3. `SUMOLOGIC_CATEGORY` can also be set if a different category from the default (`sdp/dev/tide`) is required. 4. The following search query can then be used in SumoLogic to view the logs: ``` _collector="SDP Syslog - OTEL - " and _sourceCategory="sdp/dev/tide" ``` Debug ----- [](#debug) Some very basic debug messages can be printed locally (or remotely if you have drush access) by setting the following config variable: ``` drush config:set tide_logs.settings debug 1 ``` ### Health Score 41 — FairBetter than 89% of packages Maintenance62 Regular maintenance activity Popularity27 Limited adoption so far Community15 Small or concentrated contributor base Maturity50 Maturing project, gaining track record Bus Factor2 2 contributors hold 50%+ of commits How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~392 days Total 3 Last Release 588d ago Major Versions 1.0.0 → 2.0.02023-11-17 ### Community Maintainers ![](https://www.gravatar.com/avatar/db9df7f3a34b868452362f865fd9ef955870e8bd169d3c068d2fbe0f53ef2822?d=identicon)[dpc-admin](/maintainers/dpc-admin) --- Top Contributors [![yusufhm](https://avatars.githubusercontent.com/u/1160048?v=4)](https://github.com/yusufhm "yusufhm (4 commits)")[![GROwen](https://avatars.githubusercontent.com/u/3916040?v=4)](https://github.com/GROwen "GROwen (3 commits)")[![MdNadimHossain](https://avatars.githubusercontent.com/u/20810541?v=4)](https://github.com/MdNadimHossain "MdNadimHossain (2 commits)") --- Tags drupal-modulesdp-terraform-github ### Embed Badge ![Health badge](/badges/dpc-sdp-tide-logs/health.svg) ``` [![Health](https://phpackages.com/badges/dpc-sdp-tide-logs/health.svg)](https://phpackages.com/packages/dpc-sdp-tide-logs) ``` PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)