A File node is most often used to track a configuration file. The files that are tracked for each OS are specified by patterns. File nodes are under the full control of patterns.
File node lifecycle
The following section describes the scenarios in which a File node is created, updated or removed.
This is under the full control of patterns and as a result there is no default File node behavior.
The generated key for a File node is entirely dependent on the pattern that creates the File node.
A File node can be destroyed in one of following ways:
- Explicitly by the pattern that created it. See Removal in the Pattern Language guide
- If the File node is triggered from another Inferred node, then when this inferred node is destroyed, so will the File node. This is a Cascade Removal type, see Cascade Removal.
- Manually, by selecting the necessary File node, and picking Destroy from the Actions list.
File node attributes
The attributes and relationships on a File node are described in the tables below.
The absolute path to the tracked configuration file.
The size (in bytes) of the tracked configuration file.
The md5 checksum of the file.
The time and date of the last modification to tracked configuration file. This date and time is taken from the file's timestamp on the host machine.
The raw contents of the tracked configuration file. This attribute is populated by a cat command on UNIX or a type command in Windows. Binary files can be modelled, but the contents will not included.
File node relationships
The relationships on a File node are described in the table below.
Hosts on which this File node is tracked.
Software Instances which use this File node.
Depended Upon By
Details depending on this file.
Pattern maintaining this file.