Giter VIP home page Giter VIP logo

amazon-eventbridge-user-guide's Introduction

amazon-eventbridge-user-guide's People

Contributors

ajmay-aws avatar amitjoki avatar bjhogan avatar chrisdr avatar ebi-yade avatar fermanjj avatar joshbean avatar jpeddicord avatar jveldboom avatar kevindenotariis avatar kinclay avatar mvdobrinin avatar randalld-aws avatar ridwaanmanuel avatar smckenzie23 avatar volatus avatar

Stargazers

 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

amazon-eventbridge-user-guide's Issues

Filtering on nested fields doesnt work

as stated in the docs it should be possible to filter on nested fields:

https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-event-patterns.html (value matching)

  1. Sample Event
{
  "version": "0",
  "id": "4cb1378f-3e1a-1c32-f5d9-832b2fd53d8a",
  "detail-type": "SomeEventType",
  "source": "some.source",
  "account": "111",
  "time": "2022-05-16T08:29:16Z",
  "region": "eu-central-1",
  "resources": [],
  "detail": {
    "attributes": {
      "some_attribute": {
        // ...
      }
    }
  }
}
  1. Event-Filter
{
  "detail": {
    "attributes": {
      "some_attribute": [{
        "exists": true
      }]
    }
  }
}

The Test Tool always says:

Sample event did not match the event pattern.

Possible Incorrect Syntax in Event Bridge Transform Docs

Hi, there! I happened to be browsing AWS' documentation about Event Bridge transformations, and I noticed what appears to be an incorrect example. The input template example labeled "Amazon CloudWatch log group" shows output that is invalid JSON. The output has an unclosed string and the resultant object is closed by a right parenthesis ()) instead of a right brace (}). Furthermore, the output contains unescaped double quotes around the instance ID. I just want to bring this possible mistake to your attention or verify whether this is the correct/intended output.

The line in question can be found here:

| **Amazon CloudWatch log group** | <pre>{<br /> "timestamp" : <timestamp>,<br /> "message": "instance \"<instance>\" is in <state>"<br />}</pre> | <pre>{<br /> "timestamp" : 2015-11-11T21:29:54Z,<br /> "message": "instance "i-0123456789" is in RUNNING<br />)</pre> |

The page in AWS's documentation can be found here:

https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-transform-target-input.html#eb-transform-input-examples

eb-monitoring.md: dimensions for rules on custom event bus

I see that #11 was closed recently, but the error still exists in the documentation, just in a different file then what was linked in the original issue (looks like mv was made in 4ddcc77)

Current documentation:
https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-monitoring.html#eb-metrics-dimensions

## Dimensions for EventBridge metrics<a name="eb-metrics-dimensions"></a>
EventBridge metrics have one *dimension*, or sortable attribute, which is listed below\.
| Dimension | Description |
| --- | --- |
| RuleName | Filters the available metrics by rule name\. |




In addition to the MetricName: EventBusName getting published for non default event buses, an undocumented MetricName: Events, and Dimension: EventSourceName are published for partner event source buses.

$ aws cloudwatch list-metrics --namespace "AWS/Events"
{
    "Metrics": [
        ... other metrics ...,
        {
            "Namespace": "AWS/Events",
            "MetricName": "Events",
            "Dimensions": [
                {
                    "Name": "EventSourceName",
                    "Value": "aws.partner/opsgenie.com/<id>"
                }
            ]
        },
        {
            "Namespace": "AWS/Events",
            "MetricName": "Invocations",
            "Dimensions": [
                {
                    "Name": "EventBusName",
                    "Value": "aws.partner/opsgenie.com/<id>"
                },
                {
                    "Name": "RuleName",
                    "Value": "opsgenie-to-some-target"
                }
            ]
        },
        {
            "Namespace": "AWS/Events",
            "MetricName": "Invocations",
            "Dimensions": [
                {
                    "Name": "EventBusName",
                    "Value": "my-custom-bus"
                },
                {
                    "Name": "RuleName",
                    "Value": "custom-to-some-target"
                }
            ]
        },
        {
            "Namespace": "AWS/Events",
            "MetricName": "Invocations",
            "Dimensions": []
        },
       {
            "Namespace": "AWS/Events",
            "MetricName": "Invocations",
            "Dimensions": [
                {
                    "Name": "RuleName",
                    "Value": "default-to-some-target"
                }
            ]
        },
       ... other metrics ...,
    ]
}

Put the TOC in the README

The README is not very useful as it stands.

At least point to the index in doc_source so that people can browse the docs right away

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.