-
Notifications
You must be signed in to change notification settings - Fork 508
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting StatsD to work in OnlyOffice Kubernetes/Docker 8.2 #781
Comments
Hello @torsten-simon, metrics generally work, I checked it on the latest Helm release v4.4.0 with Grafana, but there is a issue #71746 with some of them - no data in |
Hi @igwyd thanks for taking a look! Unfortunately, the only stats I'm able to retrieve come from the statsd exporter metrics itself. Could you confirm that there should be log messages when stats are flushed by the docserver (I've set the log level to We're mostly interested in the editing & viewing stats ( |
Maybe it becase you add your |
Hi @igwyd , I tried both with |
Can you show env for docservice process? PS i dont know about metrics logging in k8s yet, but i will let you know. |
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
StatsD / Metrics not working
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
In addition to that, since I had issues with the
METRICS_ENABLED
env in previous versions (7.5):Add a secret for
local-production-linux.json
with contents of(I can confirm that the docserver is parsing this file since it fails with an error on startup if I put in a syntax error on purpose.)
What is the expected behavior?
Pushing metrics to statsd in cluster, seeing log messages like
Flushing stats at
Did this work in previous versions of DocumentServer?
Yes, last tested on a docker based install with
onlyoffice/documentserver-ee:7.5
DocumentServer Docker tag:
onlyoffice/docs-docservice-ee:8.2.0-1 (also tried with "de" variant)
Helm chart version 4.3.0
Host Operating System:
Kubernetes Rancher / Ubuntu Worker
The text was updated successfully, but these errors were encountered: