Trivy not discovered by Prometheus with ServiceMonitor

[JoeSpiral]

I have installed the Trivy Operator and it is not being discovered by my Prometheus ServiceMonitor. I am using kube-prometheus-stack and have other services like ArgoCD that have been discovered without issue. I see the Trivy serviceMonitor in k9s as well. Any insight would be appreciated. Below is my Trivy values config:

service:
  headless: true
  metricsPort: 80
  # -- annotations added to the operator's service
  annotations: {}

# -- Prometheus ServiceMonitor configuration -- to install the trivy operator with the ServiceMonitor
# you must have Prometheus already installed and running. If you do not have Prometheus installed, enabling this will
# have no effect.
serviceMonitor:
  # -- enabled determines whether a serviceMonitor should be deployed
  enabled: true
  # -- The namespace where Prometheus expects to find service monitors
  namespace: "default"
  # -- Interval at which metrics should be scraped. If not specified Prometheus’ global scrape interval is used.
  interval: ~
  # -- Additional annotations for the serviceMonitor
  annotations: {}
  # -- Additional labels for the serviceMonitor
  labels: {}
  # -- HonorLabels chooses the metric’s labels on collisions with target labels
  honorLabels: true
  # -- EndpointAdditionalProperties allows setting additional properties on the endpoint such as relabelings, metricRelabelings etc.
  endpointAdditionalProperties: {}

[JoeSpiral]

Forgot this is Operator 0.17.1.

[chen-keinan]

@JoeSpiral have you reviewed dashboard tutorials

[JoeSpiral]

@chen-keinan , thanks for the reply, yes I went through that. I have an existing kube-Prometheus stack running in my environment that has successfully made service monitor discovery for other services.

[AnaisUrlichs]

Are the other services in specific namespaces? Maybe worth installing another test application with sevricemonitor into the trivy-system namespace to see whether it is a trivy-operator issue or that Prometheus does not have permission to scrape the namespace?

[JoeSpiral]

Thank you for all your assistance. I am able to get another servicemonitor in trivy-system to work. I'm sure this is a one off issue on my end so I just added a manual scrape config to my prometheus operator and I am off and running. Thank you again for the assistance and for the very nice product.

[Shirueopseo]

How does you created the scrape config section on the prometheus operator? Can you show it to us? Thanks!