GithubHelp home page GithubHelp logo

monitoringartist / grafana-aws-cloudwatch-dashboards Goto Github PK

View Code? Open in Web Editor NEW
2.0K 72.0 779.0 18.7 MB

:cloud: 40+ Grafana dashboards for AWS CloudWatch metrics: EC2, Lambda, S3, ELB, EMR, EBS, SNS, SES, SQS, RDS, EFS, ElastiCache, Billing, API Gateway, VPN, Step Functions, Route 53, CodeBuild, ...

Home Page: https://grafana.com/orgs/monitoringartist/dashboards

License: GNU General Public License v3.0

Jsonnet 100.00%
aws aws-cloudwatch grafana dashboard monitoring devops monitoring-artist

grafana-aws-cloudwatch-dashboards's Introduction

Managed by Monitoring Artist: DevOps / Docker / Kubernetes / AWS ECS / Zabbix / Zenoss / Terraform / Monitoring

Grafana dashboards for AWS CloudWatch

Set of AWS Grafana dashboards published on grafana.com - 10M+ downloads.

Doc:

Feel free to create pull request for additional AWS resources/printscreens/...

Please set your dashboard variables (Region, ...) after dashboard import. Empty dashboard variables are reason of initial "Unable to call AWS API" or "Metric request error" error.

Import all Monitoring Artist AWS dashboards in one go (example script, bash/curl/jq required):

#!/bin/bash
jq --version >/dev/null 2>&1 || { echo >&2 "I require jq but it's not installed. Aborting."; exit 1; }
### Please edit grafana_* variables to match your Grafana setup:
grafana_host="http://localhost:3000"
grafana_cred="admin:admin"
# Keep grafana_folder empty for adding the dashboards in "General" folder
grafana_folder="AWS CloudWatch"
ds=(1516 677 139 674 590 659 758 623 617 551 653 969 650 644 607 593 707 575 1519 581 584 2969 8050 11099 11154 11155 12979 13018 13040 13104 13892 14189 14391 14392 14954 14955 15016 16899 17741 17978 20007 20008 20009 20144);
folderId=$(curl -s -k -u "$grafana_cred" $grafana_host/api/folders | jq -r --arg grafana_folder  "$grafana_folder" '.[] | select(.title==$grafana_folder).id')
if [ -z "$folderId" ] ; then echo "Didn't get folderId" ; else echo "Got folderId $folderId" ; fi
for d in "${ds[@]}"; do
  echo -n "Processing $d: "
  j=$(curl -s -k -u "$grafana_cred" $grafana_host/api/gnet/dashboards/$d | jq .json)
  payload="{\"dashboard\":$j,\"overwrite\":true"
  if [ ! -z "$folderId" ] ; then payload="${payload}, \"folderId\": $folderId }";  else payload="${payload} }" ; fi
  curl -s -k -u "$grafana_cred" -XPOST -H "Accept: application/json" \
    -H "Content-Type: application/json" \
    -d "$payload" \
    $grafana_host/api/dashboards/import; echo ""
done

Use AWS Policy Generator, which fits your needs. Example of minimal IAM role for Grafana (CloudWatch + EC2 metrics):

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AllowReadingMetricsFromCloudWatch",
            "Effect": "Allow",
            "Action": [
                "cloudwatch:DescribeAlarmsForMetric",
                "cloudwatch:DescribeAlarmHistory",
                "cloudwatch:DescribeAlarms",
                "cloudwatch:ListMetrics",
                "cloudwatch:GetMetricStatistics",
                "cloudwatch:GetMetricData"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AllowReadingTagsInstancesRegionsFromEC2",
            "Effect": "Allow",
            "Action": [
                "ec2:DescribeTags",
                "ec2:DescribeInstances",
                "ec2:DescribeRegions"
            ],
            "Resource": "*"
        },
        {
            "Sid": "AllowReadingResourcesForTags",
            "Effect" : "Allow",
            "Action" : "tag:GetResources",
            "Resource" : "*"
        }
    ]
}

See https://github.com/monitoringartist/grafana-cross-account-cloudwatch-access for AWS cross account access.

You can also install this project as a Jsonnet library with jsonnet-bundler:

