add log min limit option to value axis options

[nickofthyme]

Summary

fixes #83917

Add option to Y-Axes config in visualize xy charts to set a log min limit to contain log data using an explicit limit and not the kibana implicit limit of 1.

This option is only available when an axes config is linked to one or more non-stacked line series. This is to discourage bad practices for area charts and stacked lines.

Note: When Set log min limit is disabled, the implied value of 1 will be used.

Screen.Recording.2021-04-06.at.06.12.40.PM.mp4

Checklist

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[nickofthyme]

Waiting on elastic/elastic-charts#1057

[kibanamachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request
• Commit: 1865bb2
• Storybooks Preview
• Pipeline Steps (look for red circles / failed steps)
• Interpreting CI Failures

Failed CI Steps

• Setup Build Environment and Dependencies
• Jest Unit Tests
• Check Types
• Setup Build Environment and Dependencies

---

Test Failures

Kibana Pipeline / jest / Jest Tests.src/plugins/vis_type_xy/public/editor/components/options/metrics_axes.ValueAxesPanel component should init with the default set of props

Link to Jenkins

Standard Out

Failed Tests Reporter:
  - Test has not failed recently on tracked branches

Stack Trace

Error: expect(received).toMatchSnapshot()

Snapshot name: `ValueAxesPanel component should init with the default set of props 1`

- Snapshot  - 0
+ Received  + 2

@@ -118,10 +118,11 @@
        }
        index={0}
        onValueAxisPositionChanged={[MockFunction]}
        setMultipleValidity={[MockFunction]}
        setParamByIndex={[MockFunction]}
+       showLogOptions={false}
        valueAxis={
          Object {
            "id": "ValueAxis-1",
            "labels": Object {
              "color": "black",
@@ -226,10 +227,11 @@
        }
        index={1}
        onValueAxisPositionChanged={[MockFunction]}
        setMultipleValidity={[MockFunction]}
        setParamByIndex={[MockFunction]}
+       showLogOptions={false}
        valueAxis={
          Object {
            "id": "ValueAxis-2",
            "labels": Object {
              "color": "black",
    at Object.<anonymous> (/var/lib/jenkins/workspace/elastic+kibana+pipeline-pull-request/kibana/src/plugins/vis_type_xy/public/editor/components/options/metrics_axes/value_axes_panel.test.tsx:67:18)
    at Promise.then.completed (/var/lib/jenkins/workspace/elastic+kibana+pipeline-pull-request/kibana/node_modules/jest-circus/build/utils.js:276:28)
    at new Promise (<anonymous>)
    at callAsyncCircusFn (/var/lib/jenkins/workspace/elastic+kibana+pipeline-pull-request/kibana/node_modules/jest-circus/build/utils.js:216:10)
    at _callCircusTest (/var/lib/jenkins/workspace/elastic+kibana+pipeline-pull-request/kibana/node_modules/jest-circus/build/run.js:212:40)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at _runTest (/var/lib/jenkins/workspace/elastic+kibana+pipeline-pull-request/kibana/node_modules/jest-circus/build/run.js:149:3)
    at _runTestsForDescribeBlock (/var/lib/jenkins/workspace/elastic+kibana+pipeline-pull-request/kibana/node_modules/jest-circus/build/run.js:63:9)
    at _runTestsForDescribeBlock (/var/lib/jenkins/workspace/elastic+kibana+pipeline-pull-request/kibana/node_modules/jest-circus/build/run.js:57:9)
    at run (/var/lib/jenkins/workspace/elastic+kibana+pipeline-pull-request/kibana/node_modules/jest-circus/build/run.js:25:3)
    at runAndTransformResultsToJestFormat (/var/lib/jenkins/workspace/elastic+kibana+pipeline-pull-request/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapterInit.js:176:21)
    at jestAdapter (/var/lib/jenkins/workspace/elastic+kibana+pipeline-pull-request/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:109:19)
    at runTestInternal (/var/lib/jenkins/workspace/elastic+kibana+pipeline-pull-request/kibana/node_modules/jest-runner/build/runTest.js:380:16)
    at runTest (/var/lib/jenkins/workspace/elastic+kibana+pipeline-pull-request/kibana/node_modules/jest-runner/build/runTest.js:472:34)
    at Object.worker (/var/lib/jenkins/workspace/elastic+kibana+pipeline-pull-request/kibana/node_modules/jest-runner/build/testWorker.js:133:12)

---

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
visTypeXy	110.9KB	113.2KB	+2.3KB

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[markov00]

I've tested it locally and I've to admit that this is a bit too complicated to understand for me.
In particular, I can't understand exactly what is the difference between setting the domain extent to 0.01 or the log min limit to 0.01 what is the actual difference?

[nickofthyme]

I've tested it locally and I've to admit that this is a bit too complicated to understand for me.
In particular, I can't understand exactly what is the difference between setting the domain extent to 0.01 or the log min limit to 0.01 what is the actual difference?

The difference is that the log limit is more of a soft limit and the extent is a hard limit. The log limit excludes values that are smaller than the given value. I agree it is not the most obvious but I don't know how else to explain it.

[nickofthyme]

Apologies for the delay on this @th0ger. We couldn't find a good way to implement this with adding a new parameter to the vis editor. I opened a new issue in charts repo to set this min log limit automatically instead of hardcoding it to 1 see elastic/elastic-charts#1257.