mirror of
https://git.mirrors.martin98.com/https://github.com/SigNoz/signoz
synced 2025-07-25 07:24:24 +08:00
feat: azure monitoring docs (#5159)
* feat: azure monitoring docs * chore: mapped paths * chore: fixed instructions * fix: added central collector steps * fix: handle default azure steps, card alignment and reload issues * fix: removed return true --------- Co-authored-by: YounixM <myounis.ar@live.com>
This commit is contained in:
CheetoDa
GitHub
parent
b59d9c7b90
commit
8ff392bc96
1
frontend/public/Logos/azure-aks.svg
Normal file
1
frontend/public/Logos/azure-aks.svg
Normal file
@ -0,0 +1 @@
|
||||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 18 18"><defs><linearGradient id="a" x1="2.94" y1="3.74" x2="8.67" y2="3.74" gradientUnits="userSpaceOnUse"><stop offset="0" stop-color="#b77af4"/><stop offset="1" stop-color="#773adc"/></linearGradient><linearGradient id="b" x1="9.13" y1="3.79" x2="14.85" y2="3.79" gradientUnits="userSpaceOnUse"><stop offset="0" stop-color="#b77af4"/><stop offset="1" stop-color="#773adc"/></linearGradient><linearGradient id="c" x1=".01" y1="9.12" x2="5.73" y2="9.12" gradientUnits="userSpaceOnUse"><stop offset="0" stop-color="#b77af4"/><stop offset="1" stop-color="#773adc"/></linearGradient><linearGradient id="d" x1="6.18" y1="9.08" x2="11.9" y2="9.08" gradientUnits="userSpaceOnUse"><stop offset="0" stop-color="#b77af4"/><stop offset="1" stop-color="#773adc"/></linearGradient><linearGradient id="e" x1="12.35" y1="9.13" x2="18.08" y2="9.13" gradientUnits="userSpaceOnUse"><stop offset="0" stop-color="#b77af4"/><stop offset="1" stop-color="#773adc"/></linearGradient><linearGradient id="f" x1="2.87" y1="14.56" x2="8.6" y2="14.56" gradientUnits="userSpaceOnUse"><stop offset="0" stop-color="#b77af4"/><stop offset="1" stop-color="#773adc"/></linearGradient><linearGradient id="g" x1="9.05" y1="14.6" x2="14.78" y2="14.6" gradientUnits="userSpaceOnUse"><stop offset="0" stop-color="#b77af4"/><stop offset="1" stop-color="#773adc"/></linearGradient></defs><path fill="url(#a)" d="M5.8 1.22l-2.86.53v3.9l2.86.61 2.87-1.15V2.2L5.8 1.22z"/><path d="M5.91 6.2l2.62-1.06A.2.2 0 008.65 5V2.36a.21.21 0 00-.13-.18l-2.65-.9h-.12l-2.6.48a.2.2 0 00-.15.18v3.53a.19.19 0 00.15.19l2.63.55a.32.32 0 00.13-.01z" fill="none"/><path d="M2.94 1.75v3.9l2.89.61v-5zm1.22 3.6l-.81-.16v-3l.81-.13zm1.26.23l-.93-.15V2l.93-.16z" fill="#341a6e"/><path fill="url(#b)" d="M11.99 1.27l-2.86.53v3.9l2.86.61 2.86-1.16v-2.9l-2.86-.98z"/><path d="M9.13 1.8v3.9l2.87.61v-5zm1.21 3.6l-.81-.16v-3l.81-.13zm1.26.23l-.93-.15V2.05l.93-.17z" fill="#341a6e"/><path fill="url(#c)" d="M2.87 6.6l-2.86.53v3.9l2.86.61 2.87-1.15V7.58L2.87 6.6z"/><path d="M0 7.13V11l2.89.61v-5zm1.21 3.61l-.81-.17v-3l.81-.14zm1.27.26l-.93-.15V7.38l.93-.16z" fill="#341a6e"/><path fill="url(#d)" d="M9.04 6.56l-2.86.53v3.9l2.86.62 2.86-1.16V7.54l-2.86-.98z"/><path d="M6.18 7.09V11l2.88.61v-5zm1.21 3.61l-.81-.17v-3l.81-.14zm1.26.22l-.93-.15V7.34l.93-.16z" fill="#341a6e"/><path fill="url(#e)" d="M15.21 6.61l-2.86.53v3.9l2.86.61 2.87-1.15V7.59l-2.87-.98z"/><path d="M12.35 7.14V11l2.89.61v-5zm1.22 3.61l-.81-.17v-3l.81-.14zm1.26.22l-.93-.15V7.39l.93-.16z" fill="#341a6e"/><path fill="url(#f)" d="M5.73 12.04l-2.86.52v3.9l2.86.62 2.87-1.16v-2.9l-2.87-.98z"/><path d="M5.84 17l2.61-1a.18.18 0 00.12-.18v-2.6a.2.2 0 00-.13-.22l-2.64-.9a.17.17 0 00-.12 0l-2.6.47a.19.19 0 00-.16.19v3.54a.19.19 0 00.15.19L5.7 17a.23.23 0 00.14 0z" fill="none"/><path d="M2.87 12.56v3.9l2.89.62V12zm1.22 3.61L3.28 16v-3l.81-.14zm1.26.23l-.93-.15v-3.44l.93-.16z" fill="#341a6e"/><path fill="url(#g)" d="M11.91 12.08l-2.86.53v3.9l2.86.61 2.87-1.15v-2.91l-2.87-.98z"/><path d="M9.05 12.61v3.9l2.89.61v-5zm1.22 3.61l-.81-.17v-3l.81-.14zm1.26.22l-.93-.15v-3.43l.93-.16z" fill="#341a6e"/></svg>
|
||||
|
After Width: | Height: | Size: 3.1 KiB |
1
frontend/public/Logos/azure-app-service.svg
Normal file
1
frontend/public/Logos/azure-app-service.svg
Normal file
@ -0,0 +1 @@
|
||||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 18 18"><defs><linearGradient id="b" x1="4.4" y1="11.48" x2="4.37" y2="7.53" gradientUnits="userSpaceOnUse"><stop offset="0" stop-color="#ccc"/><stop offset="1" stop-color="#fcfcfc"/></linearGradient><linearGradient id="c" x1="10.13" y1="15.45" x2="10.13" y2="11.9" gradientUnits="userSpaceOnUse"><stop offset="0" stop-color="#ccc"/><stop offset="1" stop-color="#fcfcfc"/></linearGradient><linearGradient id="d" x1="14.18" y1="11.15" x2="14.18" y2="7.38" gradientUnits="userSpaceOnUse"><stop offset="0" stop-color="#ccc"/><stop offset="1" stop-color="#fcfcfc"/></linearGradient><radialGradient id="a" cx="13428.81" cy="3518.86" r="56.67" gradientTransform="matrix(.15 0 0 .15 -2005.33 -518.83)" gradientUnits="userSpaceOnUse"><stop offset=".18" stop-color="#5ea0ef"/><stop offset="1" stop-color="#0078d4"/></radialGradient></defs><path d="M14.21 15.72A8.5 8.5 0 013.79 2.28l.09-.06a8.5 8.5 0 0110.33 13.5" fill="url(#a)"/><path d="M6.69 7.23a13 13 0 018.91-3.58 8.47 8.47 0 00-1.49-1.44 14.34 14.34 0 00-4.69 1.1 12.54 12.54 0 00-4.08 2.82 2.76 2.76 0 011.35 1.1zM2.48 10.65a17.86 17.86 0 00-.83 2.62 7.82 7.82 0 00.62.92c.18.23.35.44.55.65a17.94 17.94 0 011.08-3.47 2.76 2.76 0 01-1.42-.72z" fill="#fff" opacity=".6"/><path d="M3.46 6.11a12 12 0 01-.69-2.94 8.15 8.15 0 00-1.1 1.45A12.69 12.69 0 002.24 7a2.69 2.69 0 011.22-.89z" fill="#f2f2f2" opacity=".55"/><circle cx="4.38" cy="8.68" r="2.73" fill="url(#b)"/><path d="M8.36 13.67a1.77 1.77 0 01.54-1.27 11.88 11.88 0 01-2.53-1.86 2.74 2.74 0 01-1.49.83 13.1 13.1 0 001.45 1.28 12.12 12.12 0 002.05 1.25 1.79 1.79 0 01-.02-.23zM14.66 13.88a12 12 0 01-2.76-.32.41.41 0 010 .11 1.75 1.75 0 01-.51 1.24 13.69 13.69 0 003.42.24A8.21 8.21 0 0016 13.81a11.5 11.5 0 01-1.34.07z" fill="#f2f2f2" opacity=".55"/><circle cx="10.13" cy="13.67" r="1.78" fill="url(#c)"/><path d="M12.32 8.93a1.83 1.83 0 01.61-1 25.5 25.5 0 01-4.46-4.14 16.91 16.91 0 01-2-2.92 7.64 7.64 0 00-1.09.42 18.14 18.14 0 002.15 3.18 26.44 26.44 0 004.79 4.46z" fill="#f2f2f2" opacity=".7"/><circle cx="14.18" cy="9.27" r="1.89" fill="url(#d)"/><path d="M17.35 10.54l-.35-.17-.3-.16h-.06l-.26-.21h-.07L16 9.8a1.76 1.76 0 01-.64.92c.12.08.25.15.38.22l.08.05.35.19.86.45a8.63 8.63 0 00.29-1.11z" fill="#f2f2f2" opacity=".55"/><circle cx="4.38" cy="8.68" r="2.73" fill="url(#b)"/><circle cx="10.13" cy="13.67" r="1.78" fill="url(#c)"/></svg>
|
||||
|
After Width: | Height: | Size: 2.3 KiB |
2
frontend/public/Logos/azure-blob-storage.svg
Normal file
2
frontend/public/Logos/azure-blob-storage.svg
Normal file
File diff suppressed because one or more lines are too long
|
After Width: | Height: | Size: 6.7 KiB |
1
frontend/public/Logos/azure-container-apps.svg
Normal file
1
frontend/public/Logos/azure-container-apps.svg
Normal file
@ -0,0 +1 @@
|
||||
<svg xmlns="http://www.w3.org/2000/svg" width="18" height="18" viewBox="0 0 18 18"><defs><linearGradient id="b27f1ad0-7d11-4247-9da3-91bce6211f32" x1="8.798" y1="8.703" x2="14.683" y2="8.703" gradientUnits="userSpaceOnUse"><stop offset="0.001" stop-color="#773adc" /><stop offset="1" stop-color="#552f99" /></linearGradient><linearGradient id="b2f92112-4ca9-4b17-a019-c9f26c1a4a8f" x1="5.764" y1="3.777" x2="5.764" y2="13.78" gradientUnits="userSpaceOnUse"><stop offset="0" stop-color="#a67af4" /><stop offset="0.999" stop-color="#773adc" /></linearGradient></defs><g id="b8a0486a-5501-4d92-b540-a766c4b3b548"><g><g><g><path d="M16.932,11.578a8.448,8.448,0,0,1-7.95,5.59,8.15,8.15,0,0,1-2.33-.33,2.133,2.133,0,0,0,.18-.83c.01,0,.03.01.04.01a7.422,7.422,0,0,0,2.11.3,7.646,7.646,0,0,0,6.85-4.28l.01-.01Z" fill="#32bedd" /><path d="M3.582,14.068a2.025,2.025,0,0,0-.64.56,8.6,8.6,0,0,1-1.67-2.44l1.04.23v.26a.6.6,0,0,0,.47.59l.14.03a6.136,6.136,0,0,0,.62.73Z" fill="#32bedd" /><path d="M12.352.958a2.28,2.28,0,0,0-.27.81c-.02-.01-.05-.02-.07-.03a7.479,7.479,0,0,0-3.03-.63,7.643,7.643,0,0,0-5.9,2.8l-.29.06a.6.6,0,0,0-.48.58v.46l-1.02.19A8.454,8.454,0,0,1,8.982.268,8.6,8.6,0,0,1,12.352.958Z" fill="#32bedd" /><path d="M16.872,5.7l-1.09-.38a6.6,6.6,0,0,0-.72-1.16c-.02-.03-.04-.05-.05-.07a2.083,2.083,0,0,0,.72-.45A7.81,7.81,0,0,1,16.872,5.7Z" fill="#32bedd" /><path d="M10.072,11.908l2.54.56L8.672,14.1c-.02,0-.03.01-.05.01a.154.154,0,0,1-.15-.15V3.448a.154.154,0,0,1,.15-.15.09.09,0,0,1,.05.01l4.46,1.56-3.05.57a.565.565,0,0,0-.44.54v5.4A.537.537,0,0,0,10.072,11.908Z" fill="#fff" /><g><g id="e918f286-5032-4942-ad29-ea17e6f1cc90"><path d="M1.1,5.668l1.21-.23v6.55l-1.23-.27-.99-.22a.111.111,0,0,1-.09-.12v-5.4a.12.12,0,0,1,.09-.12Z" fill="#a67af4" /></g><g><g id="a47a99dd-4d47-4c70-8c42-c5ac274ce496"><g><path d="M10.072,11.908l2.54.56L8.672,14.1c-.02,0-.03.01-.05.01a.154.154,0,0,1-.15-.15V3.448a.154.154,0,0,1,.15-.15.09.09,0,0,1,.05.01l4.46,1.56-3.05.57a.565.565,0,0,0-.44.54v5.4A.537.537,0,0,0,10.072,11.908Z" fill="url(#b27f1ad0-7d11-4247-9da3-91bce6211f32)" /><path d="M8.586,3.3,2.878,4.378a.177.177,0,0,0-.14.175V12.68a.177.177,0,0,0,.137.174L8.581,14.1a.176.176,0,0,0,.21-.174V3.478A.175.175,0,0,0,8.619,3.3Z" fill="url(#b2f92112-4ca9-4b17-a019-c9f26c1a4a8f)" /></g></g><polygon points="5.948 4.921 5.948 12.483 7.934 12.814 7.934 4.564 5.948 4.921" fill="#b796f9" opacity="0.5" /><polygon points="3.509 5.329 3.509 11.954 5.238 12.317 5.238 5.031 3.509 5.329" fill="#b796f9" opacity="0.5" /></g></g></g><path d="M16,2.048a1.755,1.755,0,1,1-1.76-1.76A1.756,1.756,0,0,1,16,2.048Z" fill="#32bedd" /><circle cx="4.65" cy="15.973" r="1.759" fill="#32bedd" /></g><path d="M18,6.689v3.844a.222.222,0,0,1-.133.2l-.766.316-3.07,1.268-.011,0a.126.126,0,0,1-.038,0,.1.1,0,0,1-.1-.1V5.234a.1.1,0,0,1,.054-.088l0,0,.019,0a.031.031,0,0,1,.019,0,.055.055,0,0,1,.034.008l.011,0,.012,0L17.05,6.2l.8.282A.213.213,0,0,1,18,6.689Z" fill="#773adc" /><path d="M13.959,5.14l-3.8.715a.118.118,0,0,0-.093.117v5.409a.118.118,0,0,0,.091.116l3.8.831a.115.115,0,0,0,.137-.09.109.109,0,0,0,0-.026V5.256a.117.117,0,0,0-.115-.118A.082.082,0,0,0,13.959,5.14Z" fill="#a67af4" /></g></g></svg>
|
||||
|
After Width: | Height: | Size: 3.1 KiB |
1
frontend/public/Logos/azure-functions.svg
Normal file
1
frontend/public/Logos/azure-functions.svg
Normal file
@ -0,0 +1 @@
|
||||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 18 18"><defs><linearGradient id="a" x1="-175.993" y1="-343.723" x2="-175.993" y2="-359.232" gradientTransform="matrix(1.156 0 0 1.029 212.573 370.548)" gradientUnits="userSpaceOnUse"><stop offset="0" stop-color="#fea11b"/><stop offset=".284" stop-color="#fea51a"/><stop offset=".547" stop-color="#feb018"/><stop offset=".8" stop-color="#ffc314"/><stop offset="1" stop-color="#ffd70f"/></linearGradient></defs><path d="M5.54 13.105l-.586.588a.267.267 0 01-.377 0L.223 9.353a.533.533 0 010-.755l.588-.59 4.732 4.718a.267.267 0 010 .378z" fill="#50e6ff"/><path d="M4.863 4.305l.59.588a.267.267 0 010 .378L.806 9.932l-.59-.589a.533.533 0 01-.001-.754l4.273-4.285a.267.267 0 01.376 0z" fill="#1490df"/><path d="M17.19 8.012l.588.59a.533.533 0 01-.001.754l-4.354 4.34a.267.267 0 01-.377 0l-.586-.587a.267.267 0 010-.377l4.732-4.718z" fill="#50e6ff"/><path d="M17.782 9.34l-.59.589-4.648-4.662a.267.267 0 010-.377l.59-.588a.267.267 0 01.378 0l4.273 4.286a.533.533 0 010 .753z" fill="#1490df"/><path d="M8.459 9.9H4.87a.193.193 0 01-.2-.181.166.166 0 01.018-.075L8.991 1.13a.206.206 0 01.186-.106h4.245a.193.193 0 01.2.181.165.165 0 01-.035.1L8.534 7.966h4.928a.193.193 0 01.2.181.176.176 0 01-.052.122l-8.189 8.519c-.077.046-.624.5-.356-.189z" fill="url(#a)"/></svg>
|
||||
|
After Width: | Height: | Size: 1.3 KiB |
1
frontend/public/Logos/azure-sql-database-metrics.svg
Normal file
1
frontend/public/Logos/azure-sql-database-metrics.svg
Normal file
@ -0,0 +1 @@
|
||||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 18 18"><defs><radialGradient id="b" cx="9.36" cy="10.57" r="7.07" gradientUnits="userSpaceOnUse"><stop offset="0" stop-color="#f2f2f2"/><stop offset=".58" stop-color="#eee"/><stop offset="1" stop-color="#e6e6e6"/></radialGradient><linearGradient id="a" x1="2.59" y1="10.16" x2="15.41" y2="10.16" gradientUnits="userSpaceOnUse"><stop offset="0" stop-color="#005ba1"/><stop offset=".07" stop-color="#0060a9"/><stop offset=".36" stop-color="#0071c8"/><stop offset=".52" stop-color="#0078d4"/><stop offset=".64" stop-color="#0074cd"/><stop offset=".82" stop-color="#006abb"/><stop offset="1" stop-color="#005ba1"/></linearGradient></defs><path d="M9 5.14c-3.54 0-6.41-1-6.41-2.32v12.36c0 1.27 2.82 2.3 6.32 2.32H9c3.54 0 6.41-1 6.41-2.32V2.82c0 1.29-2.87 2.32-6.41 2.32z" fill="url(#a)"/><path d="M15.41 2.82c0 1.29-2.87 2.32-6.41 2.32s-6.41-1-6.41-2.32S5.46.5 9 .5s6.41 1 6.41 2.32" fill="#e8e8e8"/><path d="M13.92 2.63c0 .82-2.21 1.48-4.92 1.48s-4.92-.66-4.92-1.48S6.29 1.16 9 1.16s4.92.66 4.92 1.47" fill="#50e6ff"/><path d="M9 3a11.55 11.55 0 00-3.89.57A11.42 11.42 0 009 4.11a11.15 11.15 0 003.89-.58A11.84 11.84 0 009 3z" fill="#198ab3"/><path d="M12.9 11.4V8H12v4.13h2.46v-.73zM5.76 9.73a1.83 1.83 0 01-.51-.31.44.44 0 01-.12-.32.34.34 0 01.15-.3.68.68 0 01.42-.12 1.62 1.62 0 011 .29v-.86a2.58 2.58 0 00-1-.16 1.64 1.64 0 00-1.09.34 1.08 1.08 0 00-.42.89c0 .51.32.91 1 1.21a2.88 2.88 0 01.62.36.42.42 0 01.15.32.38.38 0 01-.16.31.81.81 0 01-.45.11 1.66 1.66 0 01-1.09-.42V12a2.17 2.17 0 001.07.24 1.88 1.88 0 001.18-.33 1.08 1.08 0 00.33-.91 1.05 1.05 0 00-.25-.7 2.42 2.42 0 00-.83-.57zM11 11.32a2.34 2.34 0 00.33-1.26A2.32 2.32 0 0011 9a1.81 1.81 0 00-.7-.75 2 2 0 00-1-.26 2.11 2.11 0 00-1.08.27 1.86 1.86 0 00-.73.74 2.46 2.46 0 00-.26 1.14 2.26 2.26 0 00.24 1 1.76 1.76 0 00.69.74 2.06 2.06 0 001 .3l.86 1h1.21L10 12.08a1.79 1.79 0 001-.76zm-1-.25a.94.94 0 01-.76.35.92.92 0 01-.76-.36 1.52 1.52 0 01-.29-1 1.53 1.53 0 01.29-1 1 1 0 01.78-.37.87.87 0 01.75.37 1.62 1.62 0 01.27 1 1.46 1.46 0 01-.28 1.01z" fill="url(#b)"/></svg>
|
||||
|
After Width: | Height: | Size: 2.0 KiB |
1
frontend/public/Logos/azure-vm.svg
Normal file
1
frontend/public/Logos/azure-vm.svg
Normal file
@ -0,0 +1 @@
|
||||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 18 18"><defs><linearGradient id="a" x1="8.88" y1="12.21" x2="8.88" y2=".21" gradientUnits="userSpaceOnUse"><stop offset="0" stop-color="#0078d4"/><stop offset=".82" stop-color="#5ea0ef"/></linearGradient><linearGradient id="b" x1="8.88" y1="16.84" x2="8.88" y2="12.21" gradientUnits="userSpaceOnUse"><stop offset=".15" stop-color="#ccc"/><stop offset="1" stop-color="#707070"/></linearGradient></defs><rect x="-.12" y=".21" width="18" height="12" rx=".6" fill="url(#a)"/><path fill="#50e6ff" d="M11.88 4.46v3.49l-3 1.76v-3.5l3-1.75z"/><path fill="#c3f1ff" d="M11.88 4.46l-3 1.76-3-1.76 3-1.75 3 1.75z"/><path fill="#9cebff" d="M8.88 6.22v3.49l-3-1.76V4.46l3 1.76z"/><path fill="#c3f1ff" d="M5.88 7.95l3-1.74v3.5l-3-1.76z"/><path fill="#9cebff" d="M11.88 7.95l-3-1.74v3.5l3-1.76z"/><path d="M12.49 15.84c-1.78-.28-1.85-1.56-1.85-3.63H7.11c0 2.07-.06 3.35-1.84 3.63a1 1 0 00-.89 1h9a1 1 0 00-.89-1z" fill="url(#b)"/></svg>
|
||||
|
After Width: | Height: | Size: 973 B |
@ -8,6 +8,7 @@
|
||||
"GET_STARTED_LOGS_MANAGEMENT": "SigNoz | Get Started | Logs",
|
||||
"GET_STARTED_INFRASTRUCTURE_MONITORING": "SigNoz | Get Started | Infrastructure",
|
||||
"GET_STARTED_AWS_MONITORING": "SigNoz | Get Started | AWS",
|
||||
"GET_STARTED_AZURE_MONITORING": "SigNoz | Get Started | AZURE",
|
||||
"TRACE": "SigNoz | Trace",
|
||||
"TRACE_DETAIL": "SigNoz | Trace Detail",
|
||||
"TRACES_EXPLORER": "SigNoz | Traces Explorer",
|
||||
|
||||
@ -13,6 +13,7 @@ const ROUTES = {
|
||||
GET_STARTED_INFRASTRUCTURE_MONITORING:
|
||||
'/get-started/infrastructure-monitoring',
|
||||
GET_STARTED_AWS_MONITORING: '/get-started/aws-monitoring',
|
||||
GET_STARTED_AZURE_MONITORING: '/get-started/azure-monitoring',
|
||||
USAGE_EXPLORER: '/usage-explorer',
|
||||
APPLICATION: '/services',
|
||||
ALL_DASHBOARD: '/dashboard',
|
||||
|
||||
@ -236,7 +236,8 @@ function AppLayout(props: AppLayoutProps): JSX.Element {
|
||||
pathname === ROUTES.GET_STARTED_APPLICATION_MONITORING ||
|
||||
pathname === ROUTES.GET_STARTED_INFRASTRUCTURE_MONITORING ||
|
||||
pathname === ROUTES.GET_STARTED_LOGS_MANAGEMENT ||
|
||||
pathname === ROUTES.GET_STARTED_AWS_MONITORING;
|
||||
pathname === ROUTES.GET_STARTED_AWS_MONITORING ||
|
||||
pathname === ROUTES.GET_STARTED_AZURE_MONITORING;
|
||||
|
||||
const [showTrialExpiryBanner, setShowTrialExpiryBanner] = useState(false);
|
||||
|
||||
|
||||
@ -0,0 +1,111 @@
|
||||
## Setup
|
||||
|
||||
### Installing with OpenTelemetry Helm Charts
|
||||
|
||||
Prior to installation, you must ensure your Kubernetes cluster is ready and that you have the necessary permissions to deploy applications. Follow these steps to use Helm for setting up the Collector:
|
||||
|
||||
1. **Add the OpenTelemetry Helm repository:**
|
||||
|
||||
```bash
|
||||
helm repo add open-telemetry https://open-telemetry.github.io/opentelemetry-helm-charts
|
||||
```
|
||||
|
||||
2. **Prepare the `otel-collector-values.yaml` Configuration**
|
||||
|
||||
#### Azure Event Hub Receiver Configuration
|
||||
If you haven't created the logs Event Hub, you can create one by following the steps in the [Azure Event Hubs documentation](../../bootstrapping/data-ingestion).
|
||||
|
||||
and replace the placeholders `<Primary Connection String>` with the primary connection string for your Event Hub, it should look something like this:
|
||||
|
||||
```yaml
|
||||
connection: Endpoint=sb://namespace.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=superSecret1234=;EntityPath=hubName
|
||||
```
|
||||
The Event Hub docs have a step to create a SAS policy for the event hub and copy the connection string.
|
||||
|
||||
#### Azure Monitor Receiver Configuration
|
||||
|
||||
You will need to set up a [service principal](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal) with Read permissions to receive data from Azure Monitor.
|
||||
|
||||
1. Follow the steps in the [Create a service principal Azure Doc](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal#register-an-application-with-microsoft-entra-id-and-create-a-service-principal) documentation to create a service principal.
|
||||
You can name it `signoz-central-collector-app` the redirect URI can be empty.
|
||||
2. To add read permissions to Azure Monitor, Follow the [Assign Role](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal#assign-a-role-to-the-application) documentation. The read acess can be given to the full subscription.
|
||||
3. There are multiple ways to authenticate the service principal, we will use the client secret option, follow [Creating a client secret](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal#option-3-create-a-new-client-secret) and don't forget to copy the client secret. The secret is used in the configuration file as `client_secret`.
|
||||
|
||||
4. To find `client_id` and `tenant_id`, go to the [Azure Portal](https://portal.azure.com/) and search for the `Application` you created. You would see the `Application (client) ID` and `Directory (tenant) ID` in the Overview section.
|
||||
|
||||
<figure data-zoomable align="center">
|
||||
<img
|
||||
src="/img/docs/azure-monitoring/service-principal-app-overview.webp"
|
||||
alt="Application Overview"
|
||||
/>
|
||||
<figcaption>
|
||||
<i>
|
||||
Application Overview
|
||||
</i>
|
||||
</figcaption>
|
||||
</figure>
|
||||
|
||||
5. To find `subscription_id`, follow steps in [Find Your Subscription](https://learn.microsoft.com/en-us/azure/azure-portal/get-subscription-tenant-id#find-your-azure-subscription) and populate them in the configuration file.
|
||||
|
||||
6. Ensure you replace the placeholders `<region>` and `<ingestion-key>` with the appropriate values for your signoz cloud instance.
|
||||
|
||||
|
||||
|
||||
Below is an example targeting the SigNoz backend with Azure Monitor receivers configured:
|
||||
|
||||
```yaml
|
||||
service:
|
||||
pipelines:
|
||||
metrics/am:
|
||||
receivers: [azuremonitor]
|
||||
exporters: [otlp]
|
||||
traces:
|
||||
receivers: [otlp]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
metrics:
|
||||
receivers: [otlp]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
logs:
|
||||
receivers: [otlp, azureeventhub]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
receivers:
|
||||
otlp:
|
||||
protocols:
|
||||
grpc:
|
||||
endpoint: 0.0.0.0:4317
|
||||
http:
|
||||
endpoint: 0.0.0.0:4318
|
||||
azureeventhub:
|
||||
connection: Endpoint=sb://namespace.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=superSecret1234=;EntityPath=hubName
|
||||
format: "azure"
|
||||
azuremonitor:
|
||||
subscription_id: "<Subscription ID>"
|
||||
tenant_id: "<AD Tenant ID>"
|
||||
client_id: "<Client ID>"
|
||||
client_secret: "<Client Secret>"
|
||||
resource_groups: ["<rg-1>"]
|
||||
collection_interval: 60s
|
||||
processors:
|
||||
batch: {}
|
||||
exporters:
|
||||
otlp:
|
||||
endpoint: "ingest.<region>.signoz.cloud:443"
|
||||
tls:
|
||||
insecure: false
|
||||
headers:
|
||||
"signoz-access-token": "<ingestion-key>"
|
||||
```
|
||||
|
||||
3. **Deploy the OpenTelemetry Collector to your Kubernetes cluster:**
|
||||
|
||||
You'll need to prepare a custom configuration file, say `otel-collector-values.yaml`, that matches your environment's specific needs. Replace `<namespace>` with the Kubernetes namespace where you wish to install the Collector.
|
||||
|
||||
```bash
|
||||
helm install -n <namespace> --create-namespace otel-collector open-telemetry/opentelemetry-collector -f otel-collector-values.yaml
|
||||
|
||||
```
|
||||
|
||||
For more detail, refer to the [official OpenTelemetry Helm Chart documentation](https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-collector), which offers comprehensive installation instructions and configuration options tailored to your environment's requirements.
|
||||
@ -0,0 +1,8 @@
|
||||
## Prerequisite
|
||||
|
||||
- An AKS cluster
|
||||
- Central Collector Setup
|
||||
|
||||
|
||||
|
||||
Once you have setup the Central Collector, it will automatically start collecting your Logs.
|
||||
@ -0,0 +1,8 @@
|
||||
## Prerequisite
|
||||
|
||||
- An AKS cluster
|
||||
- Central Collector Setup
|
||||
|
||||
|
||||
|
||||
Once you have setup the Central Collector, it will automatically start sending your Metrics to SigNoz.
|
||||
@ -0,0 +1,40 @@
|
||||
## Overview
|
||||
|
||||
Azure Event Hubs is a big data streaming platform ideal for centralizing logging and real-time log streaming for applications on Azure or on-premises.
|
||||
|
||||
Integrate SigNoz with Azure Event Hubs for a robust log management solution, leveraging SigNoz's log aggregation, querying, visualization, and alerting features.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- An active Azure subscription
|
||||
|
||||
## Setup
|
||||
|
||||
### 1. Create an Event Hubs Namespace
|
||||
|
||||
1. In the [Azure portal](https://portal.azure.com), create an Event Hubs namespace.
|
||||
2. Fill in the required details:
|
||||
- **Resource group**: Choose or create a new one.
|
||||
- **Namespace name**: Enter a unique name, e.g., `<orgName>-obs-signoz`.
|
||||
- **Pricing tier**: Based on your logging requirements.
|
||||
- **Region**: Should match the region of the resources you want to monitor.
|
||||
- **Throughput units**: Choose based on logging needs.
|
||||
3. Click "Review + create" and then "Create".
|
||||
|
||||
### 2. Create an Event Hub
|
||||
|
||||
1. Navigate to the Event Hubs namespace you created in the Azure portal.
|
||||
2. Click "+ Event Hub" to create a new event hub.
|
||||
3. Enter a name, e.g., `logs`and click "Create"
|
||||
|
||||
### 3. Create a SAS Policy and Copy Connection String
|
||||
|
||||
1. Navigate to the Event Hub in the Azure portal.
|
||||
2. Click "Shared access policies" in the left menu.
|
||||
3. Click "Add" to create a new policy named `signozListen`.
|
||||
4. Select the "Listen" permission and set the expiration time.
|
||||
5. Click "Save".
|
||||
6. Copy the *Connection string–primary key*.
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,16 @@
|
||||
## Application level Tracing
|
||||
|
||||
For application-level tracing, you can use the OpenTelemetry SDKs integrated with your application. These SDKs will automatically collect and forward traces to the Central Collector.
|
||||
|
||||
|
||||
|
||||
To see how you can instrument your applications like FastAPI, NextJS, Node.js, Spring etc. you can check out the **Application Monitoring** section available at the start of this onboarding or you can checkout this [documentation](https://signoz.io/docs/instrumentation/).
|
||||
|
||||
## Configure the OpenTelemetry SDK
|
||||
|
||||
```bash
|
||||
# Set env vars or config file
|
||||
export OTEL_EXPORTER_OTLP_ENDPOINT="http://otel-collector.kubelet-otel.svc.cluster.local:4318/"
|
||||
```
|
||||
|
||||
For application-level traces and metrics, configure your application to use the `kube-dns` name of the **Central Collector** you set up earlier.
|
||||
@ -0,0 +1,129 @@
|
||||
Set up the OpenTelemetry Collector on a Virtual Machine (VM). The setup is compatible with cloud VM instances, your own data center, or even a local VM on your development machine. Here's how to do it:
|
||||
|
||||
|
||||
## Download and Install the OpenTelemetry Collector Binary
|
||||
|
||||
Please visit [Documentation For VM](https://signoz.io/docs/tutorial/opentelemetry-binary-usage-in-virtual-machine/) which provides further guidance on a VM installation.
|
||||
|
||||
|
||||
|
||||
## Configure OpenTelemetry Collector
|
||||
|
||||
While following the documentation above for installing the OpenTelemetry Collector Binary, you must have created `config.yaml` file. Replace the content of the `config.yaml` with the below config file which includes the **Azure Monitor receiver**.
|
||||
|
||||
```yaml
|
||||
receivers:
|
||||
otlp:
|
||||
protocols:
|
||||
grpc:
|
||||
endpoint: 0.0.0.0:4317
|
||||
http:
|
||||
endpoint: 0.0.0.0:4318
|
||||
azureeventhub:
|
||||
connection: <Primary Connection String>
|
||||
format: "azure"
|
||||
azuremonitor:
|
||||
subscription_id: "<Subscription ID>"
|
||||
tenant_id: "<AD Tenant ID>"
|
||||
client_id: "<Client ID>"
|
||||
client_secret: "<Client Secret>"
|
||||
resource_groups: ["<rg-1>"]
|
||||
collection_interval: 60s
|
||||
processors:
|
||||
batch: {}
|
||||
exporters:
|
||||
otlp:
|
||||
endpoint: "ingest.{{REGION}}.signoz.cloud:443"
|
||||
tls:
|
||||
insecure: false
|
||||
headers:
|
||||
"signoz-access-token": "{{SIGNOZ_INGESTION_KEY}}"
|
||||
service:
|
||||
pipelines:
|
||||
metrics/am:
|
||||
receivers: [azuremonitor]
|
||||
exporters: [otlp]
|
||||
traces:
|
||||
receivers: [otlp]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
metrics:
|
||||
receivers: [otlp]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
logs:
|
||||
receivers: [otlp, azureeventhub]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
|
||||
```
|
||||
**NOTE:**
|
||||
Replace the `<Primary Connection String>` in the config file with the primary connection string for your Event Hub that you created in the previous section. It would look something like this:
|
||||
|
||||
```bash
|
||||
Endpoint=sb://namespace.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=superSecret1234=;EntityPath=hubName
|
||||
```
|
||||
|
||||
|
||||
|
||||
## Azure Monitor Receiver Configuration
|
||||
|
||||
You will need to set up a [service principal](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal) with Read permissions to receive data from Azure Monitor.
|
||||
|
||||
1. Follow the steps in the [Create a service principal Azure Doc](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal#register-an-application-with-microsoft-entra-id-and-create-a-service-principal) documentation to create a service principal.
|
||||
You can name it `signoz-central-collector-app` the redirect URI can be empty.
|
||||
|
||||
2. To add read permissions to Azure Monitor, Follow the [Assign Role](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal#assign-a-role-to-the-application) documentation. The read access can be given to the full subscription.
|
||||
|
||||
3. There are multiple ways to authenticate the service principal, we will use the client secret option, follow [Creating a client secret](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal#option-3-create-a-new-client-secret) and don't forget to copy the client secret. The secret is used in the configuration file as `client_secret`.
|
||||
|
||||
4. To find `client_id` and `tenant_id`, go to the [Azure Portal](https://portal.azure.com/) and search for the `Application` you created. You would see the `Application (client) ID` and `Directory (tenant) ID` in the Overview section.
|
||||
|
||||
5. To find `subscription_id`, follow steps in [Find Your Subscription](https://learn.microsoft.com/en-us/azure/azure-portal/get-subscription-tenant-id#find-your-azure-subscription) and populate them in the configuration file.
|
||||
|
||||
**NOTE:**
|
||||
By following the above steps, you will get the values for `<Subscription ID>`, `<AD Tenant ID>`, `<Client ID>` and `<Client Secret>` which you need to fill in the `config.yaml` file.
|
||||
|
||||
|
||||
|
||||
## Run the Collector
|
||||
|
||||
With your configuration file ready, you can now start the Collector using the following command:
|
||||
|
||||
```bash
|
||||
# Runs in background with the configuration we just created
|
||||
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
|
||||
```
|
||||
|
||||
|
||||
|
||||
### Open Ports
|
||||
|
||||
You will need to open the following ports on your Azure VM:
|
||||
- 4317 for gRPC
|
||||
- 4318 for HTTP
|
||||
|
||||
You can do this by navigating to the Azure VM's Networking section and adding a new inbound rule for the ports.
|
||||
|
||||
|
||||
|
||||
### Validating the Deployment
|
||||
|
||||
Once the Collector is running, ensure that telemetry data is being successfully sent and received. Use the logging exporter as defined in your configuration file, or check the logs for any startup errors.
|
||||
|
||||
|
||||
|
||||
## Configure DNS label For Collector
|
||||
|
||||
To the IP address of the collector, you can add a DNS label to the Public IP address. This will make it easier to refer to the centralized collector from other services. You can do this by following these steps:
|
||||
|
||||
1. Go to the Public IP address of the collector. This would be the IP address of the VM or Load Balancer in case of Kubernetes or Load Balanced collector.
|
||||
2. Click on the "Configuration" tab.
|
||||
3. Enter the DNS label you want to use for the collector.
|
||||
4. Click on "Save".
|
||||
|
||||
**NOTE:** Please take note of the DNS label you have entered. You will need this in the next steps.
|
||||
|
||||
|
||||
|
||||
If you encounter any difficulties, please refer to this [troubleshooting section](https://signoz.io/docs/azure-monitoring/bootstrapping/collector-setup/#troubleshooting)
|
||||
@ -0,0 +1,33 @@
|
||||
Follow these steps if you want to setup logging for your Azure App Service.
|
||||
|
||||
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- EventHub Setup
|
||||
- Central Collector Setup
|
||||
|
||||
|
||||
## Setup
|
||||
|
||||
1. Navigate to your App Service in the Azure portal
|
||||
|
||||
2. Search for "Diagnostic settings" in the left navigation menu
|
||||
|
||||
3. Click on "Add Diagnostic Setting"
|
||||
|
||||
4. Select the desired log categories to export:
|
||||
- HTTP logs
|
||||
- App Service Console Logs
|
||||
- App Service Application Logs
|
||||
- Access Audit Logs
|
||||
- IPSecurity Audit logs
|
||||
- App Service Platform logs
|
||||
|
||||
|
||||
5. Configure the destination details as **"Stream to an Event Hub"** and select the Event Hub namespace and Event Hub name created during the EventHub Setup in the earlier steps.
|
||||
|
||||
6. Save the diagnostic settings
|
||||
|
||||
|
||||
This will start sending your Azure App Service Logs to SigNoz!
|
||||
@ -0,0 +1,25 @@
|
||||
Follow these steps if you want to monitor System metrics like CPU Percentage, Memory Percentage etc. of your Azure App Service.
|
||||
|
||||
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- EventHub Setup
|
||||
- Central Collector Setup
|
||||
|
||||
## Dashboard Example
|
||||
|
||||
Once you have completed the prerequisites, you can start monitoring your Azure App Service's system metrics with SigNoz Cloud. Here's how you can do it:
|
||||
|
||||
1. Log in to your SigNoz account
|
||||
2. Navigate to the Dashboards section, and [add a dashboard](https://signoz.io/docs/userguide/manage-dashboards/)
|
||||
3. Add a Timeseries Panel
|
||||
4. In **Metrics**, select `azure_memorypercentage_total` and **Avg By** select tag `location`
|
||||
5. In Filter say `name = <app-svc-plan-name>`
|
||||
6. Hit “Save Changes” and you now have Memory Usage of your App Service in a Dashboard for reporting and alerting
|
||||
|
||||
In this way, you can monitor system metrics of your Azure App Service in SigNoz Cloud.
|
||||
|
||||
|
||||
|
||||
If you encounter any difficulties, please refer to this [troubleshooting section](https://signoz.io/docs/azure-monitoring/app-service/metrics/#troubleshooting)
|
||||
@ -0,0 +1,54 @@
|
||||
## Overview
|
||||
|
||||
Azure Event Hubs is a big data streaming platform ideal for centralizing logging and real-time log streaming for applications on Azure or on-premises.
|
||||
|
||||
Integrate SigNoz with Azure Event Hubs for a robust log management solution, leveraging SigNoz's log aggregation, querying, visualization, and alerting features.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- An active Azure subscription
|
||||
|
||||
## Setup
|
||||
|
||||
### 1. Create an Event Hubs Namespace
|
||||
|
||||
1. In the [Azure portal](https://portal.azure.com), create an Event Hubs namespace.
|
||||
2. Fill in the required details:
|
||||
- **Resource group**: Choose or create a new one.
|
||||
- **Namespace name**: Enter a unique name, e.g., `<orgName>-obs-signoz`.
|
||||
- **Pricing tier**: Based on your logging requirements.
|
||||
- **Region**: Should match the region of the resources you want to monitor.
|
||||
- **Throughput units**: Choose based on logging needs.
|
||||
3. Click "Review + create" and then "Create".
|
||||
|
||||
### 2. Create an Event Hub
|
||||
|
||||
1. Navigate to the Event Hubs namespace you created in the Azure portal.
|
||||
2. Click "+ Event Hub" to create a new event hub.
|
||||
3. Enter a name, e.g., `logs`and click "Create"
|
||||
|
||||
### 3. Create a SAS Policy and Copy Connection String
|
||||
|
||||
1. Navigate to the Event Hub in the Azure portal.
|
||||
2. Click "Shared access policies" in the left menu.
|
||||
3. Click "Add" to create a new policy named `signozListen`.
|
||||
4. Select the "Listen" permission and set the expiration time.
|
||||
5. Click "Save".
|
||||
6. Copy the *Connection string–primary key*.
|
||||
|
||||
<!-- ### 4. Configure OpenTelemetry Integration
|
||||
|
||||
1. Add a new receiver to [Central Collector Setup](../collector-setup).
|
||||
2. Configure the receiver with the Event Hubs namespace connection string and the event hub name.
|
||||
|
||||
### 5. Stream Logs to Event Hubs
|
||||
|
||||
1. Configure Azure services' diagnostic settings to forward logs to the Event Hub.
|
||||
2. Ensure logs are in [Azure Common Log Format](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/resource-logs-schema).
|
||||
3. Verify logs are streaming to Event Hubs and received by SigNoz.
|
||||
|
||||
For detailed instructions, refer to the Azure documentation: [Azure Event Hub](https://learn.microsoft.com/en-us/azure/event-hubs/event-hubs-create). -->
|
||||
|
||||
<!-- For more configuration options, see the [OpenTelemetry Documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/azureeventhubreceiver). -->
|
||||
|
||||
|
||||
@ -0,0 +1,29 @@
|
||||
## Application level Tracing
|
||||
|
||||
For application-level tracing, you can use the OpenTelemetry SDKs integrated with your application. These SDKs will automatically collect and forward traces to the Central Collector.
|
||||
|
||||
|
||||
|
||||
To see how you can instrument your applications like FastAPI, NextJS, Node.js, Spring etc. you can check out the **Application Monitoring** section available at the start of this onboarding or you can checkout this [documentation](https://signoz.io/docs/instrumentation/).
|
||||
|
||||
|
||||
|
||||
## Prerequisites
|
||||
|
||||
1. **Azure Subscription & App Service**: You need an active Azure subscription with a running Azure App Service instance.
|
||||
2. **Central Collector Setup**: Make sure you have set up the Central Collector
|
||||
|
||||
|
||||
|
||||
## Configure the OpenTelemetry SDK
|
||||
|
||||
```bash
|
||||
# Set env vars or config file
|
||||
export OTEL_EXPORTER_OTLP_ENDPOINT="http://<Your-Central-Collector-DNS>:4318/"
|
||||
```
|
||||
|
||||
For application-level traces, configure your application to use the DNS name of the **Central Collector** you set up earlier. This Central Collector will automatically forward the collected data to SigNoz.
|
||||
|
||||
|
||||
|
||||
If you encounter any difficulties, please refer to this [troubleshooting section](https://signoz.io/docs/azure-monitoring/app-service/tracing/#troubleshooting)
|
||||
@ -0,0 +1,129 @@
|
||||
Set up the OpenTelemetry Collector on a Virtual Machine (VM). The setup is compatible with cloud VM instances, your own data center, or even a local VM on your development machine. Here's how to do it:
|
||||
|
||||
|
||||
## Download and Install the OpenTelemetry Collector Binary
|
||||
|
||||
Please visit [Documentation For VM](https://signoz.io/docs/tutorial/opentelemetry-binary-usage-in-virtual-machine/) which provides further guidance on a VM installation.
|
||||
|
||||
|
||||
|
||||
## Configure OpenTelemetry Collector
|
||||
|
||||
While following the documentation above for installing the OpenTelemetry Collector Binary, you must have created `config.yaml` file. Replace the content of the `config.yaml` with the below config file which includes the **Azure Monitor receiver**.
|
||||
|
||||
```yaml
|
||||
receivers:
|
||||
otlp:
|
||||
protocols:
|
||||
grpc:
|
||||
endpoint: 0.0.0.0:4317
|
||||
http:
|
||||
endpoint: 0.0.0.0:4318
|
||||
azureeventhub:
|
||||
connection: <Primary Connection String>
|
||||
format: "azure"
|
||||
azuremonitor:
|
||||
subscription_id: "<Subscription ID>"
|
||||
tenant_id: "<AD Tenant ID>"
|
||||
client_id: "<Client ID>"
|
||||
client_secret: "<Client Secret>"
|
||||
resource_groups: ["<rg-1>"]
|
||||
collection_interval: 60s
|
||||
processors:
|
||||
batch: {}
|
||||
exporters:
|
||||
otlp:
|
||||
endpoint: "ingest.{{REGION}}.signoz.cloud:443"
|
||||
tls:
|
||||
insecure: false
|
||||
headers:
|
||||
"signoz-access-token": "{{SIGNOZ_INGESTION_KEY}}"
|
||||
service:
|
||||
pipelines:
|
||||
metrics/am:
|
||||
receivers: [azuremonitor]
|
||||
exporters: [otlp]
|
||||
traces:
|
||||
receivers: [otlp]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
metrics:
|
||||
receivers: [otlp]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
logs:
|
||||
receivers: [otlp, azureeventhub]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
|
||||
```
|
||||
**NOTE:**
|
||||
Replace the `<Primary Connection String>` in the config file with the primary connection string for your Event Hub that you created in the previous section. It would look something like this:
|
||||
|
||||
```bash
|
||||
Endpoint=sb://namespace.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=superSecret1234=;EntityPath=hubName
|
||||
```
|
||||
|
||||
|
||||
|
||||
## Azure Monitor Receiver Configuration
|
||||
|
||||
You will need to set up a [service principal](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal) with Read permissions to receive data from Azure Monitor.
|
||||
|
||||
1. Follow the steps in the [Create a service principal Azure Doc](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal#register-an-application-with-microsoft-entra-id-and-create-a-service-principal) documentation to create a service principal.
|
||||
You can name it `signoz-central-collector-app` the redirect URI can be empty.
|
||||
|
||||
2. To add read permissions to Azure Monitor, Follow the [Assign Role](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal#assign-a-role-to-the-application) documentation. The read access can be given to the full subscription.
|
||||
|
||||
3. There are multiple ways to authenticate the service principal, we will use the client secret option, follow [Creating a client secret](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal#option-3-create-a-new-client-secret) and don't forget to copy the client secret. The secret is used in the configuration file as `client_secret`.
|
||||
|
||||
4. To find `client_id` and `tenant_id`, go to the [Azure Portal](https://portal.azure.com/) and search for the `Application` you created. You would see the `Application (client) ID` and `Directory (tenant) ID` in the Overview section.
|
||||
|
||||
5. To find `subscription_id`, follow steps in [Find Your Subscription](https://learn.microsoft.com/en-us/azure/azure-portal/get-subscription-tenant-id#find-your-azure-subscription) and populate them in the configuration file.
|
||||
|
||||
**NOTE:**
|
||||
By following the above steps, you will get the values for `<Subscription ID>`, `<AD Tenant ID>`, `<Client ID>` and `<Client Secret>` which you need to fill in the `config.yaml` file.
|
||||
|
||||
|
||||
|
||||
## Run the Collector
|
||||
|
||||
With your configuration file ready, you can now start the Collector using the following command:
|
||||
|
||||
```bash
|
||||
# Runs in background with the configuration we just created
|
||||
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
|
||||
```
|
||||
|
||||
|
||||
|
||||
### Open Ports
|
||||
|
||||
You will need to open the following ports on your Azure VM:
|
||||
- 4317 for gRPC
|
||||
- 4318 for HTTP
|
||||
|
||||
You can do this by navigating to the Azure VM's Networking section and adding a new inbound rule for the ports.
|
||||
|
||||
|
||||
|
||||
### Validating the Deployment
|
||||
|
||||
Once the Collector is running, ensure that telemetry data is being successfully sent and received. Use the logging exporter as defined in your configuration file, or check the logs for any startup errors.
|
||||
|
||||
|
||||
|
||||
## Configure DNS label For Collector
|
||||
|
||||
To the IP address of the collector, you can add a DNS label to the Public IP address. This will make it easier to refer to the centralized collector from other services. You can do this by following these steps:
|
||||
|
||||
1. Go to the Public IP address of the collector. This would be the IP address of the VM or Load Balancer in case of Kubernetes or Load Balanced collector.
|
||||
2. Click on the "Configuration" tab.
|
||||
3. Enter the DNS label you want to use for the collector.
|
||||
4. Click on "Save".
|
||||
|
||||
**NOTE:** Please take note of the DNS label you have entered. You will need this in the next steps.
|
||||
|
||||
|
||||
|
||||
If you encounter any difficulties, please refer to this [troubleshooting section](https://signoz.io/docs/azure-monitoring/bootstrapping/collector-setup/#troubleshooting)
|
||||
@ -0,0 +1,23 @@
|
||||
Follow these steps if you want to setup logging for your Azure App Service.
|
||||
|
||||
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- EventHub Setup
|
||||
- Central Collector Setup
|
||||
|
||||
## Setup
|
||||
|
||||
1. Navigate to the relevant Storage Account in the Azure portal
|
||||
2. Search for "Diagnostic settings" in the left navigation menu
|
||||
3. Click on `blob` under the storage account
|
||||
4. Click on "Add Diagnostic Setting"
|
||||
5. Select the desired log categories to export:
|
||||
- Storage Read
|
||||
- Storage Write
|
||||
- Storage Delete
|
||||
5. Configure the destination details as "**Stream to an Event Hub**" and select the Event Hub namespace and Event Hub name created during the EventHub Setup
|
||||
6. Save the diagnostic settings
|
||||
|
||||
That's it! You have successfully set up logging for your Azure Blob Storage.
|
||||
@ -0,0 +1,28 @@
|
||||
Follow these steps if you want to monitor system metrics like Total Requests, Total Ingress / Egress, and Total Errors etc., of your Azure Blob Storage.
|
||||
|
||||
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- Azure Subscription and Azure Blob storage instance running
|
||||
- Central Collector Setup
|
||||
|
||||
|
||||
|
||||
## Dashboard Example
|
||||
|
||||
Once you have completed the prerequisites, you can start monitoring your Azure Blob Storage's system metrics with SigNoz.
|
||||
|
||||
1. Log in to your SigNoz account.
|
||||
2. Navigate to the Dashboards, and [add a dashboard](https://signoz.io/docs/userguide/manage-dashboards/)
|
||||
3. Add a Timeseries Panel
|
||||
4. In **Metrics**, select `azure_ingress_total` and **Avg B*y* select tag `location`
|
||||
5. In Filter say `name = <storage-account-name>`
|
||||
6. Hit “Save Changes”. You now have Total Ingress of your Azure Blob Storage in a Dashboard for reporting and alerting
|
||||
|
||||
|
||||
That's it! You have successfully set up monitoring for your Azure Blob Storage's system metrics with SigNoz. You can now start creating other panels and dashboards to monitor other Azure Blob Storage's metrics.
|
||||
|
||||
|
||||
|
||||
If you encounter any difficulties, please refer to this [troubleshooting section](https://signoz.io/docs/azure-monitoring/az-blob-storage/metrics/#troubleshooting)
|
||||
@ -0,0 +1,54 @@
|
||||
## Overview
|
||||
|
||||
Azure Event Hubs is a big data streaming platform ideal for centralizing logging and real-time log streaming for applications on Azure or on-premises.
|
||||
|
||||
Integrate SigNoz with Azure Event Hubs for a robust log management solution, leveraging SigNoz's log aggregation, querying, visualization, and alerting features.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- An active Azure subscription
|
||||
|
||||
## Setup
|
||||
|
||||
### 1. Create an Event Hubs Namespace
|
||||
|
||||
1. In the [Azure portal](https://portal.azure.com), create an Event Hubs namespace.
|
||||
2. Fill in the required details:
|
||||
- **Resource group**: Choose or create a new one.
|
||||
- **Namespace name**: Enter a unique name, e.g., `<orgName>-obs-signoz`.
|
||||
- **Pricing tier**: Based on your logging requirements.
|
||||
- **Region**: Should match the region of the resources you want to monitor.
|
||||
- **Throughput units**: Choose based on logging needs.
|
||||
3. Click "Review + create" and then "Create".
|
||||
|
||||
### 2. Create an Event Hub
|
||||
|
||||
1. Navigate to the Event Hubs namespace you created in the Azure portal.
|
||||
2. Click "+ Event Hub" to create a new event hub.
|
||||
3. Enter a name, e.g., `logs`and click "Create"
|
||||
|
||||
### 3. Create a SAS Policy and Copy Connection String
|
||||
|
||||
1. Navigate to the Event Hub in the Azure portal.
|
||||
2. Click "Shared access policies" in the left menu.
|
||||
3. Click "Add" to create a new policy named `signozListen`.
|
||||
4. Select the "Listen" permission and set the expiration time.
|
||||
5. Click "Save".
|
||||
6. Copy the *Connection string–primary key*.
|
||||
|
||||
<!-- ### 4. Configure OpenTelemetry Integration
|
||||
|
||||
1. Add a new receiver to [Central Collector Setup](../collector-setup).
|
||||
2. Configure the receiver with the Event Hubs namespace connection string and the event hub name.
|
||||
|
||||
### 5. Stream Logs to Event Hubs
|
||||
|
||||
1. Configure Azure services' diagnostic settings to forward logs to the Event Hub.
|
||||
2. Ensure logs are in [Azure Common Log Format](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/resource-logs-schema).
|
||||
3. Verify logs are streaming to Event Hubs and received by SigNoz.
|
||||
|
||||
For detailed instructions, refer to the Azure documentation: [Azure Event Hub](https://learn.microsoft.com/en-us/azure/event-hubs/event-hubs-create). -->
|
||||
|
||||
<!-- For more configuration options, see the [OpenTelemetry Documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/azureeventhubreceiver). -->
|
||||
|
||||
|
||||
@ -0,0 +1,129 @@
|
||||
Set up the OpenTelemetry Collector on a Virtual Machine (VM). The setup is compatible with cloud VM instances, your own data center, or even a local VM on your development machine. Here's how to do it:
|
||||
|
||||
|
||||
## Download and Install the OpenTelemetry Collector Binary
|
||||
|
||||
Please visit [Documentation For VM](https://signoz.io/docs/tutorial/opentelemetry-binary-usage-in-virtual-machine/) which provides further guidance on a VM installation.
|
||||
|
||||
|
||||
|
||||
## Configure OpenTelemetry Collector
|
||||
|
||||
While following the documentation above for installing the OpenTelemetry Collector Binary, you must have created `config.yaml` file. Replace the content of the `config.yaml` with the below config file which includes the **Azure Monitor receiver**.
|
||||
|
||||
```yaml
|
||||
receivers:
|
||||
otlp:
|
||||
protocols:
|
||||
grpc:
|
||||
endpoint: 0.0.0.0:4317
|
||||
http:
|
||||
endpoint: 0.0.0.0:4318
|
||||
azureeventhub:
|
||||
connection: <Primary Connection String>
|
||||
format: "azure"
|
||||
azuremonitor:
|
||||
subscription_id: "<Subscription ID>"
|
||||
tenant_id: "<AD Tenant ID>"
|
||||
client_id: "<Client ID>"
|
||||
client_secret: "<Client Secret>"
|
||||
resource_groups: ["<rg-1>"]
|
||||
collection_interval: 60s
|
||||
processors:
|
||||
batch: {}
|
||||
exporters:
|
||||
otlp:
|
||||
endpoint: "ingest.{{REGION}}.signoz.cloud:443"
|
||||
tls:
|
||||
insecure: false
|
||||
headers:
|
||||
"signoz-access-token": "{{SIGNOZ_INGESTION_KEY}}"
|
||||
service:
|
||||
pipelines:
|
||||
metrics/am:
|
||||
receivers: [azuremonitor]
|
||||
exporters: [otlp]
|
||||
traces:
|
||||
receivers: [otlp]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
metrics:
|
||||
receivers: [otlp]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
logs:
|
||||
receivers: [otlp, azureeventhub]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
|
||||
```
|
||||
**NOTE:**
|
||||
Replace the `<Primary Connection String>` in the config file with the primary connection string for your Event Hub that you created in the previous section. It would look something like this:
|
||||
|
||||
```bash
|
||||
Endpoint=sb://namespace.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=superSecret1234=;EntityPath=hubName
|
||||
```
|
||||
|
||||
|
||||
|
||||
## Azure Monitor Receiver Configuration
|
||||
|
||||
You will need to set up a [service principal](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal) with Read permissions to receive data from Azure Monitor.
|
||||
|
||||
1. Follow the steps in the [Create a service principal Azure Doc](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal#register-an-application-with-microsoft-entra-id-and-create-a-service-principal) documentation to create a service principal.
|
||||
You can name it `signoz-central-collector-app` the redirect URI can be empty.
|
||||
|
||||
2. To add read permissions to Azure Monitor, Follow the [Assign Role](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal#assign-a-role-to-the-application) documentation. The read access can be given to the full subscription.
|
||||
|
||||
3. There are multiple ways to authenticate the service principal, we will use the client secret option, follow [Creating a client secret](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal#option-3-create-a-new-client-secret) and don't forget to copy the client secret. The secret is used in the configuration file as `client_secret`.
|
||||
|
||||
4. To find `client_id` and `tenant_id`, go to the [Azure Portal](https://portal.azure.com/) and search for the `Application` you created. You would see the `Application (client) ID` and `Directory (tenant) ID` in the Overview section.
|
||||
|
||||
5. To find `subscription_id`, follow steps in [Find Your Subscription](https://learn.microsoft.com/en-us/azure/azure-portal/get-subscription-tenant-id#find-your-azure-subscription) and populate them in the configuration file.
|
||||
|
||||
**NOTE:**
|
||||
By following the above steps, you will get the values for `<Subscription ID>`, `<AD Tenant ID>`, `<Client ID>` and `<Client Secret>` which you need to fill in the `config.yaml` file.
|
||||
|
||||
|
||||
|
||||
## Run the Collector
|
||||
|
||||
With your configuration file ready, you can now start the Collector using the following command:
|
||||
|
||||
```bash
|
||||
# Runs in background with the configuration we just created
|
||||
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
|
||||
```
|
||||
|
||||
|
||||
|
||||
### Open Ports
|
||||
|
||||
You will need to open the following ports on your Azure VM:
|
||||
- 4317 for gRPC
|
||||
- 4318 for HTTP
|
||||
|
||||
You can do this by navigating to the Azure VM's Networking section and adding a new inbound rule for the ports.
|
||||
|
||||
|
||||
|
||||
### Validating the Deployment
|
||||
|
||||
Once the Collector is running, ensure that telemetry data is being successfully sent and received. Use the logging exporter as defined in your configuration file, or check the logs for any startup errors.
|
||||
|
||||
|
||||
|
||||
## Configure DNS label For Collector
|
||||
|
||||
To the IP address of the collector, you can add a DNS label to the Public IP address. This will make it easier to refer to the centralized collector from other services. You can do this by following these steps:
|
||||
|
||||
1. Go to the Public IP address of the collector. This would be the IP address of the VM or Load Balancer in case of Kubernetes or Load Balanced collector.
|
||||
2. Click on the "Configuration" tab.
|
||||
3. Enter the DNS label you want to use for the collector.
|
||||
4. Click on "Save".
|
||||
|
||||
**NOTE:** Please take note of the DNS label you have entered. You will need this in the next steps.
|
||||
|
||||
|
||||
|
||||
If you encounter any difficulties, please refer to this [troubleshooting section](https://signoz.io/docs/azure-monitoring/bootstrapping/collector-setup/#troubleshooting)
|
||||
@ -0,0 +1,28 @@
|
||||
Follow these steps if you want to setup logging for your Azure Container App.
|
||||
|
||||
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- EventHub Setup
|
||||
- Central Collector Setup
|
||||
|
||||
|
||||
## Setup
|
||||
|
||||
1. Navigate to your Container Apps in the Azure portal
|
||||
2. Click on "Container Apps Environment" to open the Container Apps Environment
|
||||
3. Search for "Diagnostic settings" in the left navigation menu
|
||||
4. Click on "Add Diagnostic Setting"
|
||||
5. Select the desired log categories to export:
|
||||
- Container App console logs
|
||||
- Container App system logs
|
||||
- Spring App console logs
|
||||
|
||||
|
||||
6. Configure the destination details as **"Stream to an Event Hub"** and select the Event Hub namespace and Event Hub name created during the EventHub Setup.
|
||||
|
||||
7. Save the diagnostic settings
|
||||
|
||||
|
||||
That's it! You have successfully set up logging for your Azure Container App.
|
||||
@ -0,0 +1,27 @@
|
||||
Follow these steps if you want to monitor System metrics like CPU Percentage, Memory Percentage etc. of your Azure Container App.
|
||||
|
||||
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- Azure subscription and an Azure Container App instance running
|
||||
- Central Collector Setup
|
||||
|
||||
|
||||
|
||||
# Dashboard Example
|
||||
|
||||
Once you have completed the prerequisites, you can start monitoring your Azure Container App's system metrics with SigNoz. Here's how you can do it:
|
||||
|
||||
1. Log in to your SigNoz account.
|
||||
2. Navigate to the Dashboards, and [add an dashboard](https://signoz.io/docs/userguide/manage-dashboards/)
|
||||
3. Add a Timeseries Panel
|
||||
4. In **Metrics**, select `azure_replicas_count` and **Avg By** select tag `name`
|
||||
5. In Filter say `type = Microsoft.App/containerApps`
|
||||
6. Hit “Save Changes”. You now have Memory Usage of your Container App in a Dashboard for reporting and alerting
|
||||
|
||||
In this way, you can monitor system metrics of your Azure Container App in SigNoz!
|
||||
|
||||
|
||||
|
||||
If you encounter any difficulties, please refer to this [troubleshooting section](https://signoz.io/docs/azure-monitoring/az-container-apps/metrics/#troubleshooting)
|
||||
@ -0,0 +1,54 @@
|
||||
## Overview
|
||||
|
||||
Azure Event Hubs is a big data streaming platform ideal for centralizing logging and real-time log streaming for applications on Azure or on-premises.
|
||||
|
||||
Integrate SigNoz with Azure Event Hubs for a robust log management solution, leveraging SigNoz's log aggregation, querying, visualization, and alerting features.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- An active Azure subscription
|
||||
|
||||
## Setup
|
||||
|
||||
### 1. Create an Event Hubs Namespace
|
||||
|
||||
1. In the [Azure portal](https://portal.azure.com), create an Event Hubs namespace.
|
||||
2. Fill in the required details:
|
||||
- **Resource group**: Choose or create a new one.
|
||||
- **Namespace name**: Enter a unique name, e.g., `<orgName>-obs-signoz`.
|
||||
- **Pricing tier**: Based on your logging requirements.
|
||||
- **Region**: Should match the region of the resources you want to monitor.
|
||||
- **Throughput units**: Choose based on logging needs.
|
||||
3. Click "Review + create" and then "Create".
|
||||
|
||||
### 2. Create an Event Hub
|
||||
|
||||
1. Navigate to the Event Hubs namespace you created in the Azure portal.
|
||||
2. Click "+ Event Hub" to create a new event hub.
|
||||
3. Enter a name, e.g., `logs`and click "Create"
|
||||
|
||||
### 3. Create a SAS Policy and Copy Connection String
|
||||
|
||||
1. Navigate to the Event Hub in the Azure portal.
|
||||
2. Click "Shared access policies" in the left menu.
|
||||
3. Click "Add" to create a new policy named `signozListen`.
|
||||
4. Select the "Listen" permission and set the expiration time.
|
||||
5. Click "Save".
|
||||
6. Copy the *Connection string–primary key*.
|
||||
|
||||
<!-- ### 4. Configure OpenTelemetry Integration
|
||||
|
||||
1. Add a new receiver to [Central Collector Setup](../collector-setup).
|
||||
2. Configure the receiver with the Event Hubs namespace connection string and the event hub name.
|
||||
|
||||
### 5. Stream Logs to Event Hubs
|
||||
|
||||
1. Configure Azure services' diagnostic settings to forward logs to the Event Hub.
|
||||
2. Ensure logs are in [Azure Common Log Format](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/resource-logs-schema).
|
||||
3. Verify logs are streaming to Event Hubs and received by SigNoz.
|
||||
|
||||
For detailed instructions, refer to the Azure documentation: [Azure Event Hub](https://learn.microsoft.com/en-us/azure/event-hubs/event-hubs-create). -->
|
||||
|
||||
<!-- For more configuration options, see the [OpenTelemetry Documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/azureeventhubreceiver). -->
|
||||
|
||||
|
||||
@ -0,0 +1,29 @@
|
||||
## Application level Tracing
|
||||
|
||||
For application-level tracing, you can use the OpenTelemetry SDKs integrated with your application. These SDKs will automatically collect and forward traces to the Central Collector.
|
||||
|
||||
|
||||
|
||||
To see how you can instrument your applications like FastAPI, NextJS, Node.js, Spring etc. you can check out the **Application Monitoring** section available at the start of this onboarding or you can checkout this [documentation](https://signoz.io/docs/instrumentation/).
|
||||
|
||||
|
||||
|
||||
## Prerequisites
|
||||
|
||||
1. **Azure Subscription & App Service**: You need an active Azure subscription with a running Azure App Service instance.
|
||||
2. **Central Collector Setup**: Make sure you have set up the Central Collector
|
||||
|
||||
|
||||
|
||||
## Configure the OpenTelemetry SDK
|
||||
|
||||
```bash
|
||||
# Set env vars or config file
|
||||
export OTEL_EXPORTER_OTLP_ENDPOINT="http://<Your-Central-Collector-DNS>:4318/"
|
||||
```
|
||||
|
||||
For application-level traces, configure your application to use the DNS name of the **Central Collector** you set up earlier. This Central Collector will automatically forward the collected data to SigNoz.
|
||||
|
||||
|
||||
|
||||
If you encounter any difficulties, please refer to this [troubleshooting section](https://signoz.io/docs/azure-monitoring/az-container-apps/tracing/#troubleshooting)
|
||||
@ -0,0 +1,129 @@
|
||||
Set up the OpenTelemetry Collector on a Virtual Machine (VM). The setup is compatible with cloud VM instances, your own data center, or even a local VM on your development machine. Here's how to do it:
|
||||
|
||||
|
||||
## Download and Install the OpenTelemetry Collector Binary
|
||||
|
||||
Please visit [Documentation For VM](https://signoz.io/docs/tutorial/opentelemetry-binary-usage-in-virtual-machine/) which provides further guidance on a VM installation.
|
||||
|
||||
|
||||
|
||||
## Configure OpenTelemetry Collector
|
||||
|
||||
While following the documentation above for installing the OpenTelemetry Collector Binary, you must have created `config.yaml` file. Replace the content of the `config.yaml` with the below config file which includes the **Azure Monitor receiver**.
|
||||
|
||||
```yaml
|
||||
receivers:
|
||||
otlp:
|
||||
protocols:
|
||||
grpc:
|
||||
endpoint: 0.0.0.0:4317
|
||||
http:
|
||||
endpoint: 0.0.0.0:4318
|
||||
azureeventhub:
|
||||
connection: <Primary Connection String>
|
||||
format: "azure"
|
||||
azuremonitor:
|
||||
subscription_id: "<Subscription ID>"
|
||||
tenant_id: "<AD Tenant ID>"
|
||||
client_id: "<Client ID>"
|
||||
client_secret: "<Client Secret>"
|
||||
resource_groups: ["<rg-1>"]
|
||||
collection_interval: 60s
|
||||
processors:
|
||||
batch: {}
|
||||
exporters:
|
||||
otlp:
|
||||
endpoint: "ingest.{{REGION}}.signoz.cloud:443"
|
||||
tls:
|
||||
insecure: false
|
||||
headers:
|
||||
"signoz-access-token": "{{SIGNOZ_INGESTION_KEY}}"
|
||||
service:
|
||||
pipelines:
|
||||
metrics/am:
|
||||
receivers: [azuremonitor]
|
||||
exporters: [otlp]
|
||||
traces:
|
||||
receivers: [otlp]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
metrics:
|
||||
receivers: [otlp]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
logs:
|
||||
receivers: [otlp, azureeventhub]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
|
||||
```
|
||||
**NOTE:**
|
||||
Replace the `<Primary Connection String>` in the config file with the primary connection string for your Event Hub that you created in the previous section. It would look something like this:
|
||||
|
||||
```bash
|
||||
Endpoint=sb://namespace.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=superSecret1234=;EntityPath=hubName
|
||||
```
|
||||
|
||||
|
||||
|
||||
## Azure Monitor Receiver Configuration
|
||||
|
||||
You will need to set up a [service principal](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal) with Read permissions to receive data from Azure Monitor.
|
||||
|
||||
1. Follow the steps in the [Create a service principal Azure Doc](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal#register-an-application-with-microsoft-entra-id-and-create-a-service-principal) documentation to create a service principal.
|
||||
You can name it `signoz-central-collector-app` the redirect URI can be empty.
|
||||
|
||||
2. To add read permissions to Azure Monitor, Follow the [Assign Role](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal#assign-a-role-to-the-application) documentation. The read access can be given to the full subscription.
|
||||
|
||||
3. There are multiple ways to authenticate the service principal, we will use the client secret option, follow [Creating a client secret](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal#option-3-create-a-new-client-secret) and don't forget to copy the client secret. The secret is used in the configuration file as `client_secret`.
|
||||
|
||||
4. To find `client_id` and `tenant_id`, go to the [Azure Portal](https://portal.azure.com/) and search for the `Application` you created. You would see the `Application (client) ID` and `Directory (tenant) ID` in the Overview section.
|
||||
|
||||
5. To find `subscription_id`, follow steps in [Find Your Subscription](https://learn.microsoft.com/en-us/azure/azure-portal/get-subscription-tenant-id#find-your-azure-subscription) and populate them in the configuration file.
|
||||
|
||||
**NOTE:**
|
||||
By following the above steps, you will get the values for `<Subscription ID>`, `<AD Tenant ID>`, `<Client ID>` and `<Client Secret>` which you need to fill in the `config.yaml` file.
|
||||
|
||||
|
||||
|
||||
## Run the Collector
|
||||
|
||||
With your configuration file ready, you can now start the Collector using the following command:
|
||||
|
||||
```bash
|
||||
# Runs in background with the configuration we just created
|
||||
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
|
||||
```
|
||||
|
||||
|
||||
|
||||
### Open Ports
|
||||
|
||||
You will need to open the following ports on your Azure VM:
|
||||
- 4317 for gRPC
|
||||
- 4318 for HTTP
|
||||
|
||||
You can do this by navigating to the Azure VM's Networking section and adding a new inbound rule for the ports.
|
||||
|
||||
|
||||
|
||||
### Validating the Deployment
|
||||
|
||||
Once the Collector is running, ensure that telemetry data is being successfully sent and received. Use the logging exporter as defined in your configuration file, or check the logs for any startup errors.
|
||||
|
||||
|
||||
|
||||
## Configure DNS label For Collector
|
||||
|
||||
To the IP address of the collector, you can add a DNS label to the Public IP address. This will make it easier to refer to the centralized collector from other services. You can do this by following these steps:
|
||||
|
||||
1. Go to the Public IP address of the collector. This would be the IP address of the VM or Load Balancer in case of Kubernetes or Load Balanced collector.
|
||||
2. Click on the "Configuration" tab.
|
||||
3. Enter the DNS label you want to use for the collector.
|
||||
4. Click on "Save".
|
||||
|
||||
**NOTE:** Please take note of the DNS label you have entered. You will need this in the next steps.
|
||||
|
||||
|
||||
|
||||
If you encounter any difficulties, please refer to this [troubleshooting section](https://signoz.io/docs/azure-monitoring/bootstrapping/collector-setup/#troubleshooting)
|
||||
@ -0,0 +1,21 @@
|
||||
Follow these steps if you want to setup logging for your Azure Functions.
|
||||
|
||||
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- EventHub Setup
|
||||
- Central Collector Setup
|
||||
|
||||
|
||||
## Setup
|
||||
|
||||
1. Navigate to your Azure Function in the Azure portal
|
||||
2. Search for "Diagnostic settings" in the left navigation menu
|
||||
3. Click on "Add Diagnostic Setting"
|
||||
4. Select the desired log categories to export:
|
||||
- Function App logs
|
||||
5. Configure the destination details as "**Stream to an Event Hub**" and select the Event Hub namespace and Event Hub name created during the EventHub Setup
|
||||
6. Save the diagnostic settings
|
||||
|
||||
That's it! You have successfully set up logging for your Azure Function.
|
||||
@ -0,0 +1,28 @@
|
||||
Follow these steps if you want to monitor System metrics like CPU Percentage, Memory Percentage etc. of your Azure Functions.
|
||||
|
||||
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- Azure subscription and an Azure Container App instance running
|
||||
- Central Collector Setup
|
||||
|
||||
|
||||
|
||||
## Dashboard Example
|
||||
|
||||
Once you have completed the prerequisites, you can start monitoring your Azure Function's system metrics with SigNoz. Here's how you can do it:
|
||||
|
||||
1. Log in to your SigNoz account.
|
||||
2. Navigate to the Dashboards, and add an dashboard
|
||||
3. Add a Timeseries Panel
|
||||
4. In *Metrics*, select `azure_requests_total` and *Avg By* select tag `location`
|
||||
5. In Filter say `name = <function-name>`
|
||||
6. Hit “Save Changes” You now have Total Requests of your Azure Function in a Dashboard for reporting and alerting
|
||||
|
||||
|
||||
That's it! You have successfully set up monitoring for your Azure Function's system metrics with SigNoz.
|
||||
|
||||
|
||||
|
||||
If you encounter any difficulties, please refer to this [troubleshooting section](https://signoz.io/docs/azure-monitoring/az-fns/metrics/#troubleshooting)
|
||||
@ -0,0 +1,54 @@
|
||||
## Overview
|
||||
|
||||
Azure Event Hubs is a big data streaming platform ideal for centralizing logging and real-time log streaming for applications on Azure or on-premises.
|
||||
|
||||
Integrate SigNoz with Azure Event Hubs for a robust log management solution, leveraging SigNoz's log aggregation, querying, visualization, and alerting features.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- An active Azure subscription
|
||||
|
||||
## Setup
|
||||
|
||||
### 1. Create an Event Hubs Namespace
|
||||
|
||||
1. In the [Azure portal](https://portal.azure.com), create an Event Hubs namespace.
|
||||
2. Fill in the required details:
|
||||
- **Resource group**: Choose or create a new one.
|
||||
- **Namespace name**: Enter a unique name, e.g., `<orgName>-obs-signoz`.
|
||||
- **Pricing tier**: Based on your logging requirements.
|
||||
- **Region**: Should match the region of the resources you want to monitor.
|
||||
- **Throughput units**: Choose based on logging needs.
|
||||
3. Click "Review + create" and then "Create".
|
||||
|
||||
### 2. Create an Event Hub
|
||||
|
||||
1. Navigate to the Event Hubs namespace you created in the Azure portal.
|
||||
2. Click "+ Event Hub" to create a new event hub.
|
||||
3. Enter a name, e.g., `logs`and click "Create"
|
||||
|
||||
### 3. Create a SAS Policy and Copy Connection String
|
||||
|
||||
1. Navigate to the Event Hub in the Azure portal.
|
||||
2. Click "Shared access policies" in the left menu.
|
||||
3. Click "Add" to create a new policy named `signozListen`.
|
||||
4. Select the "Listen" permission and set the expiration time.
|
||||
5. Click "Save".
|
||||
6. Copy the *Connection string–primary key*.
|
||||
|
||||
<!-- ### 4. Configure OpenTelemetry Integration
|
||||
|
||||
1. Add a new receiver to [Central Collector Setup](../collector-setup).
|
||||
2. Configure the receiver with the Event Hubs namespace connection string and the event hub name.
|
||||
|
||||
### 5. Stream Logs to Event Hubs
|
||||
|
||||
1. Configure Azure services' diagnostic settings to forward logs to the Event Hub.
|
||||
2. Ensure logs are in [Azure Common Log Format](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/resource-logs-schema).
|
||||
3. Verify logs are streaming to Event Hubs and received by SigNoz.
|
||||
|
||||
For detailed instructions, refer to the Azure documentation: [Azure Event Hub](https://learn.microsoft.com/en-us/azure/event-hubs/event-hubs-create). -->
|
||||
|
||||
<!-- For more configuration options, see the [OpenTelemetry Documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/azureeventhubreceiver). -->
|
||||
|
||||
|
||||
@ -0,0 +1,29 @@
|
||||
## Application level Tracing
|
||||
|
||||
For application-level tracing, you can use the OpenTelemetry SDKs integrated with your application. These SDKs will automatically collect and forward traces to the Central Collector.
|
||||
|
||||
|
||||
|
||||
To see how you can instrument your applications like FastAPI, NextJS, Node.js, Spring etc. you can check out the **Application Monitoring** section available at the start of this onboarding or you can checkout this [documentation](https://signoz.io/docs/instrumentation/).
|
||||
|
||||
|
||||
|
||||
## Prerequisites
|
||||
|
||||
1. **Azure Subscription & App Service**: You need an active Azure subscription with a running Azure Function App instance.
|
||||
2. **Central Collector Setup**: Make sure you have set up the Central Collector
|
||||
|
||||
|
||||
|
||||
## Configure the OpenTelemetry SDK
|
||||
|
||||
```bash
|
||||
# Set env vars or config file
|
||||
export OTEL_EXPORTER_OTLP_ENDPOINT="http://<Your-Central-Collector-DNS>:4318/"
|
||||
```
|
||||
|
||||
For application-level traces, configure your application to use the DNS name of the **Central Collector** you set up earlier. This Central Collector will automatically forward the collected data to SigNoz.
|
||||
|
||||
|
||||
|
||||
If you encounter any difficulties, please refer to this [troubleshooting section](https://signoz.io/docs/azure-monitoring/az-fns/tracing/#troubleshooting)
|
||||
@ -0,0 +1,129 @@
|
||||
Set up the OpenTelemetry Collector on a Virtual Machine (VM). The setup is compatible with cloud VM instances, your own data center, or even a local VM on your development machine. Here's how to do it:
|
||||
|
||||
|
||||
## Download and Install the OpenTelemetry Collector Binary
|
||||
|
||||
Please visit [Documentation For VM](https://signoz.io/docs/tutorial/opentelemetry-binary-usage-in-virtual-machine/) which provides further guidance on a VM installation.
|
||||
|
||||
|
||||
|
||||
## Configure OpenTelemetry Collector
|
||||
|
||||
While following the documentation above for installing the OpenTelemetry Collector Binary, you must have created `config.yaml` file. Replace the content of the `config.yaml` with the below config file which includes the **Azure Monitor receiver**.
|
||||
|
||||
```yaml
|
||||
receivers:
|
||||
otlp:
|
||||
protocols:
|
||||
grpc:
|
||||
endpoint: 0.0.0.0:4317
|
||||
http:
|
||||
endpoint: 0.0.0.0:4318
|
||||
azureeventhub:
|
||||
connection: <Primary Connection String>
|
||||
format: "azure"
|
||||
azuremonitor:
|
||||
subscription_id: "<Subscription ID>"
|
||||
tenant_id: "<AD Tenant ID>"
|
||||
client_id: "<Client ID>"
|
||||
client_secret: "<Client Secret>"
|
||||
resource_groups: ["<rg-1>"]
|
||||
collection_interval: 60s
|
||||
processors:
|
||||
batch: {}
|
||||
exporters:
|
||||
otlp:
|
||||
endpoint: "ingest.{{REGION}}.signoz.cloud:443"
|
||||
tls:
|
||||
insecure: false
|
||||
headers:
|
||||
"signoz-access-token": "{{SIGNOZ_INGESTION_KEY}}"
|
||||
service:
|
||||
pipelines:
|
||||
metrics/am:
|
||||
receivers: [azuremonitor]
|
||||
exporters: [otlp]
|
||||
traces:
|
||||
receivers: [otlp]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
metrics:
|
||||
receivers: [otlp]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
logs:
|
||||
receivers: [otlp, azureeventhub]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
|
||||
```
|
||||
**NOTE:**
|
||||
Replace the `<Primary Connection String>` in the config file with the primary connection string for your Event Hub that you created in the previous section. It would look something like this:
|
||||
|
||||
```bash
|
||||
Endpoint=sb://namespace.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=superSecret1234=;EntityPath=hubName
|
||||
```
|
||||
|
||||
|
||||
|
||||
## Azure Monitor Receiver Configuration
|
||||
|
||||
You will need to set up a [service principal](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal) with Read permissions to receive data from Azure Monitor.
|
||||
|
||||
1. Follow the steps in the [Create a service principal Azure Doc](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal#register-an-application-with-microsoft-entra-id-and-create-a-service-principal) documentation to create a service principal.
|
||||
You can name it `signoz-central-collector-app` the redirect URI can be empty.
|
||||
|
||||
2. To add read permissions to Azure Monitor, Follow the [Assign Role](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal#assign-a-role-to-the-application) documentation. The read access can be given to the full subscription.
|
||||
|
||||
3. There are multiple ways to authenticate the service principal, we will use the client secret option, follow [Creating a client secret](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal#option-3-create-a-new-client-secret) and don't forget to copy the client secret. The secret is used in the configuration file as `client_secret`.
|
||||
|
||||
4. To find `client_id` and `tenant_id`, go to the [Azure Portal](https://portal.azure.com/) and search for the `Application` you created. You would see the `Application (client) ID` and `Directory (tenant) ID` in the Overview section.
|
||||
|
||||
5. To find `subscription_id`, follow steps in [Find Your Subscription](https://learn.microsoft.com/en-us/azure/azure-portal/get-subscription-tenant-id#find-your-azure-subscription) and populate them in the configuration file.
|
||||
|
||||
**NOTE:**
|
||||
By following the above steps, you will get the values for `<Subscription ID>`, `<AD Tenant ID>`, `<Client ID>` and `<Client Secret>` which you need to fill in the `config.yaml` file.
|
||||
|
||||
|
||||
|
||||
## Run the Collector
|
||||
|
||||
With your configuration file ready, you can now start the Collector using the following command:
|
||||
|
||||
```bash
|
||||
# Runs in background with the configuration we just created
|
||||
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
|
||||
```
|
||||
|
||||
|
||||
|
||||
### Open Ports
|
||||
|
||||
You will need to open the following ports on your Azure VM:
|
||||
- 4317 for gRPC
|
||||
- 4318 for HTTP
|
||||
|
||||
You can do this by navigating to the Azure VM's Networking section and adding a new inbound rule for the ports.
|
||||
|
||||
|
||||
|
||||
### Validating the Deployment
|
||||
|
||||
Once the Collector is running, ensure that telemetry data is being successfully sent and received. Use the logging exporter as defined in your configuration file, or check the logs for any startup errors.
|
||||
|
||||
|
||||
|
||||
## Configure DNS label For Collector
|
||||
|
||||
To the IP address of the collector, you can add a DNS label to the Public IP address. This will make it easier to refer to the centralized collector from other services. You can do this by following these steps:
|
||||
|
||||
1. Go to the Public IP address of the collector. This would be the IP address of the VM or Load Balancer in case of Kubernetes or Load Balanced collector.
|
||||
2. Click on the "Configuration" tab.
|
||||
3. Enter the DNS label you want to use for the collector.
|
||||
4. Click on "Save".
|
||||
|
||||
**NOTE:** Please take note of the DNS label you have entered. You will need this in the next steps.
|
||||
|
||||
|
||||
|
||||
If you encounter any difficulties, please refer to this [troubleshooting section](https://signoz.io/docs/azure-monitoring/bootstrapping/collector-setup/#troubleshooting)
|
||||
@ -0,0 +1,31 @@
|
||||
## Prerequisite
|
||||
|
||||
- Azure subscription and Database instance running
|
||||
- Central Collector Setup
|
||||
- [SQL monitoring profile](https://learn.microsoft.com/en-us/azure/azure-sql/database/sql-insights-enable?view=azuresql#create-sql-monitoring-profile) created to monitor the databases in Azure Monitor
|
||||
|
||||
|
||||
|
||||
|
||||
## Setup
|
||||
|
||||
Once you have completed the prerequisites, you can start monitoring your Database's system metrics with SigNoz. Here's how you can do it:
|
||||
|
||||
1. Log in to your SigNoz account.
|
||||
2. Navigate to the Dashboards Section, and [add an dashboard](https://signoz.io/docs/userguide/manage-dashboards/)
|
||||
3. Add a Timeseries Panel
|
||||
4. In **Metrics**, select `azure_storage_maximum` and **Avg By** select tag `location`
|
||||
5. In Filter say `name = <database-name>`
|
||||
6. Hit “Save Changes”. You now have Memory Usage of your Database in a Dashboard for reporting and alerting
|
||||
|
||||
That's it! You have successfully set up monitoring for your Database's system metrics with SigNoz.
|
||||
|
||||
|
||||
|
||||
**NOTE:**
|
||||
Make sure you have created a sql monitoring profile in Azure Monitor if not, follow this guide to [Create SQL Monitoring Profile](https://learn.microsoft.com/en-us/azure/azure-sql/database/sql-insights-enable?view=azuresql#create-sql-monitoring-profile).
|
||||
You can monitor multiple databases in a single profile.
|
||||
|
||||
|
||||
|
||||
If you encounter any difficulties, please refer to this [troubleshooting section](https://signoz.io/docs/azure-monitoring/db-metrics/#troubleshooting)
|
||||
@ -0,0 +1,54 @@
|
||||
## Overview
|
||||
|
||||
Azure Event Hubs is a big data streaming platform ideal for centralizing logging and real-time log streaming for applications on Azure or on-premises.
|
||||
|
||||
Integrate SigNoz with Azure Event Hubs for a robust log management solution, leveraging SigNoz's log aggregation, querying, visualization, and alerting features.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- An active Azure subscription
|
||||
|
||||
## Setup
|
||||
|
||||
### 1. Create an Event Hubs Namespace
|
||||
|
||||
1. In the [Azure portal](https://portal.azure.com), create an Event Hubs namespace.
|
||||
2. Fill in the required details:
|
||||
- **Resource group**: Choose or create a new one.
|
||||
- **Namespace name**: Enter a unique name, e.g., `<orgName>-obs-signoz`.
|
||||
- **Pricing tier**: Based on your logging requirements.
|
||||
- **Region**: Should match the region of the resources you want to monitor.
|
||||
- **Throughput units**: Choose based on logging needs.
|
||||
3. Click "Review + create" and then "Create".
|
||||
|
||||
### 2. Create an Event Hub
|
||||
|
||||
1. Navigate to the Event Hubs namespace you created in the Azure portal.
|
||||
2. Click "+ Event Hub" to create a new event hub.
|
||||
3. Enter a name, e.g., `logs`and click "Create"
|
||||
|
||||
### 3. Create a SAS Policy and Copy Connection String
|
||||
|
||||
1. Navigate to the Event Hub in the Azure portal.
|
||||
2. Click "Shared access policies" in the left menu.
|
||||
3. Click "Add" to create a new policy named `signozListen`.
|
||||
4. Select the "Listen" permission and set the expiration time.
|
||||
5. Click "Save".
|
||||
6. Copy the *Connection string–primary key*.
|
||||
|
||||
<!-- ### 4. Configure OpenTelemetry Integration
|
||||
|
||||
1. Add a new receiver to [Central Collector Setup](../collector-setup).
|
||||
2. Configure the receiver with the Event Hubs namespace connection string and the event hub name.
|
||||
|
||||
### 5. Stream Logs to Event Hubs
|
||||
|
||||
1. Configure Azure services' diagnostic settings to forward logs to the Event Hub.
|
||||
2. Ensure logs are in [Azure Common Log Format](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/resource-logs-schema).
|
||||
3. Verify logs are streaming to Event Hubs and received by SigNoz.
|
||||
|
||||
For detailed instructions, refer to the Azure documentation: [Azure Event Hub](https://learn.microsoft.com/en-us/azure/event-hubs/event-hubs-create). -->
|
||||
|
||||
<!-- For more configuration options, see the [OpenTelemetry Documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/azureeventhubreceiver). -->
|
||||
|
||||
|
||||
@ -0,0 +1,134 @@
|
||||
## Prerequisites
|
||||
|
||||
- An Azure subscription with Azure VM and SSH access enabled
|
||||
- Central Collector Setup
|
||||
|
||||
|
||||
### Connect to the VM
|
||||
The [SSH Keys Guide](https://learn.microsoft.com/en-us/azure/virtual-machines/ssh-keys-portal#connect-to-the-vm) has steps on how to connect to your VM via SSH.
|
||||
|
||||
|
||||
|
||||
### Install OpenTelemetry Collector
|
||||
|
||||
Follow the [OpenTelemetry SigNoz documentation](https://signoz.io/docs/tutorial/opentelemetry-binary-usage-in-virtual-machine/) to install the OpenTelemetry Collector.
|
||||
|
||||
|
||||
|
||||
### Configure Collector
|
||||
|
||||
We send the logs, traces and metrics to the central collector that we set up in the previous step instead of SigNoz directly, in order to adopt a scalable architecture pattern. We recommend to our users to use the same pattern in your Azure subscription.
|
||||
|
||||
Replace the content of the `config.yaml` file that you created while installing the collector.
|
||||
|
||||
```yaml
|
||||
receivers:
|
||||
filelog:
|
||||
include: [ <file paths> ] # /var/log/myservice/*.json
|
||||
operators:
|
||||
- type: json_parser
|
||||
timestamp:
|
||||
parse_from: attributes.time
|
||||
layout: '%Y-%m-%d %H:%M:%S'
|
||||
otlp:
|
||||
protocols:
|
||||
grpc:
|
||||
endpoint: 0.0.0.0:4317
|
||||
http:
|
||||
endpoint: 0.0.0.0:4318
|
||||
hostmetrics:
|
||||
collection_interval: 60s
|
||||
scrapers:
|
||||
cpu: {}
|
||||
disk: {}
|
||||
load: {}
|
||||
filesystem: {}
|
||||
memory: {}
|
||||
network: {}
|
||||
paging: {}
|
||||
process:
|
||||
mute_process_name_error: true
|
||||
mute_process_exe_error: true
|
||||
mute_process_io_error: true
|
||||
processes: {}
|
||||
prometheus:
|
||||
config:
|
||||
global:
|
||||
scrape_interval: 60s
|
||||
scrape_configs:
|
||||
- job_name: otel-collector-binary
|
||||
static_configs:
|
||||
- targets:
|
||||
# - localhost:8888
|
||||
processors:
|
||||
batch:
|
||||
send_batch_size: 1000
|
||||
timeout: 10s
|
||||
# Ref: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/resourcedetectionprocessor/README.md
|
||||
resourcedetection:
|
||||
detectors: [env, azure, system]
|
||||
# Using OTEL_RESOURCE_ATTRIBUTES envvar, env detector adds custom labels.
|
||||
timeout: 2s
|
||||
system:
|
||||
hostname_sources: [dns, os]
|
||||
extensions:
|
||||
health_check: {}
|
||||
zpages: {}
|
||||
exporters:
|
||||
otlp:
|
||||
endpoint: "<Central Collector DNS Name>:4318"
|
||||
logging:
|
||||
verbosity: normal
|
||||
service:
|
||||
telemetry:
|
||||
metrics:
|
||||
address: 0.0.0.0:8888
|
||||
extensions: [health_check, zpages]
|
||||
pipelines:
|
||||
metrics:
|
||||
receivers: [otlp]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
metrics/internal:
|
||||
receivers: [prometheus, hostmetrics]
|
||||
processors: [resourcedetection, batch]
|
||||
exporters: [otlp]
|
||||
traces:
|
||||
receivers: [otlp]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
logs:
|
||||
receivers: [otlp, filelog]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
```
|
||||
|
||||
|
||||
#### OLTP Exporter Configuration
|
||||
Make sure to replace `<Central Collector DNS Name>` with the DNS name of your central collector that you set up earlier.
|
||||
|
||||
|
||||
|
||||
#### File Logs Receiver Configuration
|
||||
The file logs receiver needs to be configured with the paths to the log files that you want to stream to SigNoz. You can specify multiple paths by separating them as a array.
|
||||
|
||||
You can also specify globed path patterns to match multiple log files. For example, `/var/log/myservice/*.json` will match all log files in the `/var/log/myservice` directory with a `.json` extension.
|
||||
|
||||
|
||||
|
||||
### Start the OpenTelemetry Collector
|
||||
|
||||
Once we are done with the above configurations, we can now run the collector service with the following command:
|
||||
|
||||
```bash
|
||||
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
|
||||
```
|
||||
|
||||
|
||||
|
||||
### Hostmetrics Dashboard
|
||||
|
||||
Once the collector is running, you can access the SigNoz dashboard to view the logs and metrics from your Azure VM.
|
||||
|
||||
Please refer to the [Hostmetrics Dashboard](https://signoz.io/docs/userguide/hostmetrics/) for information on how to import and use the dashboard.
|
||||
|
||||
@ -0,0 +1,129 @@
|
||||
Set up the OpenTelemetry Collector on a Virtual Machine (VM). The setup is compatible with cloud VM instances, your own data center, or even a local VM on your development machine. Here's how to do it:
|
||||
|
||||
|
||||
## Download and Install the OpenTelemetry Collector Binary
|
||||
|
||||
Please visit [Documentation For VM](https://signoz.io/docs/tutorial/opentelemetry-binary-usage-in-virtual-machine/) which provides further guidance on a VM installation.
|
||||
|
||||
|
||||
|
||||
## Configure OpenTelemetry Collector
|
||||
|
||||
While following the documentation above for installing the OpenTelemetry Collector Binary, you must have created `config.yaml` file. Replace the content of the `config.yaml` with the below config file which includes the **Azure Monitor receiver**.
|
||||
|
||||
```yaml
|
||||
receivers:
|
||||
otlp:
|
||||
protocols:
|
||||
grpc:
|
||||
endpoint: 0.0.0.0:4317
|
||||
http:
|
||||
endpoint: 0.0.0.0:4318
|
||||
azureeventhub:
|
||||
connection: <Primary Connection String>
|
||||
format: "azure"
|
||||
azuremonitor:
|
||||
subscription_id: "<Subscription ID>"
|
||||
tenant_id: "<AD Tenant ID>"
|
||||
client_id: "<Client ID>"
|
||||
client_secret: "<Client Secret>"
|
||||
resource_groups: ["<rg-1>"]
|
||||
collection_interval: 60s
|
||||
processors:
|
||||
batch: {}
|
||||
exporters:
|
||||
otlp:
|
||||
endpoint: "ingest.{{REGION}}.signoz.cloud:443"
|
||||
tls:
|
||||
insecure: false
|
||||
headers:
|
||||
"signoz-access-token": "{{SIGNOZ_INGESTION_KEY}}"
|
||||
service:
|
||||
pipelines:
|
||||
metrics/am:
|
||||
receivers: [azuremonitor]
|
||||
exporters: [otlp]
|
||||
traces:
|
||||
receivers: [otlp]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
metrics:
|
||||
receivers: [otlp]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
logs:
|
||||
receivers: [otlp, azureeventhub]
|
||||
processors: [batch]
|
||||
exporters: [otlp]
|
||||
|
||||
```
|
||||
**NOTE:**
|
||||
Replace the `<Primary Connection String>` in the config file with the primary connection string for your Event Hub that you created in the previous section. It would look something like this:
|
||||
|
||||
```bash
|
||||
Endpoint=sb://namespace.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=superSecret1234=;EntityPath=hubName
|
||||
```
|
||||
|
||||
|
||||
|
||||
## Azure Monitor Receiver Configuration
|
||||
|
||||
You will need to set up a [service principal](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal) with Read permissions to receive data from Azure Monitor.
|
||||
|
||||
1. Follow the steps in the [Create a service principal Azure Doc](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal#register-an-application-with-microsoft-entra-id-and-create-a-service-principal) documentation to create a service principal.
|
||||
You can name it `signoz-central-collector-app` the redirect URI can be empty.
|
||||
|
||||
2. To add read permissions to Azure Monitor, Follow the [Assign Role](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal#assign-a-role-to-the-application) documentation. The read access can be given to the full subscription.
|
||||
|
||||
3. There are multiple ways to authenticate the service principal, we will use the client secret option, follow [Creating a client secret](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal#option-3-create-a-new-client-secret) and don't forget to copy the client secret. The secret is used in the configuration file as `client_secret`.
|
||||
|
||||
4. To find `client_id` and `tenant_id`, go to the [Azure Portal](https://portal.azure.com/) and search for the `Application` you created. You would see the `Application (client) ID` and `Directory (tenant) ID` in the Overview section.
|
||||
|
||||
5. To find `subscription_id`, follow steps in [Find Your Subscription](https://learn.microsoft.com/en-us/azure/azure-portal/get-subscription-tenant-id#find-your-azure-subscription) and populate them in the configuration file.
|
||||
|
||||
**NOTE:**
|
||||
By following the above steps, you will get the values for `<Subscription ID>`, `<AD Tenant ID>`, `<Client ID>` and `<Client Secret>` which you need to fill in the `config.yaml` file.
|
||||
|
||||
|
||||
|
||||
## Run the Collector
|
||||
|
||||
With your configuration file ready, you can now start the Collector using the following command:
|
||||
|
||||
```bash
|
||||
# Runs in background with the configuration we just created
|
||||
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
|
||||
```
|
||||
|
||||
|
||||
|
||||
### Open Ports
|
||||
|
||||
You will need to open the following ports on your Azure VM:
|
||||
- 4317 for gRPC
|
||||
- 4318 for HTTP
|
||||
|
||||
You can do this by navigating to the Azure VM's Networking section and adding a new inbound rule for the ports.
|
||||
|
||||
|
||||
|
||||
### Validating the Deployment
|
||||
|
||||
Once the Collector is running, ensure that telemetry data is being successfully sent and received. Use the logging exporter as defined in your configuration file, or check the logs for any startup errors.
|
||||
|
||||
|
||||
|
||||
## Configure DNS label For Collector
|
||||
|
||||
To the IP address of the collector, you can add a DNS label to the Public IP address. This will make it easier to refer to the centralized collector from other services. You can do this by following these steps:
|
||||
|
||||
1. Go to the Public IP address of the collector. This would be the IP address of the VM or Load Balancer in case of Kubernetes or Load Balanced collector.
|
||||
2. Click on the "Configuration" tab.
|
||||
3. Enter the DNS label you want to use for the collector.
|
||||
4. Click on "Save".
|
||||
|
||||
**NOTE:** Please take note of the DNS label you have entered. You will need this in the next steps.
|
||||
|
||||
|
||||
|
||||
If you encounter any difficulties, please refer to this [troubleshooting section](https://signoz.io/docs/azure-monitoring/bootstrapping/collector-setup/#troubleshooting)
|
||||
@ -0,0 +1,54 @@
|
||||
## Overview
|
||||
|
||||
Azure Event Hubs is a big data streaming platform ideal for centralizing logging and real-time log streaming for applications on Azure or on-premises.
|
||||
|
||||
Integrate SigNoz with Azure Event Hubs for a robust log management solution, leveraging SigNoz's log aggregation, querying, visualization, and alerting features.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- An active Azure subscription
|
||||
|
||||
## Setup
|
||||
|
||||
### 1. Create an Event Hubs Namespace
|
||||
|
||||
1. In the [Azure portal](https://portal.azure.com), create an Event Hubs namespace.
|
||||
2. Fill in the required details:
|
||||
- **Resource group**: Choose or create a new one.
|
||||
- **Namespace name**: Enter a unique name, e.g., `<orgName>-obs-signoz`.
|
||||
- **Pricing tier**: Based on your logging requirements.
|
||||
- **Region**: Should match the region of the resources you want to monitor.
|
||||
- **Throughput units**: Choose based on logging needs.
|
||||
3. Click "Review + create" and then "Create".
|
||||
|
||||
### 2. Create an Event Hub
|
||||
|
||||
1. Navigate to the Event Hubs namespace you created in the Azure portal.
|
||||
2. Click "+ Event Hub" to create a new event hub.
|
||||
3. Enter a name, e.g., `logs`and click "Create"
|
||||
|
||||
### 3. Create a SAS Policy and Copy Connection String
|
||||
|
||||
1. Navigate to the Event Hub in the Azure portal.
|
||||
2. Click "Shared access policies" in the left menu.
|
||||
3. Click "Add" to create a new policy named `signozListen`.
|
||||
4. Select the "Listen" permission and set the expiration time.
|
||||
5. Click "Save".
|
||||
6. Copy the *Connection string–primary key*.
|
||||
|
||||
<!-- ### 4. Configure OpenTelemetry Integration
|
||||
|
||||
1. Add a new receiver to [Central Collector Setup](../collector-setup).
|
||||
2. Configure the receiver with the Event Hubs namespace connection string and the event hub name.
|
||||
|
||||
### 5. Stream Logs to Event Hubs
|
||||
|
||||
1. Configure Azure services' diagnostic settings to forward logs to the Event Hub.
|
||||
2. Ensure logs are in [Azure Common Log Format](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/resource-logs-schema).
|
||||
3. Verify logs are streaming to Event Hubs and received by SigNoz.
|
||||
|
||||
For detailed instructions, refer to the Azure documentation: [Azure Event Hub](https://learn.microsoft.com/en-us/azure/event-hubs/event-hubs-create). -->
|
||||
|
||||
<!-- For more configuration options, see the [OpenTelemetry Documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/azureeventhubreceiver). -->
|
||||
|
||||
|
||||
@ -31,7 +31,7 @@
|
||||
|
||||
.onboardingHeader {
|
||||
text-align: center;
|
||||
margin-top: 48px;
|
||||
margin-top: 24px;
|
||||
}
|
||||
|
||||
.onboardingHeader h1 {
|
||||
@ -51,13 +51,14 @@
|
||||
justify-content: center;
|
||||
gap: 36px;
|
||||
margin: 36px;
|
||||
flex-wrap: wrap;
|
||||
}
|
||||
|
||||
.moduleStyles {
|
||||
padding: 0;
|
||||
box-sizing: border-box;
|
||||
cursor: pointer;
|
||||
width: 400px;
|
||||
width: 300px;
|
||||
transition: 0.3s;
|
||||
|
||||
.ant-card-body {
|
||||
|
||||
@ -25,6 +25,7 @@ import { DataSourceType } from './Steps/DataSource/DataSource';
|
||||
import {
|
||||
defaultApplicationDataSource,
|
||||
defaultAwsServices,
|
||||
defaultAzureServices,
|
||||
defaultInfraMetricsType,
|
||||
defaultLogsType,
|
||||
moduleRouteMap,
|
||||
@ -32,6 +33,7 @@ import {
|
||||
import {
|
||||
APM_STEPS,
|
||||
AWS_MONITORING_STEPS,
|
||||
AZURE_MONITORING_STEPS,
|
||||
getSteps,
|
||||
INFRASTRUCTURE_MONITORING_STEPS,
|
||||
LOGS_MANAGEMENT_STEPS,
|
||||
@ -42,6 +44,7 @@ export enum ModulesMap {
|
||||
LogsManagement = 'LogsManagement',
|
||||
InfrastructureMonitoring = 'InfrastructureMonitoring',
|
||||
AwsMonitoring = 'AwsMonitoring',
|
||||
AzureMonitoring = 'AzureMonitoring',
|
||||
}
|
||||
|
||||
export interface ModuleProps {
|
||||
@ -81,6 +84,12 @@ export const useCases = {
|
||||
desc:
|
||||
'Monitor your traces, logs and metrics for AWS services like EC2, ECS, EKS etc.',
|
||||
},
|
||||
AzureMonitoring: {
|
||||
id: ModulesMap.AzureMonitoring,
|
||||
title: 'Azure Monitoring',
|
||||
desc:
|
||||
'Monitor your traces, logs and metrics for Azure services like AKS, Container Apps, App Service etc.',
|
||||
},
|
||||
};
|
||||
|
||||
export default function Onboarding(): JSX.Element {
|
||||
@ -172,6 +181,7 @@ export default function Onboarding(): JSX.Element {
|
||||
setSelectedModuleSteps(APM_STEPS);
|
||||
};
|
||||
|
||||
// eslint-disable-next-line sonarjs/cognitive-complexity
|
||||
useEffect(() => {
|
||||
if (selectedModule?.id === ModulesMap.InfrastructureMonitoring) {
|
||||
if (selectedDataSource) {
|
||||
@ -194,6 +204,13 @@ export default function Onboarding(): JSX.Element {
|
||||
setSelectedModuleSteps(AWS_MONITORING_STEPS);
|
||||
updateSelectedDataSource(defaultAwsServices);
|
||||
}
|
||||
} else if (selectedModule?.id === ModulesMap.AzureMonitoring) {
|
||||
if (selectedDataSource) {
|
||||
setModuleStepsBasedOnSelectedDataSource(selectedDataSource);
|
||||
} else {
|
||||
setSelectedModuleSteps(AZURE_MONITORING_STEPS);
|
||||
updateSelectedDataSource(defaultAzureServices);
|
||||
}
|
||||
} else if (selectedModule?.id === ModulesMap.APM) {
|
||||
handleAPMSteps();
|
||||
|
||||
@ -240,18 +257,24 @@ export default function Onboarding(): JSX.Element {
|
||||
};
|
||||
|
||||
useEffect(() => {
|
||||
if (location.pathname === ROUTES.GET_STARTED_APPLICATION_MONITORING) {
|
||||
const { pathname } = location;
|
||||
|
||||
if (pathname === ROUTES.GET_STARTED_APPLICATION_MONITORING) {
|
||||
handleModuleSelect(useCases.APM);
|
||||
updateSelectedDataSource(defaultApplicationDataSource);
|
||||
handleNextStep();
|
||||
} else if (
|
||||
location.pathname === ROUTES.GET_STARTED_INFRASTRUCTURE_MONITORING
|
||||
) {
|
||||
} else if (pathname === ROUTES.GET_STARTED_INFRASTRUCTURE_MONITORING) {
|
||||
handleModuleSelect(useCases.InfrastructureMonitoring);
|
||||
handleNextStep();
|
||||
} else if (location.pathname === ROUTES.GET_STARTED_LOGS_MANAGEMENT) {
|
||||
} else if (pathname === ROUTES.GET_STARTED_LOGS_MANAGEMENT) {
|
||||
handleModuleSelect(useCases.LogsManagement);
|
||||
handleNextStep();
|
||||
} else if (pathname === ROUTES.GET_STARTED_AWS_MONITORING) {
|
||||
handleModuleSelect(useCases.AwsMonitoring);
|
||||
handleNextStep();
|
||||
} else if (pathname === ROUTES.GET_STARTED_AZURE_MONITORING) {
|
||||
handleModuleSelect(useCases.AzureMonitoring);
|
||||
handleNextStep();
|
||||
}
|
||||
// eslint-disable-next-line react-hooks/exhaustive-deps
|
||||
}, []);
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
import { MarkdownRenderer } from 'components/MarkdownRenderer/MarkdownRenderer';
|
||||
import { ApmDocFilePaths } from 'container/OnboardingContainer/constants/apmDocFilePaths';
|
||||
import { AwsMonitoringDocFilePaths } from 'container/OnboardingContainer/constants/awsMonitoringDocFilePaths';
|
||||
import { AzureMonitoringDocFilePaths } from 'container/OnboardingContainer/constants/azureMonitoringDocFilePaths';
|
||||
import { InfraMonitoringDocFilePaths } from 'container/OnboardingContainer/constants/infraMonitoringDocFilePaths';
|
||||
import { LogsManagementDocFilePaths } from 'container/OnboardingContainer/constants/logsManagementDocFilePaths';
|
||||
import {
|
||||
@ -69,6 +70,8 @@ export default function MarkdownStep(): JSX.Element {
|
||||
docFilePaths = InfraMonitoringDocFilePaths;
|
||||
} else if (selectedModule?.id === ModulesMap.AwsMonitoring) {
|
||||
docFilePaths = AwsMonitoringDocFilePaths;
|
||||
} else if (selectedModule?.id === ModulesMap.AzureMonitoring) {
|
||||
docFilePaths = AzureMonitoringDocFilePaths;
|
||||
}
|
||||
// @ts-ignore
|
||||
if (docFilePaths && docFilePaths[path]) {
|
||||
|
||||
@ -0,0 +1,82 @@
|
||||
import AzureMonitoring_azureAks_setupCentralCollector from '../Modules/AzureMonitoring/AKS/aks-installCentralCollector.md';
|
||||
import AzureMonitoring_azureAks_sendLogs from '../Modules/AzureMonitoring/AKS/aks-logs.md';
|
||||
import AzureMonitoring_azureAks_sendMetrics from '../Modules/AzureMonitoring/AKS/aks-metrics.md';
|
||||
import AzureMonitoring_azureAks_setupAzureEventsHub from '../Modules/AzureMonitoring/AKS/aks-setupEventsHub.md';
|
||||
import AzureMonitoring_azureAks_sendTraces from '../Modules/AzureMonitoring/AKS/aks-tracing.md';
|
||||
// Azure App Service
|
||||
import AzureMonitoring_azureAppService_setupCentralCollector from '../Modules/AzureMonitoring/AppService/appService-installCentralCollector.md';
|
||||
import AzureMonitoring_azureAppService_sendLogs from '../Modules/AzureMonitoring/AppService/appService-logs.md';
|
||||
import AzureMonitoring_azureAppService_sendMetrics from '../Modules/AzureMonitoring/AppService/appService-metrics.md';
|
||||
import AzureMonitoring_azureAppService_setupAzureEventsHub from '../Modules/AzureMonitoring/AppService/appService-setupEventsHub.md';
|
||||
import AzureMonitoring_azureAppService_sendTraces from '../Modules/AzureMonitoring/AppService/appService-tracing.md';
|
||||
// Azure Blob Storage
|
||||
import AzureMonitoring_azureBlobStorage_setupCentralCollector from '../Modules/AzureMonitoring/BlobStorage/blobStorage-installCentralCollector.md';
|
||||
import AzureMonitoring_azureBlobStorage_sendLogs from '../Modules/AzureMonitoring/BlobStorage/blobStorage-logs.md';
|
||||
import AzureMonitoring_azureBlobStorage_sendMetrics from '../Modules/AzureMonitoring/BlobStorage/blobStorage-metrics.md';
|
||||
import AzureMonitoring_azureBlobStorage_setupAzureEventsHub from '../Modules/AzureMonitoring/BlobStorage/blobStorage-setupEventsHub.md';
|
||||
// Azure Container Apps
|
||||
import AzureMonitoring_azureContainerApps_setupCentralCollector from '../Modules/AzureMonitoring/ContainerApps/containerApps-installCentralCollector.md';
|
||||
import AzureMonitoring_azureContainerApps_sendLogs from '../Modules/AzureMonitoring/ContainerApps/containerApps-logs.md';
|
||||
import AzureMonitoring_azureContainerApps_sendMetrics from '../Modules/AzureMonitoring/ContainerApps/containerApps-metrics.md';
|
||||
import AzureMonitoring_azureContainerApps_setupAzureEventsHub from '../Modules/AzureMonitoring/ContainerApps/containerApps-setupEventsHub.md';
|
||||
import AzureMonitoring_azureContainerApps_sendTraces from '../Modules/AzureMonitoring/ContainerApps/containerApps-tracing.md';
|
||||
// Azure Functions
|
||||
import AzureMonitoring_azureFunctions_setupCentralCollector from '../Modules/AzureMonitoring/Functions/functions-installCentralCollector.md';
|
||||
import AzureMonitoring_azureFunctions_sendLogs from '../Modules/AzureMonitoring/Functions/functions-logs.md';
|
||||
import AzureMonitoring_azureFunctions_sendMetrics from '../Modules/AzureMonitoring/Functions/functions-metrics.md';
|
||||
import AzureMonitoring_azureFunctions_setupAzureEventsHub from '../Modules/AzureMonitoring/Functions/functions-setupEventsHub.md';
|
||||
import AzureMonitoring_azureFunctions_sendTraces from '../Modules/AzureMonitoring/Functions/functions-tracing.md';
|
||||
// Azure SQL Database Metrics
|
||||
import AzureMonitoring_azureSQLDatabaseMetrics_setupCentralCollector from '../Modules/AzureMonitoring/SqlDatabaseMetrics/sqlDatabaseMetrics-installCentralCollector.md';
|
||||
import AzureMonitoring_azureSQLDatabaseMetrics_sendMetrics from '../Modules/AzureMonitoring/SqlDatabaseMetrics/sqlDatabaseMetrics-metrics.md';
|
||||
import AzureMonitoring_azureSQLDatabaseMetrics_setupAzureEventsHub from '../Modules/AzureMonitoring/SqlDatabaseMetrics/sqlDatabaseMetrics-setupEventsHub.md';
|
||||
import AzureMonitoring_azureVm_sendHostmetricsLogs from '../Modules/AzureMonitoring/Vm/vm-hostmetrics-and-logs.md';
|
||||
// Azure VM
|
||||
import AzureMonitoring_azureVm_setupCentralCollector from '../Modules/AzureMonitoring/Vm/vm-installCentralCollector.md';
|
||||
import AzureMonitoring_azureVm_setupAzureEventsHub from '../Modules/AzureMonitoring/Vm/vm-setupEventsHub.md';
|
||||
|
||||
export const AzureMonitoringDocFilePaths = {
|
||||
// Azure AKS
|
||||
AzureMonitoring_azureAks_setupCentralCollector,
|
||||
AzureMonitoring_azureAks_setupAzureEventsHub,
|
||||
AzureMonitoring_azureAks_sendTraces,
|
||||
AzureMonitoring_azureAks_sendLogs,
|
||||
AzureMonitoring_azureAks_sendMetrics,
|
||||
|
||||
// Azure App Service
|
||||
AzureMonitoring_azureFunctions_setupCentralCollector,
|
||||
AzureMonitoring_azureFunctions_setupAzureEventsHub,
|
||||
AzureMonitoring_azureFunctions_sendTraces,
|
||||
AzureMonitoring_azureFunctions_sendLogs,
|
||||
AzureMonitoring_azureFunctions_sendMetrics,
|
||||
|
||||
// Azure Functions
|
||||
AzureMonitoring_azureAppService_setupCentralCollector,
|
||||
AzureMonitoring_azureAppService_setupAzureEventsHub,
|
||||
AzureMonitoring_azureAppService_sendTraces,
|
||||
AzureMonitoring_azureAppService_sendLogs,
|
||||
AzureMonitoring_azureAppService_sendMetrics,
|
||||
|
||||
// Azure Container Apps
|
||||
AzureMonitoring_azureContainerApps_setupCentralCollector,
|
||||
AzureMonitoring_azureContainerApps_setupAzureEventsHub,
|
||||
AzureMonitoring_azureContainerApps_sendTraces,
|
||||
AzureMonitoring_azureContainerApps_sendLogs,
|
||||
AzureMonitoring_azureContainerApps_sendMetrics,
|
||||
|
||||
// Azure VM
|
||||
AzureMonitoring_azureVm_setupCentralCollector,
|
||||
AzureMonitoring_azureVm_setupAzureEventsHub,
|
||||
AzureMonitoring_azureVm_sendHostmetricsLogs,
|
||||
|
||||
// Azure SQL Database Metrics
|
||||
AzureMonitoring_azureSQLDatabaseMetrics_setupCentralCollector,
|
||||
AzureMonitoring_azureSQLDatabaseMetrics_setupAzureEventsHub,
|
||||
AzureMonitoring_azureSQLDatabaseMetrics_sendMetrics,
|
||||
|
||||
// Azure Blob Storage
|
||||
AzureMonitoring_azureBlobStorage_setupCentralCollector,
|
||||
AzureMonitoring_azureBlobStorage_setupAzureEventsHub,
|
||||
AzureMonitoring_azureBlobStorage_sendLogs,
|
||||
AzureMonitoring_azureBlobStorage_sendMetrics,
|
||||
};
|
||||
@ -35,6 +35,12 @@ export const stepsMap = {
|
||||
deployTaskDefinition: `deployTaskDefinition`,
|
||||
ecsSendLogsData: `ecsSendLogsData`,
|
||||
monitorDashboard: `monitorDashboard`,
|
||||
setupCentralCollector: `setupCentralCollector`,
|
||||
setupAzureEventsHub: `setupAzureEventsHub`,
|
||||
sendTraces: `sendTraces`,
|
||||
sendLogs: `sendLogs`,
|
||||
sendMetrics: `sendMetrics`,
|
||||
sendHostmetricsLogs: `sendHostmetricsLogs`,
|
||||
};
|
||||
|
||||
export const DataSourceStep: SelectedModuleStepProps = {
|
||||
@ -201,3 +207,33 @@ export const MonitorDashboard: SelectedModuleStepProps = {
|
||||
title: 'Monitor using Dashboard ',
|
||||
component: <MarkdownStep />,
|
||||
};
|
||||
export const SetupCentralCollectorStep: SelectedModuleStepProps = {
|
||||
id: stepsMap.setupCentralCollector,
|
||||
title: 'Setup Central Collector ',
|
||||
component: <MarkdownStep />,
|
||||
};
|
||||
export const SetupAzureEventsHub: SelectedModuleStepProps = {
|
||||
id: stepsMap.setupAzureEventsHub,
|
||||
title: 'Setup EventsHub',
|
||||
component: <MarkdownStep />,
|
||||
};
|
||||
export const SendTraces: SelectedModuleStepProps = {
|
||||
id: stepsMap.sendTraces,
|
||||
title: 'Send Traces',
|
||||
component: <MarkdownStep />,
|
||||
};
|
||||
export const SendLogs: SelectedModuleStepProps = {
|
||||
id: stepsMap.sendLogs,
|
||||
title: 'Send Logs',
|
||||
component: <MarkdownStep />,
|
||||
};
|
||||
export const SendMetrics: SelectedModuleStepProps = {
|
||||
id: stepsMap.sendMetrics,
|
||||
title: 'Send Metrics',
|
||||
component: <MarkdownStep />,
|
||||
};
|
||||
export const SendHostmetricsLogs: SelectedModuleStepProps = {
|
||||
id: stepsMap.sendHostmetricsLogs,
|
||||
title: 'HostMetrics and Logging',
|
||||
component: <MarkdownStep />,
|
||||
};
|
||||
|
||||
@ -8,6 +8,7 @@ export enum ModulesMap {
|
||||
LogsManagement = 'LogsManagement',
|
||||
InfrastructureMonitoring = 'InfrastructureMonitoring',
|
||||
AwsMonitoring = 'AwsMonitoring',
|
||||
AzureMonitoring = 'AzureMonitoring',
|
||||
}
|
||||
|
||||
export const frameworksMap = {
|
||||
@ -82,6 +83,7 @@ export const frameworksMap = {
|
||||
LogsManagement: {},
|
||||
InfrastructureMonitoring: {},
|
||||
AwsMonitoring: {},
|
||||
AzureMonitoring: {},
|
||||
};
|
||||
|
||||
export const defaultApplicationDataSource = {
|
||||
@ -270,6 +272,50 @@ const supportedAwsServices = [
|
||||
},
|
||||
];
|
||||
|
||||
export const defaultAzureServices = {
|
||||
name: 'VM',
|
||||
id: 'azureVm',
|
||||
imgURL: `/Logos/azure-vm.svg`,
|
||||
};
|
||||
|
||||
const supportedAzureServices = [
|
||||
{
|
||||
name: 'VM',
|
||||
id: 'azureVm',
|
||||
imgURL: `/Logos/azure-vm.svg`,
|
||||
},
|
||||
{
|
||||
name: 'App Service',
|
||||
id: 'azureAppService',
|
||||
imgURL: `/Logos/azure-app-service.svg`,
|
||||
},
|
||||
{
|
||||
name: 'AKS',
|
||||
id: 'azureAks',
|
||||
imgURL: `/Logos/azure-aks.svg`,
|
||||
},
|
||||
{
|
||||
name: 'Azure Functions',
|
||||
id: 'azureFunctions',
|
||||
imgURL: `/Logos/azure-functions.svg`,
|
||||
},
|
||||
{
|
||||
name: 'Azure Container Apps',
|
||||
id: 'azureContainerApps',
|
||||
imgURL: `/Logos/azure-container-apps.svg`,
|
||||
},
|
||||
{
|
||||
name: 'SQL Database Metrics',
|
||||
id: 'azureSQLDatabaseMetrics',
|
||||
imgURL: `/Logos/azure-sql-database-metrics.svg`,
|
||||
},
|
||||
{
|
||||
name: 'Azure Blob Storage',
|
||||
id: 'azureBlobStorage',
|
||||
imgURL: `/Logos/azure-blob-storage.svg`,
|
||||
},
|
||||
];
|
||||
|
||||
export const getDataSources = (module: ModuleProps): DataSourceType[] => {
|
||||
if (module.id === ModulesMap.APM) {
|
||||
return supportedLanguages;
|
||||
@ -283,7 +329,11 @@ export const getDataSources = (module: ModuleProps): DataSourceType[] => {
|
||||
return supportedLogsTypes;
|
||||
}
|
||||
|
||||
return supportedAwsServices;
|
||||
if (module.id === ModulesMap.AwsMonitoring) {
|
||||
return supportedAwsServices;
|
||||
}
|
||||
|
||||
return supportedAzureServices;
|
||||
};
|
||||
|
||||
export const getSupportedFrameworks = ({
|
||||
@ -347,4 +397,5 @@ export const moduleRouteMap = {
|
||||
[ModulesMap.InfrastructureMonitoring]:
|
||||
ROUTES.GET_STARTED_INFRASTRUCTURE_MONITORING,
|
||||
[ModulesMap.AwsMonitoring]: ROUTES.GET_STARTED_AWS_MONITORING,
|
||||
[ModulesMap.AzureMonitoring]: ROUTES.GET_STARTED_AZURE_MONITORING,
|
||||
};
|
||||
|
||||
@ -22,7 +22,13 @@ import {
|
||||
RestartOtelCollector,
|
||||
RunApplicationStep,
|
||||
SelectMethodStep,
|
||||
SendHostmetricsLogs,
|
||||
SendLogs,
|
||||
SendLogsCloudwatch,
|
||||
SendMetrics,
|
||||
SendTraces,
|
||||
SetupAzureEventsHub,
|
||||
SetupCentralCollectorStep,
|
||||
SetupDaemonService,
|
||||
SetupLogDrains,
|
||||
SetupOtelCollectorStep,
|
||||
@ -57,6 +63,10 @@ export const INFRASTRUCTURE_MONITORING_STEPS: SelectedModuleStepProps[] = [
|
||||
|
||||
export const AWS_MONITORING_STEPS: SelectedModuleStepProps[] = [DataSourceStep];
|
||||
|
||||
export const AZURE_MONITORING_STEPS: SelectedModuleStepProps[] = [
|
||||
DataSourceStep,
|
||||
];
|
||||
|
||||
export const getSteps = ({
|
||||
selectedDataSource,
|
||||
}: GetStepsProps): SelectedModuleStepProps[] => {
|
||||
@ -144,6 +154,70 @@ export const getSteps = ({
|
||||
];
|
||||
case 'awsEks':
|
||||
return [DataSourceStep, SetupOtelCollectorStep, MonitorDashboard];
|
||||
case 'azureVm':
|
||||
return [
|
||||
DataSourceStep,
|
||||
SetupAzureEventsHub,
|
||||
SetupCentralCollectorStep,
|
||||
SendHostmetricsLogs,
|
||||
];
|
||||
// eslint-disable-next-line sonarjs/no-duplicated-branches
|
||||
case 'azureAks':
|
||||
return [
|
||||
DataSourceStep,
|
||||
SetupAzureEventsHub,
|
||||
SetupCentralCollectorStep,
|
||||
SendTraces,
|
||||
SendLogs,
|
||||
SendMetrics,
|
||||
];
|
||||
// eslint-disable-next-line sonarjs/no-duplicated-branches
|
||||
case 'azureAppService':
|
||||
return [
|
||||
DataSourceStep,
|
||||
SetupAzureEventsHub,
|
||||
SetupCentralCollectorStep,
|
||||
SendTraces,
|
||||
SendLogs,
|
||||
SendMetrics,
|
||||
];
|
||||
// eslint-disable-next-line sonarjs/no-duplicated-branches
|
||||
case 'azureFunctions':
|
||||
return [
|
||||
DataSourceStep,
|
||||
SetupAzureEventsHub,
|
||||
SetupCentralCollectorStep,
|
||||
SendTraces,
|
||||
SendLogs,
|
||||
SendMetrics,
|
||||
];
|
||||
// eslint-disable-next-line sonarjs/no-duplicated-branches
|
||||
case 'azureContainerApps':
|
||||
return [
|
||||
DataSourceStep,
|
||||
SetupAzureEventsHub,
|
||||
SetupCentralCollectorStep,
|
||||
SendTraces,
|
||||
SendLogs,
|
||||
SendMetrics,
|
||||
];
|
||||
// eslint-disable-next-line sonarjs/no-duplicated-branches
|
||||
case 'azureBlobStorage':
|
||||
return [
|
||||
DataSourceStep,
|
||||
SetupAzureEventsHub,
|
||||
SetupCentralCollectorStep,
|
||||
SendLogs,
|
||||
SendMetrics,
|
||||
];
|
||||
// eslint-disable-next-line sonarjs/no-duplicated-branches
|
||||
case 'azureSQLDatabaseMetrics':
|
||||
return [
|
||||
DataSourceStep,
|
||||
SetupAzureEventsHub,
|
||||
SetupCentralCollectorStep,
|
||||
SendMetrics,
|
||||
];
|
||||
|
||||
default:
|
||||
return [DataSourceStep];
|
||||
|
||||
@ -112,6 +112,7 @@ export const routesToSkip = [
|
||||
ROUTES.GET_STARTED_INFRASTRUCTURE_MONITORING,
|
||||
ROUTES.GET_STARTED_LOGS_MANAGEMENT,
|
||||
ROUTES.GET_STARTED_AWS_MONITORING,
|
||||
ROUTES.GET_STARTED_AZURE_MONITORING,
|
||||
ROUTES.VERSION,
|
||||
ROUTES.ALL_DASHBOARD,
|
||||
ROUTES.ORG_SETTINGS,
|
||||
|
||||
@ -181,6 +181,7 @@ export const routesToSkip = [
|
||||
ROUTES.GET_STARTED_INFRASTRUCTURE_MONITORING,
|
||||
ROUTES.GET_STARTED_LOGS_MANAGEMENT,
|
||||
ROUTES.GET_STARTED_AWS_MONITORING,
|
||||
ROUTES.GET_STARTED_AZURE_MONITORING,
|
||||
ROUTES.VERSION,
|
||||
ROUTES.ALL_DASHBOARD,
|
||||
ROUTES.ORG_SETTINGS,
|
||||
|
||||
@ -86,6 +86,7 @@ export const routePermission: Record<keyof typeof ROUTES, ROLES[]> = {
|
||||
GET_STARTED_INFRASTRUCTURE_MONITORING: ['ADMIN', 'EDITOR', 'VIEWER'],
|
||||
GET_STARTED_LOGS_MANAGEMENT: ['ADMIN', 'EDITOR', 'VIEWER'],
|
||||
GET_STARTED_AWS_MONITORING: ['ADMIN', 'EDITOR', 'VIEWER'],
|
||||
GET_STARTED_AZURE_MONITORING: ['ADMIN', 'EDITOR', 'VIEWER'],
|
||||
WORKSPACE_LOCKED: ['ADMIN', 'EDITOR', 'VIEWER'],
|
||||
BILLING: ['ADMIN', 'EDITOR', 'VIEWER'],
|
||||
SUPPORT: ['ADMIN', 'EDITOR', 'VIEWER'],
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user