[Postgresql] [Bugfix] create new field query_id field to replace query field as dimension field

[agithomas]

• Bug

Proposed commit message

WHAT: The change helps to prevent the errors of storing data in ES when the query field in pg_stat_activity table exceeds 1024 byte length.
WHY: The length of the values stored in the query field can extend beyond 1024 bytes, which is the limit of dimension field length after a limit override

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

Author's Checklist

• elastic-package build
• elastic-package stack up -v -d --services package-registry
• Validation of relationship between query and query_id field
• Record count validation
• Index Field mapping validation
• Index Settings validation

How to test this PR locally

• elastic-package build
• elastic-package stack up -v -d --services package-registry
• Upgrade the package

Screenshots

Priority

High.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-10-26T04:58:12.134+0000

• Duration: 18 min 3 sec

Test stats 🧪

Test	Results
Failed	0
Passed	41
Skipped	0
Total	41

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (1/1)	💚
Files	100.0% (4/4)	💚
Classes	100.0% (4/4)	💚
Methods	93.333% (28/30)	👍 1.026
Lines	97.059% (165/170)	👍 5.482
Conditionals	100.0% (0/0)	💚

[agithomas]

Index mappings after the change

  "query": {
    "type": "keyword",
    "ignore_above": 1024
  },
  "query_id": {
    "type": "keyword",
    "time_series_dimension": true
  },

[lalit-satapathy]

@agithomas, @aliabbas-elastic,

Can we reproduce and verify that the issue is getting resolved by the PR?

BTW, I am able to get a user query populated into: postgresql.activity.query

[ali786XI]

Can we reproduce and verify that the issue is getting resolved by the PR?

Sure @lalit-satapathy Let me look into it

[ali786XI]

Performed TSDB testing over the changes and everything is working fine

All 234 documents taken from index .ds-metrics-postgresql.activity-default-2023.10.23-000001 were successfully placed to index tsdb-index-enabled.

[lalit-satapathy]

LGTM.

The original below error was not reproduced during the testing. The fix should address the issue.

Dimension fields must be less than [1024] bytes but was [1307]

[elasticmachine]

Package postgresql - 1.17.1 containing this change is available at https://epr.elastic.co/search?package=postgresql