influxdata/telegraf

[inputs.directory_monitor] Preserve original file timestamps (created/updated time) when moving files to "finished_directory"

Closed

#16,885 opened on Apr 27, 2025

View on GitHubContributor guide
 (3 comments) (1 reaction) (0 assignees)Go (5,836 forks)batch import
feature requesthelp wantedsize/s

Repository metrics

Stars
 (17,753 stars)
PR merge metrics
 (Avg merge 2d 12h) (136 merged PRs in 30d)

Description

Use Case

When using the [inputs.directory_monitor] plugin in Telegraf to process files from a directory, it's common to move processed files to a "finished" directory for archiving and tracking purposes. For compliance, auditing, or tracking reasons, it is often important to preserve the original file's created and updated timestamps instead of overwriting them with the current time during the move operation.

Expected behavior

When moving a processed file to the finished directory, the system should preserve the file's original created and updated timestamps. Alternatively, provide a configurable option (e.g., preserve_timestamps = true) for users who want to retain original file metadata during move operations.

Actual behavior

Currently, when a file is processed and moved to the finished directory, its created and updated timestamps are reset to the current time. This causes loss of the original file metadata, making it difficult to trace the actual file history.

Additional info

No response

Contributor guide

Research direction
Examine the move logic in plugins/inputs/directory monitor. After moving a file, use os.Chtimes to set the file's creation and modification timestamps to the original values. Consider adding a config field 'preserve timestamps' to toggle this behavior. Look at existing Telegraf plugins for similar timestamp preservation patterns.
Tech stack
go
Domain
backendtooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go programmingTelegraf plugin developmentFile system operations in Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75