aws-samples / aws-samples/eks-workshop-v2

doc: Explain more about the response AMP is returning

Open
#1,405 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
HCL
Stars
626
Forks
613
Avg merge
2d 7h
Merged PRs (30d)
9

Description

### What would you like to be added?

Storing metrics with AMP

Let's verify the successful ingestion of the metrics:

awscurl -X POST --region $AWS_REGION --service aps "${AMP_ENDPOINT}api/v1/query?query=up" | jq '.data.result[1]'

`
{
"metric": {

"__name__": "up",

"account_id": "1234567890",

"beta_kubernetes_io_arch": "amd64",

"beta_kubernetes_io_instance_type": "m5.large",

"beta_kubernetes_io_os": "linux",

"cluster": "eks-workshop",

"eks_amazonaws_com_capacityType": "ON_DEMAND",

"eks_amazonaws_com_nodegroup": "managed-ondemand-2022110404042617720000001b",

"eks_amazonaws_com_nodegroup_image": "ami-01dfb5782bffd09d6",

"eks_amazonaws_com_sourceLaunchTemplateId": "lt-0566ef61fb851d6e1",

"eks_amazonaws_com_sourceLaunchTemplateVersion": "1",

"failure_domain_beta_kubernetes_io_region": "us-west-2",

"failure_domain_beta_kubernetes_io_zone": "us-west-2c",

"instance": "ip-10-42-12-99.us-west-2.compute.internal",

"job": "kubernetes-kubelet",

"k8s_io_cloud_provider_aws": "ffc60533e6d069826fca0578b02694a2",

"kubernetes_io_arch": "amd64",

"kubernetes_io_hostname": "ip-10-42-12-99.us-west-2.compute.internal",

"kubernetes_io_os": "linux",

"node_kubernetes_io_instance_type": "m5.large",

"region": "us-west-2",

"topology_ebs_csi_aws_com_zone": "us-west-2c",

"topology_kubernetes_io_region": "us-west-2",

"topology_kubernetes_io_zone": "us-west-2c",

"workshop_default": "yes"

},

"value": [

1667597359,

"1"

]

}`

### Why is this needed?

What does the above response signify? Could we add more information about this?

Contributor guide

Open the contributing guide

Research direction

Start with the awscurl AMP query and its jq '.data.result[1]' selection shown in the issue, then review the displayed metric and value fields. Done means the documentation explains what the returned labels, timestamp, and sample value signify in the successful ingestion check.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes, prometheus, shell
Domain
documentation, observability-sre
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.