Monika Configuration

Monika configuration file

*monika*.yaml*monika*.ymlmonika.json

Validate

Check your file against this schema

Opens the validator with this schema already loaded. Paste your *monika*.yaml and it validates in your browser — nothing is uploaded.

Validate a *monika*.yaml → View raw schema

Reference

Fields

Generated directly from the schema, following local $refs, to two levels of nesting.

Field	Type	Description
`probes`	`array<object>`	Probe is a description of the target, methods, timing and payloads to begin monitoring/probing a target.
`notifications`	`array`	Alerts of incidents and recoveries will be sent via these notification channels
`db_limit`	`object`	Database internal configuration
`db_limit.max_db_size`required	`number`	Maximum Monika database size default: `1000000000`
`db_limit.deleted_data`required	`integer`	Delete strategy when limit reached default: `1`
`db_limit.cron_schedule`required	`string`	Schedule to trim the db in crontab default: `"/1 * * *"`
`status-notification`	`string`	Sends status notification periodically according to a cron schedule. Set to false to disable. default: `"0 6 * * *"`
`certificate`	`object`	Check validity of your TLS certificate(s).
`certificate.domains`required	`array`	The list of domains to check
`certificate.reminder`	`integer`	The number of days to send notification to user before the domain expires
`version`	`string`	Monika configuration version default: `"1"`

Audit

What we found in this schema

Declared draft: draft-07
Validates cleanly against its own meta-schema.
Has 6 place(s) where keywords sit beside $ref. Under draft-07 those keywords are silently ignored by every conforming validator — first at #/properties/notifications/items/anyOf/1/properties/data/properties/url.
187 properties, 79% carrying a description, max nesting depth 12.

Standards

Specification sections for the keywords in this schema

Keyword	Document	Section
`$ref`	JSON Schema Core, draft 2020-12	§8.2.3.1 — Direct References with "$ref"
`additionalProperties`	JSON Schema Core, draft 2020-12	§10.3.2.3 — "additionalProperties"
`anyOf`	JSON Schema Core, draft 2020-12	§10.2.1.2 — "anyOf"
`const`	JSON Schema Validation, draft 2020-12	§6.1.3 — "const"
`default`	JSON Schema Validation, draft 2020-12	§9.2 — "default"
`description`	JSON Schema Validation, draft 2020-12	§9.1 — "title" and "description"
`examples`	JSON Schema Validation, draft 2020-12	§9.5 — "examples"
`items`	JSON Schema Core, draft 2020-12	§10.3.1.2 — "items"
`properties`	JSON Schema Core, draft 2020-12	§10.3.2.1 — "properties"
`required`	JSON Schema Validation, draft 2020-12	§6.5.3 — "required"
`type`	JSON Schema Validation, draft 2020-12	§6.1.1 — "type"

Documents

JSON Schema Core, draft 2020-12 — JSON Schema: A Media Type for Describing JSON Documents, A. Wright, H. Andrews, B. Hutton, G. Dennis, Eds., 2022. draft-bhutton-json-schema-01. An expired Internet-Draft with no formal standing in the IETF standards process; it is nonetheless the specification of record for JSON Schema 2020-12, published by json-schema.org.
JSON Schema Validation, draft 2020-12 — JSON Schema Validation: A Vocabulary for Structural Validation of JSON, A. Wright, H. Andrews, B. Hutton, Eds., 2022.
RFC 8259 (STD 90) — The JavaScript Object Notation (JSON) Data Interchange Format, T. Bray, Ed., 2017. The format a schema describes.
RFC 6901 — JavaScript Object Notation (JSON) Pointer. Defines the pointer syntax used by $ref fragments and the ~0 / ~1 escapes.

Source

Attribution

This schema comes from SchemaStore, distributed under the Apache License 2.0. Copyright 2015–present Mads Kristensen and contributors. View the original file. The field table and audit on this page are generated by JSONTools.tools; the schema itself is unmodified.

← All schemas