Ad Widget

Collapse

Zabbix intergration with CloudWatch-No data on Zabbix server LLD

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • dragan979
    Member
    • Apr 2018
    • 49

    #1

    Zabbix intergration with CloudWatch-No data on Zabbix server LLD

    I followed this guide:https://github.com/omni-lchen/zabbix-cloudwatch

    Added dummy host with 127.0.0.1 IP, it's located on Zabbix server itself

    ./awsLLD.py -a "default" -r "eu-west-1" -q "SNSTopics" -c 'topic'
    {
    "data": [
    {
    "{#AWS_REGION}": "eu-west-1",
    "{#AWS_ACCOUNT}": "default",
    "{#TOPIC_INAME}": "",
    "{#TOPIC_NAME}": "topic"
    }
    ]
    }

    AWS-CloudWatch-display name of zabbix-host
    localhost:zabbix server
    default-AWS account

    ./cron.SNS.sh "topic" "AWS-CloudWatch" "localhost" "default" "eu-west-1"
    {'host': 'AWS-CloudWatch', 'value': 2.0, 'key': u'SNS.NumberOfMessagesPublished.Sum["default","eu-west-1","topic"]', 'clock': 1532180160}
    {'host': 'AWS-CloudWatch', 'value': 2.0, 'key': u'SNS.NumberOfNotificationsDelivered.Sum["default","eu-west-1","topic"]', 'clock': 1532180160}
    {'host': 'AWS-CloudWatch', 'value': 0.0, 'key': u'SNS.NumberOfNotificationsFailed.Average["default","eu-west-1","topic"]', 'clock': 1532180160}
    Count: 3

    Monitoring-Latest Data-empty

    Imported example SNS template and attached it to host

    Click image for larger version  Name:	Capture.PNG Views:	1 Size:	92.7 KB ID:	363240

    No items but item properties


    Click image for larger version  Name:	1.PNG Views:	1 Size:	143.0 KB ID:	363241



    Click image for larger version  Name:	2.PNG Views:	1 Size:	151.4 KB ID:	363242





    Click image for larger version  Name:	3.PNG Views:	1 Size:	59.8 KB ID:	363243
    Last edited by dragan979; 21-07-2018, 16:05.
  • dragan979
    Member
    • Apr 2018
    • 49

    #2
    solved:turned out i have to copy awsLLD.py to externalscripts folder

    Comment

    • multazim
      Junior Member
      • May 2018
      • 18

      #3
      I tried the same but my SNS autodiscovery is not working.

      I get "Value should be a JSON object."

      I have manually run the script and verified that output is a json

      I created same discovery rule as normal text item and i get valid json data in it. I don't understand why it is a problem with discovery rule?. Please help.

      { "data": [ { "{#TABLE_NAME}": "prod.corr_data", "{#AWS_REGION}": "us-east-1", "{#AWS_ACCOUNT}": "aws_account_1" }, { "{#TABLE_NAME}": "prod.corr_data2", "{#AWS_REGION}": "us-east-1", "{#AWS_ACCOUNT}": "aws_account_1" }, { "{#TABLE_NAME}": "prod.corr_data3", "{#AWS_REGION}": "us-east-1", "{#AWS_ACCOUNT}": "aws_account_1" }, { "{#TABLE_NAME}": "prod.corr_data4", "{#AWS_REGION}": "us-east-1", "{#AWS_ACCOUNT}": "aws_account_1" }, { "{#TABLE_NAME}": "prod.items", "{#AWS_REGION}": "us-east-1", "{#AWS_ACCOUNT}": "aws_account_1" }, { "{#TABLE_NAME}": "prod.jobStatus", "{#AWS_REGION}": "us-east-1", "{#AWS_ACCOUNT}": "aws_account_1" }, { "{#TABLE_NAME}": "prod.jobStatusLog", "{#AWS_REGION}": "us-east-1", "{#AWS_ACCOUNT}": "aws_account_1" }, { "{#TABLE_NAME}": "prod.tstable1", "{#AWS_REGION}": "us-east-1", "{#AWS_ACCOUNT}": "aws_account_1" }, { "{#TABLE_NAME}": "prod.tstable2", "{#AWS_REGION}": "us-east-1", "{#AWS_ACCOUNT}": "aws_account_1" }, { "{#TABLE_NAME}": "prod.tstable3", "{#AWS_REGION}": "us-east-1", "{#AWS_ACCOUNT}": "aws_account_1" }, { "{#TABLE_NAME}": "prod.tstable4", "{#AWS_REGION}": "us-east-1", "{#AWS_ACCOUNT}": "aws_account_1" } ] }
      Last edited by multazim; 20-03-2019, 15:49.

      Comment

      Working...