[AWS API Gateway] Dashboard for metrics datastream

[lucian-ioan]

What does this PR do?

Adds a dashboard for API Gateway metrics data stream. WIP.

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

• [ ]

How to test this PR locally

Related issues

• Closes [AWS API Gateway] Dashboard for metrics datastream #6315

Screenshots

[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-06-19T13:14:55.358+0000

• Duration: 56 min 13 sec

Test stats 🧪

Test	Results
Failed	0
Passed	193
Skipped	4
Total	197

🤖 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% (15/15)	💚
Files	93.75% (15/16)	👎 -3.36
Classes	93.75% (15/16)	👎 -3.36
Methods	85.714% (240/280)	👎 -6.5
Lines	85.925% (7387/8597)	👎 -6.335
Conditionals	100.0% (0/0)	💚

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 9cc7621

History

• 💚 Build #188 succeeded cc5d299

cc @zmoog @lucian-ioan

[zmoog]

The data types on the dashboard look good: request count, bytes, latency, 4xx, and 5xx errors.

I have a few general questions:

• Labels: should we add a space between the words? For example, "IntegrationErrors" vs. "Integration Error".
• Unit of measure: some visualization may benefit from adding a UOM, like the "ms" on latency values.
• Field name differences: I know that different API Gateway types use distinct field names (4xx vs. 4XXError), but should we make this visible or use the same name on the dashboard for consistency since the semantics is the same?
• The dashboard is very tall: should we consider splitting somehow?

I am looking forward to hearing from Drew o other Kibana Visualization team members!

[stratoula]

@zmoog thanx a lot. I agree that the dashboard looks good and also on:

• labels, yes let's add some space between the words. Panel title has space in general so we can safely do it and will be more readable
• Units, absolutely yes, it helps a lot for readability

Field name differences: I know that different API Gateway types use distinct field names (4xx vs. 4XXError), but should we make this visible or use the same name on the dashboard for consistency since the semantics is the same?

I agree, let's use the same name on dashboard for consistency

Now about the height, in general we encourage small dashboards. I don't know if it makes sense to make 2 or 3 dashboards semantically but if yes I agree. Otherwise we could possibly have more panels per row.

[lucian-ioan]

@zmoog @stratoula This is how the updated dashboard looks:

For now I would just bundle all API types in a single dashboard since they all use API Gateway.
Suggestions are welcome as this is the first dashboard ever for me 😁

WDYT?

[stratoula]

Changes LGTM! We can def improve in the future and split in more dashboards but I think is fine for now!

[zmoog]

LGTM as 1.0 🚢

[lucian-ioan]

/test

[elasticmachine]

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