!<1-      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~                                                                                                                                 None!"#$%&',-.127=>?@AHMPSUVWX_\5datadogA Datadog monitor. These monitors actively check multiple different types of data within Datadog against user-provided conditions, triggering notifications when condition(s) are met.datadog7Datadog's internal reference to this specific monitor.datadog=The specification from which this monitor can be re-created.datadog3Datadog's internal reference to a specific monitor.datadogVA representation of a monitor's configuration, from which a monitor could be rebuilt.datadog:The query string the monitor uses to determine its state. datadog'The human-readable name of the monitor. datadogFThe message sent with the notification when the monitor is triggered. datadogIOptional configuration parameters specifying advanced monitor beahviour. datadog0Advanced configuration parameters for a monitor.datadog^Each monitor is of a specific type, which determines what sort of check the monitor performs.datadogOWatches a (combination of) metric(s), alerting when it crosses some threshold.datadogFWatches a service and alerts when the service enters a failing state.datadog=Checks the event stream for events meeting certain criteria.+datadogjAn event stored within Datadog. An event represents some sort of occurrence that was recorded in Datadog.-datadog'Datadog's unique reference to the event.datadog*Context on what happened during this event/datadog1Datadog's internal reference to a specific event.0datadogDetails that describe an event.3datadog!The description/body of the event4datadog$The time at which the event occurred6datadog&The hostname associated with the event9datadog*The trigger of the event (if identifiable):datadogBA source from which an event may originate, recognized by Datadog.Gdatadog The failure levels for an alert.Ldatadog>A set of priorities used to denote the importance of an event.Odatadog'A scheduled donwtime stored in Datadog.Qdatadog4Datadog's unique reference to the scheduled downtimeRdatadog Context on the downtime scheduleSdatadog=Datadog's internal reference to a specific donwtime instance.Tdatadog,A description of when downtime should occur.Vdatadog+When to start the downtime (or immediately)Wdatadog+When to stop the downtime (or indefinitely)Xdatadog9A message to include with notifications for this downtimeYdatadog}The scope to apply downtime to (if applying downtime to a host, use a tag of the form "host:hostname", NOT just "hostname")Zdatadog.The result of running a check on some service.\datadogText describing the check]datadog+Name of the host which the check applies to^datadogStatus result of the check_datadoglTime at which the check occurred (Nothing will wait until the check is sent to Datadog to compute the time)`datadogNInformation related to why this specific check run supplied the status it didadatadog%Tags to associate with this check runbdatadogAThe status of a service, based on a check that is run against it.cdatadogEverything is as it should be.ddatadog/Something abnormal, but not critical, is amiss.edatadog(Something dangerously critical is amiss.fdatadog(The current status cannot be determined.gdatadogEntity descriptor.Entities in Datadog (hosts, metrics, events, etc) are frequently associated with one more more "tags". These tags are labels that identify an entity as belonging to a particular group or having particular properties. A tag can come in two forms: a simple text label, describing entities associated with the tag, or a key-value pair, associating entities with a specific slice of a larger categorization.MAs strings, the key and value parts of a key-value pair are separated by a (:v). As such, any tag with no colons is a label, and any tag with one (or more) is a key-value pair - if more than one : is specified, the additional : s will become part of the value.jdatadogCAn Environment contains everything needed to interact with Datadog.ldatadog.Auth keys to permit communication with Datadogmdatadog The root URL for the Datadog APIndatadog-HTTP manager used to make requests to Datadogodatadog9Wraps the keys needed by Datadog to fully access the API.  ! "#$%&'()*+,.-/0198765432:FEDCBA@?>=<;GIJKHLNMOPRQSTUYXWVZ[a`_^]\bfedcgihjknmloprqstvuwxzy{|}~~{|}wxzystvuoprqjknmlgihbfedcZ[a`_^]\TUYXWVSOPRQLNMGIJKH:FEDCBA@?>=<;0198765432/+,.-()*%&'"#$!   None""#$%&',-.127=>?@ACHMPSUVWX_ali    %$#"! '*)(,0/.-i    %$#"! '*)(,0/.-None!"#$%&',-.127=>?@AHMPSUVWX_rN9datadogCreates the most basic specification required by a monitor, containing the type of monitor and the query string used to detect the monitor's state.zGenerates a set of "default" Monitor options, which specify as little optional configuration as possible. This includes:'No silencing of any part of the monitor;No notification when data related to the monitor is missing0No alert timeout after the monitor is triggeredn/No renotification when the monitor is triggered,No notification when the monitor is modified In production situations, it is not safe to rely on this documented default behaviour for critical setitngs; use the helper functions to introspect the MonitorOptions instance provided by this function. This also protects against future modifications to this API.  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHKJILMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~     !"#$%'()*,-./02345678945678923None!"#$%&',-.127=>?@AHMPSUVWX_^datadogProvide a list of the silenced scopes for this monitor and the time at which the silencer will expire (may be indefinite). The monitor  "*" - refers to the monitor at large (un-scoped)._datadogSilence a given scope until some time (or indefinitely), replacing the current silencer on the given scope if one already exists.`datadogLRemove the silencer from a given scope, if the scope is currently silenced.adatadogAUnsilence every scope in the monitor, including the global scope.bdatadogDetermine how long without data a monitor will go before notifying to such, providing Nothing if the monitor will never notify on lack of data.cdatadogzHave the monitor notify when it does not receive data for some given amount of time (rounded down to the nearest minute).ddatadog;Prevent the monitor from notifying when it is missing data.edatadogDetermine after how long the monitor will stop alerting after it is triggered, providing Nothing if the monitor will never stop alerting.fdatadogaHave the monitor stop alerting some time after it is triggered (rounded up to the nearest hour).gdatadog:Prevent the monitor from timing out after it is triggered.hdatadogDetermine after how long after being triggered the monitor will re-notify, and what message it will include in the re-notification (if any), providing Nothing if the monitor will never re-notify.idatadogHave the monitor re-notify some amount of time after the most recent notification (rounded down to the nearest minute) and optionally what text it will include in the re-notification.jdatadogUPrevent the monitor from re-notifying after it triggers an un-resolved notification.kdatadogEDetermine if the monitor triggers a notification when it is modified.ldatadog<Have the monitor trigger a notification when it is modified.mdatadogGPrevent the monitor from triggering a notification when it is modified.ndatadogCreates the most basic specification required by a monitor, containing the type of monitor and the query string used to detect the monitor's state. This uses 9; to set the options (see that function for disclaimer(s)).odatadog9Create a new monitor in Datadog matching a specification.pdatadog&Load a monitor from Datadog by its ID.qdatadogSync a monitor with Datadog.This must be called on any active monitors to apply the changes with Datadog itself; merely modifying a monitor locally is not enough to store the changes.Beware: If a monitor has changed on the Datadog remote endpoint between the time it was copied locally and when this function is called, those changes already made remotely will be overwritten by this change.rdatadogDelete a monitor from Datadog.Note that once a monitor is deleted, it cannot be used locally anymore, however you can always create a new monitor using the deleted monitor's specification.sdatadogLoad monitors from Datadog.3This function takes a filter list argument, which should contain any tags the user wishes to filter on. If the filter list is left empty, no filters will be applied. The list of tags is ANDed together; if you specify more than one filter tag, only metrics which match all filter tags will be provided.tdatadog1Prevent all monitors from notifying indefinitely.udatadogAllow all monitors to notify.sdatadog#Tags on which to filter the resultsN ,-./0^_`abcdefghijklmnopqrstuN  ^_`abcdefghijklmnoqrpstu,-./0None!"#$%&',-.127=>?@AHMPSUVWX_E !"#$'()*vw"#$ !wv'()*None!"#$%&',-.127=>?@AHMPSUVWX_ xdatadog1Do not allow alerts to trigger on a specific hostydatadog*Allow alerts to trigger on a specific hostxyxyNone!"#$%&',-.127=>?@AHMPSUVWX_$zdatadogCreates the most basic description required for an event, containing the event title, descriptive text, time of occurrence, and priority of the event. This event will be of type Info.{datadogStore a new event in Datadog.|datadog%Load an event from Datadog by its ID.}datadog6Query Datadog for events within a specific time range.}datadog*The range within which to query for eventsdatadog6Optionally filter results by a specific priority leveldatadogA list of tags to filter byS+-./0123456789:;<=>?@ABCDEFGHKJILMN   !"#$%z{|}SLMNGHKJI:;<=>?@ABCDEF0123456789+-./z{|}   !"#$%None!"#$%&',-.127=>?@AHMPSUVWX_~datadoguCreates the most basic possible downtime specification, which just contains the scope to which the downtime applies.datadog#Schedule a new downtime in Datadog.datadog2Update the specification of a downtime in Datadog.datadog%Cancel scheduled downtime in Datadog.datadog1Load a scheduled downtime from Datadog by its ID.datadogaLoad all scheduled downtimes, optionally filtering for only downtimes that are currently active.OSTUVWXY~TUVWXYO~S None!"#$%&',-.127=>?@AHMPSUVWX_ɶdatadog(Record the result of a check in Datadog. Z[\]^_`abcdef   bcdefZ[\]^_`a  None!"#$%&',-.127=>?@AHMPSUVWX_5datadog-Load Datadog keys from environment variables.6The keys will be read from the enviornment variables DATADOG_API_KEY and DATADOG_APP_KEY;. If the keys cannot be read, this function will throw an  IOException.datadogjCreate a new environment using authentication keys, defaulting to the Datadog documented default API URL.  !"#$+-./0123456789:;<=>?@ABCDEFGHKJILMNOSTUVWXYZ[\]^_`abcdefjopqr     !"#$%'()*,-./0^_`abcdefghijklmnopqrstuvwxyz{|}~ opqrj None#"#$%&',-.127=>?@ACHMPSUVWX_ datadog7The fields accessible through corresponding lenses are: ::  ::  ::  ::  a => a :: []datadog}Converts a supported numeric type to the format understood by DogStatsD. Currently limited by BufferBuilder encoding options.datadogGauges measure the value of a particular thing at a particular time, like the amount of fuel in a car s gas tank or the number of users connected to a system.datadogpCounters track how many times something happened per second, like the number of database requests or page views.datadogStatsD only supports histograms for timing, not generic values (like the size of uploaded files or the number of rows returned from a query). Timers are essentially a special case of histograms, so they are treated in the same manner by DogStatsD for backwards compatibility.datadogHistograms track the statistical distribution of a set of values, like the duration of a number of database queries or the size of files uploaded by users. Each histogram will track the average, the minimum, the maximum, the median and the 95th percentile.datadogSets are used to count the number of unique elements in a group. If you want to track the number of unique visitor to your site, sets are a great way to do that.datadogaTags are a Datadog specific extension to StatsD. They allow you to tag a metric with a dimension that s meaningful to you and slice and dice along that dimension in your graphs. For example, if you wanted to measure the performance of two video rendering algorithms, you could tag the rendering time metric with the version of the algorithm you used.datadogTCreate a tag from a key-value pair. Useful for slicing and dicing events in Datadog.aKey and value text values are normalized by converting ":"s, "|"s, and "@"s to underscores ("_").datadogSmart @ constructor. Use the lens functions to set the optional fields.datadog7The fields accessible through corresponding lenses are:  ::  ::  ::   ::   ::   ::   ::   ::   :: []datadog(Special setter to update the value of a . Cmetric ("foo"" :: Text) Counter (1 :: Int) & value .~ (5 :: Double)datadogSmart @ constructor. Use the lens functions to set the optional fields.datadog7The fields accessible through corresponding lenses are: ::  ::  ::   ::   ::   :: []datadog?The hostname or IP of the DogStatsD server (default: 127.0.0.1)datadogBThe port that the DogStatsD server is listening on (default: 8125)datadogMaximum buffer size. Stats are sent over UDP, so the maximum possible value is 65507 bytes per packet. In some scenarios, however, you may wish to send smaller packets. (default: 65507)datadogMaximum amount of time (in microseconds) between having no stats to send locally and when new stats will be sent to the statsd server. (default: 1 second)datadog>Handler to recover from exceptions thrown while sending stats to the server. Caution: Throwing an exception from this handler will shut down the worker that sends stats to the server, but is not able to prevent you from enqueuing stats via the client. Default: print the exception and throw away any accumulated stats.datadog Convert an , , or  StatusCheck to their wire format.datadogRNote that Dummy is not the only constructor, just the only publicly available one.datadogJust drops all stats.datadog0Create a stats client. Be sure to close it with k in order to send any pending stats and close the underlying handle when done using it. Alternatively, use  to finalize it automatically.datadog Create a . and provide it to the provided function. The ^ will be finalized as soon as the inner block is exited, whether normally or via an exception.datadogSend a , , or  StatusCheck to the DogStatsD server.dSince UDP is used to send the events, there is no ack that sent values are successfully dealt with. withDogStatsD defaultSettings $ \client -> do send client $ event "Wombat attack" "A host of mighty wombats has breached the gates" send client $ metric "wombat.force_count" Gauge (9001 :: Int) send client $ serviceCheck "Wombat Radar" ServiceOkdatadogWSend all pending unsent events and close the connection to the specified statsd server.datadogname datadogMax buffer sizedatadog Items to sendWW None""#$%&',-.127=>?@AHMPSUVWX_       !"##$%&'()*++,--.//011234556789:;<=>?@ABCDEFGHIJKLMNOPQRSSTUVWWXYZ[\\]^_`abcdefghijkklmnoopqrrstuuvwxxyzz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~       #    ) *    h       }   1 K L M N O              !                                                                                &datadog-0.2.5.0-9XzZN9U50gnJuuzff1AVBbNetwork.Datadog.TypesNetwork.Datadog.LensNetwork.Datadog.InternalNetwork.Datadog.MonitorNetwork.Datadog.MetricsNetwork.Datadog.HostNetwork.Datadog.EventNetwork.Datadog.DowntimeNetwork.Datadog.CheckNetwork.DatadogNetwork.StatsD.Datadog Paths_datadogMonitor monitorId' monitorSpec MonitorId MonitorSpecmonitorSpecType'monitorSpecQuerymonitorSpecNamemonitorSpecMessagemonitorSpecOptionsMonitorOptionsmonitorOptionsSilencedmonitorOptionsNotifyNoDatamonitorOptionsNoDataTimeframemonitorOptionsTimeoutHmonitorOptionsRenotifyIntervalmonitorOptionsEscalationMessagemonitorOptionsNotifyAudit MonitorType MetricAlert ServiceCheck EventAlertMetric metricName metricPoints metricHost metricTags MetricPointsGaugeCounterSeries fromSeries WrappedEvents wrappedEvents WrappedEvent wrappedEventEventeventId' eventDetailsEventId EventSpeceventSpecTitle eventSpecTexteventSpecDateHappenedeventSpecPriority eventSpecHost eventSpecTagseventSpecAlertTypeeventSpecSourceType SourceTypeNagiosHudsonJenkinsUserMyAppsFeedChefPuppetGit BitBucketFabric Capistrano AlertTypeErrorWarningInfoSuccess EventPriorityNormalPriority LowPriorityDowntime downtimeId' downtimeSpec DowntimeId DowntimeSpecdowntimeSpecStartdowntimeSpecEnddowntimeSpecMessagedowntimeSpecScope CheckResultcheckResultCheckcheckResultHostNamecheckResultStatuscheckResultTimestampcheckResultMessagecheckResultTags CheckStatusCheckOk CheckWarning CheckCritical CheckUnknownTag KeyValueTagLabelTag EnvironmentenvironmentKeysenvironmentApiUrlenvironmentManagerKeysapiKeyappKey DatadogClientdatadogClientManagerdatadogClientKeys ReadWritereadWriteApiKeyreadWriteApplicationKeyWrite writeApiKey Timestamp fromTimestamp $fReadTag $fShowTag$fShowEventPriority$fShowAlertType$fShowSourceType$fShowMonitorType$fEqKeys$fEqTag$fEqCheckStatus$fEqCheckResult$fEqDowntimeSpec $fEqDowntime$fEqEventPriority $fEqAlertType$fEqSourceType $fEqEventSpec$fShowEventSpec $fEqEvent $fShowEvent$fSemigroupSeries$fMonoidSeries$fEqMonitorType$fEqMonitorOptions$fEqMonitorSpec $fEqMonitor HasTimestamp timestampHasTagstags HasStatusstatus HasMessagemessage HasHostNamehostNameHasCheckcheck$fHasCheckCheckResultText$fHasHostNameCheckResultText$fHasMessageCheckResultMaybe!$fHasStatusCheckResultCheckStatus$fHasTagsCheckResult[]$fHasTimestampCheckResultMaybeHasStartstartHasScopescopeHasEndend$fHasMessageDowntimeSpecMaybe$fHasEndDowntimeSpecMaybe$fHasScopeDowntimeSpecTag$fHasStartDowntimeSpecMaybeHasSpecspecHasId'id'$fHasId'DowntimeInt$fHasSpecDowntimeDowntimeSpecHasTitletitleHasTexttext HasSourceType sourceType HasPrioritypriorityHasHosthostHasDateHappened dateHappened HasAlertType alertType$fHasTagsEventSpec[] $fHasAlertTypeEventSpecAlertType!$fHasDateHappenedEventSpecUTCTime$fHasHostEventSpecMaybe#$fHasPriorityEventSpecEventPriority$fHasSourceTypeEventSpecMaybe$fHasTextEventSpecText$fHasTitleEventSpecText HasDetailsdetails$fHasId'EventInt$fHasDetailsEventEventSpec HasPointspointsHasNamename$fHasTagsMetric[]$fHasHostMetricMaybe$fHasNameMetricText$fHasPointsMetricMetricPoints HasTimeoutHtimeoutH HasSilencedsilencedHasRenotifyIntervalrenotifyIntervalHasNotifyNoData notifyNoDataHasNotifyAudit notifyAuditHasNoDataTimeframenoDataTimeframeHasEscalationMessageescalationMessage($fHasEscalationMessageMonitorOptionsText'$fHasNoDataTimeframeMonitorOptionsMaybe"$fHasNotifyAuditMonitorOptionsBool#$fHasNotifyNoDataMonitorOptionsBool($fHasRenotifyIntervalMonitorOptionsMaybe"$fHasSilencedMonitorOptionsHashMap $fHasTimeoutHMonitorOptionsMaybeHasType'type'HasQueryquery HasOptionsoptions$fHasNameMonitorSpecMaybe$fHasMessageMonitorSpecMaybe%$fHasOptionsMonitorSpecMonitorOptions$fHasQueryMonitorSpecText $fHasType'MonitorSpecMonitorType$fHasSpecMonitorMonitorSpec$fHasId'MonitorIntAsTag_Tag _KeyValueTag _LabelTag $fAsTagTag AsCheckStatus _CheckStatus_CheckOk _CheckWarning_CheckCritical _CheckUnknown$fAsCheckStatusCheckStatusAsEventPriority_EventPriority_NormalPriority _LowPriority$fAsEventPriorityEventPriority AsAlertType _AlertType_Error_Warning_Info_Success$fAsAlertTypeAlertType AsSourceType _SourceType_Nagios_Hudson_Jenkins_User_MyApps_Feed_Chef_Puppet_Git _BitBucket_Fabric _Capistrano$fAsSourceTypeSourceTypeAsMetricPoints _MetricPoints_Gauge_Counter$fAsMetricPointsMetricPoints AsMonitorType _MonitorType _MetricAlert _ServiceCheck _EventAlert$fAsMonitorTypeMonitorTypeDatadogCredentials signRequest prependMaybe prependBool datadogHttp decodeDatadog baseRequestdefaultMonitorOptions$fFromJSONMonitor$fToJSONMonitor$fFromJSONMonitorSpec$fToJSONMonitorSpec$fFromJSONMonitorOptions$fToJSONMonitorOptions$fFromJSONMonitorType$fToJSONMonitorType$fToJSONMetric$fToJSONMetricPoints$fToJSONTimestamp$fToJSONSeries$fFromJSONWrappedEvents$fFromJSONWrappedEvent$fFromJSONEvent $fToJSONEvent$fFromJSONEventSpec$fToJSONEventSpec$fFromJSONSourceType$fToJSONSourceType$fFromJSONAlertType$fToJSONAlertType$fFromJSONEventPriority$fToJSONEventPriority$fFromJSONDowntime$fToJSONDowntime$fFromJSONCheckResult$fToJSONCheckResult$fFromJSONCheckStatus$fToJSONCheckStatus $fFromJSONTag $fToJSONTag$fFromJSONDowntimeSpec$fToJSONDowntimeSpec$fDatadogCredentialsReadWrite$fDatadogCredentialsWritegetSilencedMonitorScopessilenceMonitorScopeunsilenceMonitorScopeunsilenceAllMonitorScopedoesNotifyOnNoMonitorDatanotifyOnNoMonitorDatanoNotifyOnNoMonitorDatagetMonitorTimeoutsetMonitorTimeoutclearMonitorTimeoutdoesRenotifyMonitorrenotifyMonitornoRenotifyMonitordoesNotifyOnAudit notifyOnAuditnoNotifyOnAuditminimalMonitorSpec createMonitor loadMonitor updateMonitor deleteMonitor loadMonitorsmuteAllMonitorsunmuteAllMonitorsseries sendMetricsmuteHost unmuteHostminimalEventSpec createEvent loadEvent loadEventsminimalDowntimeSpecscheduleDowntimeupdateDowntimecancelDowntime loadDowntime loadDowntimes recordCheckloadKeysFromEnvcreateEnvironment withDatadogwriteCredentialsreadWriteCredentials ToMetricValue encodeValue MetricTypeTimer HistogramSetfromTag MetricNamefromMetricNametagmetric$fToMetricValueDouble$fToMetricValueIntPriorityLowNormal HasSampleRate sampleRatevalueevent$fHasNameMetricMetricName$fHasSampleRateMetricDouble$fHasType'MetricMetricTypeServiceCheckStatus ServiceOkServiceWarningServiceCriticalServiceUnknownHasSourceTypeNamesourceTypeName HasHostnamehostnameHasAggregationKeyaggregationKey$fHasTagsEvent[]$fHasAggregationKeyEventMaybe$fHasAlertTypeEventMaybe$fHasDateHappenedEventMaybe$fHasHostnameEventMaybe$fHasPriorityEventMaybe$fHasSourceTypeNameEventMaybe$fHasTextEventText$fHasTitleEventText$fReadServiceCheckStatus$fShowServiceCheckStatus$fEqServiceCheckStatus$fOrdServiceCheckStatus$fEnumServiceCheckStatusDogStatsSettingsdogStatsSettingsHostdogStatsSettingsPortdogStatsSettingsBufferSizedogStatsSettingsMaxDelaydogStatsSettingsOnExceptionToStatsD serviceCheck$fHasTagsServiceCheck[]$fHasNameServiceCheckText$fHasHostnameServiceCheckMaybe"$fHasDateHappenedServiceCheckMaybe$fHasMessageServiceCheckMaybe)$fHasStatusServiceCheckServiceCheckStatus$fToStatsDServiceCheck$fToStatsDEvent$fToStatsDMetric StatsClientDummyHasPortportHasOnException onException HasMaxDelaymaxDelay HasBufferSize bufferSizedefaultSettings mkStatsClient withDogStatsDsendfinalizeStatsClient"$fHasBufferSizeDogStatsSettingsInt$fHasHostDogStatsSettings[] $fHasMaxDelayDogStatsSettingsInt"$fHasOnExceptionDogStatsSettings->$fHasPortDogStatsSettingsIntghc-prim GHC.TypesDouble text-1.2.3.1Data.Text.InternalTextbase GHC.MaybeMaybe time-1.8.0.2 Data.Time.Clock.Internal.UTCTimeUTCTimeaccumulateStatsversion getBinDir getLibDir getDynLibDir getDataDir getLibexecDir getSysconfDirgetDataFileName