Pipelines and processors operate on incoming logs, parsing and transforming them into structured attributes for easier querying.
-
See the pipelines configuration page for a list of the pipelines and processors currently configured in web UI.
-
Additional API-related information about processors can be found in the processors documentation.
-
For more information about Pipelines, see the pipeline documentation.
Notes:
Grok parsing rules may effect JSON output and require
returned data to be configured before using in a request.
For example, if you are using the data returned from a
request for another request body, and have a parsing rule
that uses a regex pattern like \s for spaces, you will
need to configure all escaped spaces as %{space} to use
in the body data.
# NPM
npm install @datadog/datadog-api-client-logs-pipelines
# Yarn
yarn add @datadog/datadog-api-client-logs-pipelinesimport { createConfiguration } from "@datadog/datadog-api-client";
import { LogsPipelinesApiV1 } from "@datadog/datadog-api-client-logs-pipelines";
import { v1 } from "@datadog/datadog-api-client-logs-pipelines";
const configuration = createConfiguration();
const apiInstance = new LogsPipelinesApiV1(configuration);
apiInstance.getLogsPipelineOrder().then((data: v1.LogsPipelinesOrder) => {
console.log("API called successfully. Returned data: " + JSON.stringify(data));
}).catch((error) => {
console.error("Error calling API: " + error);
});