Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update for LA log routing options for containers #170

Merged
merged 7 commits into from Feb 15, 2020

Conversation

megastef
Copy link
Contributor

@megastef megastef commented Feb 5, 2020

Documentation changes for Logagent PR sematext/logagent-js#179

Note, Logagent is backward compatible LOGSENE_TOKEN and LOGS_TOKEN are equivalent. In the documentation we should use LOGS_TOKEN for new users.

@otisg
Copy link
Member

otisg commented Feb 5, 2020

Is this ready for review @megastef ?

@otisg otisg requested a review from adnanrahic February 5, 2020 13:15
@@ -484,21 +484,31 @@ The component for detecting and parsing log messages — [logagent-js](http://se

### Log Routing

Routing logs from different containers to separate Sematext Cloud Logs Apps can be configured via docker labels (or environment variables e.g. on Kubernetes). Simply tag a container with the label (or environment variable) ```LOGS_TOKEN=YOUR_LOGS_TOKEN```.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

via docker labels => via Docker labels

The following container environment variables and labels are supported:
- `LOGS_TOKEN=<YOUR_LOGS_TOKEN>` - logs token for the container
- `LOGS_ENABLED=<true|false>` - switch log collection for the container on or off. Note, the default value is configurable in Logagent configuration via the setting LOGSENE_ENABLED_DEFAULT.
- `LOGS_RECEIVER_URL=<URL, URL, URL>` - set multiple log destinations. The URL should include the token or index of an Elasticsearch API endpoint. E.g. `https://logsene-receiver.sematext.com/your_logs_token`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to explain that you don't need LOGS_RECEIVER_URL for shipping to Sematext, only for custom ES endpoints?

@adnanrahic adnanrahic self-requested a review February 14, 2020 18:22
@adnanrahic adnanrahic merged commit 12ec693 into master Feb 15, 2020
@adnanrahic adnanrahic deleted the megastef-logagent-updates branch February 15, 2020 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants