---
title: Send Logs from a Custom Log File with Heightened Read Permissions
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > Log Management > Logs Guides > Send Logs from a Custom Log File with
  Heightened Read Permissions
---

# Send Logs from a Custom Log File with Heightened Read Permissions

Often, log files, especially system logs such as *syslog* or *journald*, have heightened read-permissions blocking the Datadog Agent log collection as it does not have *sudo* or *admin* access.

There are three potential solutions to get around this:

- (Not Recommended) Give the Agent root access so it can tail those files. Datadog strongly recommends against going this route.
- Change the file permission to let the Agent access it. The Agent needs execute and read permissions on the directories and also read permission on the file. Run the following commands to provide those permissions (for any user, not just the Agent):
  - chmod 755 `<folder name>`
  - chmod 644 `<file name>`
- Configure an open source log shipper (such as Rsyslog, NXLog, …) that has root access to send those logs either directly to your Datadog platform or locally to a running Datadog Agent. For instructions, read the dedicated documentation for [Rsyslog](https://docs.datadoghq.com/integrations/rsyslog.md), [Syslog-ng](https://docs.datadoghq.com/integrations/syslog_ng.md), [NXlog](https://docs.datadoghq.com/integrations/nxlog.md), [FluentD](https://docs.datadoghq.com/integrations/fluentd.md#log-collection), or [Logstash](https://docs.datadoghq.com/integrations/logstash.md#log-collection).

- [Learn how to collect your logs](https://docs.datadoghq.com/logs/log_collection.md)
- [Learn how to explore your logs](https://docs.datadoghq.com/logs/explorer.md)
- [Glossary entry for "tail"](https://docs.datadoghq.com/glossary.md#tail)