Skip to content

Conversation

@karenzone
Copy link
Contributor

No description provided.

@karenzone karenzone self-assigned this Nov 21, 2025
@github-actions
Copy link
Contributor

🤖 GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds documentation for the codec-pretty plugin to the Logstash codec plugins documentation. The change integrates the new codec into the existing plugin listing in alphabetical order between plain and protobuf.

Key changes:

  • Added codec-pretty entry to the plugins table with description and GitHub repository link
  • Added include statement for the pretty codec documentation following the same pattern as other codecs
  • Minor wording improvement to the Support Matrix reference line (changed "please consult" to "check out")

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

| <<plugins-codecs-netflow,netflow>> | Reads Netflow v5 and Netflow v9 data | https://github.com/logstash-plugins/logstash-codec-netflow[logstash-codec-netflow]
| <<plugins-codecs-nmap,nmap>> | Reads Nmap data in XML format | https://github.com/logstash-plugins/logstash-codec-nmap[logstash-codec-nmap]
| <<plugins-codecs-plain,plain>> | Reads plaintext with no delimiting between events | https://github.com/logstash-plugins/logstash-codec-plain[logstash-codec-plain]
| <<plugins-codecs-pretty,pretty>> | Prints your event data using the Ruby Awesome Print library | https://github.com/logstash-plugins/logstash-codec-pretty[logstash-codec-pretty]
Copy link

Copilot AI Dec 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The description "Prints your event data using the Ruby Awesome Print library" is very similar to the rubydebug codec's description "Applies the Ruby Awesome Print library to Logstash events" on line 37. These descriptions suggest both plugins do the same thing, which may confuse users. Consider clarifying how the pretty codec differs from rubydebug, or use a more distinctive description that highlights the unique features or use cases of the pretty codec.

Suggested change
| <<plugins-codecs-pretty,pretty>> | Prints your event data using the Ruby Awesome Print library | https://github.com/logstash-plugins/logstash-codec-pretty[logstash-codec-pretty]
| <<plugins-codecs-pretty,pretty>> | Formats event data in a human-friendly, colorized layout for console output, ideal for development and debugging | https://github.com/logstash-plugins/logstash-codec-pretty[logstash-codec-pretty]

Copilot uses AI. Check for mistakes.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is cool, but I don't know if it is technically correct.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I'd be inclined to leave it as it is. The existing description is the one taken from the plugin docs

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IIUC, your recommendation is using my original text, and not implementing the Copilot suggestion. Did I get that right?

Copy link
Contributor Author

@karenzone karenzone Jan 16, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

New plan after discussions with @robbavey: Add this plugin to skiplist (@karenzone)

The new docs system requires every file to be linked, and this approach should keep codec-pretty out of the generated output.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants