text stringlengths 0 1.8k |
|---|
[1706.24 --> 1707.58] epis out of the |
[1707.58 --> 1708.96] box it doesn't |
[1708.96 --> 1709.50] happen at the |
[1709.50 --> 1710.30] moment because open |
[1710.30 --> 1711.04] telemetry is still |
[1711.04 --> 1712.16] emerging standard but |
[1712.16 --> 1713.26] how i would foresee |
[1713.26 --> 1715.48] it that basically any |
[1715.48 --> 1716.64] enterprise grade ci |
[1716.64 --> 1717.68] system would |
[1717.68 --> 1719.32] include a number of |
[1719.32 --> 1720.10] open telemetry |
[1720.10 --> 1721.36] collectors so that |
[1721.36 --> 1722.20] you can just connect |
[1722.20 --> 1723.40] to them and retrieve |
[1723.40 --> 1724.66] this information and |
[1724.66 --> 1726.18] it can be opt-in so |
[1726.18 --> 1727.34] that you set some |
[1727.34 --> 1728.38] flags for example in |
[1728.38 --> 1729.52] your helen charts and |
[1729.52 --> 1730.86] then all your open |
[1730.86 --> 1732.06] telemetry collection is |
[1732.06 --> 1733.38] configured because it's |
[1733.38 --> 1734.58] again a building block |
[1734.58 --> 1735.86] if you need to do |
[1735.86 --> 1737.10] something complex to |
[1737.10 --> 1738.44] enable open telemetry |
[1738.44 --> 1739.78] that probably doesn't |
[1739.78 --> 1741.76] achieve its goal and |
[1741.76 --> 1742.80] once the technology |
[1742.80 --> 1743.76] measures i would |
[1743.76 --> 1744.62] rather expect that |
[1744.62 --> 1745.94] every tool just |
[1745.94 --> 1747.98] adopts that and it |
[1747.98 --> 1748.96] becomes a commodity |
[1748.96 --> 1750.42] for any system you |
[1750.42 --> 1751.36] run so what about |
[1751.36 --> 1752.56] today what ci city |
[1752.56 --> 1753.60] tool can i use today |
[1753.60 --> 1755.14] that has this out of |
[1755.14 --> 1756.22] the box wow that's a |
[1756.22 --> 1757.16] good question because |
[1757.16 --> 1758.62] actually almost none of |
[1758.62 --> 1759.22] the tools have |
[1759.22 --> 1760.38] serial ones yeah |
[1760.38 --> 1761.80] there are two ci |
[1761.80 --> 1763.24] platforms i am aware |
[1763.24 --> 1765.10] of who provide native |
[1765.10 --> 1765.90] open telemetry |
[1765.90 --> 1767.56] instrumentation and they |
[1767.56 --> 1769.96] are jenkins and i am |
[1769.96 --> 1770.80] of course for the |
[1770.80 --> 1772.26] integration and also |
[1772.26 --> 1773.56] concourse ci what do |
[1773.56 --> 1774.84] we need to do to get |
[1774.84 --> 1775.66] open telemetry in |
[1775.66 --> 1776.94] jenkins so you just |
[1776.94 --> 1778.50] need to install the |
[1778.50 --> 1779.82] jenkins open telemetry |
[1779.82 --> 1781.28] plugin going through |
[1781.28 --> 1782.44] your jenkins plugins |
[1782.44 --> 1784.32] manager and then you |
[1784.32 --> 1785.60] once jenkins is |
[1785.60 --> 1786.50] instrumented with open |
[1786.50 --> 1787.44] telemetry you have to |
[1787.44 --> 1790.26] connect your jenkins to |
[1790.26 --> 1791.50] an open telemetry |
[1791.50 --> 1793.54] endpoint backend which |
[1793.54 --> 1795.18] can be maybe elastic i |
[1795.18 --> 1796.82] work for elastic or |
[1796.82 --> 1798.10] maybe you can use |
[1798.10 --> 1799.30] jaeger if you want to |
[1799.30 --> 1800.42] use jaeger it's very |
[1800.42 --> 1801.76] popular open source |
[1801.76 --> 1802.94] distributed tracing |
[1802.94 --> 1804.40] visualization that has |
[1804.40 --> 1806.40] been created at uber you |
[1806.40 --> 1807.50] will need to install a |
[1807.50 --> 1808.54] small component called |
[1808.54 --> 1809.74] open telemetry collector |
[1809.74 --> 1811.56] in between your ci |
[1811.56 --> 1812.72] platform on jaeger |
[1812.72 --> 1814.18] because jaeger don't |
[1814.18 --> 1815.16] speak natively open |
[1815.16 --> 1815.88] telemetry for the |
[1815.88 --> 1817.16] moment and then you |
[1817.16 --> 1818.64] are good to go in |
[1818.64 --> 1820.02] jenkins with this open |
[1820.02 --> 1821.26] telemetry integration we |
[1821.26 --> 1822.38] have started with |
[1822.38 --> 1824.26] traces initially to |
[1824.26 --> 1825.46] trace pipeline execution |
[1825.46 --> 1827.18] we have also captured |
[1827.18 --> 1829.34] health metrics so you |
[1829.34 --> 1830.86] can also leverage our |
[1830.86 --> 1832.20] jenkins open telemetry |
[1832.20 --> 1833.84] integration to capture |
[1833.84 --> 1835.62] the health metrics of |
[1835.62 --> 1837.26] your jenkins ci platform |
[1837.26 --> 1839.44] route them to maybe |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.