ES|QL PromQL: implicit type coercion for counter/gauge - #149985

@felixbarny please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation.

Pinging @elastic/es-storage-engine (Team:StorageEngine)

@stratoula fyi. this means that promql allows running rate on gauges - I don't think we should be using these in auto-complete, but I wonder if you have validation for promql queries that needs to be updated.

Hi @felixbarny, I've created a changelog YAML for you.

🔍 Preview links for changed docs

⏳ Building and deploying preview... View progress

This comment will be updated with preview links when the build is complete.

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

ℹ️ Important: Docs version tagging

👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version.

We use applies_to tags to mark version-specific features and changes.

🤔 Need help?

• Check out the cumulative docs guidelines
• Reach out in the #docs Slack channel

@stratoula fyi. this means that promql allows running rate on gauges - I don't think we should be using these in auto-complete, but I wonder if you have validation for promql queries that needs to be updated.

No we dont have such a strong validation. We are relying on the definitions you are sending us

const rateDefinition: PromQLFunctionDefinition = {
  type: PromQLFunctionDefinitionTypes.WITHIN_SERIES,
  name: 'rate',
  description: i18n.translate('kbn-esql-language.promql.definitions.rate', {
    defaultMessage:
      'Calculates the per-second average rate of increase of the time series in the range vector.',
  }),
  preview: true,
  signatures: [
    {
      params: [
        {
          name: 'v',
          type: 'range_vector',
          optional: false,
          description: 'Range vector input.',
        },
      ],
      returnType: 'instant_vector',
    },
  ],
  locationsAvailable: [Location.PROMQL],
  examples: ['rate(http_requests_total[5m])'],
};

and it is a bit vague so we are ok

Hi @felixbarny, I've updated the changelog YAML for you.