One of the key attributes of DevOps and SRE engineers is their ability to meticulously observe and monitor all of their applications. A task which can be achieved more efficiently by centralizing all generated logs to a central endpoint. By centralizing logging, engineers can, at any time, have an accurate overview of all events which take place across their applications, from just one place. Storing logs in an external system also allows companies to ensure compliance with many certifications. Not to mention, centralizing can ensure logs are retained and cannot be altered by a third party.Documentation Index
Fetch the complete documentation index at: https://developer.upsun.com/llms.txt
Use this file to discover all available pages before exploring further.
Our integrations
While we have been streaming logs on Enterprise Dedicated Generation 2 clusters for years to rsyslog endpoints, we are now rolling out a more complete logs forwarding experience for all customers on Grid and Dedicated Generation 3 architectures. Every Enterprise and Elite plan with the Observability Suite will now be able to forward Platform.sh logs to 3rd party endpoints such as: Also, to other 3rd party service that supports syslog as a protocol such as: Regardless of the infrastructure, we rely on the journald component of systemd to collect logs from applications and services. Custom application logs can be streamed to the integration by either writing them to the stdout of an application or service managed by systemd. Or by writing them to /dev/log over the syslog protocol. The following services will also include their logs in the integration:- MariaDB general log + slow query log
- Elasticsearch
- Redis
- RabbitMQ
- Python
- Nodejs
- Php