Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ECS relevant info for container insight receiver #3864

Closed

Conversation

JohnWu20
Copy link
Contributor

Description:
This commit add the ecs info that are used by container insight receiver for ecs instance level metrics. This includes:

Get task info, clusterName and containerInstanceId from Amazon ECS container agent introspection.

Get reserved_cpu from Cgroup based on task id and clusterName.
Get reserved_mem from Cgroup based on task id, clustername and container info from task info.

Link to tracking Issue:
#2307

Testing:
Unit test

Documentation:

@JohnWu20 JohnWu20 requested a review from anuraaga as a code owner June 23, 2021 05:45
@JohnWu20 JohnWu20 requested a review from a team June 23, 2021 05:45
@JohnWu20 JohnWu20 closed this Jun 23, 2021
alexperez52 referenced this pull request in open-o11y/opentelemetry-collector-contrib Aug 20, 2021
…us advanced features (#3864)

With this change, we reject advanced Prometheus features that the
collector won't support. This way users will be cognizant of what isn't
supported. This way, anyone who adds this configuration to their
Prometheus receiver section

```yaml
receivers:
  prometheus:
    buffer_period: 234
    buffer_count: 45
    use_start_time_metric: true
    start_time_metric_regex: '^(.+_)*process_start_time_seconds$'
    config:
      scrape_configs:
        - job_name: 'demo'
          scrape_interval: 5s
      remote_write:
        - url: "https://example.org/write"

      remote_read:
        - url: "https://example.org/read"

      rule_files: ["a", "b"]

      alerting:
        alert_relabel_configs:
          - separator: ","
            target_label: "fix"

          - separator: "|"
            target_label: "gotham"

        alertmanagers:
          - scheme: "http"
            path_prefix: "/prefix1"
            timeout: 1s
```

will be shown what we don't support these features with this error
message:

```shell
receiver "prometheus" has invalid configuration: unsupported features:
        alert_config.alertmanagers
        alert_config.relabel_configs
        remote_read
        remote_write
        rule_files
```

Fixes #3864
Fixes open-telemetry/prometheus-interoperability-spec#3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants