chore(greptimedb_metrics sink): fix greptimedb examples

[sunng87]

Summary

This patch updates examples of greptimedb_metrics

• corrected example value of gzip_compression
• add example of new_naming
• removed redundant example of endpoint

Change Type

• Bug fix
• New feature
• Non-functional (chore, refactoring, docs)
• Performance

Is this a breaking change?

• Yes
• No

How did you test this PR?

N/A

Does this PR include user facing changes?

• Yes. Please add a changelog fragment based on our guidelines.
• No. A maintainer will apply the "no-changelog" label to this PR.

Checklist

• Please read our Vector contributor resources.
• If this PR introduces changes Vector dependencies (modifies Cargo.lock), please
  run dd-rust-license-tool write to regenerate the license inventory and commit the changes (if any). More details here.

References

[jszwedko]

Thanks @sunng87 !

[sunng87]

@jszwedko Thank you for fast response! I have a question. My idea is to change default value of this new_naming to true eventually. But this change will affect existing users, if done wrong, it will break users' data, because this option control how we name timestamp column in GreptimeDB.

My idea is to:

1. Add a breaking change to greptimedb_metrics sink, to make this option a required one and change default value from false to true. So users will get notified when upgrading from older versions and set correct value of this field.
2. After several months and a few minor releases of vector, change this option back to optional so new users won't need to know this option.

Do you think this will work? Do you have similar practice at Vector before?

[jszwedko]

@jszwedko Thank you for fast response! I have a question. My idea is to change default value of this new_naming to true eventually. But this change will affect existing users, if done wrong, it will break users' data, because this option control how we name timestamp column in GreptimeDB.

My idea is to:

1. Add a breaking change to greptimedb_metrics sink, to make this option a required one and change default value from false to true. So users will get notified when upgrading from older versions and set correct value of this field.
2. After several months and a few minor releases of vector, change this option back to optional so new users won't need to know this option.

Do you think this will work? Do you have similar practice at Vector before?

Hey! Yes, something like that would work. It matches the deprecation process we have documented. See the deprecation process documentation for more details on the process.

[pront]

For https://github.com/vectordotdev/vector/actions/runs/12247198112/job/34178224846?pr=21984:

./website/scripts/cue.sh fmt
CI=true make check-docs

[sunng87]

@pront Thank you! It seems example is not allowed for bool fields