All Classes and Interfaces

Class	Description
AlertEngine	Framework-pure alert engine: the extracted heart of the original Logback NtfyAlertAppender, decoupled from any logging framework.
AlertEvent	Framework-neutral snapshot of a single log event, handed to AlertEngine.submit(io.github.pimak.ntfy.core.AlertEvent).
AlertEvent.Cause	One link of an exception chain: the throwable's class name and its message (either may be null in degenerate cases, mirroring the source throwable).
AlertLevel	The severity of an AlertEvent, as far as the alerting engine is concerned — the value AlertEngine routes on.
AuthMode	Auth strategy for an outbound ntfy publish request, modeled as a sealed hierarchy so each mode carries only the fields it needs and knows how to build its own Authorization header.
AuthMode.BasicAuth	Sends Authorization: Basic <base64(username:password)>.
AuthMode.BearerToken	Sends Authorization: Bearer <token>.
AuthMode.None	Sends no Authorization header at all — a valid anonymous publish.
ConfigLoader	Resolves an NtfyConfig from the ambient environment.
Diagnostics	Self-diagnostic sink for AlertEngine.
DurationParser	Parses the several duration spellings the ntfy configuration surface accepts into a Duration.
LogbackAlertAppender	A thin Logback UnsynchronizedAppenderBase<ILoggingEvent> shell over the framework-neutral AlertEngine.
MdcProjector	Projects a logging framework's diagnostic context (MDC) onto the small, bounded, sanitized map of key -> value pairs an alert body may carry — the include-mdc-keys feature.
NtfyAction	A single ntfy notification action button, modeled as a sealed hierarchy so each action type carries only the fields it needs (mirroring the AuthMode pattern).
NtfyAction.Broadcast	Sends an Android broadcast intent when tapped (only actioned by ntfy's Android app).
NtfyAction.BroadcastExtra	A single intent extra (name/value) carried by a NtfyAction.Broadcast action.
NtfyAction.Http	Sends an HTTP request to url when tapped.
NtfyAction.HttpHeader	A single request header (name/value) carried by an NtfyAction.Http action.
NtfyAction.View	Opens url in the browser/app when the action button is tapped.
NtfyAutoConfiguration	Auto-configuration that turns ntfy.* properties into a live ntfy integration for a Spring Boot application.
NtfyClient	Generic, standalone ntfy notification client — the "send an arbitrary notification" surface, independent of AlertEngine's log-alert lifecycle.
NtfyClientFactory	Exposes the injectable NtfyClient bean, built from the bound NtfyConfiguration.
NtfyClientProducer	Exposes a generic, application-scoped NtfyClient for CDI injection, so Quarkus apps can @Inject NtfyClient to send arbitrary notifications independent of the log-alert path.
NtfyConfig	Immutable, framework-neutral configuration for the ntfy engine and client.
NtfyConfig.Builder	Fluent builder for NtfyConfig; every setter returns this.
NtfyConfiguration	Binds all ntfy.* application configuration for a Micronaut application.
NtfyJulAutoHandler	Declarative zero-code entry point: name this class in a JUL logging.properties —
NtfyJulHandler	A Handler that forwards SEVERE-and-above (and, when a warn route is configured, WARNING) LogRecords to the ntfy AlertEngine.
NtfyJulInstaller	Programmatic one-liner install of the ntfy JUL handler from the ambient environment: NtfyJulInstaller.install() early in main attaches a NtfyJulHandler to the root logger when the environment configures ntfy (NTFY_URL/NTFY_TOPIC, -Dntfy.*, or a trusted classpath ntfy.properties — see JulAmbientConfig for the classpath-endpoint opt-in guard), and does nothing otherwise.
NtfyLog4j2Appender	A thin log4j2 AbstractAppender shell over the framework-neutral AlertEngine, exposed to log4j2.xml as the <Ntfy .../> element.
NtfyLog4j2Appender.Builder	Plugin builder for the <Ntfy .../> element.
NtfyLog4j2Installer	Programmatic one-liner install of the ntfy log4j2 appender from the ambient environment: NtfyLog4j2Installer.install() early in main attaches a started NtfyLog4j2Appender to the root logger at Level.ERROR when the environment configures ntfy (NTFY_URL/NTFY_TOPIC, -Dntfy.*, or a trusted classpath ntfy.properties — see Log4j2AmbientConfig for the classpath-endpoint opt-in guard), and does nothing otherwise.
NtfyLogbackConfigurator	A Logback Configurator SPI implementation that auto-installs the ntfy appender on the root logger with zero XML — activated only when the ambient environment actually configures ntfy.
NtfyLogbackInstaller	Installs the ntfy appender named "ntfy-auto" on the root Logback logger once the Micronaut context has started, and detaches it again on shutdown.
NtfyMeterBinder	Binds the ntfy pipeline observability counters to Micrometer as three FunctionCounters: ntfy.pipeline.published, ntfy.pipeline.suppressed, and ntfy.pipeline.failed — the same three meters, with the same names and meanings, that the Spring Boot starter exports.
NtfyProperties	Binds all ntfy.* application properties.
NtfyPublisher	Stateless, never-throws HTTP publisher for the ntfy wire format.
NtfyRecorder	Records the creation of the ntfy log Handler at RUNTIME_INIT.
NtfyRuntimeConfig	Run-time configuration surface for the ntfy Quarkus extension, mapped from the quarkus.ntfy.* config namespace.
NtfyStartupSelfTestException	Thrown out of AlertEngine.start() when the startup self-test fails and startup-ping-fail-fast is enabled — the deliberate opt-in that turns a broken alerting configuration into a failed deployment rather than a silent one.
PipelineCounters	Read-only, monotonic observability counters for the alert pipeline, letting operators "alert on the alerter" (e.g. a spike in PipelineCounters.failed() signalling a revoked token or a topic ACL change).
PipelineCounters.Snapshot	An immutable, point-in-time triple of the three counters.
PublishResult	Outcome of a single NtfyPublisher.publish(java.lang.String, java.lang.String, java.lang.String, io.github.pimak.ntfy.core.AuthMode, java.lang.String) call.
StartupPingMode	What the opt-in startup self-test does when AlertEngine.start() finishes activating.