$ jb install github.com/monitoringartist/grafana-aws-cloudwatch-dashboards
$ cat > aws-cloudwatch-dashboards.jsonnet <<EOF
local awsCloudWatch = import 'github.com/monitoringartist/grafana-aws-cloudwatch-dashboards/dashboards.libsonnet';

awsCloudWatch.grafanaDashboards
EOF
$ jsonnet -J vendor aws-cloudwatch-dashboards.jsonnet

Single click provisioning Gitpod ready-to-test - login as admin/admin and create CloudWatch datasource from your Access & secret key to see all dashboards with your data.

AWS API Gateway

AWS Billing

AWS Certificate Manager

AWS CloudFront

AWS Cloudwatch Browser

AWS Cloudwatch Synthetics

AWS Cloudwatch Browser

AWS CodeBuild

AWS Direct Connect

AWS EBS

AWS EC2

AWS ECS

AWS EFS

AWS ElastiCache Redis

AWS ELB Classic Load Balancer

AWS ELB Application Load Balancer

AWS EMR Hadoop 2

AWS Eventbridge

AWS FSx

AWS Inspector

AWS Kinesis

AWS Kinesis Firehose

AWS Lambda

AWS Logs

AWS Network Firewall

AWS Prometheus

AWS RDS

AWS Redshift

AWS S3

AWS SNS

AWS SQS

AWS SNS

AWS Storage Gateway

AWS Transfer Family

AWS Transit Gateway

AWS WAF

AWS X-Ray

Author

Devops Monitoring Expert, who loves monitoring systems and cutting/bleeding edge technologies: Docker, Kubernetes, ECS, AWS, Google GCP, Terraform, Lambda, Zabbix, Grafana, Elasticsearch, Kibana, Prometheus, Sysdig,...

Summary:

Professional devops / monitoring / consulting services:

Monitoring Artist

grafana-aws-cloudwatch-dashboards's People

Contributors

andrew80k avatar ankon avatar anthonywc avatar bokker avatar diego-ojeda-binbash avatar dominikhahn avatar fleaz avatar fradee avatar franciscocpg avatar jangaraj avatar jho2dot0 avatar jong82 avatar jonseymour avatar ksanjay7 avatar lusitaniae avatar maxbrunet avatar mitchellrj avatar neueda-randerson avatar paschdan avatar riupie avatar rohankmr414 avatar shubhamc183 avatar stephengoodall avatar yonahd avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

grafana-aws-cloudwatch-dashboards's Issues

Filter All AWS Resources by Tags

Similar to #14.

When you create some resources in AWS (e.g. EB applications) it's impossible to control the naming. You can however control the tagging.

Given this it's very useful to be able to filter all resources by tags similar to how we do EC2 filtering.

Templating init failed

Hello! I just tried to use the dashboard with our CW datasource, but got the following error:

Templating init failed
Metric request error

Screenshot:

image

The JavaScript console reveals a request failed with error 500 (a bug in Grafana itself?):

angular.js:12759 POST http://52.67.43.249:3000/api/tsdb/query 500 (Internal Server Error)

Details:

  • Running Grafana v5.2.2 (aeaf7b2);
  • The access key I'm using in the CW datasource is from a IAM user that has an associated role with full read-only permission on the account.

Any ideas?

No ECS statistics displayed by default

I have observed that Memory and CPU statistics do not display for selected ECS services.

The apparent reason for this is the fix for issue #9 introduced a change that removed the ServiceName dimension from the query.

I am not exactly sure what problem what the original fix was addressing but I can say this: the default dashboard currently does not work for me and only works after PR #10 is reverted as demonstrated by the screen captures below.

Screen Shot 2019-05-22 at 9 47 18 am
Screen Shot 2019-05-22 at 9 47 32 am

Not showing all regions AWS EC2

Recently I started using Grafana for AWS, using Grafana Docker version.

Noticing that in Cloudwatch Datasource its updated All regions,
But rest EC2,S3,RDS Dashboard its not showing all regions.

in above dashboard its missing regions, us-east-2 & ap-south-1

Please find attachment for your reference.

image

Problems displaying Cloudfront data

Hi!

I was trying to use your dashboard to visualise Cloudfront data but there must be some permissions I am missing as Grafana is not able to get the DistributionId of our website

