Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • F float
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 19
    • Issues 19
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ai3
  • float
  • Issues
  • #33

Closed
Open
Created Oct 27, 2018 by ale@aleOwner

Masked systemd units shouldn't alert

We sometimes have masked systemd units with a failed status, for instance:

* mariadb.service
   Loaded: masked (/dev/null; bad)
   Active: failed (Result: exit-code) since Sat 2018-10-27 07:00:49 GMT; 10min ago
 Main PID: 7939 (code=exited, status=1/FAILURE)
   Status: "MariaDB server is down"
      CPU: 214ms

this currently results in a SystemdUnitFailed alert. The alert should exclude masked units.

Assignee
Assign to
Time tracking