Datadog
Background: Datadog is a service that logs all of the responses from our integrations and webhooks (except for Genability). It can be used to help troubleshoot if an integration or webhook is not behaving as expected.
Logging in
When you go to Datadog, use the ninjas@sighten.io login that should auto-populate from Lastpass
wa
If you are NOT able to log in, you must request access by using the following link (Click Here)
Reviewing Logs
You will land on a homepage/dashboard but the page that has the information relevant to support is the Logs located in the left sidebar:
When you land on the Logs page, it will automatically show all the responses from the last 15 minutes but you can search and filter by tons of different “facets” to drill down to what you need.
Page Layout
Filtering by time
On the top right, is where you can filter by time frame. There are a lot of options available in order to locate the event you need.
Filtering by Facet
The left sidebar is where you can filter by any of the headers also known as “facets”. We have many of the commonly used facets saved to this sidebar for easy filtering. The most commonly used facets are:
Integration name - this is where you can select the exact integration you want to see the logs for.
Response_status - if you’re looking for a failure you’ll probably want to filter out the successful requests i.e. the 200s
Env. - if you’re specifically looking for a log from engine, you can filter for this. On Datadog, engine = “prod”
Instance_pk - Search by the site UUID
Instance model - tells you the type of UUID Instance pk is (usually site)
Is Webhook? - webhooks just mix into the logs, so if you’re looking for a webhook response, then you can use this facet to drill down to what you’re looking for
Searching
The bar across the top is the search bar, where you can search for any identifying value. As you filter by facets, the search bar will update to show how you’re currently filtered.
Standard response codes
Successful:
200
201
202
Errors:
404
401
403
500 - time out
501 - time out
504 - time out
Sending requests outside of Sighten for review
If you’re sending a request to a 3rd party to review, only include the following fields: response_status, request_http_method, request_url, request_body, response_content, request_headers.
Furthermore, be sure to replace some of the auth characters with : *****