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
Copy file name to clipboardExpand all lines: content/_index.en.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -324,7 +324,7 @@ The default configuration can be found in `config/default.json`. The full refere
324
324
"from":"The address from which to send the email",
325
325
"sendWarnings":"Boolean. Set to true to also send email in case of warning",
326
326
},
327
-
"timestampPrefix":"Boolean. Set to true to prefix the timestamp of the error message with the current date (in ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)"
327
+
"timestampPrefix":"Boolean. Set to true to prefix the timestamp of the error message with the current date (in ISO 8601 format YYYY-MM-DDTHH:MM:SSZ); see below"
328
328
},
329
329
"reporter": { // Reporter mechanism to create GitHub issues when terms content is inaccessible
330
330
"githubIssues": {
@@ -352,6 +352,10 @@ The default configuration is merged with (and overridden by) environment-specifi
352
352
353
353
For development, in order to have a local configuration that overrides the existing config, it is recommended to create a `config/development.json` file.
354
354
355
+
#### Logging
356
+
357
+
Setting `logger.timestampPrefix` to `false` can be useful when logs are being collected by a process manager (like PM2) that already adds timestamps to log entries. This avoids duplicate timestamps in the logs.
358
+
355
359
#### Schedules
356
360
357
361
Schedules for tracking and dataset publication are defined using Cron expressions.
0 commit comments