Meta tags:
description= The source for Datadog s documentation site. Contribute to DataDog/documentation development by creating an account on GitHub.;
Headings (most frequently used words):
navigation, about, datadog, repository, files, to, docs, contributors, footer, topics, resources, contributing, stars, watchers, forks, documentation, site, for, menu, latest, commit, history, folders, and, contribute, the, working, on, releasing, how, add, new, integration, releases, packages, used, by, languages, pr, etiquette, outside, staff, note, markdown,
Text of the page (most frequently used words):
the (61), and (29), you (26), for (23), #datadog (21), your (21), github (18), #documentation (16), docs (15), not (11), contributing (10), preview (10), yml (10), this (9), repository (9), all (9), that (8), site (8), build (8), branch (8), code (8), can (7), master (7), pull (7), claude (7), astro (7), readme (6), hugo (6), see (6), are (6), with (6), request (6), changes (6), commit (6), team (6), content (6), information (5), security (5), license (5), source (5), how (5), from (5), change (5), review (5), quality (5), support (5), one (5), navigation (4), forks (4), stars (4), 624 (4), about (4), make (4), file (4), markdown (4), should (4), use (4), ready (4), name (4), description (4), customer (4), problem (4), tab (4), files (4), more (4), folder (4), json (4), signed (4), copilot (4), time (3), resources (3), wiki (3), these (3), when (3), links (3), pages (3), our (3), work (3), will (3), website (3), such (3), guidelines (3), must (3), gitlab (3), don (3), fork (3), human (3), open (3), repo (3), edit (3), static (3), analysis (3), actions (3), another (3), window (3), refresh (3), session (3), reload (3), sign (3), developers (3), changelog (3), enterprise (3), grade (3), features (3), action (2), community (2), status (2), footer (2), contributors (2), report (2), watching (2), 630 (2), watchers (2), custom (2), properties (2), activity (2), hacktoberfest (2), topics (2), datadoghq (2), com (2), page (2), add (2), new (2), merging (2), process (2), minutes (2), takes (2), may (2), but (2), locally (2), production (2), which (2), include (2), any (2), give (2), note (2), generate (2), link (2), feature (2), consult (2), won (2), get (2), getting (2), issues (2), broken (2), using (2), notifications (2), slack (2), always (2), follow (2), steps (2), employee (2), title (2), added (2), them (2), ourselves (2), large (2), detailed (2), they (2), need (2), fix (2), made (2), descriptions (2), requests (2), updating (2), out (2), want (2), many (2), contribution (2), most (2), api (2), published (2), items (2), translate (2), yaml (2), prettier (2), config (2), general (2), synthetics (2), docker (2), compose (2), repo_reorg (2), caddyfile (2), agents (2), vale (2), ini (2), rubocop (2), prettierignore (2), gitignore (2), gitattributes (2), eslintrc (2), eslintignore (2), editorconfig (2), shared (2), vscode (2), husky (2), last (2), message (2), 792 (2), commits (2), latest (2), menu (2), star (2), settings (2), insights (2), 549 (2), universe (2), training (2), integrations (2), stories (2), center (2), learn (2), business (2), fixes (2), products (2), secret (2), perform, share, personal, manage, cookies, contact, privacy, terms, 2026, inc, languages, used, packages, releases, dedicated, doc, integration, triggers, automatic, deployment, typically, begins, within, usually, around, complete, though, times, vary, releasing, sure, names, lowercase, macs, case, insensitive, creating, images, server, tests, fail, uses, compliant, cases, extension, commonmark, goldmark, running, optional, followed, naming, conventions, above, local, builds, setup, guide, named, correctly, bot, posts, after, completes, appropriate, labels, merge, progress, until, merged, live, draft, create, forward, slash, pipeline, run, pass, makes, easier, check, also, ensures, username, off, directly, staff, technical, writer, might, ticket, number, 9000, means, has, been, internal, jira, queue, triage, necessary, finalize, back, outside, working, huge, fans, tools, like, said, rely, ensure, publish, continues, meet, high, standard, set, submit, generated, remember, think, through, people, take, helps, validate, independently, before, submitting, plan, timelines, accordingly, attention, deserves, unfiltered, output, describing, perspective, background, who, found, badly, believe, convincing, lists, bad, gets, repeated, reflect, defaults, improving, clarity, terminology, noticed, was, wrong, missing, good, written, concise, focused, solved, context, decision, itemization, easily, those, respond, timely, fashion, questions, feedback, very, reach, ask, structured, apart, whether, handle, address, maybe, two, touch, addressing, reads, reviews, every, marked, reviewing, smooth, quick, etiquette, button, sends, straight, contributions, encouraged, notice, something, needs, reviewer, automatically, contribute, exception, rendered, update, other, yet, details, reference, welcome, stored, generation, tool, view, date, folders, history, tags, branches, notification, public, discussions, dismiss, alert, switched, accounts, appearance, search, pricing, event, talks, workshops, what, next, partners, company, forum, events, webinars, blog, resource, connect, premium, advanced, ons, trust, why, evaluate, industries, government, manufacturing, financial, services, healthcare, industry, nonprofits, startups, enterprises, stage, businesses, improvements, across, place, developer, articles, sponsors, trending, repos, explore, customize, certifications, scanning, leak, prevention, protection, vulnerability, detection, remediation, secure, cloud, development, environments, codespaces, enforcement, automation, ship, coding, agent, tasks, projects, automated, hosting, collaboration, platform, skip,
Text of the page (random words):
github datadog documentation the source for datadog s documentation site github skip to content navigation menu sign in products platform github repository hosting code review and collaboration copilot ai coding agent for tasks projects and automated work build ship actions ci cd and automation code quality quality analysis fixes and enforcement codespaces cloud development environments secure code security vulnerability detection and remediation secret protection secret scanning and leak prevention all features developers learn documentation training certifications build build with copilot customize copilot integrations explore trending repos github sponsors developer articles changelog changelog your source for the latest features improvements and fixes across github products all in one place businesses by stage enterprises team startups nonprofits by industry healthcare financial services manufacturing government see all industries evaluate github why github customer stories business insights trust center add ons github advanced security enterprise grade code security copilot for business enterprise grade ai features premium support enterprise grade 24 7 support resources learn connect documentation resource center blog events webinars community forum customer stories integrations support customer support training github status company about partners changelog github universe github universe the event for developers by developers talks workshops and what s next for github pricing search sign in sign up appearance settings you signed in with another tab or window reload to refresh your session you signed out in another tab or window reload to refresh your session you switched accounts on another tab or window reload to refresh your session dismiss alert message datadog documentation repository navigation code issues 29 29 pull requests 549 549 discussions actions wiki security and quality insights more items documentation public notifications you must be signed in to change notification settings fork 1 3k 1 3k star 624 624 you must be signed in to star a repository about the source for datadog s documentation site docs datadoghq com topics datadog documentation hacktoberfest hugo wiki resources readme license contributing contributing activity custom properties stars 624 stars watchers 630 watching forks 1 3k forks report repository master branches tags go to file code open more actions menu latest commit history 73 792 commits 73 792 commits folders and files name name last commit message last commit date claude claude github github husky husky vscode vscode astro astro hugo hugo shared shared editorconfig editorconfig eslintignore eslintignore eslintrc eslintrc gitattributes gitattributes gitignore gitignore gitlab ci yml gitlab ci yml prettierignore prettierignore rubocop yml rubocop yml vale ini vale ini agents md agents md claude md claude md contributing md contributing md caddyfile caddyfile license license readme md readme md repo_reorg md repo_reorg md datadog ci preview json datadog ci preview json docker compose docs yml docker compose docs yml general preview synthetics json general preview synthetics json prettier config js prettier config js repository datadog yml repository datadog yml static analysis datadog yml static analysis datadog yml translate yaml translate yaml view all files repository files navigation readme contributing license more items documentation site for datadog welcome to the datadog documentation repository most of the markdown stored in this repo is published to the datadog documentation site using hugo a static website generation tool the api reference is the exception it s rendered by astro from the astro folder to change the api docs update the astro folder not the hugo folder all other content in the astro folder is not published yet see the astro readme for details contribute to the docs contributions are encouraged if you notice something on one of the pages that needs an edit open a pull request pr in this repo for the documentation team to review the documentation team is added as a pr reviewer automatically most pages on the documentation site feature an edit button that sends you to the source file in this repo you can make an edit straight from the github website for more information on contributing see the contribution guidelines pr etiquette a human reads and reviews every docs contribution that is marked ready for review to make the process of reviewing and merging your pr smooth and quick your pr should address one 1 problem maybe two not many it can touch many files in addressing that one problem if the pr is getting very large reach out to the docs team to ask how we want it structured one pr or broken apart or whether we want to handle the fix ourselves respond in a timely fashion to questions and feedback the pr description should be written by you the human not ai the description should be concise and focused on the problem solved with the change and the context for the decision to open the pr not an itemization of the changes made we can easily see those on the changes tab good pr descriptions i noticed this was wrong missing i m updating all links to x page or all of y terminology i m improving the clarity of this description i m updating docs to reflect code changes or new defaults support gets repeated requests for this information bad pr descriptions detailed lists of changes made detailed background of who the customer is how they found the problem how badly they need the fix we believe you and don t need convincing unfiltered claude output describing the pr from claude s perspective note ai and content quality the docs team are huge fans of ai tools like claude code and use them to generate content all the time that said we will always rely on human review to ensure that the content we publish continues to meet the high standard for quality we set for ourselves if you submit a large ai generated pr remember that it takes time for us to think through how people take in and use information it helps us if you can validate your content independently before submitting it and plan your timelines accordingly so we can give your pr the attention it deserves working on docs outside contributors follow these steps if you are not a datadog employee fork the master branch consult our contributing guidelines when you re ready to finalize your changes commit them and make a pull request back to datadog master a datadog technical writer might change your pr title with a docs ticket number such as docs 9000 which means it has been added to the team s internal jira queue to triage and review no action is necessary from you if we change the title of your pr datadog staff follow these steps if you are a datadog employee always branch off of master don t fork and don t commit directly to master you must name your branch name description if you do not include the forward slash the gitlab pipeline won t run you won t get a branch preview and your pull request will not pass in ci getting a branch preview makes it easier for us to check for any issues with your pr such as broken links using a slack username also ensures you get build notifications in slack consult our contributing guidelines when you re ready to commit create a pull request to master from your branch use github s draft pull request feature and appropriate labels such as do not merge or work in progress until your pr is ready to be merged and live on production if you ve named your branch correctly a github bot posts a link to the docs preview website for your pr after the preview build completes you can use the link to preview your changes running the build locally is optional if you followed the branch naming conventions above your pull request should generate a preview for information on local builds see the build setup guide a note about markdown this site uses goldmark for markdown which is compliant with commonmark 0 29 if you include any markdown in a file 99 9 of cases give it a md extension make sure all file names are lowercase macs are case insensitive when creating links to images and pages but our build server is not so tests may work locally but the site will fail in production releasing merging to master triggers an automatic deployment this process typically begins within 10 minutes and usually takes around 35 minutes to complete though these times may vary how to add a new integration see the dedicated doc page about the source for datadog s documentation site docs datadoghq com topics datadog documentation hacktoberfest hugo wiki resources readme license contributing contributing activity custom properties stars 624 stars watchers 630 watching forks 1 3k forks report repository releases packages used by contributors languages footer 2026 github inc footer navigation terms privacy security status community docs contact manage cookies do not share my personal information you can t perform that action at this time
|