Adding a Destination

Let's get started with Trink!

Trink’s fully managed platform centralizes all operational data collection needs in one place and ties multiple sources to multiple destinations while offering a unique dashboard that presents all routes and traffic, enabling you to observe, decide and act in real-time based on the complete picture.

Trink's Environment

Trink replaces the standard shippers with a mount point and reroutes /var/log from the client production environment so we can read them passively. Then, Trink processes, parses, filters, compresses, rotates, and enriches them without any implementation of your resources.

Trink's Discovery Map

Trink's dashboard gives full visibility and control over your log streams, allowing a plug-and-play simplicity between all sources and all destinations. You can also decide on the right route for your data pipeline without being bound to inherited commitments and past decisions.

The following documentation consists mainly of these steps -

Step 1: Onboarding

The very initial step when starting to use Trink, and consists of 3 basic steps:

  1. Choose a cloud provider and desired source
  2. Provide required details
  3. Copy and execute deployment command

You'll find a specific detailed article for each of the sources we support, including:

  • EC2
  • Kubernetes
  • Cloudwatch

Step 2: Adding Destinations

After the onboarding, you'll be directed to either your health view or your discovery map. At this point, you can add a destination of your choice to the entire pipeline and your logs will be sent there. \ You can find dedicated articles on how to add a destination on each one of the destinations we support:

  • Datadog
  • Coralogix
  • S3

If you find this article (or any other article on our documentation) incorrect, outdated or omits critical information, please let us know.

Get In Touch

Contact us for more information