docs: in_process: updates to config parameters

[eschabell]

• Sort configuration parameters table alphabetically
• Change table parameter names to lowercase to match other input plugin docs

Fixes #2329

Summary by CodeRabbit

• Documentation
  • Process input configuration keys renamed to lowercase_snake_case for consistency.
  • Configuration reference table reorganized for clearer presentation and alignment with new key names.
  • Default values and existing behavior preserved; descriptions adjusted only for naming clarity.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated the process input plugin documentation to rename configuration keys from CamelCase/mixedCase to lowercase_snake_case and reorder the table rows to match code expectations; values and descriptions remain effectively the same.

Changes

Cohort / File(s)	Summary
Documentation update pipeline/inputs/process.md	Renamed configuration keys from CamelCase/mixedCase to lowercase_snake_case (e.g., Proc_Name → proc_name, Interval_Sec → interval_sec, Interval_Nsec → interval_nsec, Alert → alert, Fd → fd, Mem → mem, Threaded → threaded); reordered table rows; preserved defaults and descriptions

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• Fixed typos, sorted config table, moved a config option from metrics table. Fixes #2233 #2234 — Performs the same configuration key renaming and reordering for input plugin documentation.

Suggested reviewers

• cosmo0920
• alexakreizinger

Poem

🐰
I nibbled through headers, tidy and brave,
CamelCase hopped out, snake_case I gave.
Keys all aligned in a neat little row,
Doc-burrow polished, ready to show! 🥕

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating configuration parameter documentation for the in_process input plugin, which aligns with the CamelCase to lowercase_snake_case parameter rename and reorganization.
Linked Issues check	✅ Passed	The pull request fulfills all coding requirements from issue #2329: parameters are sorted alphabetically, parameter names changed to lowercase_snake_case for consistency, and Interval_NSec casing corrected in examples.
Out of Scope Changes check	✅ Passed	All changes are in-scope: the modifications to pipeline/inputs/process.md consist solely of configuration parameter renaming, sorting, and case corrections as specified in issue #2329.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[eschabell]

Requested review from one of the three of you @cosmo0920, @alexakreizinger, or @esmerel, first one wins!

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

pipeline/inputs/process.md (1)

56-63: Fix Interval_NSec casing in the classic config example.

The PR objective calls out correcting this; the example still shows Interval_NSec. If the convention is Interval_Nsec, update it here to match the rest of the docs and expected keys.

🐛 Proposed fix

-  Interval_NSec 0
+  Interval_Nsec 0

🧹 Nitpick comments (1)

pipeline/inputs/process.md (1)

15-16: Consider tightening the wording in the interval_nsec description.

“In conjunction with” is a bit wordy for docs; a shorter phrasing reads better.

♻️ Suggested edit

-| `interval_nsec` | Specifies the interval between service checks, in nanoseconds. This works in conjunction with `interval_sec`. | `0`     |
+| `interval_nsec` | Specifies the interval between service checks, in nanoseconds. Used with `interval_sec`.                      | `0`     |

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

pipeline/inputs/process.md (1)

59-63: Fix Interval_NSec casing in classic conf example.

PR objective mentions correcting this, but the example still shows Interval_NSec. If the convention is Interval_Nsec, update the example to avoid conflicting guidance.

💡 Suggested change

-  Interval_NSec 0
+  Interval_Nsec 0

🧹 Nitpick comments (1)

pipeline/inputs/process.md (1)

15-16: Optional: tighten wording.

“In conjunction with” could be shortened (e.g., “works with”) without losing meaning.

[eschabell]

Thanks for the review @cosmo0920, merging!