Uploaded image for project: 'Insights Experiences'
  1. Insights Experiences
  2. HMS-2783

[FIRING:3] deployment_validation_operator_unset_memory_requirements content-sources crcs02ue1 deployment-validation-operator-metrics deployment-validation-operator

    Alert[0]: deployment_validation_operator_unset_memory_requirements Validation error for content-sources: Indicates when containers do not have memory requests and limits set.

    Annotations:

    Labels:

    • alertname = deployment_validation_operator_unset_memory_requirements
    • app = content-sources
    • check_description = Indicates when containers do not have memory requests and limits set.
    • check_remediation = Set memory requests and limits for your container based on its requirements. Refer to https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits for details.
    • cluster = crcs02ue1
    • endpoint = http-metrics
    • environment = staging
    • exported_namespace = content-sources-stage
    • instance = 10.131.9.173:8383
    • jiralert = HMS
    • job = deployment-validation-operator-metrics
    • kind = Deployment
    • name = cs-pulp-api
    • namespace = openshift-deployment-validation-operator
    • namespace_uid = cae1bed5-304f-4316-9f79-0cf8a9f395b9
    • pod = deployment-validation-operator-8488fffb8b-fpc8x
    • prometheus = openshift-customer-monitoring/app-sre
    • service = deployment-validation-operator
    • severity = medium
    • uid = e01da7db-afd6-4570-b377-f517327419df

    Source: Prometheus


    Alert[1]: deployment_validation_operator_unset_memory_requirements Validation error for content-sources: Indicates when containers do not have memory requests and limits set.

    Annotations:

    Labels:

    • alertname = deployment_validation_operator_unset_memory_requirements
    • app = content-sources
    • check_description = Indicates when containers do not have memory requests and limits set.
    • check_remediation = Set memory requests and limits for your container based on its requirements. Refer to https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits for details.
    • cluster = crcs02ue1
    • endpoint = http-metrics
    • environment = staging
    • exported_namespace = content-sources-stage
    • instance = 10.131.9.173:8383
    • jiralert = HMS
    • job = deployment-validation-operator-metrics
    • kind = Deployment
    • name = cs-pulp-content
    • namespace = openshift-deployment-validation-operator
    • namespace_uid = cae1bed5-304f-4316-9f79-0cf8a9f395b9
    • pod = deployment-validation-operator-8488fffb8b-fpc8x
    • prometheus = openshift-customer-monitoring/app-sre
    • service = deployment-validation-operator
    • severity = medium
    • uid = db5f02b8-e109-4b77-91e1-1e9151873327

    Source: Prometheus


    Alert[2]: deployment_validation_operator_unset_memory_requirements Validation error for content-sources: Indicates when containers do not have memory requests and limits set.

    Annotations:

    Labels:

    • alertname = deployment_validation_operator_unset_memory_requirements
    • app = content-sources
    • check_description = Indicates when containers do not have memory requests and limits set.
    • check_remediation = Set memory requests and limits for your container based on its requirements. Refer to https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits for details.
    • cluster = crcs02ue1
    • endpoint = http-metrics
    • environment = staging
    • exported_namespace = content-sources-stage
    • instance = 10.131.9.173:8383
    • jiralert = HMS
    • job = deployment-validation-operator-metrics
    • kind = Deployment
    • name = cs-pulp-worker
    • namespace = openshift-deployment-validation-operator
    • namespace_uid = cae1bed5-304f-4316-9f79-0cf8a9f395b9
    • pod = deployment-validation-operator-8488fffb8b-fpc8x
    • prometheus = openshift-customer-monitoring/app-sre
    • service = deployment-validation-operator
    • severity = medium
    • uid = 32a24a0d-abb8-4917-9535-3d7e1697029e

    Source: Prometheus


    Note: This issue was generated automatically by the AppSRE team. Moving this issue to a different project will result in the ticket being recreated in the current project. If you believe that this issue was created in the incorrect project, please reach out to AppSRE.

            Unassigned Unassigned
            sd-app-sre-jira App SRE Jira bot
            None
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: