- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
Supported OS
Send Signal Sciences metrics and events to Datadog to monitor real-time attacks and abuse against your applications, APIs, and microservices, and to ensure Signal Sciences is functioning and inspecting traffic as expected.
Get metrics and events from Signal Sciences in real-time to:
See metrics from the WAF related to:
See IPs that Signal Sciences has blocked and/or flagged as malicious from any of the following activities:
See alerts on Signal Sciences agent status
To use the Signal Sciences-Datadog integration, you must be a customer of Signal Sciences. For more information about Signal Sciences, see https://www.signalsciences.com.
Install the Signal Sciences agent.
Configure the Signal Sciences agent to use DogStatsD:
Add the following line to each agent’s agent.config file:
statsd-type = "dogstatsd"
When this is done the agent’s StatsD client has tagging enabled and metrics such as sigsci.agent.signal.<SIGNAL_TYPE>
are sent as sigsci.agent.signal
and tagged with signal_type:<SIGNAL_TYPE>
.
Example:sigsci.agent.signal.http404
=> sigsci.agent.signal
with tag signal_type:http404
If using Kubernetes to run the Datadog Agent, make sure to enable DogStatsD non local traffic as described in the Kubernetes DogStatsD documentation.
Configure the SigSci agent to send metrics to the Datadog Agent:
Add the following line to each agent’s agent.config
file:
statsd-address="<DATADOG_AGENT_HOSTNAME>:<DATADOG_AGENT_PORT>"
Click the button to install the integration.
In Datadog, verify that the “Signal Sciences - Overview” dashboard is created and starting to capture metrics.
Within Datadog, create an API key.
In your Signal Sciences Dashboard on the Site navigation bar, click Manage > Integrations and click Add next to the Datadog Event integration.
Enter the API Key in the API Key field.
Click Add.
For more information, see the Datadog Signal Sciences integration.
sigsci.agent.waf.total (rate) | The number of requests inspected per second. Shown as request |
sigsci.agent.waf.error (rate) | The number of errors per second while processing requests. Shown as error |
sigsci.agent.waf.allow (rate) | The number of allow operations per second. Shown as operation |
sigsci.agent.waf.block (rate) | The number of block operations per second. Shown as operation |
sigsci.agent.waf.perf.decision_time.50pct (gauge) | The decision time 50th percentile. Shown as second |
sigsci.agent.waf.perf.decision_time.95pct (gauge) | The decision time 95th percentile. Shown as second |
sigsci.agent.waf.perf.decision_time.99pct (gauge) | The decision time 99th percentile. Shown as second |
sigsci.agent.waf.perf.queue_time.50pct (gauge) | The queue time 50th percentile. Shown as second |
sigsci.agent.waf.perf.queue_time.95pct (gauge) | The queue time 95th percentile. Shown as second |
sigsci.agent.waf.perf.queue_time.99pct (gauge) | The queue time 99th percentile. Shown as second |
sigsci.agent.rpc.connections.open (gauge) | The number of open rpc connections. Shown as connection |
sigsci.agent.runtime.cpu_pct (gauge) | CPU percent used by the agent. Shown as percent |
sigsci.agent.runtime.mem.sys_bytes (gauge) | Memory used by the agent. Shown as byte |
sigsci.agent.runtime.uptime (gauge) | Agent uptime in seconds. Shown as second |
sigsci.agent.signal (rate) | Number of signals of each type per second.. |
Events are created and sent to your Datadog Event Stream when an IP address is flagged in Signal Sciences.
The Signal Sciences integration does not include any service checks.
Need help? Contact Datadog support.
Additional helpful documentation, links, and articles: