feat(gcp_stackdriver_logs sink): Support user-defined insertId

[garethpelly]

Summary

This adds support for setting a custom insertId at the root level of the LogEntry, allowing users to define their own unique identifier for each log entry.

In a similar way to how the severity_key field works with the sink now, we extract a custom insertId from log events via an insert_id_key configuration option. The named field is removed from the log event if present.

Vector configuration

sources:
  dummy_logs:
    type: "demo_logs"
    format: "syslog"
    interval: 1

transforms:
  parse_logs:
    type: "remap"
    inputs: ["dummy_logs"]
    source: |
      . = parse_syslog!(string!(.message))
      .my_insert_id = uuid_v4()

sinks:
  my_sink_id:
    type: gcp_stackdriver_logs
    project_id: "my-project"
    log_id: "test_log"
    inputs:
      - parse_logs
    insert_id_key: "my_insert_id"
    resource:
      type: "gce_instance"
      project_id: "my-project"
      instanceId: "Twilight"
      zone: "us-central1-a"

How did you test this PR?

• Ran unit tests
• Tested using my Google account and inspected logs in Google Cloud Logging

Change Type

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

Is this a breaking change?

• Yes
• No

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.

References

• Closes: Support user-defined insertId in gcp_stackdriver_logs sink #24967

Notes

• Please read our Vector contributor resources.
• Do not hesitate to use @vectordotdev/vector to reach out to us regarding this PR.
• Some CI checks run only after we manually approve them.
  • We recommend adding a pre-push hook, please see this template.
  • Alternatively, we recommend running the following locally before pushing to the remote branch:
    • make fmt
    • make check-clippy (if there are failures it's possible some of them can be fixed with make clippy-fix)
    • make test
• After a review is requested, please avoid force pushes to help us review incrementally.
  • Feel free to push as many commits as you want. They will be squashed into one before merging.
  • For example, you can run git merge origin master and git push.
• If this PR introduces changes Vector dependencies (modifies Cargo.lock), please
  run make build-licenses to regenerate the license inventory and commit the changes (if any). More details here.

[OliviaShoup]

thanks for the PR! 🚀

[garethpelly]

@vectordotdev/vector please review 🙏

[garethpelly]

@vectordotdev/vector gentlest of nudges, let me know if there is anything else you need me to do

[pront]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Bravo.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[garethpelly]

@pront Thanks! Is this fit for merging now?

[garethpelly]

@vectordotdev/vector Can we merge?