kubernetes - Sumo Logic kubernetes 集成要求不存在 Prometheus

Question

我目前正在整合 相扑逻辑 在 AWS EKS 簇。经过相扑逻辑 的关于他们与 k8s 集成的文档我已经到达以下部分 Installation Steps .文档的这一部分是一个岔路口，必须弄清楚是否要继续安装:

与您现有的 Prometheus Operator

并排

并更新您现有的 Prometheus Operator

与您的独立 Prometheus(不使用 Prometheus Operator)

没有预先存在的 Prometheus 安装

话虽如此，我正试图找出我不确定的情况。
让我解释一下，在处理这个 Sumo Logic 集成之前，我已经完成了 New Relic integration这让我想知道它是否以任何可能干扰 Sumo Logic 集成的方式使用 Prometheus？
所以为了弄清楚我开始执行:

$ kubectl get pods
NAME                                                      READY   STATUS      RESTARTS   AGE
aws-alb-ingress-controller-1600289507-7c7dc6f57d-sgpd8    1/1     Running     1          7d19h
f5-admin-ui-5cbcc464df-lh8nl                              1/1     Running     0          7d19h
f5-ambassador-5b5db5ff88-k5clw                            1/1     Running     0          7d19h
f5-api-gateway-7bdfc9cb-q57lt                             1/1     Running     0          7d19h
f5-argo-ui-7b98dd67-2cwrz                                 1/1     Running     0          7d19h
f5-auth-ui-58794664d9-rbccn                               1/1     Running     0          7d19h
f5-classic-rest-service-0                                 1/1     Running     0          7d19h
f5-connector-plugin-service-box-7f8b48b88-8jxxq           1/1     Running     0          7d19h
f5-connector-plugin-service-ldap-5d79fd4b8b-8kpcj         1/1     Running     0          7d19h
f5-connector-plugin-service-sharepoint-77b5bdbf9b-vqx4t   1/1     Running     0          7d19h
f5-devops-ui-859c97fb97-ftdxh                             1/1     Running     0          7d19h
f5-fusion-admin-64fb9df99f-svznw                          1/1     Running     0          7d19h
f5-fusion-indexing-6bbc7d4bcd-jh7cf                       1/1     Running     0          7d19h
f5-fusion-log-forwarder-78686cb8-shd6p                    1/1     Running     0          7d19h
f5-insights-6d9795f57-62qbg                               1/1     Running     0          7d19h
f5-job-launcher-9b659d984-n7h65                           1/1     Running     3          7d19h
f5-job-rest-server-55586d8db-xrzcn                        1/1     Running     2          7d19h
f5-ml-model-service-6c5bfd5b68-wwdkq                      2/2     Running     0          7d19h
f5-pm-ui-cc64c9498-gdmvp                                  1/1     Running     0          7d19h
f5-pulsar-bookkeeper-0                                    1/1     Running     0          7d19h
f5-pulsar-bookkeeper-1                                    1/1     Running     0          7d19h
f5-pulsar-bookkeeper-2                                    1/1     Running     0          7d19h
f5-pulsar-broker-0                                        1/1     Running     0          7d19h
f5-pulsar-broker-1                                        1/1     Running     0          7d19h
f5-query-pipeline-84749b6b65-9hzcx                        1/1     Running     0          7d19h
f5-rest-service-7855fdb676-6s6n8                          1/1     Running     0          7d19h
f5-rpc-service-676bfbf7f-nmbgp                            1/1     Running     0          7d19h
f5-rules-ui-6677475b8b-vbhcj                              1/1     Running     0          7d19h
f5-solr-0                                                 1/1     Running     0          20h
f5-templating-b6b964cdb-l4vjq                             1/1     Running     0          7d19h
f5-webapps-798b4d6864-b92wt                               1/1     Running     0          7d19h
f5-workflow-controller-7447466c89-pzpqk                   1/1     Running     0          7d19h
f5-zookeeper-0                                            1/1     Running     0          7d19h
f5-zookeeper-1                                            1/1     Running     0          7d19h
f5-zookeeper-2                                            1/1     Running     0          7d19h
nri-bundle-kube-state-metrics-cdc9ffd85-2s688             1/1     Running     0          2d21h
nri-bundle-newrelic-infrastructure-fj9g9                  1/1     Running     0          2d21h
nri-bundle-newrelic-infrastructure-jgckv                  1/1     Running     0          2d21h
nri-bundle-newrelic-infrastructure-pv27n                  1/1     Running     0          2d21h
nri-bundle-newrelic-logging-694hl                         1/1     Running     0          2d21h
nri-bundle-newrelic-logging-7w8cj                         1/1     Running     0          2d21h
nri-bundle-newrelic-logging-8gjw8                         1/1     Running     0          2d21h
nri-bundle-nri-kube-events-865664658d-ztq89               2/2     Running     0          2d21h
nri-bundle-nri-metadata-injection-557855f78d-rzjxd        1/1     Running     0          2d21h
nri-bundle-nri-metadata-injection-job-cxmqg               0/1     Completed   0          2d21h
nri-bundle-nri-prometheus-ccd7b7fbd-2npvn                 1/1     Running     0          2d21h
seldon-controller-manager-5b5f89545-6vxgf                 1/1     Running     1          7d19h

如您所见，New Relic 正在运行 nri-bundle-nri-prometheus-ccd7b7fbd-2npvn这似乎对应于 Kubernetes 或 Docker 的 New Relic OpenMetric 集成。浏览New Relic的 documentation我发现:

We currently offer two integration options:

• Prometheus remote write integration. Use this if you currently havePrometheus servers and want an easy access to your combined metricsfrom New Relic.
• Prometheus OpenMetrics integration for Kubernetes orDocker. Use this if you’re looking for an alternative or replacementto a Prometheus server and store all your metrics directly in NewRelic.

所以据我所知，我没有运行 普罗米修斯 服务器或运算符(operator)，我可以按照没有预先存在的 Prometheus 安装的专用安装部分继续进行 Sumo Logic 集成设置吗？这就是我要澄清的问题，想知道是否有人可以提供帮助，因为我是 的新手Kubernetes 和 普罗米修斯 .

Answer 1

我认为您很可能必须使用以下安装选项:

与您的独立 Prometheus(不使用 Prometheus Operator)

你能检查并粘贴 kubectl get prometheus 的输出吗？ .如果你看到任何正在运行的 prometheus，你可以运行 kubectl describe prometheus $prometheus_resource_name并检查标签以验证它是由运算符(operator)部署还是独立的prometheus。
如果它是由 Prometheus 运算符(operator)部署的，您可以使用以下任一方法:

与您现有的 Prometheus Operator

并排

更新您现有的 Prometheus Operator