SumoLogic / sumologic-kubernetes-collection

Sumo Logic collection solution for Kubernetes
Apache License 2.0
147 stars 184 forks source link

sumologic setup job error "Object ID must be a valid hexadecimal string." #3115

Closed cogito-cmurphy closed 1 year ago

cogito-cmurphy commented 1 year ago

Hello,

Recently took over our sumologic implementation and have to move it forward for EKS 1.24. I have a barebones sumologic 3.4.0 deployment going but it doesn't seem to create open telemetry collectors in sumo like I would expect. My bare bones values

  values:
    kube-prometheus-stack:
        enabled: false
    metadata:
      persistence:
        storageClass: general-purpose-csi
    sumologic:
      envFromSecret: sumologic-api-token-xacct-externalsecrets
      logs:
        fields:
          - cluster
          - container
          - deployment
          - host
          - namespace
          - node
          - pod
          - service
      metrics:
        enabled: false

the sumologic setup job has this failure

sumologic-sumologic-setup-ms66j setup 2023-06-30T12:31:55.985Z [DEBUG] provider: using plugin: version=5
sumologic-sumologic-setup-ms66j setup sumologic_monitor_folder.tf_monitor_folder_1: Creating...
sumologic-sumologic-setup-ms66j setup 2023-06-30T12:31:56.510Z [DEBUG] provider.terraform-provider-sumologic_v2.18.2: 2023/06/30 12:31:56 [DEBUG] Request: [Method=POST] [URL=https://api.us2.sumologic.com/api/v1/monitors?parentId=30NT0-6B2VY-NUOW8&] [Headers=map[Authorization:[xxxxxxxxxxx] Content-Type:[application/json] User-Agent:[SumoLogicTerraformProvider/2.18.2]]]. Response: [StatusCode=400 Bad Request]
sumologic-sumologic-setup-ms66j setup ╷
sumologic-sumologic-setup-ms66j setup │ Error: {"id":"62O2S-SSXZ4-HYEB3","errors":[{"code":"user:invalid_object_id","message":"Object ID must be a valid hexadecimal string.","meta":{"id":"30NT0-6B2VY-NUOW8"}}]}
kasia-kujawa commented 1 year ago

I'm not able to reproduce this problem. Do you still observe this? Why have you removed daemonset and statefulset from sumologic.logs.fields?

cogito-cmurphy commented 1 year ago

I'm not able to reproduce this problem. Do you still observe this? Why have you removed daemonset and statefulset from sumologic.logs.fields?

Yes im still having this issue. I have / had a ticket open for the fields issue, because we didnt have those fields in https://help.sumologic.com/docs/manage/fields/ it was blocking setup. I am now adding these fields and trying again.

cogito-cmurphy commented 1 year ago

For this specific error I can "bypass" it by doing the code below but it doesnt setup otel collectors

sumologic:
      setup:
        monitors:
          enabled: false
rnishtala-sumo commented 1 year ago

this error can be caused by the user missing permissions to view and manage monitors. Below is the link to the documentation.

https://help.sumologic.com/docs/manage/users-roles/roles/role-capabilities/#alerts

The error message is misleading.

cogito-cmurphy commented 1 year ago

thank you @rnishtala-sumo

izakp commented 1 year ago

Encountered this error as well and as it's misleading I think it would be worth mentioning that the setup job requires the "Manage Monitors" as well as the "Manage Fields" capabilities in the setup instructions, as this also tripped me up.