Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • I infrastructure
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 258
    • Issues 258
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • 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
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • entanglement.garden
  • infrastructure
  • Issues
  • #490

Closed
Open
Created Apr 23, 2022 by Entanglement Monitoring Bot@entanglement-monitoringReporter

Firing alert `FailedSystmedService`

warn alert FailedSystmedService occurred

Alertmanager link: http://monitoring:9093

Common labels:

  • alertname: FailedSystmedService
  • instance: 172.18.101.1:9100
  • job: node-exporter
  • name: ansible-on-boot.service
  • severity: warn
  • state: failed

Common annotations:

  • summary: systemd service ansible-on-boot.service on 172.18.101.1:9100 is failed

Alerts

  • ``
    • Starts at: 2022-04-03 02:03:18.518582447 +0000 UTC
    • Ends at: 0001-01-01 00:00:00 +0000 UTC
    • Generator URL: https://prometheus.entanglement.garden/graph?g0.expr=node_systemd_unit_state%7Bstate%3D%22failed%22%7D+%3D%3D+1&g0.tab=1
    • Labels: {alertname="FailedSystmedService", instance="172.18.101.1:9100", job="node-exporter", name="ansible-on-boot.service", severity="warn", state="failed", }

this issue was automatically generated using the default template that came with prometheus-gitlab-notifier, if it sucks please edit /etc/prometheus/gitlab-issue.tmpl on monitoring.fruit-0

Assignee
Assign to
Time tracking