Uses of Package
io.github.pimak.ntfy.core
Packages that use io.github.pimak.ntfy.core
Package
Description
-
Classes in io.github.pimak.ntfy.core used by io.github.pimak.ntfy.coreClassDescriptionFramework-neutral snapshot of a single log event, handed to
AlertEngine.submit(io.github.pimak.ntfy.core.AlertEvent).One link of an exception chain: the throwable's class name and its message (either may benullin degenerate cases, mirroring the source throwable).The severity of anAlertEvent, as far as the alerting engine is concerned — the valueAlertEngineroutes on.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 ownAuthorizationheader.Self-diagnostic sink forAlertEngine.A single ntfy notification action button, modeled as a sealed hierarchy so each action type carries only the fields it needs (mirroring theAuthModepattern).Sends an Android broadcast intent when tapped (only actioned by ntfy's Android app).Sends an HTTP request tourlwhen tapped.Opensurlin the browser/app when the action button is tapped.Immutable, framework-neutral configuration for the ntfy engine and client.Fluent builder forNtfyConfig; every setter returnsthis.Read-only, monotonic observability counters for the alert pipeline, letting operators "alert on the alerter" (e.g. a spike inPipelineCounters.failed()signalling a revoked token or a topic ACL change).An immutable, point-in-time triple of the three counters.What the opt-in startup self-test does whenAlertEngine.start()finishes activating. -
Classes in io.github.pimak.ntfy.core used by io.github.pimak.ntfy.julClassDescriptionFramework-pure alert engine: the extracted heart of the original Logback
NtfyAlertAppender, decoupled from any logging framework.Immutable, framework-neutral configuration for the ntfy engine and client.Read-only, monotonic observability counters for the alert pipeline, letting operators "alert on the alerter" (e.g. a spike inPipelineCounters.failed()signalling a revoked token or a topic ACL change). -
Classes in io.github.pimak.ntfy.core used by io.github.pimak.ntfy.log4j2ClassDescriptionRead-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). -
Classes in io.github.pimak.ntfy.core used by io.github.pimak.ntfy.logbackClassDescriptionRead-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). -
Classes in io.github.pimak.ntfy.core used by io.github.pimak.ntfy.micronautClassDescriptionGeneric, standalone ntfy notification client — the "send an arbitrary notification" surface, independent of
AlertEngine's log-alert lifecycle. -
Classes in io.github.pimak.ntfy.core used by io.github.pimak.ntfy.quarkus.runtimeClassDescriptionGeneric, standalone ntfy notification client — the "send an arbitrary notification" surface, independent of
AlertEngine's log-alert lifecycle.