Applications and infrastructure logs can be displayed in Cycloid, offering a handy and centralized way to know what is going on in your application after it has been deployed.

Cycloid logs allow you to display logs of all your servers for all your environments in user-defined groups. Filter and search can be applied on logs entries to find a specific pattern or server.

Logs

If you have multiple environments, all environments will be displayed on the left-hand side of the page, and each of them will contain all log groups found.

Cycloid Logs is compatible with two backends:

To use it simply configure it for your project in Cycloid console as described in the dedicated configuration section below.

note

You will also need to make sure your logs are sent into one of the Cycloid compatible backends. This can be done directly from your application or by using, for example, our [Cycloid Ansible Fluentd role] to send your logs directly to ElasticSearch.

# Configure for ElasticSearch

Under your project, click on the Configuration tab, then follow instructions in the Logs Configuration section:

  • Select ElasticSearch

Logs es

  • Then configure the access and mapping for each ElasticSearch environment source that must be used to search for logs entries

Logs es config

# Configure for AWS Cloudwatch logs

Under your project, click on the Configuration tab, then follow instructions in the Logs Configuration section:

Logs es

Logs are directly fetched from AWS CloudWatch, a filter is applied on Log Groups to display only the relevant ones based on the project and environment names of your stack. The Cycloid console will search them using the following format:

  • $PROJECT_$ENV

Any other Log Groups that are not matching the format will not be fetched.

By default no Log groups nor Log Streams are created for you; this is up to you to create and feed them with the logs from your systems, jobs, applications, etc. You can use services like Fluentd or Logstash to help you with the formatting of logs intended to be sent in AWS Cloudwatch.