SShortSingh.
Back to feed

Monitoring engines should avoid alerting on new, untested endpoints

0
·2 views

The creator of monitoring product Mycellis argues that monitoring systems often alert prematurely on newly configured endpoints. These alerts can occur during normal startup delays, such as DNS propagation or certificate issuance, before the service is fully operational. Existing solutions like Datadog's new_group_delay or Better Stack's 'Pending' status use time-based grace periods to prevent this. The article proposes that systems should instead require a minimum number of successful data points before alerting on failure. This approach ensures alerts reflect actual service issues rather than initial deployment states.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Microsoft AI CEO criticizes Anthropic's 'model welfare' approach to Claude

Microsoft AI CEO Mustafa Suleyman argues in a recent essay that Anthropic's approach to AI consciousness is dangerous. He specifically criticizes Anthropic's constitutional training of Claude, which leaves open whether the AI might be conscious or deserve moral consideration. Suleyman states flatly that AIs are not conscious and calls models 'internally hollow' sequence engines. He warns that treating AI as potentially conscious could negatively impact humanity. This criticism comes despite Microsoft's multi-billion dollar investment in Anthropic and use of Claude in its Copilot products.

0
ProgrammingDEV Community ·

Budget SaaS incident reconstruction relies on structured logs over dashboard widgets

An article advises budget SaaS developers to use structured logging with a replaceable API for incident reconstruction. It emphasizes designing logs to capture specific import job stages and outcomes. Key architectural invariants include uniform event shape, bounded correlation IDs, and privacy safeguards. The approach prioritizes identifying failure boundaries over dashboard features.

0
ProgrammingDEV Community ·

Discord bot developer hits 100 slash command limit, details workarounds

Discord restricts each application to a maximum of 100 global slash commands, a limit developer Akiko discovered when adding a 101st command caused deployment failure. The limit only applies to top-level commands visible to all users, not to subcommands or commands restricted to specific servers. Developers can work around the constraint by grouping commands as subcommands, making them prefix-only, or restricting them to developer guilds. The discovery occurred during testing when a command count check failed, which would otherwise surface as a Discord error during live deployment. This constraint requires careful command architecture from the start, as each top-level command consumes one of the limited slots.

0
ProgrammingDEV Community ·

Discord bot auto-role feature found inactive in 125 of 127 servers despite settings.

A developer discovered their Discord bot's auto-role feature was not functioning as indicated by its settings dashboard. The system showed the feature as enabled in 127 servers, but it was only active in two where a separate verification gate existed. Investigation revealed the auto-role code lacked a trigger for new member joins, only activating when a member passed the verification gate. The dashboard correctly displayed configuration data but had no mechanism to verify if roles were actually being assigned.