Sumo Logic kubernetes 集成要求不存在 Prometheus
Sumo Logic kubernetes integration requires that no Prometheus exists
我目前正致力于将 Sumo Logic 集成到 AWS EKS 集群中。在阅读了 Sumo Logic 关于它们与 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 have
Prometheus servers and want an easy access to your combined metrics
from New Relic.
- Prometheus OpenMetrics integration for Kubernetes or
Docker. Use this if you’re looking for an alternative or replacement
to a Prometheus server and store all your metrics directly in New
Relic.
所以据我所知，我不是 运行 Prometheus server 或 operator 并且我可以按照专用于 安装且没有预先存在的 Prometheus 安装 的部分继续 Sumo Logic 集成设置？这就是我想澄清的，想知道是否有人可以提供帮助，因为我是 Kubernetes 和 Prometheus.
的新手
我认为您很可能必须使用以下安装选项：
- 使用独立的 Prometheus（不使用 Prometheus Operator）
你能检查并粘贴 kubectl get prometheus 的输出吗？如果您看到任何 运行ning prometheus，您可以 运行 kubectl describe prometheus $prometheus_resource_name 并检查标签以验证它是由运营商部署的还是独立的 prometheus。
如果它是由 Prometheus operator 部署的，您可以使用以下任一方法：
- 与您现有的 Prometheus Operator 并存
- 更新现有的 Prometheus Operator
最后，我遵循了专门针对未安装 pre-existing Prometheus 的设置的 Sumo Logic 集成说明，一切正常。
我目前正致力于将 Sumo Logic 集成到 AWS EKS 集群中。在阅读了 Sumo Logic 关于它们与 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 have Prometheus servers and want an easy access to your combined metrics from New Relic.
- Prometheus OpenMetrics integration for Kubernetes or Docker. Use this if you’re looking for an alternative or replacement to a Prometheus server and store all your metrics directly in New Relic.
所以据我所知，我不是 运行 Prometheus server 或 operator 并且我可以按照专用于 安装且没有预先存在的 Prometheus 安装 的部分继续 Sumo Logic 集成设置？这就是我想澄清的，想知道是否有人可以提供帮助，因为我是 Kubernetes 和 Prometheus.
的新手我认为您很可能必须使用以下安装选项：
- 使用独立的 Prometheus（不使用 Prometheus Operator）
你能检查并粘贴 kubectl get prometheus 的输出吗？如果您看到任何 运行ning prometheus，您可以 运行 kubectl describe prometheus $prometheus_resource_name 并检查标签以验证它是由运营商部署的还是独立的 prometheus。
如果它是由 Prometheus operator 部署的，您可以使用以下任一方法：
- 与您现有的 Prometheus Operator 并存
- 更新现有的 Prometheus Operator
最后，我遵循了专门针对未安装 pre-existing Prometheus 的设置的 Sumo Logic 集成说明，一切正常。