At the moment, the EC2 instance has an IAM role with this policy

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Action": [
        "cloudwatch:GetMetricStatistics",
        "cloudwatch:ListMetrics"
      ],
      "Effect": "Allow",
      "Resource": "*"    
    }
  ]
}

Is anything else needed for Cloudfront?

README.md - please add quote around the

Hi

The current example script to import the dashboard does not support space char in the password. Please put quote around the $grafana_cred variable to avoid this issue.

`
j=$(curl -s -k -u "$grafana_cred" $grafana_host/api/gnet/dashboards/$d | jq .json)

curl -s -k -u "$grafana_cred" -XPOST -H "Accept: application/json"
`

Thanks.

Tag Filtering

Hi Jan, as discussed I would like to implement tag filtering on the AWS-EC2 dashboard. My end users do not know the InstanceId of their environment but I do tag each instance with a friendly name. I would like to be able to use the Name Tag for selecting the graphs rather than the InstanceId but so far have not been able to make it work. I can see the Tags but not been able to get the correct syntax.

image

image

Any suggestion on whether this is possible?

ELB RequestCount should use Sum statistic rather than Average

Hello, first of all thank you for your work on these dashboards and for sharing them.
I was looking at the Application ELB dashboard and noticed that in the RequestCount / Latency panel you are using the Average statistic for ELB RequestCount.

According to AWS Documentation the most useful statistic should be Sum and I think that Minimum, Maximum, and Average always return 1 or 0.

Edit: Actually the same holds for other metrics in the ELB Dashboard like all http code counts, connection counts and so on

No datapoint on AWS Billing

Hi, Has anyone ever faced this problem with this dashboard?
I thought it did not work, but when you set the 1-year period, it displays information.
But any other information it informs it has no data. (there are several metrics on the AWS console).
Please help me!

one year
24hs

How to add Credit details too in Billing Dashboard?

Hello,

I have few credits that I am currently using in AWS and so My billing dashboard shows 0 amount...is there a way we can track even the Credits? as to what resources is consuming how much of our credits and once all the credits are over, then automatically, we can see our billing

runtime error: invalid memory address or nil pointer dereference

I'm getting this error

runtime error: invalid memory address or nil pointer dereference

with grafana iam access policy

{
"Version": "2012-10-17",
"Statement": [
{
"Action": [
"autoscaling:Describe*",
"cloudwatch:Describe*",
"cloudwatch:Get*",
"cloudwatch:List*",
"logs:Get*",
"logs:List*",
"logs:Describe*",
"logs:TestMetricFilter",
"sns:Get*",
"sns:List*"
],
"Effect": "Allow",
"Resource": "*"
}
]
}

aws ecs service stats receive no data points

I've been having a problem with the cloudwatch browser where I can't seem to get ecs service metrics to return data points. All the other ecs cluster metrics work normally and I've verified the services have metrics in cloudwatch. The request response all seem fine to me:
my request response

I've verfied with AWS that there's nothing on the cloudwatch side and that my permissions are appropriate. They questioningly attempted to help by proposing the use of a GET not a POST request but as the structure works fine for other ECS metrics I'm hesitant. Has anyone seen or faced this recently? It's incredibly annoying to need the console for a very small amount of important metrics >.<.

RDS Dashboard for Alibaba Cloud

Hi

i am using RDS dashboard for AWS RDS monitoring, i am looking for Alibaba Cloud RDS Dashboard
i don't want to use prometheus, happy to see if you able to share

Thanks
Manjur

EKS Dashboard

Currently, no EKS dashboard supported. Is there any plan for this? thx.

Billing details for a particular instance

Hi,

Is there a way I can filter out the total cost including the data transfer, space util, and other resources consumed that are charged me for a particular instance?
for ex: I have p2.Xlarge instance...and with its corresponding instance ID, can all pull the report of how much in total it has costed me?

Thanks in Advance.

not able to get multi value selected in variables (tag filtering)

Hi, For EC2 dasboard, I am trying to get multiple instances CPU graph in one panel. I can do this with instance id. but can't do with any other tags like instance name. in default EC2 dashboard, has variables instance name and instance id with single value selection and based on it we can populate the graph for that specific instance. in my case, I want to have more then one instances graph in one panel and I want to filter out based on instance name not instance id.

