File: message-timegenerated.rst

package info (click to toggle)
rsyslog 8.2512.0-3
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 30,464 kB
  • sloc: ansic: 123,809; sh: 42,109; makefile: 5,962; javascript: 1,842; python: 1,222; lex: 607; yacc: 193; perl: 162; sql: 103; tcl: 9; ruby: 2
file content (50 lines) | stat: -rw-r--r-- 1,382 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
.. _prop-message-timegenerated:
.. _properties.message.timegenerated:

timegenerated
=============

.. index::
   single: properties; timegenerated
   single: timegenerated

.. summary-start

Records when rsyslog received the message with high resolution.

.. summary-end

This property belongs to the **Message Properties** group.

:Name: timegenerated
:Category: Message Properties
:Type: timestamp

Description
-----------
Timestamp captured when the operating system hands the message to rsyslog's
reception buffer. The value reflects the precise moment rsyslog accepted the
event, before any queueing or ruleset processing begins.

If several messages are delivered in the same receive buffer (for example when
TCP transports multiple entries together), they all carry the same
``timegenerated`` stamp because rsyslog accepted them at the same instant.

The timestamp remains stable even if the message spends time in an in-memory or
disk queue. As a result, ``timegenerated`` is usually newer than
``timereported`` (which comes from the sender) but still older than ``$now``,
which is evaluated later during processing.

Usage
-----
.. _properties.message.timegenerated-usage:

.. code-block:: rsyslog

   template(name="example" type="list") {
       property(name="timegenerated")
   }

See also
--------
See :doc:`../../configuration/properties` for the category overview.