Skip to content

Add support for Datadog Service Checks#100

Open
jeffutter wants to merge 1 commit into
beam-telemetry:mainfrom
jeffutter:service_check
Open

Add support for Datadog Service Checks#100
jeffutter wants to merge 1 commit into
beam-telemetry:mainfrom
jeffutter:service_check

Conversation

@jeffutter

Copy link
Copy Markdown

These are implemented as last_value metrics with report_as: :service_check. It does not support the "host" or "message" property, since TelemetryMetrics doesn't really seem to have a good way to express them.

Fixes #72

These are implemented as `last_value` metrics with `report_as:
:service_check`. It does not support the "host" or "message" property,
since TelemetryMetrics doesn't really seem to have a good way to express
them.

Fixes beam-telemetry#72
@arkgil

arkgil commented Jul 27, 2025

Copy link
Copy Markdown
Collaborator

It does not support the "host" or "message" property

@jeffutter are those just tags that need to be sent with the service check event?

@jeffutter

Copy link
Copy Markdown
Author

It does not support the "host" or "message" property

@jeffutter are those just tags that need to be sent with the service check event?

I don't believe they are just tags. They are additional custom fields in the statsd payload. You can see the reference here: https://docs.datadoghq.com/developers/dogstatsd/datagram_shell/?tab=servicechecks

E.x. _sc|<NAME>|<STATUS>|d:<TIMESTAMP>|h:<HOSTNAME>|#<TAG_KEY_1>:<TAG_VALUE_1>,<TAG_2>|m:<SERVICE_CHECK_MESSAGE> the m field isn't a normal tag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Allow non standard datadog metric types?

2 participants