I am able to get multi instances graph if i use only instance id variable by enabling multi-value selection. this works only if I remove instance name variables. In this scenario my variables looks like,

$region | regions()
$InstanceId | ec2_instance_attribute($region, InstanceId, {})

now, if I need to figure out how to get instance name and replace it with instance id. I tried multiple options. didn't work.
can anyone help me here? I am thinking it's issue because when we select multiple values for specific variable, grafana is not able to parse it properly. do I need regex for this?

Thanks in advance!

None of these work with the "hosted" or cloud based Grafana

They seem to not properly use the Datasource even though it is tested working with manually created dashboards and dashboards imported from other sources.
Example with the "AWS EC2" Dashboard. Once imported a pop-up error messages says:
Templating init failed Unable to call AWS API

I have attached a screen that of the error that appears on every graph.
screen shot 2017-10-02 at 10 33 28 am

EC2 to Cloudwatch?

Hi Jan, thanks for your posts. Im starting with Grafana and CloudWatch, I have a little confusion.

Im have dashboards created in Grafana with ElasticSearch as datasource, but now I need to move all that dashboards to Cloudwatch because I want to create alarms. I see your codes here, but im not clearly sure what Im doing. How I can do this?

I will appreciate if you can help me with this.

:/

No datapoint on AWS Billing

Hi
What the policy use with AWS Billing ? ,I see No datapoint after install dashboard ,also ec2/rds rds dashboard is working
Thanks.

AWS/EC2 dashboard issue

Issue with getting InstanceId
Grafana logs:

t=2016-11-01T16:14:31+0000 lvl=eror msg="Unable to call AWS API" logger=context userId=1 orgId=1 uname=admin error="InvalidParameter: 1 validation errors:\n- field too short, minimum length 1: Dimensions[0].Value"
t=2016-11-01T16:14:31+0000 lvl=eror msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=POST path=/api/datasources/proxy/1 status=500 remote_addr=195.160.233.233 time_ns=0 size=36
t=2016-11-01T16:13:01+0000 lvl=eror msg="Unable to call AWS API" logger=context userId=1 orgId=1 uname=admin error="MissingParameter: The request must contain the parameter InstanceId\n\tstatus code: 400, request id: "
t=2016-11-01T16:13:01+0000 lvl=eror msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=POST path=/api/datasources/proxy/1 status=500 remote_addr=195.160.233.233 time_ns=241ns size=36

Grafana v3.1.1 (commit: a4d2708)

Show ec2 instance name

On RDS dashboard we can choose by Instance name.
On EC2 I'm only able to pick by instance_id.

Should I replace it with instance name picker or instead make a new box to show the name?

PS: Same applies to EBS dashboard

AWS EFS Dashboard not showing any data

We love your dashboards, thanks for the work, but we got an issue with the EFS dashboard. No matter what we are selecting as region, it never shows and file systems.

Do you know if the dashboard should be functional as it is? It last updated 3 years ago, so maybe something changed in the CloudWatch API?

For Example other dashboards like Billing are working, therefore our CloudWatch connection is functional.

Display ec2 instance tag/tags

Hi,

first - thanks! Really cool dashboards.
Is there any way I could display tags from an instance in ec2 dashboard?
I've tried to use Templating with:
ec2_instance_attribute($region,Tags, {"instance-id": ["$instanceid"]})
but this returns a JSON array, and grafana simply displays this as [Object Object]. I cannot apply regex to it and extract only the Value I want, because internally grafana also treats this a a json array and tries to apply Regex not on a string representation but on the array itself

Thanks!

Metrics query failures on AWS / EC2 dashboard if not using EC2 "Name" tags

Perhaps this should just be in the readme, but it looks like if an AWS account does not make use of "Name" Tags for EC2 (e.g. all of my EC2 instances have a blank Name since we use other custom tags), then queries that rely on the $instancename variable will fail. Once I changed the variables to use our custom tags, the queries worked. I wouldn't expect custom tags to be in the scope of this project, but it might be helpful to mention in the readme that this can be an issue.

