Sflow-RT REST API

[Alisson Medeiros]

Hello guys,

I'm having a problem identifying the resources associated with a docker container through sflow-rt's api.

To access the link below by the browser, I can see all the metrics associated with each docker container, however, I would like to know how to access the features of a particular docker container.

http://localhost:8008/metric/192.168.0.108/json

Result:

3.143625.vir_machine_type	"x86_64"
2.1.load_fifteen	0.36
5.ifindex	"5"
3.113065.vir_uuid	"83b035a2-a0bc-4cfa-8178-1f358e4ba1cb"
4.ifadminstatus	"up"
2.1.cpu_guest_nice	0
3.128056.host_parent	"2.1"
3.113065.vir_bytes_out	0
3.113065.vir_mem_total	9223372036854772000
3.143625.vir_pkts_in	11.08702900966989
2.1.icmp_inechos	0
2.1.errs_out	0
3.113065.vir_errors	0
2.1.icmp_outtimestamps	0
2.1.node_mem_free	247812096
3.128056.vir_errors	0
3.128056.vir_bytes_out	749.1663887962654
3.143625.vir_drops_out	0
2.1.disk_utilization	54.4610857963562
3.113065.vir_disk_allocation	0
2.1.icmp_intimeexcds	0.32938076416337286
3.143625.vir_host_name	"dockermonitoring_cadvisor_1"
3.113065.vir_mem_utilization	2.1853630016721581e-10
2.1.swap_total	1023406080
2.1.host_name	"alisson"
3.128056.vir_disk_allocation	0
2.1.icmp_inaddrmaskreps	0
2.1.udp_rcvbuferrors	0
2.1.icmp_outmsgs	0
4.ifname	"docker_gwbridge"
3.128056.vir_os_name	"linux"
2.1.proc_run	1
3.143625.host_parent	"2.1"
3.143625.vir_disk_allocation	0
2.1.drops_out	0
4.ifinucastpkts	0
3.113065.vir_disk_capacity	0
2.1.ip_outrequests	2.7997364953886694
2.1.tcp_currestab	1
2.1.write_time	53.378684807256235
5.iftype	"ethernetCsmacd"
2.1.cpu_user	10.244711737868105
3.143625.vir_cpu_num	0
2.1.ip_inunknownprotos	0
3.113065.vir_cpu_num	0
2.1.drops_in	0
3.128056.vir_writes	0
2.1.bytes_written	322445.32279314887
3.113065.vir_writes	0
3.128056.vir_disk_physical	0
2.1.ip_indelivers	1.3175230566534915
3.143625.vir_mem_utilization	2.9167779302952113e-10
3.113065.vir_errs_in	0
3.113065.vir_bytes_written	0
2.1.cpu_idle	84.0937370385732
3.113065.vir_cpu_state	"running"
3.143625.vir_mem_free	9223372036827869000
3.143625.vir_disk_capacity	0
2.1.icmp_inaddrmasks	0
3.128056.vir_os_release	"4.4.0-103-generic"
2.1.icmp_intimestamps	0
2.1.os_name	"linux"
3.128056.vir_pkts_in	13.254418139379792
2.1.icmp_inerrors	0
2.1.icmp_insrcquenchs	0
2.1.tcp_incsumerrs	0
2.1.ip_defaultttl	64
2.1.machine_type	"x86_64"
4.ifdirection	"unknown"
3.143625.vir_writes	0
2.1.udp_inerrors	0
5.ifdirection	"unknown"
2.1.load_five	0.31
2.1.tcp_retranssegs	0.08234519104084322
2.1.read_time	0
2.1.icmp_inechoreps	0
3.128056.vir_pkts_out	11.170390130043348
2.1.ip_fragoks	0
2.1.tcp_attemptfails	0
5.ifindiscards	0
4.ifoutoctets	0
3.128056.vir_bytes_written	0
4.ifoutpkts	0
4.ifoperstatus	"up"
2.1.ip_inreceives	2.0586297760210805
2.1.tcp_activeopens	0
2.1.page_out	157.44400527009222
3.143625.vir_os_name	"linux"
2.1.disk_free	153075609600
2.1.icmp_outsrcquenchs	0
2.1.udp_indatagrams	0.32938076416337286
5.ifadminstatus	"up"
2.1.node_cpus	4
2.1.tcp_inerrs	0
2.1.errs_in	0
2.1.ip_forwarding	1
2.1.uptime	82597
2.1.icmp_outtimeexcds	0
2.1.node_cpu_mhz	1312
2.1.contexts	6457.01581027668
2.1.writes	36.31422924901186
2.1.icmp_inredirects	0
3.143625.vir_errors	0
2.1.swap_in	0
3.128056.vir_drops_out	0
2.1.icmp_outredirects	0
3.143625.vir_mem_used	26902528
2.1.icmp_inparamprobs	0
5.ifinoctets	0
3.113065.vir_mem_free	9223372036834615000
3.113065.vir_disk_physical	0
3.128056.vir_mem_utilization	2.9056757000489597e-10
2.1.cpu_num	4
4.iftype	"ethernetCsmacd"
4.ifindex	"4"
2.1.ip_inhdrerrors	0
2.1.interrupts	1309.370882740448
3.128056.vir_host_name	"dockermonitoring_influxdb_1"
2.1.ip_outnoroutes	0
2.1.proc_total	874
2.1.page_in	0
2.1.load_fifteen_per_cpu	0.09
2.1.mem_utilization	61.02299690246582
2.1.ip_reasmreqds	0
2.1.icmp_outerrors	0
2.1.load_five_per_cpu	0.0775
3.128056.vir_bytes_in	57859.53651217072
2.1.cpu_speed	1312
3.113065.vir_machine_type	"x86_64"
2.1.node_domains	3
3.128056.vir_cpu_num	0
3.128056.vir_mem_total	9223372036854772000
3.128056.vir_cpu_state	"running"
4.ifspeed	0
2.1.icmp_outtimestampreps	0
2.1.pkts_out	3.6231884057971016
2.1.swap_free	893698048
2.1.cpu_intr	0
2.1.bytes_read	0
3.128056.vir_errs_in	0
2.1.ip_outdiscards	0
2.1.disk_total	336142426112
5.ifname	"docker0"
3.143625.vir_os_release	"4.4.0-103-generic"
2.1.icmp_outaddrmasks	0
2.1.ip_reasmoks	0
3.128056.vir_drops_in	0
2.1.pkts_in	1.564558629776021
2.1.icmp_outparamprobs	0.32938076416337286
2.1.bytes_out	893.8570487483531
2.1.ip_forwdatagrams	0
2.1.mem_used	2449174528
2.1.mem_total	4013527040
3.143625.vir_bytes_read	0
3.128056.vir_cpu_utilization	1.0003334444814937
3.143625.vir_bytes_out	57856.03534511504
2.1.mem_cached	991723520
3.143625.vir_mem_total	9223372036854772000
2.1.tcp_passiveopens	0
3.113065.vir_bytes_read	0
2.1.uuid	"f0ca937c-0837-10f8-a181-3b9eba25b27e"
3.113065.vir_reads	0
5.ifinerrors	0
3.128056.vir_disk_capacity	0
3.143625.vir_disk_physical	0
2.1.bytes_in	326.4986824769434
5.ifspeed	0
2.1.tcp_outrsts	0
2.1.icmp_indestunreachs	0
2.1.tcp_rtomin	200
2.1.icmp_outaddrmaskreps	0
2.1.reads	0
3.113065.host_parent	"2.1"
3.113065.vir_drops_out	0
2.1.ip_indiscards	0
4.ifinerrors	0
3.113065.vir_host_name	"dockermonitoring_grafana_1"
3.143625.vir_bytes_written	0
4.ifindiscards	0
3.128056.vir_errs_out	0
2.1.udp_sndbuferrors	0
2.1.ip_fragfails	0
5.ifinpkts	0
4.ifouterrors	0
2.1.udp_outdatagrams	1.3175230566534915
5.ifouterrors	0
2.1.udp_noports	0
3.113065.vir_drops_in	0
5.ifoutdiscards	0
2.1.load_one_per_cpu	0.075
2.1.icmp_inmsgs	0.32938076416337286
2.1.icmp_outechos	0
2.1.ip_fragcreates	0
3.128056.vir_mem_free	9223372036827972000
2.1.cpu_wio	2.3849025300705105
2.1.part_max_used	85.75
2.1.cpu_system	3.2559104106180006
2.1.cpu_utilization	15.906262961426792
3.128056.vir_bytes_read	0
4.ifoutdiscards	0
3.128056.vir_reads	0
5.ifoutoctets	384.46148716238747
3.143625.vir_errs_in	0
2.1.mem_shared	0
3.113065.vir_os_release	"4.4.0-103-generic"
2.1.mem_buffers	324816896
3.113065.vir_mem_used	20156416
4.ifinpkts	0
4.ifoutucastpkts	0
2.1.tcp_insegs	0.6587615283267457
3.143625.vir_errs_out	0
3.143625.vir_reads	0
2.1.cpu_sintr	0.020738282870178346
3.113065.vir_bytes_in	0
3.113065.vir_pkts_in	0
3.143625.vir_bytes_in	745.6652217405801
5.ifinucastpkts	0
2.1.mem_free	247812096
2.1.tcp_maxconn	4294967295
2.1.icmp_outechoreps	0
2.1.tcp_estabresets	0
5.ifoutpkts	1.1670556852284095
2.1.icmp_outdestunreachs	0.32938076416337286
3.143625.vir_cpu_utilization	2.0840280093364454
3.143625.vir_pkts_out	13.171057019006335
2.1.ip_reasmfails	0
3.143625.vir_cpu_state	"running"
2.1.tcp_rtomax	120000
2.1.ip_reasmtimeout	0
2.1.load_one	0.3
3.143625.vir_drops_in	0
2.1.udp_incsumerrors	0
2.1.tcp_rtoalgorithm	1
5.ifoperstatus	"up"
2.1.swap_out	0
2.1.os_release	"4.4.0-103-generic"
5.ifoutucastpkts	1.1670556852284095
3.128056.vir_mem_used	26800128
3.128056.vir_machine_type	"x86_64"
3.113065.vir_pkts_out	0
3.113065.vir_errs_out	0
2.1.tcp_outsegs	1.0704874835309617
2.1.cpu_nice	0
2.1.cpu_guest	0
2.1.cpu_steal	0
3.113065.vir_os_name	"linux"
4.ifinoctets	0
3.113065.vir_cpu_utilization	0
3.143625.vir_uuid	"525abcc7-0578-729b-4c7a-45de4187c4c2"
3.128056.vir_uuid	"31e3a814-aee2-33f3-bb37-2cf7c2418f5a"
2.1.node_mem_total	4013527040
2.1.ip_inaddrerrors	0

