{"id":7163,"date":"2026-04-10T13:48:16","date_gmt":"2026-04-10T11:48:16","guid":{"rendered":"https:\/\/logmanager.com\/?post_type=learning_hub&#038;p=7163"},"modified":"2026-05-27T10:52:14","modified_gmt":"2026-05-27T08:52:14","slug":"co-je-syslog","status":"publish","type":"learning_hub","link":"https:\/\/logmanager.com\/cs\/learn\/co-je-syslog\/","title":{"rendered":"Co je syslog?"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Udr\u017eet plynul\u00fd provoz IT infrastruktury je dnes z\u00e1sadn\u00ed, proto\u017ee na n\u011bm \u010dasto z\u00e1vis\u00ed fungov\u00e1n\u00ed cel\u00e9 organizace. Kdy\u017e nastane probl\u00e9m, je d\u016fle\u017eit\u00e9 m\u00edt k dispozici informace, kter\u00e9 pomohou situaci rychle identifikovat a vy\u0159e\u0161it. A pr\u00e1v\u011b v tom spo\u010d\u00edv\u00e1 p\u0159\u00ednos syslogu, kter\u00fd umo\u017e\u0148uje efektivn\u00ed monitoring syst\u00e9m\u016f, rychl\u00e9 odhalen\u00ed probl\u00e9m\u016f a pom\u00e1h\u00e1 administr\u00e1tor\u016fm zajistit stabiln\u00ed a spolehliv\u00fd chod infrastruktury.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Syslog se od sv\u00e9ho vzniku v 80. letech stal z\u00e1kladn\u00edm mechanismem, kter\u00fdm si servery, routery, firewally a dal\u0161\u00ed za\u0159\u00edzen\u00ed a slu\u017eby p\u0159ed\u00e1vaj\u00ed informace o sv\u00e9m stavu a \u010dinnosti. Jeho pochopen\u00ed je prvn\u00edm krokem k zaveden\u00ed log managementu, monitoringu a anal\u00fdzy d\u011bn\u00ed v IT prost\u0159ed\u00ed a v d\u016fsledku i k dosa\u017een\u00ed efektivn\u011bj\u0161\u00edho a bezpe\u010dn\u011bj\u0161\u00edho fungov\u00e1n\u00ed organizace.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Tento \u010dl\u00e1nek vysv\u011btluje, co je syslog, jak funguje, kde se pou\u017e\u00edv\u00e1, jak\u00e9 m\u00e1 slabiny a jak jej lze roz\u0161\u00ed\u0159it tak, aby podporoval bezpe\u010dnost, zaji\u0161t\u011bn\u00ed hladk\u00e9ho chodu IT i soulad s p\u0159edpisy (<a href=\"https:\/\/logmanager.com\/cs\/?p=3680\">compliance<\/a>).<\/p>\n\n\n<div class=\"flex items-start gap-4 lg:gap-6 bg-white rounded-2xl lg:rounded-24 p-6 pr-8 lg:p-8 lg:pr-10 my-6 lg:my-10\">\n            <div class=\"shrink-0 size-7\">\n            <svg width=\"28\" height=\"28\" viewBox=\"0 0 28 28\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n                <g clip-path=\"url(#clip0_2972_5339)\">\n                <path d=\"M14.0025 28.0049C21.7358 28.0049 28.0049 21.7358 28.0049 14.0025C28.0049 6.26912 21.7358 0 14.0025 0C6.26912 0 0 6.26912 0 14.0025C0 21.7358 6.26912 28.0049 14.0025 28.0049Z\" fill=\"#00E24A\"\/>\n                <path d=\"M12.9659 20V11.2727H15.3864V20H12.9659ZM14.1818 10.1477C13.822 10.1477 13.5133 10.0284 13.2557 9.78977C13.0019 9.54735 12.875 9.25758 12.875 8.92045C12.875 8.58712 13.0019 8.30114 13.2557 8.0625C13.5133 7.82008 13.822 7.69886 14.1818 7.69886C14.5417 7.69886 14.8485 7.82008 15.1023 8.0625C15.3598 8.30114 15.4886 8.58712 15.4886 8.92045C15.4886 9.25758 15.3598 9.54735 15.1023 9.78977C14.8485 10.0284 14.5417 10.1477 14.1818 10.1477Z\" fill=\"white\"\/>\n                <\/g>\n                <defs>\n                <clipPath id=\"clip0_2972_5339\">\n                <rect width=\"28\" height=\"28.0049\" fill=\"white\"\/>\n                <\/clipPath>\n                <\/defs>\n            <\/svg>\n        <\/div>\n    \n    <div class=\"infobox-content leading-normal\"><p><strong>TL;DR<\/strong><\/p>\n<p>Syslog je nejpou\u017e\u00edvan\u011bj\u0161\u00ed protokol pro centralizaci log\u016f z r\u016fznorod\u00fdch IT zdroj\u016f. Umo\u017e\u0148uje shroma\u017e\u010fovat z\u00e1znamy ze server\u016f, s\u00ed\u0165ov\u00fdch za\u0159\u00edzen\u00ed, slu\u017eeb a aplikac\u00ed i bezpe\u010dnostn\u00edch n\u00e1stroj\u016f do jednoho m\u00edsta (syslog serveru), kde je lze vyhled\u00e1vat, analyzovat a archivovat.<\/p>\n<p>Syslog je z\u00e1kladem efektivn\u00edho <a href=\"https:\/\/logmanager.com\/cs\/blog\/log-management\/log-management-best-practices\/\">log managementu<\/a>, proto\u017ee umo\u017e\u0148uje IT specialist\u016fm monitorovat IT prost\u0159ed\u00ed, analyzovat a \u0159e\u0161it provozn\u00ed i bezpe\u010dnostn\u00ed probl\u00e9my a poskytovat data d\u016fle\u017eit\u00e1 pro napln\u011bn\u00ed compliance po\u017eadavk\u016f.<\/p>\n<\/div>\n<\/div>\n\n\n\n<h2 class=\"wp-block-heading\">Co je to syslog<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Syslog je univerz\u00e1ln\u00ed protokol pro zaznamen\u00e1v\u00e1n\u00ed a p\u0159ed\u00e1v\u00e1n\u00ed syst\u00e9mov\u00fdch informac\u00ed a ud\u00e1lost\u00ed mezi za\u0159\u00edzen\u00edmi v s\u00edti.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Jedn\u00e1 se o nejroz\u0161\u00ed\u0159en\u011bj\u0161\u00ed univerz\u00e1ln\u00ed jazyk, kter\u00fd umo\u017e\u0148uje router\u016fm, switch\u016fm, firewall\u016fm, Linuxov\u00fdm a Unix server\u016fm, a mnoha dal\u0161\u00edm syst\u00e9m\u016fm generovat, p\u0159en\u00e1\u0161et a ukl\u00e1dat logy, a to v jednotn\u00e9m a snadno analyzovateln\u00e9m form\u00e1tu. Typicky se takov\u00e9 logy odes\u00edlaj\u00ed do jednotn\u00e9ho \u00falo\u017ei\u0161t\u011b, tzv. syslog serveru, nap\u0159\u00edklad centralizovan\u00fd syst\u00e9m pro spr\u00e1vu log\u016f, typu Logmanager, kde je pak mo\u017en\u00e9 data prohled\u00e1vat, vizualizovat, analyzovat, a dlouhodob\u011b ulo\u017eit.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pokud hovo\u0159\u00edme o syslogu, odkazujeme t\u00edm bu\u010f na:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>protokol<\/strong>, kter\u00fd definuje form\u00e1t a strukturu log\u016f p\u0159en\u00e1\u0161en\u00fdch mezi odes\u00edlatelem a p\u0159\u00edjemcem,&nbsp;<\/li>\n\n\n\n<li><strong>zpr\u00e1vu<\/strong> ve standardizovan\u00e9m syslog form\u00e1tu,<\/li>\n\n\n\n<li>nebo obecn\u011b na<strong> framework<\/strong>, kter\u00fd umo\u017e\u0148uje r\u016fznorod\u00fdm syst\u00e9m\u016fm odes\u00edlat ud\u00e1losti na centr\u00e1ln\u00ed syslog server.&nbsp;<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Jak syslog funguje?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Syslog je postaven na t\u0159\u00edvrstv\u00e9 architektu\u0159e: <strong>aplika\u010dn\u00ed, transportn\u00ed a vrstv\u011b odpov\u00eddaj\u00edc\u00ed za sb\u011br\/ulo\u017een\u00ed log\u016f<\/strong>. Hlavn\u00ed komponenty Syslog frameworku tedy jsou:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Syslog odes\u00edlatel (klient) <\/strong>\u2013 Aplikace, syst\u00e9my nebo syst\u00e9mov\u00e9 komponenty, kter\u00e9 generuj\u00ed logy podle standardu syslog a odes\u00edlaj\u00ed je na syslog server. Ur\u010duj\u00ed jejich obsah, \u00farove\u0148 z\u00e1va\u017enosti (severitu) a dal\u0161\u00ed metadata. V praxi se nej\u010dast\u011bji jedn\u00e1 o firewally, servery, opera\u010dn\u00ed syst\u00e9my, s\u00ed\u0165ov\u00e9 prvky, bezpe\u010dnostn\u00ed n\u00e1stroje atd.<\/li>\n\n\n\n<li><strong>Transportn\u00ed vrstva <\/strong>\u2013<strong> <\/strong>Zaji\u0161\u0165uje p\u0159enos zpr\u00e1v na centr\u00e1ln\u00ed server pomoc\u00ed protokol\u016f UDP, TCP nebo TLS. UDP je nejrychlej\u0161\u00ed a nej\u010dast\u011bji pou\u017e\u00edvan\u00fd, zat\u00edmco TCP a TLS poskytuj\u00ed spolehliv\u011bj\u0161\u00ed a bezpe\u010dn\u011bj\u0161\u00ed p\u0159enos.<\/li>\n\n\n\n<li><strong>Syslog server <\/strong>\u2013<strong> <\/strong>Centralizovan\u00fd syst\u00e9m pro spr\u00e1vu log\u016f, kter\u00fd p\u0159ij\u00edm\u00e1 zpr\u00e1vy od v\u00edce zdroj\u016f, umo\u017e\u0148uje jejich filtrov\u00e1n\u00ed, p\u0159\u00edpadn\u011b anal\u00fdzu, a ulo\u017een\u00ed. V n\u011bkter\u00fdch p\u0159\u00edpadech m\u016f\u017ee na z\u00e1klad\u011b definovan\u00fdch pravidel tak\u00e9 generovat upozorn\u011bn\u00ed.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Jak vypad\u00e1 syslog zpr\u00e1va?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Syslog zpr\u00e1va je v strukturovan\u00fd textov\u00fd z\u00e1znam, kter\u00fd m\u016f\u017ee obsahovat \u0159adu parametr\u016f, mezi nimi\u017e nejb\u011b\u017en\u011bji najdeme n\u00e1sleduj\u00edc\u00ed:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>PRI (priority)<\/strong> \u2013 \u010d\u00edseln\u00e1 hodnota kter\u00e1 je kombinac\u00ed zdroje nebo typu slu\u017eby (facility) a z\u00e1va\u017enosti ud\u00e1losti (severity). Tento \u00fadaj je d\u016fle\u017eit\u00fd nap\u0159\u00edklad pro log management syst\u00e9my, kter\u00e9 d\u00edky n\u011bmu klasifikuj\u00ed typ ud\u00e1losti.<\/li>\n\n\n\n<li><strong>version<\/strong> \u2013 ozna\u010den\u00ed verze protokolu syslog.<\/li>\n\n\n\n<li><strong>timestamp (\u010dasov\u00e1 zna\u010dka)<\/strong> \u2013 ozna\u010duje datum a \u010das, kdy byl log vytvo\u0159en.<\/li>\n\n\n\n<li><strong>hostname nebo IP adresa<\/strong> \u2013 identifikuje za\u0159\u00edzen\u00ed \u010di hostitele, kter\u00fd zpr\u00e1vu vygeneroval.<\/li>\n\n\n\n<li><strong>app-name<\/strong> \u2013 identifikuje za\u0159\u00edzen\u00ed nebo aplikaci a pom\u00e1h\u00e1 analytik\u016fm rychle identifikovat zdroj ud\u00e1losti.<\/li>\n\n\n\n<li><strong>procID (ID procesu)<\/strong> &#8211;<strong> <\/strong>Identifik\u00e1tor procesu. Zm\u011bna t\u00e9to hodnoty signalizuje p\u0159eru\u0161en\u00ed kontinuity v syslog reportov\u00e1n\u00ed.<\/li>\n\n\n\n<li><strong>structured-data<\/strong> \u2013 Toto pole je jedn\u00edm ze z\u00e1sadn\u00edch vylep\u0161en\u00ed, kter\u00e9 p\u0159inesl standard RFC 5424. Pomoc\u00ed dvojic kl\u00ed\u010d\u2013hodnota podporuje roz\u0161\u00ed\u0159en\u00ed syslogu specifick\u00e1 pro jednotliv\u00e9 dodavatele. V s d\u016fsledku umo\u017e\u0148uje spolehliv\u00e9 parsov\u00e1n\u00ed.<\/li>\n\n\n\n<li><strong>MSG (message)<\/strong> \u2013 obsahuje samotnou zpr\u00e1vu nebo popis ud\u00e1losti.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Takov\u00e1 syslog zpr\u00e1va pak m\u016f\u017ee vypadat nap\u0159\u00edklad takto:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em>&lt;34&gt;1 2026-02-25T14:32:18+01:00 firewall01.example.com sshd 4821 ID47 [exampleSDID@32473 eventID=&#8220;1024&#8243; user=&#8220;admin&#8220; srcIP=&#8220;192.168.1.50&#8243;] Failed password attempt for user admin from 192.168.1.50 port 51422<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>Pozn\u00e1mka:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em>V sou\u010dasnosti se nej\u010dast\u011bji pou\u017e\u00edvaj\u00ed dva form\u00e1ty syslogu: RFC 3164 (BSD Syslog) a RFC 5424 (modern\u00ed, strukturovan\u00fd form\u00e1t). Prvn\u00ed z nich je u\u017e dnes zastaralej\u0161\u00ed, nicm\u00e9n\u011b st\u00e1le se pou\u017e\u00edv\u00e1 d\u00edky sv\u00e9 jednoduchosti a flexibilit\u011b. RFC 5424 je ji\u017e modern\u00ed form\u00e1t syslogu umo\u017e\u0148uj\u00edc\u00ed poskytovat detailn\u011bj\u0161\u00ed a strukturovan\u00e9 informace. D\u00edky tomu pak mohou nap\u0159\u00edklad log management n\u00e1stroje snadn\u011bji parsovat jednotliv\u00e1 pole zpr\u00e1v a SIEM syst\u00e9my zase l\u00e9pe korelovat ud\u00e1losti.<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">V praxi je ale b\u011b\u017en\u00e9, \u017ee ka\u017ed\u00fd v\u00fdrobce za\u0159\u00edzen\u00ed\/syst\u00e9mu\/aplikace vytv\u00e1\u0159\u00ed syslog zpr\u00e1vu jin\u00fdm zp\u016fsobem, tedy s r\u016fzn\u00fdmi polo\u017ekami a jinak popsan\u00fdmi z\u00e1znamy o ud\u00e1lostech. V d\u016fsledku se pak m\u016f\u017ee jednat o velmi komplexn\u00ed textov\u00fd \u0159et\u011bzec, jako je nap\u0159\u00edklad tento log z firewallu:<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"600\" src=\"https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/raw-syslog-example.png.webp\" alt=\"raw syslog example\" class=\"wp-image-5917\" srcset=\"https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/raw-syslog-example.png.webp 1024w, https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/raw-syslog-example.png-300x176.webp 300w, https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/raw-syslog-example.png-768x450.webp 768w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"has-xs-font-size wp-block-paragraph\"><em>Obr. 1: P\u0159\u00edklad toho, jak m\u016f\u017ee vypadat surov\u00fd syslog z\u00e1znam pod\u00e1vaj\u00edc\u00ed informace o ud\u00e1lostech ze syst\u00e9mu.<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Detailn\u011bj\u0161\u00ed popis jednotliv\u00fdch parametr\u016f (pol\u00ed) syslogu je k dispozici na str\u00e1nk\u00e1ch <a href=\"https:\/\/datatracker.ietf.org\/doc\/html\/rfc5424#page-9\" target=\"_blank\" rel=\"noopener\">IETF<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Je proto d\u016fle\u017eit\u00e9 m\u00edt <a href=\"https:\/\/logmanager.com\/cs\/reseni\/log-management\/\">n\u00e1stroj pro spr\u00e1vu log\u016f<\/a>, kter\u00fd zpr\u00e1vy dok\u00e1\u017ee parsovat a n\u00e1sledn\u011b zobrazit v srozumiteln\u011bj\u0161\u00ed podob\u011b (obvykle formou tabulky nebo pomoc\u00ed vizualizac\u00ed pro agregovan\u00e1 data).<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pro\u010d je syslog d\u016fle\u017eit\u00fd?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Syslog \u0159e\u0161\u00ed z\u00e1sadn\u00ed probl\u00e9m observability heterogenn\u00edho prost\u0159ed\u00ed. Poskytuje toti\u017e spole\u010dn\u00fd jazyk, kter\u00fd propojuje r\u016fznorod\u00e9 technologie a umo\u017e\u0148uje centralizovanou spr\u00e1vu log\u016f v komplexn\u00edch IT prost\u0159ed\u00edch s v\u00edce dodavateli\/v\u00fdrobci.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Jin\u00fdmi slovy, bez probl\u00e9m\u016f funguje nap\u0159\u00ed\u010d platformami, od s\u00ed\u0165ov\u00fdch za\u0159\u00edzen\u00ed (nap\u0159\u00edklad Cisco, Fortinet) p\u0159es opera\u010dn\u00ed syst\u00e9my (Linux, Unix, Windows), bezpe\u010dnostn\u00ed n\u00e1stroje, aplikace a slu\u017eby (Apache, Nginx, datab\u00e1ze), a\u017e po cloudov\u00e9 slu\u017eby a dal\u0161\u00ed. Pracuje s minim\u00e1ln\u00ed re\u017eijn\u00ed z\u00e1t\u011b\u017e\u00ed, umo\u017e\u0148uje nastavit syst\u00e9m upozorn\u011bn\u00ed na nestandardn\u00ed nebo ne\u017e\u00e1douc\u00ed ud\u00e1losti a konsolidovat logy do jednotn\u00e9ho rozhran\u00ed pro lep\u0161\u00ed viditelnost.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">To s sebou nese \u0159adu benefit\u016f pro provozn\u00ed a bezpe\u010dnostn\u00ed specialisty, ale i pro ty, kte\u0159\u00ed maj\u00ed na starosti compliance organizace.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Centralizovan\u00e1 viditelnost<\/strong> \u2013 d\u00edky syslogu je mo\u017en\u00e1 agregovatlogy z r\u016fznorod\u00fdch zdroj\u016f do jednoho centr\u00e1ln\u00edho pohledu.<\/li>\n\n\n\n<li><strong>\u0158e\u0161en\u00ed probl\u00e9m\u016f a diagnostika <\/strong>\u2013<strong> <\/strong>korelace ud\u00e1losti nap\u0159\u00ed\u010d syst\u00e9my umo\u017e\u0148uje rychle identifikovat hlavn\u00ed p\u0159\u00ed\u010dinu v\u00fdpadk\u016f nebo v\u00fdkonnostn\u00edch probl\u00e9m\u016f.<\/li>\n\n\n\n<li><strong>Bezpe\u010dnost a compliance <\/strong>\u2013<strong> <\/strong>poskytuje auditn\u00ed stopu bezpe\u010dnostn\u00edch incident\u016f (nap\u0159. ne\u00fasp\u011b\u0161n\u00e1 p\u0159ihl\u00e1\u0161en\u00ed nebo zm\u011bny politik) a pom\u00e1h\u00e1 plnit regulatorn\u00ed po\u017eadavky, kter\u00e9 vy\u017eaduj\u00ed sb\u011br a uchov\u00e1v\u00e1n\u00ed log\u016f (nap\u0159. <a href=\"https:\/\/logmanager.com\/cs\/blog\/it-compliance\/role-log-managementu-a-siem-v-novem-zakonu-o-kyberneticke-bezpecnosti\/\">ZoKB<\/a>, PCI-DSS, DORA).<\/li>\n\n\n\n<li><strong>Proaktivn\u00ed monitoring <\/strong>\u2013<strong> <\/strong>umo\u017e\u0148uje nastavit upozorn\u011bn\u00ed na z\u00e1klad\u011b konkr\u00e9tn\u00edch ud\u00e1lost\u00ed, tak\u017ee t\u00fdmy mohou reagovat d\u0159\u00edve, ne\u017e probl\u00e9my ovlivn\u00ed u\u017eivatele.<\/li>\n\n\n\n<li><strong>Forenzn\u00ed anal\u00fdza <\/strong>\u2013<strong> <\/strong>s pomoc\u00ed n\u00e1stroje pro log management lze ukl\u00e1dat historick\u00e9 logy pro zp\u011btnou investigaci bezpe\u010dnostn\u00edch incident\u016f nebo provozn\u00edch ud\u00e1lost\u00ed.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Syslog tak transformuje izolovan\u00e9 technick\u00e9 ud\u00e1losti na vyu\u017eiteln\u00e9 informace, kter\u00e9 podporuj\u00ed provozn\u00ed stabilitu, bezpe\u010dnostn\u00ed odolnost a shodu s regulacemi nebo odv\u011btvov\u00fdmi standardy.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Omezen\u00ed form\u00e1tu syslog<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">P\u0159esto\u017ee je syslog \u0161iroce podporovan\u00fd, relativn\u011b snadno implementovateln\u00fd a m\u00e1 \u0159adu v\u00fdhod, jsou s n\u00edm spojeny i n\u011bkter\u00e1 omezen\u00ed. Ta mohou b\u00fdt problematick\u00e1 zejm\u00e9na v rozs\u00e1hl\u00fdch prost\u0159ed\u00edch nebo t\u011bch se striktn\u00edmi bezpe\u010dnostn\u00edmi politikami.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>1.<\/strong> <strong>Nespolehliv\u00e9 doru\u010dov\u00e1n\u00ed p\u0159i pou\u017eit\u00ed UDP<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Syslog defaultn\u011b vyu\u017e\u00edv\u00e1 jako transportn\u00ed protokol UDP. Ten je rychl\u00fd a m\u00e1 n\u00edzkou re\u017eii, ale negarantuje doru\u010den\u00ed, po\u0159ad\u00ed ani integritu zpr\u00e1v.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pokud se logov\u00e1 zpr\u00e1va b\u011bhem p\u0159enosu ztrat\u00ed, neprob\u00edh\u00e1 \u017e\u00e1dn\u00e9 opakov\u00e1n\u00ed ani potvrzen\u00ed a ztr\u00e1ta obvykle z\u016fstane bez pov\u0161imnut\u00ed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">V p\u0159\u00edpad\u011b kritick\u00fdch ud\u00e1lost\u00ed, kde ztr\u00e1ta dat nen\u00ed akceptovateln\u00e1, je nutn\u00e9 pou\u017e\u00edt TCP, ide\u00e1ln\u011b \u0161ifrovan\u00e9 pomoc\u00ed TLS (verze 1.2 a vy\u0161\u0161\u00ed). Tyto protokoly v\u0161ak sni\u017euj\u00ed n\u011bkter\u00e9 v\u00fdhody syslogu v podob\u011b rychlosti a jednoduchosti.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>2.<\/strong> <strong>Nedostatek jednotn\u00e9 struktury<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Zpr\u00e1vy ve form\u00e1tu syslog typicky obsahuj\u00ed prioritu, \u010dasov\u00e9 raz\u00edtko, hostname a voln\u00fd text zpr\u00e1vy.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Obsah t\u011bla zpr\u00e1vy je v\u0161ak nestandardizovan\u00fd, resp. ka\u017ed\u00fd v\u00fdrobce nebo za\u0159\u00edzen\u00ed jej m\u016f\u017ee form\u00e1tovat odli\u0161n\u011b. Nap\u0159\u00edklad dva firewally mohou stejnou ud\u00e1lost zaznamenat zcela jin\u00fdmi textov\u00fdmi \u0159et\u011bzci.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Tato nejednotnost zt\u011b\u017euje vyhled\u00e1v\u00e1n\u00ed, filtrov\u00e1n\u00ed i anal\u00fdzu dat bez dodate\u010dn\u00e9ho zpracov\u00e1n\u00ed (transformace dat) pomoc\u00ed log management n\u00e1stroje.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>3. Absence vestav\u011bn\u00fdch metadat a kontextu<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Na rozd\u00edl od strukturovan\u00fdch form\u00e1t\u016f, jako je JSON nebo CEF, syslog nativn\u011b nepodporuje pole typu kl\u00ed\u010d\u2013hodnota.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Neexistuje standardizovan\u00fd zp\u016fsob, jak zahrnout nap\u0159\u00edklad ID u\u017eivatele, geoloka\u010dn\u00ed \u00fadaje nebo typ ud\u00e1losti. To n\u00e1sledn\u011b komplikuje anal\u00fdzu a obecn\u011b pochopen\u00ed kontextu ud\u00e1losti. Nicm\u00e9n\u011b, je mo\u017en\u00e9 o tyto informace logy obohatit, nap\u0159\u00edklad pomoc\u00ed napojen\u00ed na asset management n\u00e1stroje.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>4. Nekonzistence \u010dasov\u00fdch \u00fadaj\u016f<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Star\u0161\u00ed standardy syslogu, nap\u0159\u00edklad RFC 3164, neobsahuj\u00ed podporu \u010dasov\u00fdch p\u00e1sem v \u010dasov\u00e9m raz\u00edtku. Zaznamen\u00e1vaj\u00ed pouze m\u011bs\u00edc, den a lok\u00e1ln\u00ed \u010das, bez uveden\u00ed \u010dasov\u00e9 z\u00f3ny \u010di roku. To m\u016f\u017ee zp\u016fsobit komplikace p\u0159i agregaci log\u016f ze syst\u00e9m\u016f v r\u016fzn\u00fdch regionech a zt\u00ed\u017eit p\u0159esnou rekonstrukci \u010dasov\u00e9 osy p\u0159i vy\u0161et\u0159ov\u00e1n\u00ed incident\u016f.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>5. Chyb\u011bj\u00edc\u00ed nativn\u00ed bezpe\u010dnostn\u00ed prvky<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Star\u0161\u00ed verze syslogu (p\u0159ed rokem 2009) neobsahuj\u00ed \u017e\u00e1dn\u00e9 vestav\u011bn\u00e9 bezpe\u010dnostn\u00ed mechanismy. Zpr\u00e1vy jsou p\u0159en\u00e1\u0161eny jako prost\u00fd text, bez \u0161ifrov\u00e1n\u00ed, ov\u011b\u0159en\u00ed odes\u00edlatele \u010di ochrany proti manipulaci.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pokud nen\u00ed pou\u017eit zabezpe\u010den\u00fd p\u0159enos, nap\u0159\u00edklad TLS nad TCP, m\u016f\u017ee b\u00fdt syslogov\u00e1 komunikace zachycena, podvr\u017eena nebo upravena b\u011bhem p\u0159enosu, co\u017e p\u0159edstavuje v\u00fdznamn\u00e9 riziko zejm\u00e9na v prost\u0159ed\u00edch pracuj\u00edc\u00edch s citliv\u00fdmi daty.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Alternativy syslogu<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">V p\u0159edch\u00e1zej\u00edc\u00ed kapitole jsme se dotkli skute\u010dnosti, \u017ee ka\u017ed\u00fd v\u00fdrobce definuje strukturu syslog zpr\u00e1vy jinak, co\u017e vytv\u00e1\u0159\u00ed nekonzistence komplikuj\u00edc\u00ed pr\u00e1ci s logy. Podoba syslogu tak m\u016f\u017ee b\u00fdt, p\u0159edev\u0161\u00edm v p\u0159\u00edpad\u011b star\u0161\u00ed verze, zdroj od zdroje velmi odli\u0161n\u00e1.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Na tuto skute\u010dnost se sna\u017e\u00ed reagovat form\u00e1ty alternativn\u00ed syslogu, kter\u00e9 tento nedostatek \u0159e\u0161\u00ed v\u011bt\u0161\u00ed konzistenc\u00ed, p\u0159ehlednost\u00ed a lep\u0161\u00ed podporou pro automatiza\u010dn\u00ed n\u00e1stroje typu SIEM a log management.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pod\u00edvejme se tedy na nej\u010dast\u011bj\u0161\u00ed alternativy syslogu..<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1. Form\u00e1t JSON<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">JavaScript Object Notation (JSON) je form\u00e1t zalo\u017een\u00fd na dvojic\u00edch kl\u00ed\u010d\u2013hodnota, nap\u0159\u00edklad \u201euser\u201c a \u201eip\u201c jako kl\u00ed\u010de a konkr\u00e9tn\u00ed u\u017eivatelsk\u00e9 jm\u00e9no a IP adresa jako hodnoty.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">B\u011b\u017en\u011b jej pou\u017e\u00edvaj\u00ed aplikace, API a cloud-native platformy, proto\u017ee je \u010diteln\u00fd pro \u010dlov\u011bka a z\u00e1rove\u0148 usnad\u0148uje parsov\u00e1n\u00ed zpr\u00e1v.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">JSON umo\u017e\u0148uje jasn\u011b definovat jednotliv\u00e1 pole a snadno je extrahovat, co\u017e jej \u010din\u00ed vhodn\u011bj\u0161\u00edm pro automatizovanou anal\u00fdzu ne\u017e syslog, kter\u00fd typicky zaznamen\u00e1v\u00e1 zpr\u00e1vy jako voln\u00fd text.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"253\" src=\"https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/JSON-format-example-1024x253.png\" alt=\"JSON form\u00e1t uk\u00e1zka\" class=\"wp-image-5934\" srcset=\"https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/JSON-format-example-1024x253.png 1024w, https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/JSON-format-example-300x74.png 300w, https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/JSON-format-example-768x190.png 768w, https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/JSON-format-example.png 1341w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"has-xs-font-size wp-block-paragraph\"><em>Obr. 2: Uk\u00e1zka JSON form\u00e1tu (Windows Event log p\u0159eveden\u00fd na JSON)<\/em><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Windows Event Logs<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Syst\u00e9my Windows nativn\u011b nepou\u017e\u00edvaj\u00ed form\u00e1t syslog. Generuj\u00ed logy ve vlastn\u00edm bin\u00e1rn\u00edm form\u00e1tu spravovan\u00e9m opera\u010dn\u00edm syst\u00e9mem.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Tyto logy vy\u017eaduj\u00ed speci\u00e1ln\u00ed n\u00e1stroje nebo agenty pro jejich \u010dten\u00ed. Pro centralizaci Windows log\u016f spole\u010dn\u011b se syslogem organizace \u010dasto vyu\u017e\u00edvaj\u00ed kolektory log\u016f, kter\u00e9 je p\u0159ev\u00e1d\u011bj\u00ed do syslogu nebo jin\u00e9ho standardizovan\u00e9ho form\u00e1tu.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"827\" height=\"608\" src=\"https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/windows-event-log-example.png\" alt=\"p\u0159\u00edklad windows event logu\" class=\"wp-image-5932\" srcset=\"https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/windows-event-log-example.png 827w, https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/windows-event-log-example-300x221.png 300w, https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/windows-event-log-example-768x565.png 768w\" sizes=\"auto, (max-width: 827px) 100vw, 827px\" \/><\/figure>\n\n\n\n<p class=\"has-xs-font-size wp-block-paragraph\"><em>Obr. 3: P\u0159\u00edklad toho, jak m\u016f\u017ee vypadat Windows Event log<\/em><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. CEF a LEEF<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Common Event Format (CEF) a Log Event Extended Format (LEEF) jsou form\u00e1ty ur\u010den\u00e9 p\u0159edev\u0161\u00edm pro zaznamen\u00e1v\u00e1n\u00ed bezpe\u010dnostn\u00edch ud\u00e1lost\u00ed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Obsahuj\u00ed p\u0159eddefinovan\u00e1 pole, nap\u0159\u00edklad zdrojovou IP adresu, u\u017eivatelsk\u00e9 jm\u00e9no nebo typ ud\u00e1losti, co\u017e usnad\u0148uje jejich parsov\u00e1n\u00ed a korelaci v SIEM platform\u00e1ch.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Oba form\u00e1ty jsou \u010dasto p\u0159en\u00e1\u0161eny uvnit\u0159 syslog zpr\u00e1vy, \u010d\u00edm\u017e kombinuj\u00ed univerz\u00e1lnost syslogu s vy\u0161\u0161\u00ed m\u00edrou strukturovanosti samotn\u00e9ho obsahu zpr\u00e1vy.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"60\" src=\"https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/CEF-format-example-1024x60.png\" alt=\"CEF form\u00e1t\" class=\"wp-image-5936\" srcset=\"https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/CEF-format-example-1024x60.png 1024w, https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/CEF-format-example-300x18.png 300w, https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/CEF-format-example-768x45.png 768w, https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/CEF-format-example.png 1519w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"has-sm-font-size wp-block-paragraph\"><em>Obr. 4: Uk\u00e1zka CEF form\u00e1tu<\/em><\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"63\" src=\"https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/LEEF-format-example-1024x63.png\" alt=\"LEEF form\u00e1t\" class=\"wp-image-5938\" srcset=\"https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/LEEF-format-example-1024x63.png 1024w, https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/LEEF-format-example-300x19.png 300w, https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/LEEF-format-example-768x47.png 768w, https:\/\/logmanager.com\/wp-content\/uploads\/2025\/08\/LEEF-format-example.png 1522w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"has-xs-font-size wp-block-paragraph\"><em>Obr. 5: Form\u00e1t LEEF<\/em><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Best practices pro logov\u00e1n\u00ed pomoc\u00ed syslogu<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Pro p\u0159ekon\u00e1n\u00ed tradi\u010dn\u00edch omezen\u00ed syslogu se v praxi osv\u011bd\u010dily n\u00e1sleduj\u00edc\u00ed postupy:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>\u2192<\/strong>&nbsp;<strong>Pou\u017e\u00edvejte syslog p\u0159es TLS (port 6514)<\/strong> \u2013 V p\u0159\u00edpad\u011b citliv\u00fdch dat nebo z d\u016fvodu striktn\u00edch bezpe\u010dnostn\u00edch pravidel vy\u017eadovan\u00fdch p\u0159edpisy a standardy (compliance) preferujte RFC 5425 (syslog p\u0159es TLS), kter\u00fd zaji\u0161\u0165uje \u0161ifrov\u00e1n\u00ed a integritu p\u0159enosu.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><strong>\u2192<\/strong><\/strong> <strong>Up\u0159ednostn\u011bte TCP p\u0159ed UDP<\/strong> \u2013 Pro kritick\u00e9 logy pou\u017e\u00edvejte transport p\u0159es TCP, kter\u00fd garantuje doru\u010den\u00ed zpr\u00e1v, i kdy\u017e b\u011b\u017e\u00ed na standardn\u00edm portu 514.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><strong>\u2192<\/strong>&nbsp;<\/strong> <strong>Vyu\u017e\u00edvejte form\u00e1t RFC 5424<\/strong> \u2013 Pokud je to mo\u017en\u00e9, nastavte za\u0159\u00edzen\u00ed a aplikace tak, aby pou\u017e\u00edvaly modern\u00ed strukturovan\u00fd form\u00e1t. Ten umo\u017e\u0148uje lep\u0161\u00ed parsov\u00e1n\u00ed a pokro\u010dilej\u0161\u00ed analytiku.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><strong>\u2192<\/strong>&nbsp; Implementujte filtrov\u00e1n\u00ed a omezen\u00ed toku log\u016f<\/strong> \u2013 Na stran\u011b odes\u00edlatele nebo relay serveru filtrujte nepot\u0159ebn\u00e9 zpr\u00e1vy (nap\u0159. debug logy), abyste sn\u00ed\u017eili z\u00e1t\u011b\u017e s\u00edt\u011b, n\u00e1roky na \u00falo\u017ei\u0161t\u011b nebo licen\u010dn\u00ed poplatky syst\u00e9m\u016f, kter\u00e9 s logy pracuj\u00ed (typicky SIEM).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><strong>\u2192<\/strong>&nbsp; Pou\u017e\u00edvejte specializovan\u00e9 \u0159e\u0161en\u00ed pro spr\u00e1vu syslogu<\/strong> \u2013 Dedikovan\u00e9 n\u00e1stroje pro spr\u00e1vu log\u016f typu Logmanager umo\u017e\u0148uj\u00ed parsov\u00e1n\u00ed, ukl\u00e1d\u00e1n\u00ed, anal\u00fdzu a generov\u00e1n\u00ed upozorn\u011bn\u00ed, \u010d\u00edm\u017e transformuj\u00ed surov\u00e1 syslog data na vyu\u017eiteln\u00e9 informace.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Jak ze syslogu z\u00edskat maximum<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Syslog je nepostradateln\u00fdm n\u00e1strojem pro monitorov\u00e1n\u00ed syst\u00e9m\u016f, bezpe\u010dnostn\u00ed dohled a \u0159e\u0161en\u00ed probl\u00e9m\u016f. Jeho spr\u00e1va ale ve v\u011bt\u0161\u00edm m\u011b\u0159\u00edtku, p\u0159i sb\u011bru log\u016f z r\u016fzn\u00fdch zdroj\u016f, kter\u00e9 nav\u00edc loguj\u00ed r\u016fzn\u011b, vy\u017eaduje specializovan\u00fd n\u00e1stroj.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">P\u0159istupovat toti\u017e p\u0159i ne\u010dekan\u00fdch ud\u00e1lostech na jednotliv\u00e1 za\u0159\u00edzen\u00ed vy\u017eaduje znalost logov\u00e1n\u00ed jednotliv\u00fdch syst\u00e9m\u016f a v d\u016fsledku prodlu\u017euje reakci na incidenty.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">K tomu je k dispozici \u0159ada open-source (nap\u0159\u00edklad syslog-ng, Grafana Loki) i profesion\u00e1ln\u00edch komer\u010dn\u00edch platforem (Logmanager). Ty umo\u017e\u0148uj\u00ed prom\u011bnit syslog v n\u00e1stroj, kter\u00fd z\u00e1sadn\u011b pom\u00e1h\u00e1 p\u0159i \u0159e\u0161en\u00ed provozn\u00edch a bezpe\u010dnostn\u00edch probl\u00e9m\u016f i napln\u011bn\u00ed compliance po\u017eadavk\u016f. A to p\u0159edev\u0161\u00edm d\u00edky:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>P\u0159edp\u0159ipraven\u00fdm parser\u016fm<\/strong> pro r\u016fzn\u00e9 zdroje dat a syslog form\u00e1ty, d\u00edky kter\u00fdm je mo\u017en\u00e9 sb\u00edrat a normalizovat data nap\u0159\u00ed\u010d infrastrukturou.<\/li>\n\n\n\n<li><strong>Centralizovan\u00e9mu ukl\u00e1d\u00e1n\u00ed<\/strong> log\u016f pro anal\u00fdzu korelaci, kdy jsou v\u0161echny logy indexov\u00e1ny pro rychl\u00e9 fulltextov\u00e9 vyhled\u00e1v\u00e1n\u00ed a forenzn\u00ed \u0161et\u0159en\u00ed.<\/li>\n\n\n\n<li><strong>Vizualizaci dat<\/strong> pomoc\u00ed dashboard\u016f, graf\u016f a tabulek, kter\u00e9 usnad\u0148uj\u00ed orientaci v surov\u00fdch datech a anal\u00fdzu.<\/li>\n\n\n\n<li><strong>Syst\u00e9mu upozorn\u011bn\u00ed<\/strong> v re\u00e1ln\u00e9m \u010dase, d\u00edky kter\u00e9mu jsou na z\u00e1klad\u011b pravidel nestandardn\u00ed nebo kritick\u00e9 ud\u00e1losti okam\u017eit\u011b detekov\u00e1ny.<\/li>\n\n\n\n<li><strong>Dlouhodob\u00e9mu ulo\u017een\u00ed v bezpe\u010dn\u00e9m \u00falo\u017ei\u0161ti<\/strong>, \u010d\u00edm\u017e m\u00e1 organizace data chr\u00e1n\u011bna proti zm\u011bn\u00e1m, neopr\u00e1vn\u011bn\u00e9 manipulaci, a tedy i pro prok\u00e1z\u00e1n\u00ed souladu s p\u0159edpisy a regulacemi (ZoKB, PCI-DSS, ISO a dal\u0161\u00ed).<\/li>\n<\/ul>\n\n\n<div class=\"flex items-start gap-4 lg:gap-6 bg-white rounded-2xl lg:rounded-24 p-6 pr-8 lg:p-8 lg:pr-10 my-6 lg:my-10\">\n            <div class=\"shrink-0 size-7\">\n            <svg width=\"28\" height=\"28\" viewBox=\"0 0 28 28\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n                <g clip-path=\"url(#clip0_2972_5339)\">\n                <path d=\"M14.0025 28.0049C21.7358 28.0049 28.0049 21.7358 28.0049 14.0025C28.0049 6.26912 21.7358 0 14.0025 0C6.26912 0 0 6.26912 0 14.0025C0 21.7358 6.26912 28.0049 14.0025 28.0049Z\" fill=\"#00E24A\"\/>\n                <path d=\"M12.9659 20V11.2727H15.3864V20H12.9659ZM14.1818 10.1477C13.822 10.1477 13.5133 10.0284 13.2557 9.78977C13.0019 9.54735 12.875 9.25758 12.875 8.92045C12.875 8.58712 13.0019 8.30114 13.2557 8.0625C13.5133 7.82008 13.822 7.69886 14.1818 7.69886C14.5417 7.69886 14.8485 7.82008 15.1023 8.0625C15.3598 8.30114 15.4886 8.58712 15.4886 8.92045C15.4886 9.25758 15.3598 9.54735 15.1023 9.78977C14.8485 10.0284 14.5417 10.1477 14.1818 10.1477Z\" fill=\"white\"\/>\n                <\/g>\n                <defs>\n                <clipPath id=\"clip0_2972_5339\">\n                <rect width=\"28\" height=\"28.0049\" fill=\"white\"\/>\n                <\/clipPath>\n                <\/defs>\n            <\/svg>\n        <\/div>\n    \n    <div class=\"infobox-content leading-normal\"><p><strong>\u2192<\/strong>\u00a0Pokud si chcete vyzkou\u0161et profesion\u00e1ln\u00ed n\u00e1stroj pro spr\u00e1vu syslogu, m\u016f\u017eete prozkoumat mo\u017enosti Logmanageru pomoc\u00ed <a href=\"https:\/\/logmanager.com\/cs\/demo\/\">interaktivn\u00edho dema<\/a>, nebo si zarezervujte <a href=\"https:\/\/logmanager.com\/cs\/demo\/\">\u017eivou uk\u00e1zku<\/a> n\u00e1stroje s na\u0161\u00edm produktov\u00fdm specialistou.<\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Pr\u016fvodce protokolem syslog a jeho rol\u00ed p\u0159i spr\u00e1v\u011b log\u016f.<\/p>\n","protected":false},"author":4,"featured_media":4496,"parent":0,"template":"","learning_hub_tag":[],"class_list":["post-7163","learning_hub","type-learning_hub","status-publish","has-post-thumbnail","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/logmanager.com\/cs\/wp-json\/wp\/v2\/learning_hub\/7163","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/logmanager.com\/cs\/wp-json\/wp\/v2\/learning_hub"}],"about":[{"href":"https:\/\/logmanager.com\/cs\/wp-json\/wp\/v2\/types\/learning_hub"}],"author":[{"embeddable":true,"href":"https:\/\/logmanager.com\/cs\/wp-json\/wp\/v2\/users\/4"}],"version-history":[{"count":5,"href":"https:\/\/logmanager.com\/cs\/wp-json\/wp\/v2\/learning_hub\/7163\/revisions"}],"predecessor-version":[{"id":7168,"href":"https:\/\/logmanager.com\/cs\/wp-json\/wp\/v2\/learning_hub\/7163\/revisions\/7168"}],"wp:attachment":[{"href":"https:\/\/logmanager.com\/cs\/wp-json\/wp\/v2\/media?parent=7163"}],"wp:term":[{"taxonomy":"learning_hub_tag","embeddable":true,"href":"https:\/\/logmanager.com\/cs\/wp-json\/wp\/v2\/learning_hub_tag?post=7163"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}