This was with Grafana 5.3.4. Not sure if this is a grafana issue with the queries as well?

Other than that, thanks for the dashboard!

ec2 dashboard not working

t=2018-02-02T11:40:58+0000 lvl=eror msg="Request error" logger=context userId=1 orgId=1 uname=admin error="runtime error: invalid memory address or nil pointer dereference" stack="/usr/local/go/src/runtime/panic.go:491 (0x431e62)\n/usr/local/go/src/runtime/panic.go:63 (0x430d6d)\n/usr/local/go/src/runtime/signal_unix.go:367 (0x44924b)\n/go/src/github.com/grafana/grafana/pkg/tsdb/cloudwatch/metric_find_query.go:490 (0xd28174)\n/go/src/github.com/grafana/grafana/pkg/tsdb/cloudwatch/metric_find_query.go:368 (0xd264b4)\n/go/src/github.com/grafana/grafana/pkg/tsdb/cloudwatch/metric_find_query.go:183 (0xd22a57)\n/go/src/github.com/grafana/grafana/pkg/tsdb/cloudwatch/cloudwatch.go:73 (0xd1768d)\n/go/src/github.com/grafana/grafana/pkg/tsdb/request.go:17 (0xbb0099)\n/go/src/github.com/grafana/grafana/pkg/api/metrics.go:46 (0xde3b5e)\n/usr/local/go/src/runtime/asm_amd64.s:511 (0x461191)\n/usr/local/go/src/reflect/value.go:434 (0x4bf934)\n/usr/local/go/src/reflect/value.go:302 (0x4bef13)\n/go/src/github.com/grafana/grafana/vendor/github.com/go-macaron/inject/inject.go:177 (0x7d4ba8)\n/go/src/github.com/grafana/grafana/vendor/github.com/go-macaron/inject/inject.go:137 (0x7d44a9)\n/go/src/github.com/grafana/grafana/pkg/api/common.go:37 (0xdff9cb)\n/usr/local/go/src/runtime/asm_amd64.s:509 (0x46107a)\n/usr/local/go/src/reflect/value.go:434 (0x4bf934)\n/usr/local/go/src/reflect/value.go:302 (0x4bef13)\n/go/src/github.com/grafana/grafana/vendor/github.com/go-macaron/inject/inject.go:177 (0x7d4ba8)\n/go/src/github.com/grafana/grafana/vendor/github.com/go-macaron/inject/inject.go:137 (0x7d44a9)\n/go/src/github.com/grafana/grafana/vendor/gopkg.in/macaron.v1/context.go:121 (0x7f1bdd)\n/go/src/github.com/grafana/grafana/vendor/gopkg.in/macaron.v1/context.go:112 (0x7f1b15)\n/go/src/github.com/grafana/grafana/pkg/middleware/request_tracing.go:25 (0xb98243)\n/usr/local/go/src/runtime/asm_amd64.s:509 (0x46107a)\n/usr/local/go/src/reflect/value.go:434 (0x4bf934)\n/usr/local/go/src/reflect/value.go:302 (0x4bef13)\n/go/src/github.com/grafana/grafana/vendor/github.com/go-macaron/inject/inject.go:177 (0x7d4ba8)\n/go/src/github.com/grafana/grafana/vendor/github.com/go-macaron/inject/inject.go:137 (0x7d44a9)\n/go/src/github.com/grafana/grafana/vendor/gopkg.in/macaron.v1/context.go:121 (0x7f1bdd)\n/go/src/github.com/grafana/grafana/vendor/gopkg.in/macaron.v1/context.go:112 (0x7f1b15)\n/go/src/github.com/grafana/grafana/pkg/middleware/request_metrics.go:17 (0xb97ac4)\n/usr/local/go/src/runtime/asm_amd64.s:509 (0x46107a)\n/usr/local/go/src/reflect/value.go:434 (0x4bf934)\n/usr/local/go/src/reflect/value.go:302 (0x4bef13)\n/go/src/github.com/grafana/grafana/vendor/github.com/go-macaron/inject/inject.go:177 (0x7d4ba8)\n/go/src/github.com/grafana/grafana/vendor/github.com/go-macaron/inject/inject.go:137 (0x7d44a9)\n/go/src/github.com/grafana/grafana/vendor/gopkg.in/macaron.v1/context.go:121 (0x7f1bdd)\n/go/src/github.com/grafana/grafana/vendor/gopkg.in/macaron.v1/context.go:112 (0x7f1b15)\n/go/src/github.com/grafana/grafana/pkg/middleware/session.go:79 (0xb985ca)\n/usr/local/go/src/runtime/asm_amd64.s:509 (0x46107a)\n/usr/local/go/src/reflect/value.go:434 (0x4bf934)\n/usr/local/go/src/reflect/value.go:302 (0x4bef13)\n/go/src/github.com/grafana/grafana/vendor/github.com/go-macaron/inject/inject.go:177 (0x7d4ba8)\n/go/src/github.com/grafana/grafana/vendor/github.com/go-macaron/inject/inject.go:137 (0x7d44a9)\n/go/src/github.com/grafana/grafana/vendor/gopkg.in/macaron.v1/context.go:121 (0x7f1bdd)\n/go/src/github.com/grafana/grafana/vendor/gopkg.in/macaron.v1/context.go:112 (0x7f1b15)\n/go/src/github.com/grafana/grafana/pkg/middleware/recovery.go:146 (0xb979e0)\n/go/src/github.com/grafana/grafana/vendor/gopkg.in/macaron.v1/context.go:79 (0x7f19c0)\n/go/src/github.com/grafana/grafana/vendor/github.com/go-macaron/inject/inject.go:157 (0x7d4863)\n/go/src/github.com/grafana/grafana/vendor/github.com/go-macaron/inject/inject.go:135 (0x7d459a)\n/go/src/github.com/grafana/grafana/vendor/gopkg.in/macaron.v1/context.go:121 (0x7f1bdd)\n/go/src/github.com/grafana/grafana/vendor/gopkg.in/macaron.v1/context.go:112 (0x7f1b15)\n/go/src/github.com/grafana/grafana/pkg/middleware/logger.go:33 (0xb95571)\n/usr/local/go/src/runtime/asm_amd64.s:509 (0x46107a)\n/usr/local/go/src/reflect/value.go:434 (0x4bf934)\n/usr/local/go/src/reflect/value.go:302 (0x4bef13)\n/go/src/github.com/grafana/grafana/vendor/github.com/go-macaron/inject/inject.go:177 (0x7d4ba8)\n/go/src/github.com/grafana/grafana/vendor/github.com/go-macaron/inject/inject.go:137 (0x7d44a9)\n/go/src/github.com/grafana/grafana/vendor/gopkg.in/macaron.v1/context.go:121 (0x7f1bdd)\n/go/src/github.com/grafana/grafana/vendor/gopkg.in/macaron.v1/router.go:187 (0x803412)\n/go/src/github.com/grafana/grafana/vendor/gopkg.in/macaron.v1/router.go:296 (0x7fd98b)\n/go/src/github.com/grafana/grafana/vendor/gopkg.in/macaron.v1/macaron.go:220 (0x7f6387)\n/usr/local/go/src/net/http/server.go:2619 (0x692de3)\n/usr/local/go/src/net/http/server.go:1801 (0x68f09c)\n/usr/local/go/src/runtime/asm_amd64.s:2337 (0x4638c0)\n"