[Peter Phaal]

You can query specific metrics using the following query:

http://localhost:8008/metric/10.0.0.16/3.100012.vir_cpu_utilization,3.100012.vir_bytes_in,3.100012.vir_bytes_out/json

Alternatively, you can use a filter to select the metrics container:

http://localhost:8008/metric/10.0.0.16/vir_cpu_utilization,vir_bytes_in,vir_bytes_out/json?vir_uuid=5559775a-ccf5-8a4b-f207-d28e9d44dfea

There are also table and dump variants of these queries. For more information, see:

http://sflow-rt.com/writing_applications.php#handleinterval

[Alisson Medeiros]

Hello Peter,

Thank you for your attention, I was very useful.

Do you know how to normalize the containers metrics made available by sflow-rt?

For example:
cpu usage in %
memory usage in % or in kilobyte(kb) or megabyte(mb)

--
You received this message because you are subscribed to the Google Groups "sFlow-RT" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sflow-rt+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Peter Phaal]

On Sun, Dec 10, 2017 at 5:25 AM, Alisson Medeiros <alissonp...@gmail.com> wrote:

Do you know how to normalize the containers metrics made available by sflow-rt?

For example:
cpu usage in %
memory usage in % or in kilobyte(kb) or megabyte(mb)

I am not sure I understand your question. The metrics are consistent for all containers and virtual machines. For many metrics there are two values presented, a base value, for example mem_used is the memory in bytes, and mem_utilization  is the % of total memory used.

The metric query can also compute summary statistics across groups of containers / hosts:

http://blog.sflow.com/2013/02/cluster-performance-metrics.html

Grouping containers by service can be a useful way to summarize metrics:

http://blog.sflow.com/2016/10/collecting-docker-swarm-service-metrics.html

It is left up to applications presenting the data to convert units from the base value (e.g. bytes) to kilobytes, megabytes etc.