Skip to content

Send all configured tags with process checks.#2976

Merged
olivielpeau merged 1 commit intoDataDog:masterfrom
jdavisp3:process-check-tags
Dec 5, 2016
Merged

Send all configured tags with process checks.#2976
olivielpeau merged 1 commit intoDataDog:masterfrom
jdavisp3:process-check-tags

Conversation

@jdavisp3
Copy link
Contributor

@jdavisp3 jdavisp3 commented Oct 29, 2016

Send the tags configured on the instance with the process checks. Given the tests around the old behavior I imagine there might be some reason why this isn't the case now, but just in case there isn't I think it would be useful if the checks had the same tags that were configured for the metrics.

This fixes #2974, FYI.

Copy link
Member

@olivielpeau olivielpeau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jdavisp3 Thanks for your contribution!

To preserve backwards compatibility with existing monitors on this service check, we should still send the service check with the process:<process_name> tag. The metrics are sent with a process_name:<process_name> tag, but if we changed the tag key on the service check to process_name we'd break a lot of monitors.

Could you add the existing process: tag to the tags that you send with service checks? It would create kind of a duplicate "process name" tag on the service checks but it's better than breaking all the existing monitors.

Let me know what you think, thanks!

@olivielpeau olivielpeau self-assigned this Nov 14, 2016
@jdavisp3
Copy link
Contributor Author

Oh, right, I missed that the two tags were actually different. I added the process:name tag back in f272356. Thanks @olivielpeau !

[olivier.vielpeau@datadoghq.com: Fix conflicts and use different
variable name]
@olivielpeau
Copy link
Member

Thanks @jdavisp3! I've made a few cosmetic changes and pushed to your branch.

Merging!

@olivielpeau olivielpeau merged commit 4e1bd40 into DataDog:master Dec 5, 2016
@jdavisp3
Copy link
Contributor Author

jdavisp3 commented Dec 6, 2016

Thanks very much!

@jdavisp3 jdavisp3 deleted the process-check-tags branch December 6, 2016 00:11
degemer added a commit that referenced this pull request Dec 21, 2016
* master: (53 commits)
  [nginx] Update example config
  [service_discovery] Add a Zookeeper service discovery implementation.
  [aggregator] if sample rate is bad, fix it but still parse tags. (#3073)
  [yarn] whitelist authorized application_tags
  Alex poe/update jmx with refresh beans (#3068)
  [config] Fix `_is_affirmative` when passed argument is `None` (#3063)
  Send all configured tags with process checks. (#2976)
  fix flake8 errors
  [flare] ignore whitespace before proxy credentials
  [core] add a switch to disable profiling, but still use developer mode (#2898)
  [tests] allow tests to use the additional_checksd parameter (#3056)
  [service_discovery][jmx] trying to pick-up JMX changes with SD. (#3010)
  [install_script] Make `dd-agent` group of `datadog.conf` (#3036)
  [postgres] Allow disable postgresql.database_size (#3035)
  [core] Fixes IndexError for process lookup (#3043)
  remove warning message leaking password strings (#3053)
  trap psutil.NoSuchProcess exception (#3052)
  Fix grammar and casing in exception text (#3050)
  allow override of kubelet host with KUBERNETES_KUBELET_HOST env var
  [service discovery] properly handle config reload for removed containers
  ...
@masci masci modified the milestones: 5.11.0, 5.12.0 Jan 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Process checks do not pass configured tags

3 participants