Above error is coming when accessing the ec2 dashboard. In the dashboard the volume based data is not coming. cpu related data is coming.

Can't apply default region

Hello

First of all thanks for all these dashboards. They are working very well.

I have a question. How can force panel to use only eu-west-1.
I have set my region to eu-west-1 in cloudwatch plugin but when i use your dashboard, default region is ap-northest-1

Regard,

EC2 and RDS has same refId in aws-billing.json

in the file aws-billing.json the metrics for EC2 and RDS have the same refId. The Dashboard still works, but they both won't display at the same time.

           {
              "alias": "AmazonEC2",
              "application": {
                "filter": ""
              },
              "dimensions": {
                "Currency": "USD",
                "ServiceName": "AmazonEC2"
              },
              "functions": [],
              "group": {
                "filter": ""
              },
              "host": {
                "filter": ""
              },
              "item": {
                "filter": ""
              },
              "metricName": "EstimatedCharges",
              "mode": 0,
              "namespace": "AWS/Billing",
              "options": {
                "showDisabledItems": false
              },
              "period": "",
              "refId": "B",
              "region": "us-east-1",
              "statistics": [
                "Average"
              ]
            },
            {
              "alias": "AmazonRDS",
              "application": {
                "filter": ""
              },
              "dimensions": {
                "Currency": "USD",
                "ServiceName": "AmazonRDS"
              },
              "functions": [],
              "group": {
                "filter": ""
              },
              "host": {
                "filter": ""
              },
              "item": {
                "filter": ""
              },
              "metricName": "EstimatedCharges",
              "mode": 0,
              "namespace": "AWS/Billing",
              "options": {
                "showDisabledItems": false
              },
              "period": "",
              "refId": "B",
              "region": "us-east-1",
              "statistics": [
                "Average"
              ]
            },

