Cluster-logging-operator with only external elasticsearch not working
Closed this issue · 3 comments
Hi all,
I followed the documentation to install the cluster-logging-operator (https://docs.okd.io/latest/logging/cluster-logging-external.html). The goal is to only forward application logs to an external ElasticSearch cluster via the clusterLogForwarder.
The cluster-logging-operator keeps on logging the following event: _message":"Unable to generate log configuration","_error":{"msg":"No recognized input types: []"}}
My configuration for the logging operator:
apiVersion: "logging.openshift.io/v1"
kind: "ClusterLogging"
metadata:
name: "instance"
namespace: "openshift-logging"
spec:
managementState: "Managed"
collection:
logs:
type: "fluentd"
fluentd: {}
My configuration for the ClusterLogForwarder:
apiVersion: "logging.openshift.io/v1"
kind: ClusterLogForwarder
metadata:
name: instance
namespace: openshift-logging
spec:
outputs:
name: elasticsearch-secure
type: "elasticsearch"
url: https://xxxxxxxxx:9200
secret:
name: elasticsearch
pipelines:
name: application-logs
inputRefs:
application
outputRefs:
elasticsearch-secure
All help really appreciated.
Peter
Environment
- 4.7.0-0.okd-2021-09-19-013247
- cluster-logging.5.2.1-5 Red Hat OpenShift Logging 5.2.1-5
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle stale
Closing. Please try the latest and re-open at issues.redhat.com if you still have issues