: to connect to dogstatsd (default \"127.0.0.1:8125\")\n -exclude-metrics value\n\texclude metrics using a regular expression pattern (can be specified multiple times)\n -interval duration\n\tinterval for collecting metrics (default \"none\")\n -lookupd-http-address value\n\t

: of nsqlookupd to query nodes for\n -namespace string\n\tnamespace for metrics (default \"nsq\")\n -nsqd-http-address value\n\t

: of nsqd node to query stats for\n -tag value\n\tadd global tags (can be specified multiple times)\n -version\n\tshow version information\n```\n\nIf both `lookupd-http-address` and `nsqd-http-address` are provided, all nsqd nodes will be used - those provided by `nsqlookupd` in addition to those defined separately by the `nsqd-http-address` flag. Duplicate nsqd nodes will be ignored.\n\nThe following example connects to a local `nsqlookupd` instance running on `127.0.0.1:4161` and uses a polling interval of 5 seconds to query for statistics while applying a global tag of `environment:development`:\n\n```sh\n❯ docker run --rm ruimarinho/nsq-dogstatsd -lookupd-http-address 127.0.0.1:4161 -interval 5s -tag environment:development\n```\n\nConnecting to a local `nsqd` directly is also possible. Consider an instance running on `127.0.0.1:4141`:\n\n```sh\n❯ docker run --rm ruimarinho/nsq-dogstatsd -nsqd-http-address 127.0.0.1:4151\n```\n\nUse the [Metrics > Summary](https://app.datadoghq.com/metric/summary) view of Datadog to check if your metrics are being sent correctly. It may take a few minutes for them to appear for the first time.\n\n## Monitors\n\nOne of most powerful features of Datadog are its monitors. They allow you to monitor certain metrics for specific changes and alert you when those conditions are met. This is extremely useful to monitor nsq clusters and prevent potential issues.\n\nHere's how you can can create a monitor:\n\n1. **Define the metric**\n\n For instance, choose `nsq.channel.depth` and select avg by `channel`, `topic`, `node`.\n\n Check _Trigger a separate alert for each (multi alert)_.\n\n2. **Set alert conditions**\n\n Select _Threshold Alert_:\n\n- Trigger when the metric is: **above** the threshold **on average** during the last **5 minutes** for any **channel**, **topic**, **node**.\n- Alert threshold: **100**\n\n3. **Say what's happening**\n\n- Subject: `nsq depth on channel {{channel.name}} ({{topic.name}}) is increasing on {{node.name}}`\n\n4. **Notify your team**\n\n Choose whoever should be notified about potential monitor changes.\n\n## License\n\nMIT\n","has_starred","hub_user","immutable_tags_settings",{"_144":11,"_145":146},"enabled","rules",[147],".*","is_automated","permissions",{"_151":22,"_152":11,"_153":11},"read","write","admin","user","storage_size",66149659,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","tagAttestations","displaySecurityMetadata","showSbxLogoOverride","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_27":28,"_106":-7,"_104":-7,"_105":-7,"_29":168,"_35":46,"_172":173,"_178":11},{"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":169,"_67":68,"_69":34,"_70":71,"_72":73,"_74":75,"_76":77,"_78":50,"_79":68,"_80":59,"_81":22},[170,171],{"_44":45,"_35":46,"_47":48,"_49":50,"_51":52,"_53":54,"_55":48,"_56":-5,"_57":38,"_58":59,"_60":-5},{"_44":62,"_35":63,"_47":48,"_49":64,"_51":65,"_53":54,"_55":48,"_56":-5,"_57":66,"_58":59,"_60":-5},"imageWithLayers",{"_44":45,"_35":46,"_47":48,"_49":50,"_51":52,"_85":174,"_53":54,"_55":48,"_56":-5,"_57":38,"_58":59,"_60":-5},[175,176,177],{"_57":88,"_89":90,"_35":48},{"_35":92,"_57":38,"_89":93},{"_57":88,"_89":95,"_35":48},"hasPermissionToViewRepoSettings","actionData","errors"]

ruimarinho/nsq-dogstatsd:1.2.0