You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add support for monitoring specific files and their metadata (e.g., size, last accessed time, modification time) in MetricsHub. The new feature should allow users to collect metrics about specific files.
Proposed Solution
Introduce a new "file" source in MetricsHub that:
Supports monitoring file metadata (e.g., size, last accessed time, modification time, creation time).
Allows filtering of files based on user-defined criteria (e.g., most recent file, file name pattern, etc.).
Optionally, provide support through extensions like SSH, WMI, and WinRM to enable cross-platform support (Linux, Windows, Darwin).
Metrics to be Reported
file.size: The size of the file in bytes. file.atime: Time since the file was last accessed, in seconds since Epoch. file.mtime: Time since the file was last modified, in seconds since Epoch. file.ctime: Time since the file's metadata (e.g., permissions) was last changed, in seconds since Epoch. file.count: The number of files that match the specified pattern or criteria. file.lines: Total number of lines in the file. This metric helps monitor file growth, particularly for logs. file.keywords: Customizable count of user-defined or connector-defined keywords (e.g., "ERROR", "WARNING", "SUCCESS", "TIMEOUT", "EXCEPTION"). This provides flexibility for the user to track specific log events or patterns. This is helpful for detecting failures in log files or system output files. file.io{direction="read|write"}: Total bytes read or written to the file. Resource attributes like file.name and file.path.
The text was updated successfully, but these errors were encountered:
Summary
Add support for monitoring specific files and their metadata (e.g., size, last accessed time, modification time) in MetricsHub. The new feature should allow users to collect metrics about specific files.
Proposed Solution
Introduce a new "file" source in MetricsHub that:
Metrics to be Reported
file.size
: The size of the file in bytes.file.atime
: Time since the file was last accessed, in seconds since Epoch.file.mtime
: Time since the file was last modified, in seconds since Epoch.file.ctime
: Time since the file's metadata (e.g., permissions) was last changed, in seconds since Epoch.file.count
: The number of files that match the specified pattern or criteria.file.lines
: Total number of lines in the file. This metric helps monitor file growth, particularly for logs.file.keywords
: Customizable count of user-defined or connector-defined keywords (e.g., "ERROR", "WARNING", "SUCCESS", "TIMEOUT", "EXCEPTION"). This provides flexibility for the user to track specific log events or patterns. This is helpful for detecting failures in log files or system output files.file.io{direction="read|write"}
: Total bytes read or written to the file.Resource attributes like
file.name
andfile.path
.The text was updated successfully, but these errors were encountered: