content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 51
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
`process.parent` `ptrace.tracee` `ptrace.tracee.ancestors` `ptrace.tracee.parent` `setrlimit.target` `setrlimit.target.ancestors` `setrlimit.target.parent` `signal.target` `signal.target.ancestors` `signal.target.parent` ### `\*.envp` {#common-process-envp-doc} Type: string Definition: Environment variables of the proc... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
-0.034325748682022095,
-0.05545422062277794,
-0.03146965429186821,
-0.06918220221996307,
0.029954399913549423,
-0.11041449755430222,
-0.026267599314451218,
0.07191040366888046,
-0.02359144017100334,
0.044117074459791183,
0.02733776532113552,
-0.0652594342827797,
-0.007396820932626724,
0.00... | 0.086169 |
`signal.target.parent` ### `\*.group` {#common-filefields-group-doc} Type: string Definition: Group of the file's owner `\*.group` has 46 possible prefixes: `cgroup\_write.file` `chdir.file` `chmod.file` `chown.file` `exec.file` `exec.interpreter.file` `exit.file` `exit.interpreter.file` `link.file` `link.file.destinat... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
-0.05023670569062233,
-0.046824026852846146,
-0.06843401491641998,
-0.027110083028674126,
0.007174556143581867,
-0.054203376173973083,
-0.015789998695254326,
0.07532694935798645,
-0.019892485812306404,
0.008690044283866882,
0.06790773570537567,
-0.03535888344049454,
-0.05696556717157364,
0... | 0.109523 |
### `\*.is\_thread` {#common-process-is\_thread-doc} Type: bool Definition: Indicates whether the process is considered a thread (that is, a child process that hasn't executed another program) `\*.is\_thread` has 14 possible prefixes: `exec` `exit` `process` `process.ancestors` `process.parent` `ptrace.tracee` `ptrace.... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
-0.03409262374043465,
-0.0449945293366909,
0.0028821032028645277,
-0.03585314378142357,
-0.00859822891652584,
-0.0659155324101448,
0.03460768237709999,
0.011920208111405373,
0.033509884029626846,
0.03700835630297661,
0.01629517786204815,
-0.10164573788642883,
-0.03900084272027016,
-0.02711... | 0.164909 |
`setrlimit.target.parent.interpreter.file` `setxattr.file` `signal.target.ancestors.file` `signal.target.ancestors.interpreter.file` `signal.target.file` `signal.target.interpreter.file` `signal.target.parent.file` `signal.target.parent.interpreter.file` `splice.file` `unlink.file` `utimes.file` ### `\*.mount\_id` {#co... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
-0.0625796690583229,
-0.03283735364675522,
-0.05434751883149147,
-0.05905359610915184,
-0.029772847890853882,
-0.03977329656481743,
-0.05152367800474167,
0.13181081414222717,
-0.025020387023687363,
-0.0027014105580747128,
0.09781713038682938,
-0.03135308623313904,
-0.022411588579416275,
0.... | 0.071982 |
`rename.file` `rename.file.destination` `rmdir.file` `setrlimit.target.ancestors.file` `setrlimit.target.ancestors.interpreter.file` `setrlimit.target.file` `setrlimit.target.interpreter.file` `setrlimit.target.parent.file` `setrlimit.target.parent.interpreter.file` `setxattr.file` `signal.target.ancestors.file` `signa... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
-0.07560115307569504,
-0.021886354312300682,
0.015725793316960335,
-0.08342232555150986,
0.029252715408802032,
-0.04218378663063049,
-0.008429954759776592,
0.06716938316822052,
-0.010141528211534023,
0.005869959481060505,
0.08914228528738022,
-0.007436284329742193,
-0.0047959438525140285,
... | 0.092276 |
the corresponding element `\*.root\_domain` has 3 possible prefixes: `accept.addr.hostname` `connect.addr.hostname` `dns.question.name` ### `\*.session\_type` {#common-usersessioncontext-session\_type-doc} Type: int Definition: Type of the user session `\*.session\_type` has 14 possible prefixes: `exec.user\_session` `... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
-0.021744897589087486,
-0.029964743182063103,
-0.06369888037443161,
-0.06131008267402649,
-0.04734790325164795,
-0.11550093442201614,
0.07879063487052917,
0.051198024302721024,
-0.021336747333407402,
0.04914242774248123,
0.013684296049177647,
-0.07111312448978424,
-0.03010786511003971,
0.0... | 0.082559 |
`mmap.file` `open.file` `process.ancestors.file` `process.ancestors.interpreter.file` `process.file` `process.interpreter.file` `process.parent.file` `process.parent.interpreter.file` `ptrace.tracee.ancestors.file` `ptrace.tracee.ancestors.interpreter.file` `ptrace.tracee.file` `ptrace.tracee.interpreter.file` `ptrace.... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
-0.07420112937688828,
0.01918596588075161,
-0.07891032099723816,
-0.07635966688394547,
0.02920079044997692,
-0.09889324754476547,
0.03909783810377121,
0.04828833416104317,
-0.002774659311398864,
0.007631728891283274,
0.03745744749903679,
-0.021260250359773636,
-0.017255598679184914,
0.0278... | 0.128765 |
Definition: the queried domain name ### `dns.question.type` {#dns-question-type-doc} Type: int Definition: a two octet code which specifies the DNS question type Constants: [DNS qtypes](#dns-qtypes) ### `dns.response.cnames` {#dns-response-cnames-doc} Type: string Definition: CNAME targets returned by the DNS response ... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
-0.13326162099838257,
-0.012252348475158215,
0.005574364680796862,
0.014574130065739155,
-0.044309101998806,
-0.10048360377550125,
-0.03193757310509682,
-0.0656861811876297,
0.10013341903686523,
-0.0036953326780349016,
-0.03767182677984238,
-0.019387729465961456,
-0.033122558146715164,
0.0... | 0.016534 |
new kernel module ### `mkdir.file.destination.mode` {#mkdir-file-destination-mode-doc} Type: int Definition: Mode of the new directory Constants: [File mode constants](#file-mode-constants) ### `mkdir.file.destination.rights` {#mkdir-file-destination-rights-doc} Type: int Definition: Rights of the new directory Constan... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
-0.02145623043179512,
-0.015823055058717728,
-0.06220930814743042,
-0.006259791553020477,
0.04422159120440483,
-0.09657689183950424,
0.008779004216194153,
0.09795967489480972,
-0.04860435053706169,
-0.0006805287557654083,
0.10596778988838196,
-0.016695622354745865,
-0.06522181630134583,
0.... | 0.137439 |
(hard) limit value ### `setsockopt.filter\_hash` {#setsockopt-filter\_hash-doc} Type: string Definition: Hash of the currently attached filter using sha256. Only available if the optname is `SO\_ATTACH\_FILTER` ### `setsockopt.filter\_instructions` {#setsockopt-filter\_instructions-doc} Type: string Definition: Instruc... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
-0.012559879571199417,
0.06011137366294861,
0.014802751131355762,
-0.044311702251434326,
-0.0045831394381821156,
-0.027925236150622368,
0.1025487631559372,
0.0044794888235628605,
-0.01918793097138405,
-0.08411489427089691,
-0.0003805600281339139,
-0.019794151186943054,
-0.008180823177099228,... | -0.010086 |
| | `UNKNOWN\_ABI` | all | ### `Architecture` {#architecture} Architecture of the binary. | Name | Architectures | | ---- |---------------| | `X86` | all | | `X86\_64` | all | | `ARM` | all | | `ARM64` | all | | `UNKNOWN\_ARCHITECTURE` | all | ### `BPF attach types` {#bpf-attach-types} BPF attach types are the supporte... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
-0.007845624350011349,
-0.04233134910464287,
-0.07490695267915726,
-0.007780849002301693,
-0.0306718647480011,
0.01380159892141819,
0.012902507558465004,
0.021832264959812164,
-0.10949768871068954,
-0.01125151477754116,
-0.00210172007791698,
-0.13844718039035797,
-0.02209414727985859,
0.00... | 0.142635 |
| `BPF\_L4\_CSUM\_REPLACE` | all | | `BPF\_TAIL\_CALL` | all | | `BPF\_CLONE\_REDIRECT` | all | | `BPF\_GET\_CURRENT\_PID\_TGID` | all | | `BPF\_GET\_CURRENT\_UID\_GID` | all | | `BPF\_GET\_CURRENT\_COMM` | all | | `BPF\_GET\_CGROUP\_CLASSID` | all | | `BPF\_SKB\_VLAN\_PUSH` | all | | `BPF\_SKB\_VLAN\_POP` | all | | `B... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
0.007028073538094759,
-0.012683159671723843,
-0.07711469382047653,
-0.036324672400951385,
-0.0375966802239418,
-0.04368480667471886,
0.09276236593723297,
0.04140549525618553,
-0.022597260773181915,
0.031124331057071686,
0.10163487493991852,
-0.0722360834479332,
0.0034649213775992393,
-0.07... | 0.087995 |
| `BPF\_XDP\_OUTPUT` | all | | `BPF\_GET\_NETNS\_COOKIE` | all | | `BPF\_GET\_CURRENT\_ANCESTOR\_CGROUP\_ID` | all | | `BPF\_SK\_ASSIGN` | all | | `BPF\_KTIME\_GET\_BOOT\_NS` | all | | `BPF\_SEQ\_PRINTF` | all | | `BPF\_SEQ\_WRITE` | all | | `BPF\_SK\_CGROUP\_ID` | all | | `BPF\_SK\_ANCESTOR\_CGROUP\_ID` | all | | `BPF... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
-0.001531459973193705,
-0.04177568852901459,
-0.1312117576599121,
0.01891128532588482,
-0.022427009418606758,
-0.022492455318570137,
0.11221510916948318,
0.03568536788225174,
-0.010456300340592861,
-0.0010834751883521676,
0.09978675097227097,
-0.0775238573551178,
0.04866645112633705,
-0.13... | 0.084476 |
`BPF\_PROG\_TYPE\_TRACING` | all | | `BPF\_PROG\_TYPE\_STRUCT\_OPS` | all | | `BPF\_PROG\_TYPE\_EXT` | all | | `BPF\_PROG\_TYPE\_LSM` | all | | `BPF\_PROG\_TYPE\_SK\_LOOKUP` | all | ### `Boolean constants` {#boolean-constants} Boolean constants are the supported boolean constants. | Name | Architectures | | ---- |-----... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
-0.08299251645803452,
0.028289318084716797,
-0.1275952309370041,
0.01909334771335125,
0.02794673852622509,
-0.0839821845293045,
0.06611789017915726,
0.010679032653570175,
-0.09168638288974762,
0.006979877594858408,
-0.007799466606229544,
-0.04657316580414772,
0.01279920618981123,
-0.000792... | 0.119416 |
| `CDNSKEY` | all | | `OPENPGPKEY` | all | | `CSYNC` | all | | `ZONEMD` | all | | `SVCB` | all | | `HTTPS` | all | | `SPF` | all | | `UINFO` | all | | `UID` | all | | `GID` | all | | `UNSPEC` | all | | `NID` | all | | `L32` | all | | `L64` | all | | `LP` | all | | `EUI48` | all | | `EUI64` | all | | `URI` | all | | `CA... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
-0.012218276970088482,
-0.00439735921099782,
-0.10213065147399902,
-0.0423937626183033,
-0.000165003992151469,
-0.06687989085912704,
0.04355315491557121,
0.05403515323996544,
-0.05234897881746292,
0.036090221256017685,
0.0554468110203743,
-0.030234884470701218,
0.04233473539352417,
-0.0740... | 0.078616 |
`ENOKEY` | all | | `ENOLCK` | all | | `ENOLINK` | all | | `ENOMEDIUM` | all | | `ENOMEM` | all | | `ENOMSG` | all | | `ENONET` | all | | `ENOPKG` | all | | `ENOPROTOOPT` | all | | `ENOSPC` | all | | `ENOSR` | all | | `ENOSTR` | all | | `ENOSYS` | all | | `ENOTBLK` | all | | `ENOTCONN` | all | | `ENOTDIR` | all | | `ENO... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
0.014293400570750237,
0.025174420326948166,
-0.047675684094429016,
-0.08568057417869568,
-0.024389004334807396,
-0.05031323805451393,
0.07167700678110123,
0.024997267872095108,
-0.04754767566919327,
0.03171626105904579,
0.11287127435207367,
-0.05909501388669014,
0.08256825059652328,
-0.050... | 0.154051 |
| all | | `S\_IXUSR` | all | | `S\_IRWXG` | all | | `S\_IRGRP` | all | | `S\_IWGRP` | all | | `S\_IXGRP` | all | | `S\_IRWXO` | all | | `S\_IROTH` | all | | `S\_IWOTH` | all | | `S\_IXOTH` | all | ### `Kernel Capability constants` {#kernel-capability-constants} Kernel Capability constants are the supported Linux Kernel... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
0.009379514493048191,
-0.029124408960342407,
-0.11414464563131332,
-0.004094684962183237,
0.0919007882475853,
-0.010993074625730515,
-0.00004497495319810696,
0.06332731246948242,
-0.11327672749757767,
-0.034671202301979065,
0.06981302052736282,
-0.032254405319690704,
0.0033856797963380814,
... | 0.16508 |
| `ETH\_P\_FIP` | all | | `ETH\_P\_80221` | all | | `ETH\_P\_HSR` | all | | `ETH\_P\_NSH` | all | | `ETH\_P\_LOOPBACK` | all | | `ETH\_P\_QINQ1` | all | | `ETH\_P\_QINQ2` | all | | `ETH\_P\_QINQ3` | all | | `ETH\_P\_EDSA` | all | | `ETH\_P\_IFE` | all | | `ETH\_P\_AFIUCV` | all | | `ETH\_P\_8023\_MIN` | all | | `ETH\_P... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
0.008414794690907001,
0.024246513843536377,
-0.0427020825445652,
-0.0704408809542656,
0.023465432226657867,
0.002306319773197174,
0.09395913034677505,
-0.031067155301570892,
-0.05999719351530075,
0.05216873809695244,
0.13453790545463562,
-0.003967681434005499,
0.05044703558087349,
-0.05781... | 0.07381 |
| `MAP\_HUGE\_1GB` | all | | `MAP\_HUGE\_2GB` | all | | `MAP\_HUGE\_16GB` | all | | `MAP\_32BIT` | amd64 | ### `Network Address Family constants` {#network-address-family-constants} Network Address Family constants are the supported network address families. | Name | Architectures | | ---- |---------------| | `AF\_UNSP... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
0.010223481804132462,
0.021753361448645592,
-0.02921009063720703,
-0.05731736123561859,
-0.010773363523185253,
-0.017161289229989052,
-0.010901776142418385,
0.007951149716973305,
-0.04968665540218353,
0.030982214957475662,
0.08455897122621536,
-0.05061985179781914,
-0.04108308255672455,
-0... | 0.121401 |
supported flags for a pipe buffer. | Name | Architectures | | ---- |---------------| | `PIPE\_BUF\_FLAG\_LRU` | all | | `PIPE\_BUF\_FLAG\_ATOMIC` | all | | `PIPE\_BUF\_FLAG\_GIFT` | all | | `PIPE\_BUF\_FLAG\_PACKET` | all | | `PIPE\_BUF\_FLAG\_CAN\_MERGE` | all | | `PIPE\_BUF\_FLAG\_WHOLE` | all | | `PIPE\_BUF\_FLAG\_L... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
-0.03073229268193245,
0.0019287379691377282,
-0.04834536090493202,
-0.024283409118652344,
0.012221773155033588,
-0.05109409615397453,
0.07856293022632599,
0.03158828616142273,
-0.051820579916238785,
-0.013609367422759533,
0.03495637699961662,
-0.09804003685712814,
-0.050622791051864624,
0.... | 0.083519 |
| | `PTRACE\_POKETEXT` | all | | `PTRACE\_POKEDATA` | all | | `PTRACE\_POKEUSR` | all | | `PTRACE\_CONT` | all | | `PTRACE\_KILL` | all | | `PTRACE\_SINGLESTEP` | all | | `PTRACE\_ATTACH` | all | | `PTRACE\_DETACH` | all | | `PTRACE\_SYSCALL` | all | | `PTRACE\_GETREGS` | all | | `PTRACE\_SETREGS` | all | | `PTRACE\_SE... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
-0.019513215869665146,
0.01675339601933956,
-0.08609461784362793,
-0.050796832889318466,
-0.021785840392112732,
-0.05384870618581772,
0.14389890432357788,
0.09072202444076538,
-0.07778742164373398,
0.07165306061506271,
0.09568999707698822,
-0.04883933439850807,
0.07148849964141846,
-0.0199... | 0.156121 |
`IP\_RECVTTL` | all | | `IP\_RECVTOS` | all | | `IP\_MTU` | all | | `IP\_FREEBIND` | all | | `IP\_IPSEC\_POLICY` | all | | `IP\_XFRM\_POLICY` | all | | `IP\_PASSSEC` | all | | `IP\_TRANSPARENT` | all | | `IP\_ORIGDSTADDR` | all | | `IP\_MINTTL` | all | | `IP\_NODEFRAG` | all | | `IP\_CHECKSUM` | all | | `IP\_BIND\_ADDR... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
-0.025750914588570595,
-0.0393802784383297,
-0.05283625051379204,
-0.08516591042280197,
0.01389741338789463,
-0.052037034183740616,
0.02765767276287079,
0.014845525845885277,
-0.05982423946261406,
0.04201874881982803,
0.09217902272939682,
-0.04458925500512123,
0.07014963030815125,
-0.09521... | 0.079837 |
`SO\_PEERPIDFD` | all | | `SO\_DEVMEM\_LINEAR` | all | | `SO\_DEVMEM\_DMABUF` | all | | `SO\_DEVMEM\_DONTNEED` | all | | `SCM\_TS\_OPT\_ID` | all | | `SO\_RCVPRIORITY` | all | | `TCP\_NODELAY` | all | | `TCP\_MAXSEG` | all | | `TCP\_CORK` | all | | `TCP\_KEEPIDLE` | all | | `TCP\_KEEPINTVL` | all | | `TCP\_KEEPCNT` | a... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
-0.012359357438981533,
0.020830562338232994,
-0.09759918600320816,
-0.02691354602575302,
0.007959957234561443,
-0.011921931058168411,
0.08883219212293625,
0.01238074991852045,
-0.04858504980802536,
0.03140798956155777,
0.062250420451164246,
-0.028844721615314484,
0.025070875883102417,
-0.0... | 0.09309 |
| | `SIGSEGV` | all | | `SIGUSR2` | all | | `SIGPIPE` | all | | `SIGALRM` | all | | `SIGTERM` | all | | `SIGSTKFLT` | all | | `SIGCHLD` | all | | `SIGCONT` | all | | `SIGSTOP` | all | | `SIGTSTP` | all | | `SIGTTIN` | all | | `SIGTTOU` | all | | `SIGURG` | all | | `SIGXCPU` | all | | `SIGXFSZ` | all | | `SIGVTALRM` | a... | https://github.com/DataDog/datadog-agent/blob/main/docs/cloud-workload-security/linux_expressions.md | main | datadog-agent | [
-0.013580874539911747,
-0.03977407142519951,
-0.06855803728103638,
-0.021076947450637817,
-0.0496760793030262,
-0.057684943079948425,
0.03878628835082054,
0.06379518657922745,
0.015046083368360996,
-0.027857042849063873,
0.032240793108940125,
-0.0423697866499424,
0.013158859685063362,
-0.0... | 0.152473 |
# Datadog Agent  [](https://codecov.io/github/DataDog/datadog-agent?br... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/index.md | main | datadog-agent | [
-0.0860801562666893,
0.00004172464832663536,
-0.05072825774550438,
0.0017972530331462622,
0.038499992340803146,
-0.11218142509460449,
-0.05623374879360199,
-0.005929899401962757,
-0.06131230667233467,
0.019127195701003075,
0.033497635275125504,
0.002694896189495921,
0.0631357803940773,
-0.... | 0.124964 |
# Examples This page walks through three annotated examples taken from or inspired by the real schema files. Each example builds on the concepts introduced in the [Keyword Reference](keywords.md). --- ## Example 1 — Simple public setting node (`api\_key`) ```yaml api\_key: node\_type: setting # (1) type: string # (2) d... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/agent-schema/examples.md | main | datadog-agent | [
-0.02268499881029129,
-0.007108788471668959,
-0.017348023131489754,
0.03705299645662308,
-0.05306650698184967,
-0.012504742480814457,
-0.01146346889436245,
-0.03562891483306885,
0.009699092246592045,
0.03204871714115143,
0.03038424625992775,
-0.09307818114757538,
0.1343618631362915,
-0.010... | 0.03925 |
nested type (`cel\_workload\_exclude`) This example shows how JSON Schema's composable validation handles a non-trivial type. `cel\_workload\_exclude` corresponds to the following Go struct: ```go type Product string type ResourceType string type RuleBundle struct { Products []Product Rules map[ResourceType][]string } ... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/agent-schema/examples.md | main | datadog-agent | [
-0.013443121686577797,
0.09238790720701218,
-0.006962527986615896,
0.0257553867995739,
0.05153413861989975,
0.003771916963160038,
0.058959610760211945,
-0.01705354079604149,
-0.004360361956059933,
-0.06494878232479095,
0.07501448690891266,
-0.03922824189066887,
0.009047065861523151,
0.0519... | 0.079628 |
# FAQ --- ## How do I add a new setting? 1. \*\*Determine the node type.\*\* If the setting holds a value (string, number, boolean, list, or dict that \*is\* the value), it is a setting node. If it groups other settings, it is a section node. 2. \*\*Choose the correct schema file.\*\* - Settings for `datadog.yaml` go i... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/agent-schema/faq.md | main | datadog-agent | [
0.0409419909119606,
-0.005357070360332727,
-0.00815692637115717,
0.023917367681860924,
0.011037778109312057,
-0.011242571286857128,
0.026070624589920044,
0.004611952230334282,
-0.07705514878034592,
0.029575789347290993,
0.05172615125775337,
-0.08094926178455353,
0.03902832418680191,
0.0043... | 0.041205 |
probes, network performance monitoring, universal service monitoring, and related features. Both files include only nodes with `visibility: public`. The separation mirrors the fact that system-probe runs as a separate binary (`system-probe`) with its own configuration file, independently of the main Agent process. | https://github.com/DataDog/datadog-agent/blob/main/docs/public/agent-schema/faq.md | main | datadog-agent | [
-0.014241313561797142,
-0.04157602787017822,
-0.09675314277410507,
0.015816157683730125,
0.13673637807369232,
-0.06406884640455246,
0.035491425544023514,
-0.05362473428249359,
0.014751768670976162,
0.03094586171209812,
0.023676574230194092,
0.06111389026045799,
0.020735424011945724,
-0.079... | 0.245792 |
# Agent Configuration Schema The Datadog Agent configuration schema is a YAML-based [JSON Schema](https://json-schema.org/) that centrally describes every configuration setting for the Agent. It is written in YAML for readability but is fully compatible with JSON Schema tooling. ## Why it exists Previously, Agent confi... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/agent-schema/index.md | main | datadog-agent | [
-0.019137687981128693,
0.013076171278953552,
-0.06885693222284317,
-0.01729186438024044,
-0.01741328276693821,
-0.017146946862339973,
-0.009192565456032753,
-0.010701793245971203,
-0.017538942396640778,
-0.03768448531627655,
0.08185692876577377,
0.018706761300563812,
0.06721245497465134,
0... | 0.10412 |
keywords are used in the Agent schema specifically. For a general introduction to JSON Schema, see [Understanding JSON Schema](https://json-schema.org/understanding-json-schema). ## Next steps - [Keyword Reference](keywords.md) — complete reference for all supported keywords. - [Examples](examples.md) — annotated, real... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/agent-schema/index.md | main | datadog-agent | [
-0.00982186384499073,
-0.031205886974930763,
-0.08181799948215485,
-0.023987893015146255,
-0.004485637880861759,
-0.0062711844220757484,
0.02107335813343525,
0.012897497974336147,
-0.045600950717926025,
0.007033602334558964,
0.04188058152794838,
0.02376239374279976,
0.09714612364768982,
0.... | 0.1537 |
# Keyword Reference This page documents keywords supported by the Agent configuration schema. Keywords are grouped into two sections: standard JSON Schema keywords and Datadog Agent extensions. --- ## Standard JSON Schema keywords The following keywords come from the [JSON Schema standard](https://json-schema.org/under... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/agent-schema/keywords.md | main | datadog-agent | [
-0.026078104972839355,
0.0037578227929770947,
-0.02110128663480282,
0.014136770740151405,
0.027609476819634438,
-0.005479480605572462,
0.03318850323557854,
-0.038889817893505096,
-0.05421365424990654,
-0.009648974053561687,
0.05393708497285843,
-0.018743516877293587,
0.09165644645690918,
0... | 0.121796 |
the JSON Schema standard, where `title` is a > concise human-readable summary of a schema. Here, `title` is specifically a banner label applied only > to section nodes that begin a new conceptual group in the generated config file. When a section has a `title`, the config example generator produces a banner like this: ... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/agent-schema/keywords.md | main | datadog-agent | [
-0.04133767634630203,
0.050181157886981964,
-0.012307153083384037,
0.025099890306591988,
-0.020489178597927094,
-0.05400959402322769,
-0.011665803380310535,
-0.027987008914351463,
-0.019831949844956398,
-0.03702027350664139,
0.06805798411369324,
-0.07506844401359558,
0.10163161903619766,
-... | 0.036663 |
reject them. | | `required` | `object` | List of keys that must be present | | `minItems` / `maxItems` | `array` | Array length bounds | | `uniqueItems` | `array` | Requires all elements to be distinct | For the complete specification of these keywords, see [Understanding JSON Schema](https://json-schema.org/understand... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/agent-schema/keywords.md | main | datadog-agent | [
-0.0384620800614357,
0.0750817358493805,
0.012953102588653564,
0.01208517886698246,
0.02496068924665451,
-0.044538453221321106,
0.012691392563283443,
-0.049632180482149124,
-0.08180956542491913,
-0.034029342234134674,
0.07149016857147217,
-0.07094646990299225,
0.10212693363428116,
0.029136... | 0.049306 |
Any node with `visibility: public` is included in the generated config examples and any public-facing configuration website. Nodes without this keyword (or with `visibility: undocumented`) are internal and will not be surfaced. > \*\*Note:\*\* It's not because a setting is undocumented that it's not known or used by cu... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/agent-schema/keywords.md | main | datadog-agent | [
0.00823996402323246,
0.0034735817462205887,
-0.045015305280685425,
0.054870136082172394,
0.07778947055339813,
-0.006708258297294378,
0.0006579249748028815,
-0.04248763248324394,
-0.03535078838467598,
0.017140399664640427,
0.09053277224302292,
-0.033447928726673126,
0.06501572579145432,
-0.... | 0.054192 |
all teams, replacing ad-hoc solutions that previously produced inconsistent behaviour. ```yaml target\_traces\_per\_second: node\_type: setting type: number default: 10 renamed\_from: - max\_traces\_per\_second ``` --- ### `tags` An arbitrary list of strings for metadata. Used by internal tooling to slice and filter se... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/agent-schema/keywords.md | main | datadog-agent | [
-0.016919663175940514,
0.0323166623711586,
0.027119088917970657,
0.013976388610899448,
0.06192599609494209,
-0.08012761175632477,
-0.013796582818031311,
-0.0118454210460186,
-0.04692599177360535,
-0.03012518584728241,
0.043528009206056595,
-0.07477196305990219,
-0.017438838258385658,
0.004... | 0.048816 |
# Set up optional development features ----- ## Tab completion <<>> /// tip There is also limited tab completion support for the legacy `invoke` tasks. Here's an example: ``` echo "source <(dda inv --print-completion-script zsh)" >> ~/.zshrc ``` /// ## Pre-commit hooks The CI runs a number of required checks using [pre... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/setup/optional.md | main | datadog-agent | [
-0.027926025912165642,
-0.023464128375053406,
-0.003296897979453206,
-0.06379339098930359,
0.0030139361042529345,
-0.1152992844581604,
-0.07362162321805954,
0.008164254017174244,
-0.06254531443119049,
0.0801759660243988,
0.010756160132586956,
-0.09015944600105286,
-0.016846908256411552,
0.... | -0.012953 |
# Set up your local machine manually ----- These instructions are maintained on a best-effort basis. Prefer using the [developer environment](../tutorials/dev/env.md) instead. ## Prerequisites Be sure that you already set up the [development requirements](required.md). /// warning Building the Agent for Windows require... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/setup/manual.md | main | datadog-agent | [
0.01342781912535429,
0.03388736769556999,
-0.009767536073923111,
-0.012730245478451252,
-0.02048685774207115,
-0.021427612751722336,
-0.0781903862953186,
0.021900668740272522,
-0.06470376253128052,
-0.009485555812716484,
-0.00919110607355833,
-0.11039628088474274,
0.05442801117897034,
0.02... | -0.039809 |
Since, for example, macOS 10.11 may provide a different version of Python than macOS 10.12, system builds on each of these platforms may produce different Agent binaries. If this doesn't matter to you—perhaps you just want to contribute a quick bugfix—do a System build; it's easier and faster than an Embedded build. Sy... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/setup/manual.md | main | datadog-agent | [
-0.02359849028289318,
0.0015989448875188828,
-0.005588230211287737,
-0.007797259837388992,
0.0206559170037508,
-0.09947548806667328,
-0.07526891678571701,
0.042931027710437775,
-0.04436007887125015,
-0.04495292529463768,
0.03760411962866783,
-0.040644120424985886,
0.058174021542072296,
0.0... | -0.002956 |
environment](../tutorials/dev/env.md) approach is recommended. /// [Microsoft Visual Studio Code](https://code.visualstudio.com/download) with the [devcontainer plugin](https://code.visualstudio.com/docs/remote/containers) allow to use a container as remote development environment in vscode. It simplify and isolate the... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/setup/manual.md | main | datadog-agent | [
0.034388743340969086,
-0.061162710189819336,
-0.018712442368268967,
-0.012290089391171932,
-0.014225641265511513,
0.016587762162089348,
-0.11394935846328735,
0.052067872136831284,
-0.001776176504790783,
0.011294199153780937,
-0.023884836584329605,
-0.06378325819969177,
-0.058039747178554535,... | 0.012985 |
# Set up development requirements ----- ## Tooling The `dda` [CLI](https://datadoghq.dev/datadog-agent-dev/) is required in all aspects of development and must be available on `PATH`. <<>> ## Docker [Docker](https://docs.docker.com/get-started/docker-overview/) is required for both running the developer environment and... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/setup/required.md | main | datadog-agent | [
0.0067917159758508205,
-0.008252669125795364,
0.04432517662644386,
-0.07781195640563965,
-0.036385878920555115,
-0.06582694500684738,
-0.04717913269996643,
0.01381387747824192,
-0.038710881024599075,
0.0204016026109457,
0.0034275406505912542,
-0.0868459939956665,
0.045251596719026566,
0.01... | -0.017198 |
# Creating go modules in the Agent project \*\*The Datadog Agent is not meant to be imported as a Go library.\*\* However, certain parts of it can be exposed as a library by making use of [nested Go modules](https://github.com/go-modules-by-example/index/blob/master/009\_submodules/README.md). This allows for exposing ... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/go/modules.md | main | datadog-agent | [
-0.017563151195645332,
-0.002743896096944809,
-0.07231460511684418,
-0.03825173154473305,
-0.008283153176307678,
0.010148006491363049,
0.015061059966683388,
0.035852786153554916,
-0.04498840123414993,
-0.049530934542417526,
0.08362520486116409,
0.00396669702604413,
0.07347039133310318,
0.0... | -0.018394 |
inv release.finish` The `release.tag-modules` task is also called by the `release.tag-version` invoke task, using the same commit as the main module, with a tag of the form `path/to/module/v0.X.Y`. /// ## The `modules.yml` file The `modules.yml` file gathers all go module configurations. Each module is listed even if t... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/go/modules.md | main | datadog-agent | [
0.008375978097319603,
0.019126031547784805,
-0.06537184864282608,
-0.025205589830875397,
0.04219662770628929,
-0.0060137673281133175,
0.006567030213773251,
0.03857868164777756,
-0.07603944838047028,
-0.07156546413898468,
0.10329780727624893,
0.03857734054327011,
-0.026780907064676285,
0.09... | -0.008099 |
# Agent Configuration This doc describes how to define new configuration parameters for the Agent. 1. Define your config. 2. Add it to the config template (optional). 3. Use your config in your code. 4. Request a review from the Agent configuration team (team/agent-configuration) If you have any questions, head over to... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/go/config.md | main | datadog-agent | [
0.007184459362179041,
-0.021839747205376625,
-0.08813302218914032,
0.034702084958553314,
-0.02097424678504467,
-0.027705175802111626,
0.01673518307507038,
0.058654990047216415,
-0.12018077075481415,
-0.026192782446742058,
0.06120800971984863,
-0.049417294561862946,
0.10760537534952164,
-0.... | 0.06548 |
# How to run unit tests ----- The `dda inv test` command runs Go tests and is a thin wrapper around [gotestsum](https://github.com/gotestyourself/gotestsum). ## Test selection The Go module to test may be selected with the `-m`/`--module` flag using a relative path, defaulting to `.`. The `-t`/`--targets` flag is used ... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/test/unit.md | main | datadog-agent | [
-0.03024960681796074,
-0.01268136128783226,
-0.08827246725559235,
-0.026255406439304352,
0.07558118551969528,
-0.09109803289175034,
-0.032722409814596176,
0.010254877619445324,
-0.0452798493206501,
-0.045406099408864975,
0.09665931016206741,
-0.03703521564602852,
-0.05174217373132706,
0.04... | 0.064894 |
# Running E2E tests End-to-End (E2E) tests validate complete user workflows in production-like environments with real infrastructure and external services. The Datadog Agent uses the [test-infra-definitions](https://github.com/DataDog/datadog-agent/test/e2e-framework) framework to provision and manage test environments... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/test/e2e.md | main | datadog-agent | [
-0.034417685121297836,
-0.03300763666629791,
0.013514471240341663,
-0.015193256549537182,
0.0027610782999545336,
-0.12489002197980881,
-0.07255512475967407,
0.050417859107255936,
-0.05078592151403427,
-0.011430551297962666,
0.02905595302581787,
-0.07801811397075653,
0.03874918445944786,
0.... | 0.009692 |
terminal ```bash E2E\_DEV\_MODE=true inv -e new-e2e-tests.run --targets ./examples --run=^TestVMSuite$ ``` or for instance add it in the `go.testEnvVars` if you are using a VSCode-based IDE ``` "go.testEnvVars": { "E2E\_DEV\_MODE": "true", }, ``` ### Test with Local Agent Packages /// admonition | Limitations type: war... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/test/e2e.md | main | datadog-agent | [
0.04203619435429573,
-0.030479740351438522,
-0.02676278166472912,
-0.03234812244772911,
0.044860903173685074,
-0.09529902040958405,
-0.044383738189935684,
0.046467434614896774,
-0.07592189311981201,
-0.012040979228913784,
0.05609339475631714,
-0.08271754533052444,
-0.012278922833502293,
0.... | -0.023798 |
- Operating system support validation ### Performance and Scale Tests - High-throughput metric collection - Resource consumption validation - Memory leak detection - Long-running stability tests ### Security and Compliance Tests - Security configuration validation - Compliance framework testing - Permission and access ... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/test/e2e.md | main | datadog-agent | [
-0.035497453063726425,
0.03757752850651741,
-0.0738295391201973,
0.029175519943237305,
-0.0061147077940404415,
-0.07544615119695663,
-0.03476206958293915,
0.0016980984946712852,
-0.07939886301755905,
-0.014132718555629253,
-0.020088957622647285,
-0.05086500942707062,
0.027287252247333527,
... | 0.168175 |
# How to perform static analysis ----- CI enforces static analysis checks for code, configuration, documentation, and more. ## Go Go code can be analyzed with the `dda inv linter.go` command. This uses [golangci-lint](https://github.com/golangci/golangci-lint) which is an aggregator for several linters. The configurati... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/test/static-analysis.md | main | datadog-agent | [
-0.05460427701473236,
0.0203722957521677,
-0.07983460277318954,
0.007071488071233034,
0.012090509757399559,
-0.0668787881731987,
-0.00048422737745568156,
0.032582640647888184,
-0.06813904643058777,
-0.04894668608903885,
0.06396625190973282,
-0.0004499917267821729,
0.008203842677175999,
0.0... | 0.1049 |
# Windows Troubleshooting Prior to 7.23, Agent binaries (Datadog Agent, Process Agent, Trace Agent, etc.) on Windows contain symbol information. Starting from 7.23, Agent binaries on Windows have debugging information stripped. The original files are packed in a file called debug package. ## Prerequisite To debug Agent... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/debug-agents/windows.md | main | datadog-agent | [
0.0023614747915416956,
0.012888307683169842,
-0.04473119601607323,
-0.011567175388336182,
0.008404124528169632,
-0.011581996455788612,
0.001958225155249238,
-0.021668488159775734,
-0.033620890229940414,
0.025393148884177208,
0.0832393616437912,
-0.05427277460694313,
-0.011229585856199265,
... | 0.071519 |
# Linux Troubleshooting ## Generating and using core dumps on Linux ### Generating core dumps on Agent crashes There are two ways to generate core dumps when the Agent crashes on Linux. Starting on version 7.27 the Datadog Agent includes the `go\_core\_dump` option that, when enabled, makes any Agent process generate a... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/debug-agents/linux.md | main | datadog-agent | [
0.018852651119232178,
-0.04881676286458969,
-0.04539336636662483,
-0.023696279153227806,
0.06166301667690277,
-0.02440525032579899,
-0.060225632041692734,
0.09090261906385422,
-0.06344816088676453,
0.04977274313569069,
-0.01199579518288374,
-0.05477873608469963,
-0.00637661200016737,
-0.01... | 0.092385 |
# Tools to troubleshoot a running Agent This page attempts to list useful tools and resources to troubleshoot and profile a running Agent. ## [pprof](https://golang.org/pkg/net/http/pprof/) The Agent exposes pprof's HTTP server on port `5000` by default. Through the pprof port you can get profiles (CPU, memory, etc) on... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/debug-agents/index.md | main | datadog-agent | [
-0.004573589190840721,
0.020748719573020935,
-0.15023721754550934,
-0.0032945626880973577,
-0.039483096450567245,
-0.04630249738693237,
0.01213746890425682,
0.07296320796012878,
-0.04920089244842529,
-0.005261954385787249,
0.07271184027194977,
-0.00047575312783010304,
-0.01521395891904831,
... | 0.088206 |
# Go tracking and troubleshooting To investigate the Go portion of the process memory, you can use the usual and expected tooling available to any Go binary. If you encounter a leak in the Agent process as seen in the process RSS, review the Go memory profile. If everything is okay, the leak may be elsewhere. The usual... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/memory-profiling/go.md | main | datadog-agent | [
0.017368678003549576,
0.009513352066278458,
-0.11920882016420364,
0.011608675122261047,
0.0018938726279884577,
-0.035943351686000824,
0.003370258491486311,
0.05519628897309303,
-0.004588289186358452,
0.01582079939544201,
0.041179314255714417,
-0.0025066169910132885,
-0.034417323768138885,
... | 0.038223 |
will help you get started, but there is more information available in the links below. ### Further Reading - [Julia Evans: go profiling](https://jvns.ca/blog/2017/09/24/profiling-go-with-pprof/) - [Detectify: memory leak investigation](https://blog.detectify.com/2019/09/05/how-we-tracked-down-a-memory-leak-in-one-of-ou... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/memory-profiling/go.md | main | datadog-agent | [
0.03566119819879532,
-0.045110512524843216,
-0.09049317985773087,
0.0268324613571167,
0.028649073094129562,
-0.006836947984993458,
0.068283811211586,
0.08671972900629044,
-0.03053932823240757,
0.02134246751666069,
0.0529802031815052,
0.03213011845946312,
-0.06775830686092377,
0.03933529183... | 0.114377 |
# Python tracking and troubleshooting Python, another runtime in the Agent process, is also garbage collected. Datadog offers two tools with the Agent that can help you identify memory issues: - Python memory telemetry (Python 3 only) - Tracemalloc - Pympler ### Python memory telemetry Python memory telemetry hooks int... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/memory-profiling/python.md | main | datadog-agent | [
0.041854970157146454,
-0.0009397247922606766,
-0.0828172117471695,
0.05454006791114807,
-0.04965319111943245,
-0.12859229743480682,
-0.008031068369746208,
0.05472968518733978,
0.006688173394650221,
0.012602201662957668,
0.012415756471455097,
0.020973743870854378,
0.024861793965101242,
-0.0... | 0.054409 |
is to allow us to more easily identify sources of allocations without the interference of the GC. Note that the GC is not permanently disabled, this is only enforced during the check run while tracemalloc is tracking allocations. Default: disabled. - `combine`: whether or not to aggregate over all traceback frames. use... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/memory-profiling/python.md | main | datadog-agent | [
-0.04586891084909439,
-0.04347837716341019,
-0.06655218452215195,
0.014872261323034763,
0.052005574107170105,
-0.07236803323030472,
0.04574074596166611,
0.008321112021803856,
-0.014929557219147682,
-0.012736104428768158,
0.03513992950320244,
0.05408833175897598,
-0.024072883650660515,
-0.0... | 0.088437 |
Troubleshooting Agent Memory Usage The Agent process presents unusual challenges when it comes to memory profiling and investigation. Multiple memory spaces, with various heaps coming from multiple different runtimes, can make identifying memory issues tricky. The Agent has three distinct memory spaces, each handled in... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/memory-profiling/overview.md | main | datadog-agent | [
0.04545339569449425,
0.012484143488109112,
-0.1108592301607132,
0.03593672066926956,
-0.018268434330821037,
-0.061427339911460876,
-0.02675621211528778,
0.03190168738365173,
-0.010775735601782799,
-0.04807783663272858,
0.0018127006478607655,
0.006215537898242474,
0.015185192227363586,
0.05... | 0.038466 |
# C/C++ tracking and troubleshooting Allocations in the Datadog cgo and [RTLoader](https://github.com/DataDog/datadog-agent/blob/main/rtloader/common/rtloader\_mem.h) code have been wrapped by a set of helper functions that help keep accounting with regard to the number of allocations made and freed, as well as their r... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/memory-profiling/c++.md | main | datadog-agent | [
-0.021909678354859352,
0.031330130994319916,
-0.012324931100010872,
0.08266126364469528,
-0.0038812800776213408,
-0.025039570406079292,
0.0005130980862304568,
0.03159460797905922,
0.013391449116170406,
0.02246914617717266,
0.042715027928352356,
-0.014163327403366566,
0.01749112457036972,
0... | 0.075107 |
# How to build agent distribution packages --- ## Intro ### What are distribution packages ? By "distribution package", we mean an artifact used by end users to install the Agent on their system. The format is OS-specific: | OS | Package Format | | ------- | ------------------------------------------- | | Linux | `.deb... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/build/distributions.md | main | datadog-agent | [
-0.08434689044952393,
-0.0162105243653059,
-0.026009541004896164,
-0.05401655659079552,
0.040746793150901794,
-0.036062560975551605,
0.0014082671841606498,
-0.0038986029103398323,
-0.05404885113239288,
-0.022233018651604652,
0.0730169266462326,
-0.08940587937831879,
0.020629022270441055,
-... | 0.132751 |
the root folder of a clone of the `datadog-agent` repo. 1. Run the following command, which will create a container for the previously-mentioned image, and run the `omnibus.build` task inside. ```bash docker run -v "$PWD:/go/src/github.com/DataDog/datadog-agent" -v "/tmp/omnibus:/omnibus" -v "/tmp/opt/datadog-agent:/op... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/build/distributions.md | main | datadog-agent | [
-0.03758564963936806,
-0.001981870736926794,
-0.04733739793300629,
-0.05123215913772583,
0.01661130040884018,
-0.11853612214326859,
-0.07537055760622025,
0.008886960335075855,
0.016822224482893944,
0.009906555525958538,
0.02443384751677513,
-0.0005254899733699858,
0.05535975471138954,
0.01... | -0.018877 |
available. This image, contrary to the main `datadog/agent-buildimages-linux` image, is not multi-arch - thus there are two flavors depending on the CPU architecture of the host machine: - For `x86\_64`/`amd64`: [`datadog/agent-buildimages-rpm\_x64`](https://hub.docker.com/r/datadog/agent-buildimages-rpm\_x64) - For `a... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/build/distributions.md | main | datadog-agent | [
-0.0025228888262063265,
0.03154393658041954,
0.004058932885527611,
-0.061015401035547256,
0.0053857765160501,
-0.08950797468423843,
-0.10999896377325058,
0.0023362631909549236,
-0.033349957317113876,
0.025474369525909424,
0.005055893678218126,
-0.07346674054861069,
0.03250308334827423,
-0.... | 0.013165 |
# How to build standalone agent binaries ----- ## Building agent binaries The Core Agent is built using the `dda inv agent.build` command. ``` dda inv agent.build --build-exclude=systemd ``` Running this command will: - Discard any changes done in `bin/agent/dist`. - Build the Agent and write the binary to `bin/agent/a... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/build/standalone.md | main | datadog-agent | [
-0.030207140371203423,
-0.015531428158283234,
-0.07053514569997787,
-0.0639754980802536,
0.0033132003154605627,
-0.0598597526550293,
-0.03775328770279884,
0.032896749675273895,
-0.06042008474469185,
0.010739847086369991,
0.0456421822309494,
-0.07894634455442429,
0.04502482712268829,
-0.023... | 0.008058 |
/// details | Under the hood open: False type: info Making a bundle - combining functionality from multiple binaries - just corresponds to building an agent binary including the source code from the others. Like other features, this is accomplished through Go build constraints. Under the hood, building with a `--bundle... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/how-to/build/standalone.md | main | datadog-agent | [
-0.04779578372836113,
0.0056748040951788425,
-0.06306588649749756,
-0.06063004955649376,
0.07384689152240753,
-0.04428902268409729,
0.030733266845345497,
0.04198642447590828,
-0.06820840388536453,
-0.036563046276569366,
0.056027721613645554,
-0.03143395483493805,
0.015156926587224007,
0.01... | 0.059526 |
# Overview of components The Agent is structured as a collection of components working together. Depending on how the binary is built, and how it is invoked, different components may be instantiated. ## What is a component? The goal of a component is to encapsulate a particular piece of logic/feature and provide a clea... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/components/overview.md | main | datadog-agent | [
-0.013077323324978352,
-0.0026250085793435574,
-0.0417742095887661,
0.006584334187209606,
-0.029611876234412193,
0.015641460195183754,
-0.006099143531173468,
0.010711712762713432,
0.017835337668657303,
-0.036683589220047,
0.020857101306319237,
-0.03784940764307976,
0.039759524166584015,
0.... | 0.129061 |
# Creating a bundle A bundle is a grouping of related components. The goal of a bundle is to ease the usage of multiple components working together to constitute a product. One example is `DogStatsD`, a server to receive metrics locally from customer apps. `DogStatsD` is composed of 9+ components, but at the binary lev... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/components/creating-bundles.md | main | datadog-agent | [
-0.06964699178934097,
-0.0326344296336174,
-0.034949980676174164,
-0.003745767753571272,
0.004270200617611408,
0.00665128231048584,
0.02888229861855507,
0.10176081955432892,
-0.03213735669851303,
-0.006916641723364592,
0.1118096336722374,
-0.02122328244149685,
0.062087174504995346,
0.07137... | 0.044662 |
# FAQ ## Optional Component You might need to express the fact that some of your dependencies are optional. This often happens for components that interact with many other components \*\*if available\*\* (that is, if they were included at compile time). This allows your component to interact with each other without for... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/components/faq.md | main | datadog-agent | [
0.017139974981546402,
-0.029266826808452606,
-0.03569379076361656,
-0.005490580573678017,
0.024143043905496597,
-0.028010286390781403,
0.019664011895656586,
0.07960030436515808,
-0.004937543533742428,
0.004361881874501705,
0.1147511675953865,
-0.0889691561460495,
0.007776699960231781,
0.04... | 0.045611 |
# Creating a Component This page explains how to create components in detail. This page uses the example of creating a compression component. This component compresses a payload before sending it to the Datadog backend. Since there are multiple ways to compress data, this component provides two implementations of the s... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/components/creating-components.md | main | datadog-agent | [
-0.10291176289319992,
0.05762676149606705,
-0.05173705145716667,
0.01521235890686512,
0.03019714541733265,
-0.04538177698850632,
0.013142210431396961,
0.053560756146907806,
0.0003407915064599365,
-0.019745618104934692,
0.02319849468767643,
0.06781528890132904,
0.08760926127433777,
0.035580... | 0.136487 |
// Decompress decompresses the input data. Decompress([]byte) ([]byte, error) } ``` /// All component interfaces must be called `Component`, so all imports have the form `.Component`. You can see that the interface only exposes the bare minimum. You should aim at having the smallest possible interface for your componen... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/components/creating-components.md | main | datadog-agent | [
-0.04312865436077118,
0.031854577362537384,
-0.051989130675792694,
-0.007519363891333342,
-0.03895020857453346,
-0.09012042731046677,
0.022370873019099236,
0.08747602999210358,
-0.04281610623002052,
-0.046166207641363144,
0.03881004452705383,
-0.06413409113883972,
0.009241088293492794,
0.0... | 0.190843 |
package zstdimpl import ( "fmt" compression "github.com/DataDog/datadog-agent/comp/compression/def" config "github.com/DataDog/datadog-agent/comp/core/config/def" log "github.com/DataDog/datadog-agent/comp/core/log/def" ) type Requires struct { Conf config.Component Log log.Component } type Provides struct { Comp compr... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/components/creating-components.md | main | datadog-agent | [
-0.07204610854387283,
0.06401437520980835,
-0.07597258687019348,
0.016197161749005318,
0.013554261066019535,
-0.03854019194841385,
0.01299177948385477,
0.08429894596338272,
-0.07641516625881195,
-0.037678979337215424,
0.014950470067560673,
0.0045594521798193455,
0.0470832996070385,
0.12880... | 0.035452 |
mock must implement the `Component` interface of the `def` folder but can expose more methods if needed. All mock constructors must take a `\*testing.T` as parameter. In the following example, your mock has no dependencies and returns the same string every time. /// tab | :octicons-file-code-16: comp/compression/mock/m... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/components/creating-components.md | main | datadog-agent | [
-0.09816064685583115,
0.05337544158101082,
-0.0701860785484314,
0.015607575885951519,
-0.047738101333379745,
-0.06937866657972336,
0.006821533665060997,
0.020783355459570885,
-0.07367287576198578,
-0.02807777374982834,
0.03873182833194733,
0.007032101508229971,
0.05597534403204918,
0.08956... | 0.00127 |
the robustness of the Agent. Documentation should include: \* Precise information on when each method may be called. Can methods be called concurrently? \* Precise information about data ownership of passed values and returned values. Users can assume that any mutable value returned by a component will not be modified ... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/components/creating-components.md | main | datadog-agent | [
-0.07017488777637482,
0.009405051358044147,
-0.045873165130615234,
0.03468434512615204,
-0.04808148369193077,
-0.034047916531562805,
-0.00869860127568245,
0.03407304733991623,
-0.0005341575015336275,
-0.011525842361152172,
0.035400569438934326,
0.0417151041328907,
0.0029448263812810183,
0.... | 0.079731 |
# Testing components Testing is an essential part of the software development life cycle. This page covers everything you need to know about testing components. One of the core benefits of using components is that each component isolates its internal logic behind its interface. Focus on asserting that each implementati... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/components/testing.md | main | datadog-agent | [
-0.04314294084906578,
0.03767034038901329,
-0.029375921934843063,
0.008608655072748661,
-0.005779542960226536,
-0.06108930706977844,
-0.03296681493520737,
-0.00798560120165348,
-0.03129059821367264,
-0.03224559500813484,
0.021316388621926308,
0.03797480836510658,
0.04366305097937584,
0.081... | 0.027402 |
`started` and `stopped` fields. To accomplish this, create a new lifecycle instance, create a `Require` struct instance, initialize the component, and validate that calling `Start` on the lifecycle instance calls the component hook and executes the logic. To create a lifecycle instance, use the helper function `compdef... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/components/testing.md | main | datadog-agent | [
-0.04321097210049629,
0.025142448022961617,
-0.08100199699401855,
-0.0013899299083277583,
0.0043181562796235085,
-0.008332004770636559,
-0.011436506174504757,
0.024670399725437164,
-0.055277761071920395,
-0.0037234548944979906,
0.09881536662578583,
0.003175963880494237,
-0.03628312051296234,... | 0.019379 |
# Overview of Fx The Agent uses [Fx](https://uber-go.github.io/fx) as its application framework. While the linked Fx documentation is thorough, it can be a bit difficult to get started with. This document describes how Fx is used within the Agent in a more approachable style. ## What Is It? Fx's core functionality is t... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/components/fx.md | main | datadog-agent | [
-0.012572191655635834,
-0.06728412955999374,
-0.013813816010951996,
0.04039676859974861,
-0.010572804138064384,
-0.0025619585067033768,
0.06608408689498901,
0.04243559390306473,
-0.0002963038859888911,
-0.09650155901908875,
-0.009508242830634117,
-0.023694800212979317,
0.011132501997053623,
... | 0.228309 |
an app that requirements are met, constructors are called, and so on. Tying the example above together, a very simple app might look like this: ```go someValue = "my password is hunter2" app := fx.New( fx.Provide(scrubber.NewScrubber), fx.Invoke(func(sc scrubber.Component) { fmt.Printf("scrubbed: %s", sc.ScrubString(so... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/components/fx.md | main | datadog-agent | [
-0.04188359156250954,
0.00022951366554480046,
-0.028527148067951202,
0.033653996884822845,
-0.0029705658089369535,
-0.02202407270669937,
0.06395933032035828,
0.09050553292036057,
-0.020907439291477203,
-0.0792144387960434,
0.034535761922597885,
-0.03294214606285095,
-0.014078417792916298,
... | 0.076116 |
by other components. For example: Here, two components add a `server.Endpoint` type to the `server` group (note the `group` label in the `fx.Out` struct). /// tab | :octicons-file-code-16: todolist/todolist.go ```go type provides struct { fx.Out Component Endpoint server.Endpoint `group:"server"` } ``` /// /// tab | :o... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/components/fx.md | main | datadog-agent | [
-0.010849940590560436,
-0.026360157877206802,
-0.04443397372961044,
0.032623469829559326,
-0.04816204309463501,
-0.00032511993777006865,
0.047518737614154816,
0.05676503852009773,
-0.0017063870327547193,
-0.07111657410860062,
0.0824805274605751,
-0.03757740929722786,
-0.09794875234365463,
... | 0.118643 |
# JMXFetch [JMXFetch](https://github.com/DataDog/jmxfetch/) is the component of the Agent which is responsible for collecting metrics from Java applications. For more details on JMXFetch or developer documentation, please visit the project documentation on the [JMXFetch GitHub repo](https://github.com/DataDog/jmxfetch/... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/components/jmxfetch.md | main | datadog-agent | [
-0.011837144382297993,
-0.0428827628493309,
-0.01894674263894558,
-0.06239213049411774,
-0.05054249241948128,
-0.004751835484057665,
-0.0029771672561764717,
0.04953771457076073,
-0.04498154670000076,
-0.014828343875706196,
0.012035145424306393,
-0.06933798640966415,
0.04241286590695381,
-0... | 0.092872 |
# Using components Using components within other components is covered on the [create components page](creating-components.md). Now let's explore how to use components in your binaries. One of the core idea behind component design is to be able to create new binaries for customers by aggregating components. ## the `cmd... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/components/using-components.md | main | datadog-agent | [
0.021239779889583588,
-0.043484367430210114,
-0.1321137398481369,
-0.06294714659452438,
-0.058529436588287354,
0.008502602577209473,
0.012048589065670967,
0.09319629520177841,
-0.08476891368627548,
-0.0166811291128397,
0.025678453966975212,
-0.07751475274562836,
0.06991611421108246,
0.0672... | 0.036088 |
migration to components is not finished, you might need to manually instruct Fx on how to use plain types. You will need to use `fx.Supply` for this. More details can be found [here](fx.md). But here is a quick example: ```go import ( logfx "github.com/DataDog/datadog-agent/comp/core/log/fx" log "github.com/DataDog/dat... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/components/using-components.md | main | datadog-agent | [
0.06926456093788147,
-0.02061537653207779,
-0.014934418722987175,
0.042376600205898285,
0.021572308614850044,
-0.015772512182593346,
0.06303854286670685,
0.10960092395544052,
-0.04147820174694061,
-0.06412400305271149,
0.03342683985829353,
-0.09207964688539505,
-0.025897154584527016,
0.112... | 0.039277 |
## Groups Fx [groups](https://pkg.go.dev/go.uber.org/fx#hdr-Value\_Groups) help you produce and group together values of the same type, even if these values are produced in different parts of the codebase. A component can add any type into a group; this group can then consumed by other components. In the following exam... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/components/common-patterns.md | main | datadog-agent | [
0.00429295701906085,
-0.019178932532668114,
-0.04630247876048088,
0.019877497106790543,
-0.05224796012043953,
0.0065953172743320465,
0.02076607011258602,
0.006201653275638819,
-0.019131185486912727,
-0.0798838660120964,
0.07505135983228683,
-0.04870534688234329,
-0.07339432090520859,
0.086... | 0.073777 |
# Flare The general idea is to register a callback within your component to be called each time a flare is created. This uses [Fx](../fx.md) groups under the hood, but helpers are there to abstract all the complexity. Once the callback is created, you will have to migrate the code related to your component from `pkg/fl... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/components/shared_features/flares.md | main | datadog-agent | [
-0.002036475343629718,
-0.04461400955915451,
-0.03668339550495148,
0.10936563462018967,
-0.017109358683228493,
-0.006639618426561356,
0.062017057090997696,
0.06847745180130005,
-0.025612320750951767,
-0.07349473237991333,
-0.03312690928578377,
-0.028181258589029312,
0.016168300062417984,
0... | 0.030351 |
# Status Components can register a status provider. When the status command is executed, we will populate the information displayed using all the status providers. ## Status Providers There are two types of status providers: - \*\*Header Providers:\*\* these providers are displayed at the top of the status output. This... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/components/shared_features/status.md | main | datadog-agent | [
-0.03712264820933342,
0.05325181037187576,
-0.06985507905483246,
0.020630070939660072,
0.007404405158013105,
-0.0053686415776610374,
-0.0020975524093955755,
0.007923892699182034,
0.007091890554875135,
-0.015684669837355614,
0.03929245471954346,
0.0036209982354193926,
0.04532844200730324,
-... | 0.162221 |
// Index renders the index func (c \*compressor) Section() int { return "Compression" } // JSON populates the status map func (c \*compressor) JSON(\_ bool, stats map[string]interface{}) error { c.populateStatus(stats) return nil } // Text renders the text output func (c \*compressor) Text(\_ bool, buffer io.Writer) er... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/components/shared_features/status.md | main | datadog-agent | [
-0.04673314094543457,
0.09319151937961578,
-0.05542870983481407,
0.07875489443540573,
0.007507710251957178,
0.04221361503005028,
-1.5787107088272023e-7,
0.07268340140581131,
0.005936304572969675,
-0.043164774775505066,
0.022860636934638023,
-0.03909284248948097,
-0.01960216462612152,
0.029... | 0.15435 |
# DogStatsD internals { loading=lazy role="img" } (click to enlarge) Information on DogStatsD, configuration and troubleshooting is available in the [Datadog documentation](https://docs.datadoghq.com/developers/dogstatsd/). ## Packet In DogStatsD, a Packet is a bytes ... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/architecture/dogstatsd/internals.md | main | datadog-agent | [
0.010290293954312801,
0.00597582571208477,
0.04821939393877983,
-0.013912854716181755,
-0.06695921719074249,
-0.05425552278757095,
-0.028564225882291794,
0.0029919296503067017,
-0.0024287074338644743,
0.019591862335801125,
0.01237077172845602,
-0.030339185148477554,
0.08590427041053772,
-0... | 0.02304 |
less than 2, the server spawns 2 workers. The Worker is using a system called StringInterner to not allocate memory every time a string is needed. Note that this StringInterner is caching a finite number of strings and when it is full it is emptied to start caching strings again. Its size is configurable with `dogstats... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/architecture/dogstatsd/internals.md | main | datadog-agent | [
-0.007343541830778122,
-0.03137599676847458,
-0.03970399871468544,
0.001220045960508287,
-0.13164012134075165,
-0.0554928332567215,
0.049194831401109695,
0.020737022161483765,
0.04697466641664505,
-0.0011008058208972216,
-0.025640344247221947,
-0.008561616763472557,
0.058133602142333984,
-... | 0.136423 |
# Config-provided hostname starting with `ip-` or `domu` ## Description of the issue In v6 and v7 Agents, if `hostname` is set in `datadog.yaml` (or through the `DD\_HOSTNAME` env var) and its value starts with `ip-` or `domu`, the hostname is not used in-app as the canonical hostname, even if it is a valid hostname. M... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/hostname/hostname_force_config_as_canonical.md | main | datadog-agent | [
0.019844401627779007,
-0.029794303700327873,
0.0333389975130558,
-0.05195463076233864,
-0.018159959465265274,
-0.09435427188873291,
-0.051780108362436295,
-0.030179576948285103,
-0.0037128368858247995,
0.018275167793035507,
0.048455558717250824,
-0.06044969707727432,
0.09504622966051102,
-... | -0.035002 |
# Using developer environments ----- Developer environments are preconfigured workspaces that provide everything required for contributing to the Agent code base, testing changes and building release artifacts. Usually, these are [images](../../reference/images/dev.md) that run using a container orchestrator like Docke... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/tutorials/dev/env.md | main | datadog-agent | [
0.014797406271100044,
-0.04236266762018204,
-0.015544882975518703,
-0.04343636333942413,
-0.0031546144746243954,
-0.11187397688627243,
-0.06934340298175812,
0.0017767079407349229,
-0.018793974071741104,
0.030447931960225105,
0.00439004972577095,
-0.10991846770048141,
0.053787946701049805,
... | 0.056022 |
``` dda env dev start --clone ``` You can also [configure][dda-config] `dda` to always [clone repositories](https://datadoghq.dev/datadog-agent-dev/reference/api/config/#dda.config.model.env.DevEnvConfig.clone\_repos) for developer environments with the following command. ``` dda config set env.dev.clone-repos true ```... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/tutorials/dev/env.md | main | datadog-agent | [
-0.0412462055683136,
-0.07447654753923416,
-0.011490068398416042,
-0.08079246431589127,
-0.014192519709467888,
-0.1162419468164444,
-0.049099214375019073,
-0.01044019777327776,
0.0048219203017652035,
0.025661982595920563,
0.04731785133481026,
-0.03225661814212799,
0.033886127173900604,
-0.... | -0.073728 |
in which to run the command is determined by the `-r`/`--repo` option, defaulting to the first defined [repository](#repository-selection). ## Building Let's [build](../../how-to/build/standalone.md) the default Agent by running the following command locally. ``` dda env dev run -- dda inv agent.build --build-exclude=s... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/tutorials/dev/env.md | main | datadog-agent | [
-0.0019483771175146103,
-0.03843310847878456,
-0.04533893242478371,
-0.12278635799884796,
0.025048760697245598,
-0.07613085210323334,
-0.06498824805021286,
0.013596760109066963,
-0.01593884453177452,
0.026345068588852882,
0.004544567782431841,
-0.07887684553861618,
0.008351875469088554,
-0... | -0.078877 |
# Lab environments ----- Lab environments are Kubernetes clusters for testing the Datadog Agent. The `dda lab` command group manages these environments. ## Supported providers | Provider | Category | Description | |----------|----------|-------------| | [Kind](kind.md) | Local | Kubernetes in Docker - lightweight local... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/tutorials/dev/lab/index.md | main | datadog-agent | [
0.008172090165317059,
-0.004461359232664108,
0.00845267716795206,
-0.0527503602206707,
0.022297710180282593,
-0.08637558668851852,
-0.029929688200354576,
-0.012845896184444427,
0.028838185593485832,
0.0009993785060942173,
0.013683948665857315,
-0.1283094584941864,
0.0116537781432271,
-0.01... | 0.102078 |
# Kind ----- [Kind](https://kind.sigs.k8s.io/) (Kubernetes in Docker) creates lightweight local Kubernetes clusters for development and testing. ## Prerequisites - Docker (or an equivalent container runtime) - [kind](https://kind.sigs.k8s.io/docs/user/quick-start/#installation) - [helm](https://helm.sh/docs/intro/insta... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/tutorials/dev/lab/kind.md | main | datadog-agent | [
0.019617248326539993,
0.030189095064997673,
0.04343513399362564,
-0.032745327800512314,
0.025641754269599915,
0.0017562549328431487,
-0.06369931995868683,
-0.013520372100174427,
0.0356949046254158,
0.033499911427497864,
0.002551580313593149,
-0.08198031038045883,
-0.007836021482944489,
-0.... | 0.081587 |
# Contributing to Datadog Agent First of all, thanks for contributing! This document provides some basic guidelines for contributing to this repository. To propose improvements, feel free to submit a PR. ## Submitting issues \* If you think you've found an issue, please search the [Agent Troubleshooting][agent-troubles... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/guidelines/contributing.md | main | datadog-agent | [
-0.031968556344509125,
-0.03837957605719566,
0.026263132691383362,
0.061537228524684906,
0.0030580349266529083,
-0.05643587186932564,
-0.01173699926584959,
-0.03850962594151497,
-0.05115516111254692,
0.08443784713745117,
0.04361404478549957,
-0.0662229135632515,
0.046510353684425354,
0.005... | -0.004563 |
-m "Fixed stuff"`. Take a moment to write meaningful commit messages. The commit message should describe the reason for the change and give extra details that will allow someone later on to understand in 5 seconds the thing you've been working on for a day. This includes editing the commit message generated by GitHub f... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/guidelines/contributing.md | main | datadog-agent | [
-0.04165346920490265,
0.020943831652402878,
-0.03677327558398247,
0.011956118047237396,
0.06217678263783455,
0.005200507119297981,
-0.0664205402135849,
0.029634937644004822,
-0.03231614828109741,
0.10135477781295776,
0.0307683777064085,
-0.0004941328661516309,
-0.026738356798887253,
-0.045... | 0.028366 |
behavior of the Agent and therefore shouldn't be mentioned in the CHANGELOG (examples: repository documentation updates, changes in code comments). PRs that don't require a release note file will be labeled `changelog/no-changelog` by maintainers. To install reno: `pip install reno` Ultra quick `Reno` HOWTO: ```bash $>... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/guidelines/contributing.md | main | datadog-agent | [
0.01609663851559162,
-0.003071774262934923,
0.01762201078236103,
0.007913573645055294,
0.05356618016958237,
0.032515134662389755,
0.02736537903547287,
0.019413596019148827,
0.0662635862827301,
0.04851710796356201,
0.059164922684431076,
0.0538562573492527,
0.0008771216380409896,
0.035894796... | 0.031052 |
- `changelog/no-changelog`: for PRs that don't require a reno releasenote (useful for PRs only changing documentation or tests). - `qa/done` or `qa/no-code-change`: used to skip the QA week: - `qa/done` label is recommended in case of code changes \*\*\*and\*\*\* manual / automated QA done before merge. - `qa/no-code-c... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/guidelines/contributing.md | main | datadog-agent | [
-0.039798326790332794,
0.012680026702582836,
-0.032837480306625366,
-0.02280302532017231,
-0.02829987183213234,
-0.017094867303967476,
-0.039008982479572296,
0.024390581995248795,
0.017482897266745567,
0.05820887163281441,
0.06435001641511917,
-0.039751939475536346,
-0.04123590141534805,
0... | 0.043895 |
# Writing developer docs ----- This site is built by [MkDocs](https://github.com/mkdocs/mkdocs) and uses the [Material for MkDocs](https://squidfunk.github.io/mkdocs-material/) theme. You can serve documentation locally with the `dda run docs serve` command. ## Organization The site structure is defined by the [`nav`](... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/guidelines/docs.md | main | datadog-agent | [
-0.08098028600215912,
-0.046051591634750366,
0.04361686855554581,
0.008784420788288116,
0.007796338759362698,
-0.07253667712211609,
-0.09434454888105392,
-0.017500340938568115,
0.031293533742427826,
0.03757870942354202,
0.006255160551518202,
0.023756489157676697,
0.02260315790772438,
0.021... | 0.089854 |
# Component Registrations Components generally need to talk to one another! In simple cases, that occurs by method calls. But in many cases, a single component needs to communicate with a number of other components that all share some characteristics. For example, the `comp/core/health` component monitors the health of... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/guidelines/deprecated-components-documentation/registrations.md | main | datadog-agent | [
-0.022423261776566505,
-0.04522661119699478,
-0.04167822375893593,
0.0722530335187912,
-0.00834063533693552,
0.0293588787317276,
0.07784465700387955,
0.031272754073143005,
0.050305914133787155,
-0.07137301564216614,
0.02661035768687725,
-0.06816946715116501,
0.022237731143832207,
0.0517031... | 0.126816 |
# Defining Apps and Binaries ## Binaries Each binary is defined as a `main` package in the `cmd/` directory, such as `cmd/iot-agent`. This top-level package contains \_only\_ a simple `main` function (or often, one for Windows and one for \*nix) which performs any platform-specific initialization and then creates and e... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/guidelines/deprecated-components-documentation/defining-apps.md | main | datadog-agent | [
-0.0556374154984951,
0.055148251354694366,
-0.06950724124908447,
-0.02242937870323658,
-0.027818789705634117,
-0.07328113168478012,
-0.008899707347154617,
0.06336072087287903,
-0.042845677584409714,
-0.04043574631214142,
0.06707844883203506,
-0.04918784275650978,
0.025251004844903946,
0.04... | 0.114667 |
subcommands := sf(&globalParams) for \_, cmd := range subcommands { agentCmd.AddCommand(cmd) } } return cmd } ``` If the available subcommands depend on build flags, move the creation of the subcommand factories to the `subcommands/` package and create the slice there using source files with `//go:build` directives. Yo... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/guidelines/deprecated-components-documentation/defining-apps.md | main | datadog-agent | [
-0.05234881490468979,
-0.012777147814631462,
-0.03536014258861542,
-0.052407167851924896,
-0.062407586723566055,
-0.008267959579825401,
-0.011191180907189846,
0.05764508992433548,
-0.111172154545784,
-0.047988034784793854,
0.08608389645814896,
-0.11880387365818024,
0.004586178343743086,
0.... | 0.075172 |
# Defining Component Bundles A bundle is defined in a dedicated package named `comp/`. The package must have the following defined in `bundle.go`: \* Extensive package-level documentation. This should define: \* The purpose of the bundle \* What components are and are not included in the bundle. Components might be omi... | https://github.com/DataDog/datadog-agent/blob/main/docs/public/guidelines/deprecated-components-documentation/defining-bundles.md | main | datadog-agent | [
-0.06754706799983978,
0.0037190087605267763,
0.008832432329654694,
0.004173486027866602,
0.06121546030044556,
0.07514358311891556,
0.055386755615472794,
0.10386944562196732,
-0.05991964787244797,
-0.04519588127732277,
0.09322233498096466,
-0.028511233627796173,
-0.04025435447692871,
0.0941... | 0.067606 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.