Files.com, the File Orchestration Platform, keeps a record of everything that happens to your files: every upload, download, failed transfer, automation run, and user action. This integration sends that record straight into New Relic as it happens, so file events live on the same dashboards your team already uses to watch system health.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
Your team already streams app and server data into New Relic. File activity is usually the piece that sits off on its own. An SFTP job fails mid-batch overnight. A partner uploads critical data that kicks off other work. A transfer arrives corrupt. Files.com becomes a New Relic log source and sends its own activity in.
Files.com sends uploads, downloads, failed transfers, automation runs, and user actions into New Relic the moment they happen. You watch and alert on file activity right beside the rest of your stack, instead of leaving it off on its own.
Files.com sends events directly into New Relic through its Log API, secured with a license key. There's no New Relic agent to install and no forwarder to run in between.
Everything streams by default. If you only want some of it, pick what each New Relic instance gets, so each team sees only the activity it watches.
The events come from the Files.com audit log, which can't be edited and is kept for 7+ years. New Relic does the charts and alerts; Files.com holds the original, trustworthy record.
Files.com processes billions of transactions a week, so a busy, multi-user file environment is normal load, not an edge case. New Relic takes in and tags the events like any other feed.
New Relic reads the events. It doesn't decide who can touch which files or keep the record of what they did. Files.com does that part: access folder by folder, every action written to a record that can't be changed, and the same company logins your team already uses.
Hand each team, project, or person the exact folders they need. The person you see on a New Relic dashboard is the same account Files.com controls access for.
Every login, upload, download, and permission change is written to the Files.com audit log, and nothing in it can be altered after the fact. That record is what makes the events in New Relic count as audit evidence.
People sign in with your company login through SSO and SAML, and SCIM keeps accounts in sync with your directory. When someone leaves, you cut their file access in one place.
The stream to New Relic is encrypted and runs with a license key. Files.com also logs the act of sending, so if a delivery fails you can see it and look into it.
Files.com sends each event into New Relic the moment it happens, ready for dashboards and alerts. This is an Enterprise-plan feature; it isn't on Starter or Power.
Files.com can also write log files to a folder on a schedule you set, from every 5 minutes up to every 6 hours. Run it alongside the live stream for batch ingest, a long-term archive, or a locked-down network.
A post-production team moves big video files between editors, partners, and render services, and each transfer kicks off the next step. Files.com sends every transfer into New Relic, where ops watch timing, throughput, and errors next to app metrics. They catch delays before those delays hit a release date.
When a file is late, arrives corrupt, or comes from somewhere it shouldn't, the event is already on its way to New Relic. Your team gets the alert before the problem derails the work.
When a nightly SFTP batch fails, your team jumps from the failed transfer in New Relic straight into the surrounding app and server logs. It’s the same screen, so you find the cause in minutes instead of hunting across systems.
After a security question, your team searches New Relic for every file an account touched: uploads, downloads, permission changes. Each event traces back to the tamper-proof Files.com record, so the answer holds up as evidence.
Every event New Relic receives comes from the Files.com audit log: the record of who did what, to which file, and when.
Learn MoreEvery automation run on Files.com is an event you can watch in New Relic. A job that breaks shows up on your dashboard instead of failing quietly.
Learn More
Send file events to Amazon SNS to kick off downstream systems while New Relic watches the same activity.
Learn MoreFiles.com bridged on-premise systems and cloud storage so sensitive vendor workflows could move forward one flow at a time.
“Files.com's strengths are simplicity, ease of use, and the cloud connectors. We don't have to invent custom infrastructure for every partner.”
“Files.com is versatile — it can manage many different situations from a single platform. We've consolidated multiple tools onto it.”
“Files.com is robust and scales to a large enterprise. We get multiple files per minute, per second — and we're a 24/7 organization, so everything has to always be up.”
How Files.com streams into New Relic, which plan you need, and what happens to your events when a delivery fails.
Files.com sends events straight into New Relic through its Log API, secured with a license key. Events arrive in JSON to New Relic's log management, and there is no forwarder to set up in between.
Files.com streams file uploads and downloads, failed transfers, automation runs, user actions, and API calls. They land next to your app and server data. Everything streams by default, and you choose which log types each New Relic instance gets.
No. Files.com streams to New Relic on the Enterprise plan only, not on Starter or Power. Starter also keeps only one week of logs.
No. Files.com records every event in a tamper-proof audit log and streams those events into New Relic as they happen. New Relic runs the dashboards, alerts, anomaly detection, and storage. Files.com delivers the events; New Relic does the monitoring work.
Files.com keeps its tamper-proof audit log for 7+ years, independent of how long the same events live in New Relic. New Relic governs its own retention by data tier; the Files.com record stays the long-term system of record for who did what to which file.
Yes. Alongside the live New Relic Log API stream, Files.com can write the same activity log as JSON or CSV files to a folder on a schedule, either to its own storage or, through the Files.com Agent, to a server you control. Teams use the live stream for monitoring and the file delivery for a long-term archive.
Files.com retries a failed New Relic delivery automatically, every 60 seconds for the first five minutes and then every 15 minutes. Nothing is lost while the endpoint is down: every event stays in the tamper-proof Files.com audit log, and Event Channels can alert your team the moment a delivery fails.
Files.com log streaming batches and forwards complete audit log categories to New Relic roughly every 60 seconds. Event Channels deliver individual operational events, such as SSO failures, user lockouts, and automation failures, to a webhook, Slack, Teams, SNS, or Pub/Sub target the moment they occur.
Yes. Files.com streams to multiple destinations at once, each with its own selection of log types. Observability data can flow to New Relic while the same events feed the security team's SIEM, with each stream trimmed independently.
Start a 7-day free trial. Drop in your New Relic license key, send a test event, and watch file activity land on your dashboards.
No credit card required • 7-day free trial • Live in minutes