Closed Bullote closed 1 year ago
I have the relevant ids and will share them internally for the investigation.
The problem is only with pipeline charts. I see the logstash collector creates 2 charts for every pipeline .
In that specific case, Cloud UI aggregated all the (pipelines) charts into monitoring-logstash
. @Bullote if you
You will get a stacked chart where a dimension will be a pipeline name (chart ID actually, but the name is a part of it).
I will update the collector:
In which version are the changes applied? I have updated the last one and I still do not see changes
@Bullote I think the fix will be available on Sat (Friday night nightly release).
@ilyam8 I'm sorry but this still doesn't solve my problem
The changes have been merged today. Will be available in the upcoming nightlies.
still doesn't solve my problem
If you mean having a subsection per pipeline on the Cloud UI - yes, the fix doesn't solve the problem. How it works now - the related charts are aggregated into one, per instance (e.g. pipeline) metrics can be seen using "Group by".
I think the problem you are mentioning now @Bullote is more related to this https://github.com/netdata/netdata-cloud/issues/654 my suggestion is to close this bug and follow that topic on the other bug
following the above suggestion, so closing this bug
sorry i forgot to close it
Regards [https://www.plexus.es/mail/dark/sm2plx.png]
Javier Boullosa García Infraestructura y Sistemas Móv. 615 264 564<tel:+34615264564> Tel. 971 750 324 ext 0000<tel:+34971750324>
[https://www.plexus.es/mail/dark/i-_0003_linkedin.png]https://www.linkedin.com/company/2650298/admin/| [https://www.plexus.es/mail/dark/i-_0002_instagram.png] https://www.instagram.com/plexus.tech/ | [https://www.plexus.es/mail/dark/i-_0001_facebook.png] https://www.facebook.com/Plexus.Techno/?modal=admin_todo_tour | [https://www.plexus.es/mail/dark/i-_0000_twitter.png] https://twitter.com/Plexology_ plexus.eshttps://www.plexus.es/
La información contenida en el presente mensaje podría ser confidencial. Si recibe este mensaje por error, le rogamos nos lo comunique de inmediato y lo elimine sin conservar copia del mismo ni de sus documentos adjuntos. Asimismo, le comunicamos que la distribución, copia o utilización de este mensaje, o de cualquier documento adjunto al mismo, cualquiera que fuera su finalidad, están prohibidas por la ley.
De: Hugo Valente @.> Enviado el: miércoles, 21 de diciembre de 2022 11:11 Para: netdata/netdata-cloud @.> CC: Javier Boullosa García @.>; Mention @.> Asunto: Re: [netdata/netdata-cloud] [Error]: Logstash metrics are not displayed in Netdata Cloud (Issue #667)
Closed #667https://github.com/netdata/netdata-cloud/issues/667 as completed.
— Reply to this email directly, view it on GitHubhttps://github.com/netdata/netdata-cloud/issues/667#event-8085830408, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A4KBK4NUVPUHQ45UQQBXATLWOLJUDANCNFSM6AAAAAASHCTVXI. You are receiving this because you were mentioned.Message ID: @.**@.>>
Bug description
The metrics captured by the Netdata agent with the Logstash plugin are not displayed in the Netdata Cloud but are displayed in Netdata On-premise. This happens in 5 different virtual machines with their 5 Netdata agents.
Expected behavior
The metrics must be visualized both in Netdata Cloud and Netdata On-Premise
Steps to reproduce
Screenshots
Error Logs
No response
Desktop
S.O: Centos 7.9 Agente: v1.36.0-371-g2d0248495
Additional context
No response