No data from17th Jan

Hello,

I am not receiving any data since Jan 17th 2019. Billing Alerts is turned on under Billing > Preferences > Receive Billing Alerts. I also have these reports sent to my S3 bucket too.

I am able to see the reports under S3 bucket but my Grafana is not getting updated. Am I missing something?

AWS S3, SQS and SNS Metric request error

I am getting Error while accessing S3, SQS and SNS dashboards

S3 Error

t=2018-03-28T11:47:18+0000 lvl=eror msg="Metric request error" logger=context userId=1 orgId=1 uname=admin error="InvalidParameter: 1 validation error(s) found.\n- minimum field size of 1, GetMetricStatisticsInput.Dimensions[0].Value.\n"
t=2018-03-28T11:47:18+0000 lvl=eror msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=POST path=/api/tsdb/query status=500 remote_addr=72.65.252.13 time_ms=1 size=34 referer="https://grafana.abc.com/d/L7Bq38kik/aws-s3?orgId=1"

SQS Error

t=2018-03-28T11:49:42+0000 lvl=eror msg="Metric request error" logger=context userId=1 orgId=1 uname=admin error="InvalidParameter: 1 validation error(s) found.\n- minimum field size of 1, GetMetricStatisticsInput.Dimensions[0].Value.\n"
t=2018-03-28T11:49:42+0000 lvl=eror msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=POST path=/api/tsdb/query status=500 remote_addr=72.65.252.13 time_ms=1 size=34 referer="https://grafana-bird.abc.com/d/42uK3Uziz/aws-sqs?orgId=1"

SNS Error

t=2018-03-28T11:50:53+0000 lvl=eror msg="Metric request error" logger=context userId=1 orgId=1 uname=admin error="InvalidParameter: 1 validation error(s) found.\n- minimum field size of 1, GetMetricStatisticsInput.Dimensions[0].Value.\n"
t=2018-03-28T11:50:53+0000 lvl=eror msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=POST path=/api/tsdb/query status=500 remote_addr=72.65.252.13 time_ms=5 size=34 referer=https://grafana.abc.com/d/iR9W6Uzmz/aws-sns

Grafana version : Grafana v5.0.3

SES visualization defaults are "weird" for low-traffic environments

For the 'Send/Delivery' graph the dashboard suggests to average the values from cloudwatch, and then connect things using lines. This leads to really odd graphs with low amounts of emails being sent, where most data points are either 0 or 1.

I've now switched to 'sum the values, and then render bars', which gives a better overview in my situation.

Auto scaling Issue

I imported the autoscaling dashboard. Selected the us-east-1 region and by side of auto scaling group it has a drop down with "None" I think the autoscaling group is not getting populated

Not able to add two AWS EC2 dashboard for two different cloudwatch data sources

Hello,
We have different cloudwatch data sources
So we wanted to add the AWS EC2 dashboard for each of the data source
When importing the AWS EC2 dashboard, it is adding the new one but removing the earlier added dashboard which is for a different data source and is in a different folder with a different name
The dashboard we are trying to import is https://grafana.com/dashboards/617
This is what we need but it is not letting us keep two copies of AWS EC2 dashboard for different datasources in different folders

Folder CW-1
AWS EC2 CW-1
Folder CW-2
AWS EC2 CW-2

Please can you help

Thanks
Santak

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.