LogEventsPerDayThresholds - System Parameter

^{New 7.12}

LogEventsPerDayThresholds is a JSON System Parameter that sets when the Log Events per day chart on the Nodinite Dashboard warns that too many Log Events were logged in a single day. The Web Client reads it and shows the warning to every user; only an Administrator can clear it.

At a Glance

How It Works

The Log Events per day chart on the Dashboard compares the number of Log Events logged each day over the last four weeks with the two levels in this parameter:

Each day's count of Log Events is compared with WarningThreshold and ErrorThreshold; green is no warning, yellow the warning level, red the error level. An Administrator clears the warning from the Dashboard, which sets ClearDateTime.

When a day exceeds a level, the chart draws the warning and error levels as dashed lines, colours the bars, and shows a banner with the worst day, for example 538 Log Events on Fri 2026-10-09, above the error level of 500.

The banner and the dashed Warning level and Error level lines on the Dashboard. Administrators also see the Clear and Edit System Parameter buttons. This test environment uses levels of 300 and 500; real environments use far higher values.

Who Sees What

Users who are not Administrators can't remove the warning. They contact a Nodinite Administrator, who investigates the cause and then clears it.

• Clear sets ClearDateTime to the current time in UTC. Days that started before that time no longer warn, so the bars and banner for them disappear. A later day that exceeds a level warns again.
• Edit System Parameter opens this parameter in Administration › Settings › System Parameters, so you can change the levels or turn the warning off.

Warning

A breach is often a sign that logging has gone rogue. Investigate before you click Clear. In a recent support case, the integrations logged about 150 million Log Events per day, roughly 1,700 every second, around the clock. The customer and the developers blamed Nodinite for the resulting performance problem, but the cause was the volume being logged. See Investigate a Breach.

Value Format

Set WarningThreshold lower than ErrorThreshold, so the warning level comes first.

The default value, pretty-printed:

{
  "Enabled": true,
  "WarningThreshold": 5000000,
  "ErrorThreshold": 10000000,
  "ClearDateTime": null
}

Example that warns only at the error level, with a warning cleared on 1 November 2026:

{
  "Enabled": true,
  "WarningThreshold": null,
  "ErrorThreshold": 20000000,
  "ClearDateTime": "2026-11-01T08:30:00Z"
}

The edit dialog shows Json model is valid while you type a valid value; see Manage System Parameters for how the validation works.

Choosing a Value

The defaults suit many environments, but normal logging volume varies a lot between installations. Set the levels from your own baseline:

1. Look at the Log Events per day chart on the Dashboard over the last four weeks and note the busiest normal day.
2. Set WarningThreshold to about 1.5–2 times that day, so a normal peak never warns.
3. Set ErrorThreshold to a volume that would need action today, for example 3 times the busiest normal day.
4. Revisit the levels when you onboard large new integrations, so planned growth doesn't warn.

Don't raise the levels just to make a warning go away. Every logged Log Event costs processing in the Logging Service, storage in the Log Databases, and time in every search in Log Views.

Investigate a Breach

When a day breaches a level, treat it as possible rogue logging and find out what changed before you clear the warning:

• Find the source. In a Log View, search the day that breached and group or filter by Log Agent and Message Type to see which integration logs the most.
• Look for common causes. Debug or verbose logging left on in production, logging inside retry or polling loops, logging every intermediate step of a high-volume flow, or a new integration put in production without a volume review.
• Fix it at the source. Change the logging in the integration, or in the Log Agent configuration, so it logs what you need for tracking and troubleshooting, not everything.
• Check the side effects. Large volumes grow the Log Databases fast (see SizeToSplitDatabaseOn) and can build a processing backlog in the Logging Service (see Logging Service performance).
• Then clear. When the volume is back to normal, click Clear on the Dashboard.

Frequently Asked Questions

Why does the warning still show after I raised the thresholds?

Only days above the new levels warn. If a day still exceeds the new ErrorThreshold or WarningThreshold, it keeps warning until an Administrator clicks Clear or the day leaves the four-week chart.

Can I turn the warning off?

Yes. Set Enabled to false. We recommend keeping it on: it is often the first visible sign that logging has gone rogue.

Why can't I see the Clear button?

Only members of the built-in Administrator Role see Clear and Edit System Parameter. Contact a Nodinite Administrator.

Next Steps

• Dashboard - Log Events per day
• Manage System Parameters

Related Topics

• System Parameters
• DashboardPluginSettings
• SizeToSplitDatabaseOn
• Logging Service
• Log Databases
• Web Client