Pushing to Netdata #15874
-
https://www.netdata.cloud/roadmap/ says that Netdata is able to collect metrics using any protocol and any methodology, using both pull (Netdata asks for metrics) and push (Netdata waits for metrics to come) architectures. But I haven't found any information on pushing metrics to Netdata online. Has anyone had experience with using this functionality, or does anyone know where there is documentation on it? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
I think StatsD might be the main "push" example that comes to mind: https://learn.netdata.cloud/docs/data-collection/apm/statsd e.g. in this example you are pushing metrics to the statsd endpoint of netdata at port 8125 now that you mention it I'm not sure we have much in our docs that discusses push vs pull which is a common thing we probably should cover more. do you have a specific use case in mind or is it just more of a general question? i know we are looking to more fully support OTEL stuff soon (prometheus collector is often enough but we need to add some more parts for OTEL in a more general sense) and am sure things like receivers and push vs pull will be a big part of that. https://opentelemetry.io/docs/collector/configuration/#receivers |
Beta Was this translation helpful? Give feedback.
I think StatsD might be the main "push" example that comes to mind: https://learn.netdata.cloud/docs/data-collection/apm/statsd
e.g. in this example you are pushing metrics to the statsd endpoint of netdata at port 8125
now that you mention it I'm not sure we have much in our docs that discusses push vs pull which is a common thing we probably should cover more.
do you have a specific use case in mind or is it just more of a general question?
i know we are looking to more fully support OTEL stuff soon (prometheus collector is often enough but we need to add some more parts for OTEL in a more general sense) and am sure things like receivers and push vs pull will be a big part of that. http…