Example 1
- 14 logged
- 18 required
Logging coverage: 77.8%
With 14 logged, 18 required the result is Logging coverage: 77.8%. This is not a SIEM.
Log coverage
The calculator uses the numbers you enter. With 14 logged, 18 required the result is Logging coverage: 77.8%. This is not a SIEM.
This is not a SIEM. API exposure is on API exposure.
Results
Enter data and click Calculate.
How it works
Log coverage in this calculator is logged event types as a share of required types. With 14 logged, 18 required the result is Logging coverage: 77.8%.
coverage = min(100, 100 × min(done, req) / req). The formula uses events and record.
Logging coverage: 77.8% is not a SIEM. Another set of numbers gives Logging coverage: 100%, and a further set gives Logging coverage: 40%. Empty optional fields do not change the result.
API exposure answers a different question. Fairness gap does too. Here 14 logged, 18 required leave Logging coverage: 77.8%.
Type 14 logged, 18 required and click Calculate. Two more ready sets sit under the form: Logging coverage: 100% and Logging coverage: 40%.
Other numbers on the same labels move the result. The first example gives Logging coverage: 77.8%.
Formula
coverage = min(100, 100 × min(done, req) / req).
How to use
- Type 14 logged, 18 required.
- Leave optional fields empty if you do not want them in the result.
- Click Calculate. This set shows Logging coverage: 77.8%.
- The second example under the result is Logging coverage: 100%, the third Logging coverage: 40%.
- This is not a SIEM.
Log coverage = Logging coverage: 77.8%
With 14 logged, 18 required the result is Logging coverage: 77.8%. This is not a SIEM.
- Log coverage
- Log coverage is this calculator's result. The first example is Logging coverage: 77.8%.
- events
- The formula includes events. The second example gives Logging coverage: 100%.
- record
- The formula includes record. The second example gives Logging coverage: 100%.
Examples
Example 2
- 18 logged
- 18 required
Logging coverage: 100%
With 18 logged, 18 required the result is Logging coverage: 100%.
Example 3
- 8 logged
- 20 required
Logging coverage: 40%
With 8 logged, 20 required the result is Logging coverage: 40%.
Related calculators
Common questions
What do you get from 14 logged, 18 required?
Logging coverage: 77.8%. This is not a SIEM.
What about the second example?
Logging coverage: 100%.
What about the third example?
Logging coverage: 40%.
Is Logging coverage: 77.8% a SIEM?
No. It is the result from the numbers you enter.
Do empty fields change Logging coverage: 77.8%?
No. Empty optional fields do not change the result.
How is this different from API exposure?
That calculator answers another question. Here Log coverage stays at Logging coverage: 77.8%.
Does a comma in the number work?
Yes. A comma and a dot mean the same in a number field.
Is the result a diagnosis or official opinion?
No. The result comes from the numbers you enter. a SIEM sits outside this calculator.
Do 18 logged, 18 required give Logging coverage: 100%?
Yes. That is the second example under the form.
How is log coverage calculated?
The calculator divides the smaller of logged and required by required, multiplies by 100, and does not go above 100. In the first example the result is Logging coverage: 77.8%.
What if logged exceeds required?
Coverage stays at 100. Extra event types do not raise the result above one hundred percent.
Is this a SIEM?
No. The result is a ratio of two numbers you enter. The calculator does not read logs and is not a SIEM.
Does 100% coverage mean the record is compliant?
No. One hundred percent only means logged is not below required. The calculator does not inspect log content.
Knowledge sources
The terms come from EU acts. The calculator result is a sketch index, not a regulator decision.
Page updated in 2026.