Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-10038

[OM 3.4] Add metric names for SNMP to docs

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: ops-manager-3.4
    • Fix Version/s: None
    • Component/s: Ops Manager
    • Labels:
      None
    • Last comment by Customer:
      true
    • Story Points:
      0.4
    • Sprint:
      KANBAN BUCKET

      Description

      We had a request for mmsAlertMetricName values for OM 3.4 metrics from a customer trying to create snmp alerts and integrate system alerts with their monitoring tool.

      Some of the values we were able to get from the code, and the rest from the Engineering team (HELP-3962). Can we add the mmsAlertMetricName values to the docs so they are available to customers?

      https://docs.opsmanager.mongodb.com/current/core/system-alerts/

      For example the system alerts map like this

      *OM System Alert name -> Value shown in the alert:*
      *Blockstore space used exceeds threshold => OUTSIDE_SPACE_USED_THRESHOLD

      • Blockstore has a running balancer => BALANCER_ON
      • Detected startup warnings on a database backing the system => BACKING_DATABASE_PROCESS_STARTUP_WARNINGS
      • Detected a problem connecting to a database backing the system => BACKING_DATABASE_PROCESS_DOWN
      • Backup Daemon free head space percentage is below => LOW_HEAD_FREE_SPACE_PERCENT
      • Backup Daemon free head space is below => LOW_HEAD_FREE_SPACE
      • Backup Daemon is down => DAEMON_DOWN

      Thanks
      Annette

        Attachments

          Activity

            People

            Assignee:
            tony.sansone Anthony Sansone
            Reporter:
            annette.morrissey Annette Morrissey (Inactive)
            Participants:
            Last commenter:
            Githook User Githook User
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Days since reply:
              2 years, 42 weeks, 1 day ago
              Date of 1st Reply: