# Mezmo Docs

> Explore guides, APIs, tutorials, and reference materials for collecting telemetry and using Mezmo’s SRE agent to manage production environments.

## Docs

- [Introduction](https://docs.mezmo.com/OptTutorial/1-intro.md): Workshop overview for using the OpenTelemetry Demo and Mezmo to understand and optimize telemetry data for both MTTR and cost.
- [Shared Sources](https://docs.mezmo.com/OptTutorial/2-shared-sources.md): Create OpenTelemetry log, metric, and trace Shared Sources in Mezmo and save their access keys for the optimization workshop.
- [Setting Up the OTel Demo App](https://docs.mezmo.com/OptTutorial/3-configure-build-demo.md): Clone the OpenTelemetry Demo, configure the collector with your Mezmo Shared Source credentials, and run it via Docker.
- [Profiling Log Data](https://docs.mezmo.com/OptTutorial/4-profile-log-data.md): Build an exploration pipeline with the Mezmo Data Profiler to surface high-volume and unparsed log patterns in the OpenTelemetry Demo.
- [Log Data Optimization Pipeline](https://docs.mezmo.com/OptTutorial/5-optimize-logs.md): Build a responsive log pipeline that enriches, parses, routes by state, aggregates, and samples logs before sending them to Mezmo Log Analysis.
- [Metrics Data Optimization Pipeline](https://docs.mezmo.com/OptTutorial/6-optimize-metrics.md): Build a Mezmo pipeline that enriches, state-routes, aggregates, and limits cardinality on OpenTelemetry metrics to reduce volume.
- [Trace Data Optimization Pipeline](https://docs.mezmo.com/OptTutorial/7-optimize-traces.md): Build a Mezmo pipeline that enriches, state-routes, and samples OpenTelemetry traces to cut volume while preserving incident fidelity.
- [Updating to Responsive Pipelines](https://docs.mezmo.com/OptTutorial/8-optimize-responsively.md): Use a REST API shell script to switch your log, metric, and trace pipelines into incident mode for full-fidelity data on demand.
- [What's Next?](https://docs.mezmo.com/OptTutorial/9-next-steps.md): Recap the four OpenTelemetry optimization pipelines you built and explore further Mezmo capabilities like rehydration, alerting, and PII redaction.
- [Get account details](https://docs.mezmo.com/api-reference/account/get-account-details.md): Get list of settings applied to an account
- [Update account details](https://docs.mezmo.com/api-reference/account/update-account-details.md): Update account settings
- [Update pipeline processing status](https://docs.mezmo.com/api-reference/account/update-pipeline-processing-status.md): Change a pipeline to enabled or disabled
- [Add usage alert](https://docs.mezmo.com/api-reference/alerting/add-usage-alert.md): Creates a new usage threshold alert configuration
- [Create component alert](https://docs.mezmo.com/api-reference/alerting/create-component-alert.md): Create an alert attached to a pipeline component
- [Delete component alert](https://docs.mezmo.com/api-reference/alerting/delete-component-alert.md): Removes an alert attached to a pipeline component
- [Fetch component alert](https://docs.mezmo.com/api-reference/alerting/fetch-component-alert.md): Retrieves an alert attached to a pipeline component
- [List all threshold alerts](https://docs.mezmo.com/api-reference/alerting/list-all-threshold-alerts.md): Returns configuration of existing threshold alerts
- [List component alerts](https://docs.mezmo.com/api-reference/alerting/list-component-alerts.md): List of alerts attached to a pipeline's components
- [Partially update an existing threshold alert](https://docs.mezmo.com/api-reference/alerting/partially-update-an-existing-threshold-alert.md): Update a part of usage threshold alert
- [Remove usage threshold alert](https://docs.mezmo.com/api-reference/alerting/remove-usage-threshold-alert.md): Removes an existing threshold alert
- [Retrieves an existing usage threshold alert](https://docs.mezmo.com/api-reference/alerting/retrieves-an-existing-usage-threshold-alert.md): Returns usage threshold configuration
- [Update component alert](https://docs.mezmo.com/api-reference/alerting/update-component-alert.md): Update an alert attached to a pipeline component
- [Update threshold alert](https://docs.mezmo.com/api-reference/alerting/update-threshold-alert.md): Replace an existing usage alert with this one
- [Create Archive Configuration](https://docs.mezmo.com/api-reference/archiving/create-archive-configuration.md): Use this method to configure archiving for an instance. Only one archiving configuration may exist at any time.
- [Delete Archive Configuration](https://docs.mezmo.com/api-reference/archiving/delete-archive-configuration.md): Use this method to delete the archiving configuration.
- [Get Archive Configuration](https://docs.mezmo.com/api-reference/archiving/get-archive-configuration.md): Use this method to get an existing archiving configuration.
- [Update Archive Configuration](https://docs.mezmo.com/api-reference/archiving/update-archive-configuration.md): Use this method to update an existing archiving configuration.
- [Create Board](https://docs.mezmo.com/api-reference/board/create-board.md): Use this method to create a board.
- [Delete Board](https://docs.mezmo.com/api-reference/board/delete-board.md): Use this method to delete a board.
- [Get Board](https://docs.mezmo.com/api-reference/board/get-board.md): Gets the configuration for a specific board.
- [List Boards](https://docs.mezmo.com/api-reference/board/list-boards.md): Get a list of boards.
- [Create New Category](https://docs.mezmo.com/api-reference/configuration/create-new-category.md): Creates a new category of this type.
- [Create Preset Alert](https://docs.mezmo.com/api-reference/configuration/create-preset-alert.md): Use this method to create a preset alert.
- [Create View](https://docs.mezmo.com/api-reference/configuration/create-view.md): Use this method to create a view and attach alerts to the view.
- [Delete Alert](https://docs.mezmo.com/api-reference/configuration/delete-alert.md): Use this method to delete a preset alert.
- [Delete Category](https://docs.mezmo.com/api-reference/configuration/delete-category.md): Use this method to delete a category.
- [Delete View](https://docs.mezmo.com/api-reference/configuration/delete-view.md): Use this method to delete a view and any attached alerts.
- [Get Category](https://docs.mezmo.com/api-reference/configuration/get-category.md): Get a specific category
- [Get Preset Alert](https://docs.mezmo.com/api-reference/configuration/get-preset-alert.md): Get a specific preset alert
- [Get View](https://docs.mezmo.com/api-reference/configuration/get-view.md): Gets the configuration for a specific view.
- [List Categories](https://docs.mezmo.com/api-reference/configuration/list-categories.md): Returns all Categories of a type.
- [List Preset Alerts](https://docs.mezmo.com/api-reference/configuration/list-preset-alerts.md): Returns all Preset Alerts in the account.
- [List Views](https://docs.mezmo.com/api-reference/configuration/list-views.md): Get a list of views.
- [Update Alert](https://docs.mezmo.com/api-reference/configuration/update-alert.md): Update a specific preset alert.
- [Update Category](https://docs.mezmo.com/api-reference/configuration/update-category.md): Update a specific category.
- [Update View](https://docs.mezmo.com/api-reference/configuration/update-view.md): Use this method to update a view. You can change the view configuration details; add or remove view specific alerts; or attach and detach preset alerts.
- [Fetch classifier information](https://docs.mezmo.com/api-reference/data-classification-&-profiling/fetch-classifier-information.md): Retrieve information about a classification of a shared source
- [Fetch usage metrics](https://docs.mezmo.com/api-reference/data-classification-&-profiling/fetch-usage-metrics.md): Query and fetch usage metrics from data profiling.
- [Get Field Summary for an analysis](https://docs.mezmo.com/api-reference/data-classification-&-profiling/get-field-summary-for-an-analysis.md): Get Field Summary for an analysis
- [Get Field Summary values for a field in an analysis](https://docs.mezmo.com/api-reference/data-classification-&-profiling/get-field-summary-values-for-a-field-in-an-analysis.md): Get Field Summary values for a field in an analysis
- [Get pipeline transform classifieranalysis](https://docs.mezmo.com/api-reference/data-classification-&-profiling/get-pipeline-transform-classifieranalysis.md)
- [Get pipelinetransformclassifieranalysis](https://docs.mezmo.com/api-reference/data-classification-&-profiling/get-pipelinetransformclassifieranalysis.md)
- [Update analysis options](https://docs.mezmo.com/api-reference/data-classification-&-profiling/update-analysis-options.md): Reset classification and profiling results
- [Add task result](https://docs.mezmo.com/api-reference/edge--local-deploy/add-task-result.md): Add results for a given task
- [Fetch logs from Edge](https://docs.mezmo.com/api-reference/edge--local-deploy/fetch-logs-from-edge.md): Receive logs from an Edge pipeline
- [Get client config](https://docs.mezmo.com/api-reference/edge--local-deploy/get-client-config.md): Gets client configuration for Edge pipelines
- [Get usage metrics](https://docs.mezmo.com/api-reference/edge--local-deploy/get-usage-metrics.md): Receive usage metrics from an Edge pipeline
- [List all heartbeats](https://docs.mezmo.com/api-reference/edge--local-deploy/list-all-heartbeats.md): List all Edge check-ins for the account
- [Poll tasks](https://docs.mezmo.com/api-reference/edge--local-deploy/poll-tasks.md): Poll and claim available local deployment tasks for a pipeline
- [Post client config](https://docs.mezmo.com/api-reference/edge--local-deploy/post-client-config.md): Posts deployment configuration+liveness for Edge pipelines, returning pipeline config
- [Remove heartbeat](https://docs.mezmo.com/api-reference/edge--local-deploy/remove-heartbeat.md): Removes existing Edge heartbeats
- [Attach a child organization to an enterprise](https://docs.mezmo.com/api-reference/enterprise/attach-a-child-organization-to-an-enterprise.md): Attaches an existing organization to an enterprise. The `retention` and `owner` field are optional, and will be defaulted if not specified. To specify which child organization to attach, one of its service keys must be supplied through our typical service key authorization schema; either as basic au…
- [Delete an Enterprise ServiceKey](https://docs.mezmo.com/api-reference/enterprise/delete-an-enterprise-servicekey.md): Delete an Enterprise ServiceKey from list of keys for the Enterprise
- [Detach a child org from Enterprise](https://docs.mezmo.com/api-reference/enterprise/detach-a-child-org-from-enterprise.md): Detaches a child organization from the enterprise. The child organization is not deleted and can continue to work afterwards.
- [Generate a new Key for the Enterprise](https://docs.mezmo.com/api-reference/enterprise/generate-a-new-key-for-the-enterprise.md): Generate a new ServiceKey for the enterprise
- [Get details of a child organization](https://docs.mezmo.com/api-reference/enterprise/get-details-of-a-child-organization.md): Retrieves a specific child organization by its id. If the organization does not belong to the enterprise, a 404 error is returned.
- [List all accounts](https://docs.mezmo.com/api-reference/enterprise/list-all-accounts.md): Retrieves a list of all child organizations that belong to the enterprise.
- [List all enterprise keys](https://docs.mezmo.com/api-reference/enterprise/list-all-enterprise-keys.md): Retrieves all keys of the enterprise
- [Retrieve a specific entperise key](https://docs.mezmo.com/api-reference/enterprise/retrieve-a-specific-entperise-key.md): Retrieves a specific enterprise key by its `id`.
- [Update Child Organization Contract](https://docs.mezmo.com/api-reference/enterprise/update-child-organization-contract.md): Makes an update to the specified child organization. Used to modify the current retention with the `retention` field or the current owner with the `owner` field.
- [Create Exclusion Rule](https://docs.mezmo.com/api-reference/exclusions/create-exclusion-rule.md): Create a new ingestion exclusion rule to help reduce log volume
- [Delete Exclusion Rule](https://docs.mezmo.com/api-reference/exclusions/delete-exclusion-rule.md): Use this method to delete an exclusion rule.
- [Get Exclusion Rule](https://docs.mezmo.com/api-reference/exclusions/get-exclusion-rule.md): Returns an exclusion rule with the id specified.
- [List Exclusion Rules](https://docs.mezmo.com/api-reference/exclusions/list-exclusion-rules.md): Returns a list of exclusion rules. Note: This does not return usage quota rules.
- [Update Exclusion Rule](https://docs.mezmo.com/api-reference/exclusions/update-exclusion-rule.md): Updates an existing exclusion rule
- [Use AI to automatically parse log text into JSON](https://docs.mezmo.com/api-reference/experimental/use-ai-to-automatically-parse-log-text-into-json.md): Generates a parsed JSON object for each textual log line provided.
- [Use AI to generate Regular Expressions](https://docs.mezmo.com/api-reference/experimental/use-ai-to-generate-regular-expressions.md): Generates one or more regular expression that will parse the given log samples
- [Export log lines](https://docs.mezmo.com/api-reference/export/export-log-lines.md): Use this method to export logs in JSON format from a logging instance.
- [Export log lines](https://docs.mezmo.com/api-reference/export/export-log-lines-1.md): Use this method to export logs in JSON format from a logging instance.
- [Create Group](https://docs.mezmo.com/api-reference/groups/create-group.md): Use this method to create a log group where you can scope the data that is accessible by members in that group.
- [Delete Group](https://docs.mezmo.com/api-reference/groups/delete-group.md): Use this method to list the log groups.
- [Get Group](https://docs.mezmo.com/api-reference/groups/get-group.md): Use this method to get information on a group.
- [List Groups](https://docs.mezmo.com/api-reference/groups/list-groups.md): Use this method to list the log groups.
- [Update Group](https://docs.mezmo.com/api-reference/groups/update-group.md): Use this method to modify a log group. You can change the name of the group and the access scope that defines the data that is accessible by members in that group.
- [Create state variable](https://docs.mezmo.com/api-reference/incident-mode/create-state-variable.md): Add a pipeline state variable to the account
- [Fetch state variable](https://docs.mezmo.com/api-reference/incident-mode/fetch-state-variable.md): Fetches the value of a state variable
- [List all state variables](https://docs.mezmo.com/api-reference/incident-mode/list-all-state-variables.md): List all state variables defined in the account
- [Partially update state variable](https://docs.mezmo.com/api-reference/incident-mode/partially-update-state-variable.md): Update one or many state variables
- [Update state variable](https://docs.mezmo.com/api-reference/incident-mode/update-state-variable.md): Edits an existing state variable
- [Get Index Rate Alert](https://docs.mezmo.com/api-reference/index-rate-alert/get-index-rate-alert.md): Gets the configuration for an Index Rate Alert
- [Update Index Rate Alert](https://docs.mezmo.com/api-reference/index-rate-alert/update-index-rate-alert.md): Use this method to update an index rate alert. You can change the alert's configuration details.
- [Send Log Lines](https://docs.mezmo.com/api-reference/ingestion/send-log-lines.md): Use this method to send logs to a logging instance.
- [Create a new key](https://docs.mezmo.com/api-reference/keys/create-a-new-key.md): Create a new key of the type specified by the `type` parameter. If a name is not supplied, one will be auto generated.
- [Delete a specific key](https://docs.mezmo.com/api-reference/keys/delete-a-specific-key.md): Delete a specific key by its `id`.
- [Retrieve a list of all the keys](https://docs.mezmo.com/api-reference/keys/retrieve-a-list-of-all-the-keys.md): Retrieve a list of all the keys for an account. Supported key types include `ingestion` and `service`. Use the `type` parameter to filter which type of keys to retrieve.
- [Retrieve a specific key](https://docs.mezmo.com/api-reference/keys/retrieve-a-specific-key.md): Retrieves a specific key by its `id`.
- [Update one or more fields of a key resource](https://docs.mezmo.com/api-reference/keys/update-one-or-more-fields-of-a-key-resource.md): Updates all of the fields described in the request body of the specified key. Fields left out of the body will remain unaffected.
- [Log Volume Reduction](https://docs.mezmo.com/api-reference/log-volume-reduction/log-volume-reduction.md): Post log volume reduction actions to a pipeline
- [Creates a new member](https://docs.mezmo.com/api-reference/members/creates-a-new-member.md): Create a new user and add to the team by providing 'email', 'role' and an optional list of RBAC groups.
- [Delete a member](https://docs.mezmo.com/api-reference/members/delete-a-member.md): Removes a member from the organization. This does not delete the user.
- [Lists all members](https://docs.mezmo.com/api-reference/members/lists-all-members.md): Retrieves all of the current members in an organization and returns their email, role, and groups.
- [Retrieve a member](https://docs.mezmo.com/api-reference/members/retrieve-a-member.md): Returns the role and groups of the specified member.
- [Update a member](https://docs.mezmo.com/api-reference/members/update-a-member.md): Updates all the fields described in the request body of the specified member. Creates a member if the member doesn't exist already. Fields left out of the body will remain unaffected.
- [Fetch account usage metics](https://docs.mezmo.com/api-reference/metrics/fetch-account-usage-metics.md): Query and fetch usage metrics for the current account.
- [Fetch log cluster samples](https://docs.mezmo.com/api-reference/metrics/fetch-log-cluster-samples.md): Query and fetch log cluster samples from data profiling.
- [Fetch log usage metrics](https://docs.mezmo.com/api-reference/metrics/fetch-log-usage-metrics.md): Query and fetch log clustering usage metrics from data profiling.
- [Fetch pipeline health metrics](https://docs.mezmo.com/api-reference/metrics/fetch-pipeline-health-metrics.md): Query and fetch health information for the current account.
- [Get event metrics for a pipeline](https://docs.mezmo.com/api-reference/metrics/get-event-metrics-for-a-pipeline.md): Query and fetch event metrics for a pipeline
- [Delete Parsing Template](https://docs.mezmo.com/api-reference/parsing-template/delete-parsing-template.md): Use this method to delete a parsing template.
- [Get Parsing Template](https://docs.mezmo.com/api-reference/parsing-template/get-parsing-template.md): Gets the configuration for a specific parsing template.
- [List Parsing Templates](https://docs.mezmo.com/api-reference/parsing-template/list-parsing-templates.md): Get a list of custom parsing templates.
- [Trigger pipeline export](https://docs.mezmo.com/api-reference/pipeline-export/trigger-pipeline-export.md): Prepare a pipeline for export into a terraform workspace.
- [Add prebuilt pipeline to account](https://docs.mezmo.com/api-reference/pipeline-management/add-prebuilt-pipeline-to-account.md): Creates a new pipeline in the account that is prebuilt
- [Create pipeline](https://docs.mezmo.com/api-reference/pipeline-management/create-pipeline.md): Creates a new pipeline (non published)
- [Deletes a pipeline](https://docs.mezmo.com/api-reference/pipeline-management/deletes-a-pipeline.md): Removes a pipeline from the account
- [Fetch audit events](https://docs.mezmo.com/api-reference/pipeline-management/fetch-audit-events.md): Retrieve a paginated list of pipeline audit events for an account
- [Fetch pipeline confg](https://docs.mezmo.com/api-reference/pipeline-management/fetch-pipeline-confg.md): Retrieve a pipeline configuration
- [Fetch pipeline revision](https://docs.mezmo.com/api-reference/pipeline-management/fetch-pipeline-revision.md): Returns a pipeline configuration from a particular version
- [Initialize a pipeline with provided components. All sources, transforms, and sinks are linked.](https://docs.mezmo.com/api-reference/pipeline-management/initialize-a-pipeline-with-provided-components-all-sources-transforms-and-sinks-are-linked.md): Populates and publishes a new pipeline as specified.
- [Initialize a pipeline with provided components. The links for all components have to be determined by the caller.](https://docs.mezmo.com/api-reference/pipeline-management/initialize-a-pipeline-with-provided-components-the-links-for-all-components-have-to-be-determined-by-the-caller.md): Populates and publishes a new pipeline as specified.
- [List all pipeline revisions](https://docs.mezmo.com/api-reference/pipeline-management/list-all-pipeline-revisions.md): Returns a list of revisions that exist in the pipeline
- [List all pipelines](https://docs.mezmo.com/api-reference/pipeline-management/list-all-pipelines.md): List all pipelines for the account
- [List available pipeline nodes](https://docs.mezmo.com/api-reference/pipeline-management/list-available-pipeline-nodes.md): A list of all available nodes for use when creating pipelines
- [Publish pipeline](https://docs.mezmo.com/api-reference/pipeline-management/publish-pipeline.md): Creates a new pipeline in the account
- [Revert pipeline to version](https://docs.mezmo.com/api-reference/pipeline-management/revert-pipeline-to-version.md): Updates a pipeline configuration to a previous version
- [Summarize pipeline health for one or more pipelines](https://docs.mezmo.com/api-reference/pipeline-management/summarize-pipeline-health-for-one-or-more-pipelines.md): Returns overall ingestion health as well as pipeline-specific health, such as lag in a pipeline's sources.
- [Update pipeline](https://docs.mezmo.com/api-reference/pipeline-management/update-pipeline.md): Update pipeline properties, like title
- [Add a sink to a pipeline](https://docs.mezmo.com/api-reference/pipeline-nodes/add-a-sink-to-a-pipeline.md)
- [Add source](https://docs.mezmo.com/api-reference/pipeline-nodes/add-source.md): Adds a source to a pipeline
- [Add transform](https://docs.mezmo.com/api-reference/pipeline-nodes/add-transform.md): Add a transform to a pipeline
- [Delete pipeline transform group](https://docs.mezmo.com/api-reference/pipeline-nodes/delete-pipeline-transform-group.md)
- [Delete sink](https://docs.mezmo.com/api-reference/pipeline-nodes/delete-sink.md): Remove sink from a pipeline
- [Fetch sink](https://docs.mezmo.com/api-reference/pipeline-nodes/fetch-sink.md): Fetch a sink configuration of a pipeline
- [Fetch transform](https://docs.mezmo.com/api-reference/pipeline-nodes/fetch-transform.md): Fetch transform configuration
- [Get pipeline transform group](https://docs.mezmo.com/api-reference/pipeline-nodes/get-pipeline-transform-group.md)
- [Post pipeline transform group](https://docs.mezmo.com/api-reference/pipeline-nodes/post-pipeline-transform-group.md)
- [Put pipeline transform group](https://docs.mezmo.com/api-reference/pipeline-nodes/put-pipeline-transform-group.md)
- [Remove source](https://docs.mezmo.com/api-reference/pipeline-nodes/remove-source.md): Removes a source from a pipeline
- [Remove transform](https://docs.mezmo.com/api-reference/pipeline-nodes/remove-transform.md): Removes transform from pipeline
- [Retrieve source](https://docs.mezmo.com/api-reference/pipeline-nodes/retrieve-source.md): Fetches configuration of a source
- [Update sink](https://docs.mezmo.com/api-reference/pipeline-nodes/update-sink.md): Updates a sink of a pipeline
- [Update source](https://docs.mezmo.com/api-reference/pipeline-nodes/update-source.md): Updates a source in a pipeline
- [Update transform](https://docs.mezmo.com/api-reference/pipeline-nodes/update-transform.md): Updates a transform of a pipeline
- [Delete transform group](https://docs.mezmo.com/api-reference/processor-groups/delete-transform-group.md): Delete a Processor Group
- [Delete transform group transform](https://docs.mezmo.com/api-reference/processor-groups/delete-transform-group-transform.md): Delete a Processor from a Processor Group
- [Get transform group](https://docs.mezmo.com/api-reference/processor-groups/get-transform-group.md): Get a Processor Group
- [Get transform group 1](https://docs.mezmo.com/api-reference/processor-groups/get-transform-group-1.md): List all Processor Groups for the account
- [Get transform group revision](https://docs.mezmo.com/api-reference/processor-groups/get-transform-group-revision.md)
- [Get transform group revision 1](https://docs.mezmo.com/api-reference/processor-groups/get-transform-group-revision-1.md)
- [Get transform group transform](https://docs.mezmo.com/api-reference/processor-groups/get-transform-group-transform.md): Get a Processor from a Processor Group
- [Post transform group](https://docs.mezmo.com/api-reference/processor-groups/post-transform-group.md): Create a new Processor Group
- [Post transform group publish](https://docs.mezmo.com/api-reference/processor-groups/post-transform-group-publish.md): Publish changes to a Processor Group
- [Post transform group transform](https://docs.mezmo.com/api-reference/processor-groups/post-transform-group-transform.md): Create a Processor in a Processor Group
- [Post transform groupfrom pipeline](https://docs.mezmo.com/api-reference/processor-groups/post-transform-groupfrom-pipeline.md): Create a new Processor Group from a set of Pipeline components
- [Put transform group](https://docs.mezmo.com/api-reference/processor-groups/put-transform-group.md): Update a Processor Group
- [Put transform group transform](https://docs.mezmo.com/api-reference/processor-groups/put-transform-group-transform.md): Update a Processor in a Processor Group
- [Create data sample](https://docs.mezmo.com/api-reference/sampling-and-simulation/create-data-sample.md): Create sample data for use in simulation
- [Delete data sample](https://docs.mezmo.com/api-reference/sampling-and-simulation/delete-data-sample.md): Remove a data sample from the pipeline
- [Fetch data sample](https://docs.mezmo.com/api-reference/sampling-and-simulation/fetch-data-sample.md): Returns a data sample
- [List data samples](https://docs.mezmo.com/api-reference/sampling-and-simulation/list-data-samples.md): Returns a list of data samples that exist in the pipeline
- [Post transform group simulate](https://docs.mezmo.com/api-reference/sampling-and-simulation/post-transform-group-simulate.md): Sends data to a vector instance with a simulated transform group
- [Retrieve grok pattern](https://docs.mezmo.com/api-reference/sampling-and-simulation/retrieve-grok-pattern.md): Retrieves a list of grok patterns available to use
- [Simulate grok pattern](https://docs.mezmo.com/api-reference/sampling-and-simulation/simulate-grok-pattern.md): Simulate data flowing through a grok pattern
- [Simulate regex pattern](https://docs.mezmo.com/api-reference/sampling-and-simulation/simulate-regex-pattern.md): View results of sending data using a regular expression
- [Simulate timestamp pattern](https://docs.mezmo.com/api-reference/sampling-and-simulation/simulate-timestamp-pattern.md): Simulate data with a timestamp format
- [Start pipeline tap](https://docs.mezmo.com/api-reference/sampling-and-simulation/start-pipeline-tap.md): Start a tap operation to view data as it flows through the pipeline.
- [Start simulation of pipeline](https://docs.mezmo.com/api-reference/sampling-and-simulation/start-simulation-of-pipeline.md): Sends data to a vector instance with a simulated pipeline
- [Update data sample](https://docs.mezmo.com/api-reference/sampling-and-simulation/update-data-sample.md): Updates an existing data sample
- [Creates a new screen](https://docs.mezmo.com/api-reference/screens/creates-a-new-screen.md): Creates a new screen
- [Delete a screen](https://docs.mezmo.com/api-reference/screens/delete-a-screen.md): Deletes a screen
- [List all screens](https://docs.mezmo.com/api-reference/screens/list-all-screens.md): List all screens in a short form that only includes the screen id and title.
- [Retrieve a screen](https://docs.mezmo.com/api-reference/screens/retrieve-a-screen.md): Retrieve a specific screen
- [Add signing key](https://docs.mezmo.com/api-reference/shared-sources/add-signing-key.md): Adds a signing key to a gateway route
- [Create access key](https://docs.mezmo.com/api-reference/shared-sources/create-access-key.md): Create an access key associated with this gateway route
- [Create gateway route](https://docs.mezmo.com/api-reference/shared-sources/create-gateway-route.md): Create a gateway route
- [Delete access key](https://docs.mezmo.com/api-reference/shared-sources/delete-access-key.md): Delete an access key
- [Delete gateway route](https://docs.mezmo.com/api-reference/shared-sources/delete-gateway-route.md): Delete an unused gateway route. If the route is used by any active pipeline, an error will be returned.
- [Delete signing key](https://docs.mezmo.com/api-reference/shared-sources/delete-signing-key.md): Removes a signing key attached to a gateway route
- [List all gateway routes](https://docs.mezmo.com/api-reference/shared-sources/list-all-gateway-routes.md): List all of the shareable gateway routes for an account
- [Retrieve gateway route](https://docs.mezmo.com/api-reference/shared-sources/retrieve-gateway-route.md): Retreive a gateway route
- [Update gateway route](https://docs.mezmo.com/api-reference/shared-sources/update-gateway-route.md): Updates a gateway route
- [Update gateway route property](https://docs.mezmo.com/api-reference/shared-sources/update-gateway-route-property.md): Patches a gateway route
- [Confirm Ingestion Suspension](https://docs.mezmo.com/api-reference/suspensions/confirm-ingestion-suspension.md): After /suspend is called, a token is returned for use with this route as a confirmation.
- [Get Ingestion Status](https://docs.mezmo.com/api-reference/suspensions/get-ingestion-status.md): Retrieve the status of ingestion
- [Initiate Ingestion Suspension](https://docs.mezmo.com/api-reference/suspensions/initiate-ingestion-suspension.md): First step in suspending ingestion for the instance. Returns a token for use in /suspend/confirm to actually stop ingestion
- [Resume Ingestion](https://docs.mezmo.com/api-reference/suspensions/resume-ingestion.md): Resumes ingestion if it has been previously suspended
- [Get Usage By App](https://docs.mezmo.com/api-reference/usage-v1/get-usage-by-app.md): Gets the aggregated usage information for an app matching the name provided as a path parameter, during a time period. Returns null when not found.
- [Get Usage by Host](https://docs.mezmo.com/api-reference/usage-v1/get-usage-by-host.md): Gets the aggregated usage information for a host matching the name provided as a path parameter, during a time period. Returns null when not found.
- [Get Usage by Tag](https://docs.mezmo.com/api-reference/usage-v1/get-usage-by-tag.md): Gets the aggregated usage information for a tag matching the name provided as a path parameter, during a time period. Returns null when not found.
- [List Usage By App](https://docs.mezmo.com/api-reference/usage-v1/list-usage-by-app.md): Lists aggregated usage information for all apps during a time period.
- [List Usage by Host](https://docs.mezmo.com/api-reference/usage-v1/list-usage-by-host.md): Lists aggregated usage information for all hosts during a time period.
- [List Usage by Tag](https://docs.mezmo.com/api-reference/usage-v1/list-usage-by-tag.md): Lists aggregated usage information for all tags during a time period.
- [Get Usage By App](https://docs.mezmo.com/api-reference/usage-v2/get-usage-by-app.md): Gets the aggregated usage information for an app matching the name provided as a path parameter during a time period. The `results` will either have a singular item, or be an empty array.
- [Get Usage by Host](https://docs.mezmo.com/api-reference/usage-v2/get-usage-by-host.md): Gets the aggregated usage information for a host matching the name provided as a path parameter during a time period. The `results` will either have a singular item, or be an empty array.
- [Get Usage by Tag](https://docs.mezmo.com/api-reference/usage-v2/get-usage-by-tag.md): Gets the aggregated usage information for a tag matching the name provided as a path parameter during a time period. The `results` will either have a singular item, or be an empty array.
- [List Usage By App](https://docs.mezmo.com/api-reference/usage-v2/list-usage-by-app.md): Lists aggregated usage information for all apps during a time period.
- [List Usage by Host](https://docs.mezmo.com/api-reference/usage-v2/list-usage-by-host.md): Lists aggregated usage information for all hosts during a time period.
- [List Usage by Tag](https://docs.mezmo.com/api-reference/usage-v2/list-usage-by-tag.md): Lists aggregated usage information for all tags during a time period.
- [Retrieve account usage totals](https://docs.mezmo.com/api-reference/usage-v2/retrieve-account-usage-totals.md): Get aggregated usage information for an account's data during a time period.
- [Mezmo Ingestion Service Limits](https://docs.mezmo.com/docs/Mezmo-ingestion-service-limits.md): Reference the size limits Mezmo enforces during ingestion for body, message, metadata, hostname, app name, log level, tags, and fields.
- [About Mezmo Log Management](https://docs.mezmo.com/docs/about-mezmo-log-analysis.md): Learn how Mezmo centralizes log ingestion, parsing, exclusion rules, alerts, spike protection, and archiving on a single platform.
- [Access Management for Enterprise Organizations](https://docs.mezmo.com/docs/access-management-for-enterprise-organizations.md): Configure sign-in policies, SAML SSO, organization discoverability, and login methods for child organizations in a Mezmo Enterprise account.
- [Add a Breakdown to a Graph](https://docs.mezmo.com/docs/add-a-breakdown-to-a-graph.md): Create histogram and pie chart breakdowns to see how aggregated plot values are distributed across fields like response codes and hosts.
- [Add a Plot to a Graph](https://docs.mezmo.com/docs/add-a-plot-to-a-graph.md): Add additional data points to a graph to compare error levels and response codes using system fields and optional plot filters.
- [Add Alerts to Views](https://docs.mezmo.com/docs/add-alerts-to-views.md): Attach presence or absence alerts to a single view, or build reusable alert presets with custom schedules to apply across multiple views.
- [Add Enterprise Admins](https://docs.mezmo.com/docs/add-enterprise-admins.md): Grant Super Admin privileges from the General page so users can view the Enterprise Dashboard, manage child organizations, and set sign-in options.
- [About Mezmo Agent Exclusion Rule: MEZMO Created - Exclude Agent-Generated Errors](https://docs.mezmo.com/docs/agent-generated-errors.md): Understand the exclusion rule Mezmo added to filter excessive, low-value log lines caused by a bug in agent versions earlier than 3.x.
- [Akamai Cloud Monitor](https://docs.mezmo.com/docs/akamai-cloud-monitor-logs.md): Configure Akamai Cloud Monitor data delivery to forward logs to Mezmo and learn how Akamai datasets and fields are parsed and formatted.
- [AWS S3](https://docs.mezmo.com/docs/amazon-s3-logs.md): Use an AWS Lambda function to subscribe to an S3 bucket, transform retrieved log data, and route your logs from S3 into Mezmo.
- [API References](https://docs.mezmo.com/docs/api-referencesk9h.md): Find links to Mezmo's Log Analysis API and Telemetry Pipelines API reference documentation.
- [AppOptics Alert Integration](https://docs.mezmo.com/docs/appoptics-alert-integration.md): Connect Mezmo alerts to the AppOptics Measurement API using a Record Only API token so triggered alerts create measurements in AppOptics.
- [Aptible](https://docs.mezmo.com/docs/aptible-logs.md): Set up Aptible log ingestion from the Mezmo Web App using your ingestion key, and learn why multi-line parsing is not supported.
- [Archive Logs](https://docs.mezmo.com/docs/archiving.md): Automatically export retained logs hourly to external storage as compressed JSON, with details on file naming, encryption, and restoration support.
- [Authenticating With The API](https://docs.mezmo.com/docs/authenticating-with-the-api.md): Authenticate Mezmo API requests with key-based tokens in the Authorization header, including enterprise delegation, token types, and best practices.
- [Azure Entra ID SAML Setup](https://docs.mezmo.com/docs/azure-saml.md): Configure SAML single sign-on between Mezmo and Azure Entra ID by exchanging sign-on URLs and uploading the federation metadata XML.
- [Billing Procedures](https://docs.mezmo.com/docs/billing-procedures.md): Understand how Mezmo handles failed payments on self-service paid plans, including retry timing, paywalls, and account archiving.
- [Browser Logger Template](https://docs.mezmo.com/docs/browser-logger-template.md): Use pre-configured Views, Boards, and Screens to analyze browser-side errors by message, OS, and browser version with the Mezmo Browser Logger.
- [Mezmo Client-Side Logger](https://docs.mezmo.com/docs/client-side-logging.md): Use Mezmo's Node.js library to send client-side JavaScript logs directly to Mezmo with multiple log levels, metadata, and tags.
- [Cloud Foundry](https://docs.mezmo.com/docs/cloudfoundry.md): Stream events from your entire Cloud Foundry deployment to Mezmo using the Mezmo nozzle and your ingestion key.
- [AWS CloudWatch](https://docs.mezmo.com/docs/cloudwatch.md): Route and transform CloudWatch log data to Mezmo using the AWS Lambda-based Mezmo CloudWatch integration.
- [Code Libraries](https://docs.mezmo.com/docs/code-libraries.md): Find official and community logging libraries for sending logs to Mezmo across languages like Go, Node.js, Python, Ruby, Java, and PHP.
- [Mezmo Architecture Overview](https://docs.mezmo.com/docs/concepts.md): Understand Mezmo's microservice architecture, including ingestion services like Buzzsaw and the retrieval services that power the Web App and API.
- [Create a Graph](https://docs.mezmo.com/docs/create-a-graph.md): Build a graph in the Mezmo Web App to aggregate metrics about your log data over time, such as counts of HTTP response codes.
- [Create a Parsing Template](https://docs.mezmo.com/docs/create-a-parsing-template.md): Parse ingested log lines into fields using extractors, delimiters, trim, concatenate, and convert operations, then validate and activate the template.
- [Create and Edit Views](https://docs.mezmo.com/docs/create-and-edit-views.md): Save filters and search queries as reusable Views, organize them by category, and attach alerts to monitor specific log conditions.
- [Create Index Rate Alerts](https://docs.mezmo.com/docs/create-index-rate-alerts.md): Set max lines/s and z-score thresholds to alert via Slack, email, webhook, or PagerDuty when your log index rate grows unexpectedly.
- [Restore Log Data](https://docs.mezmo.com/docs/data-restoration.md): Re-ingest archived logs from AWS S3 or Google Cloud Storage cold storage so you can search and filter older log data in the Mezmo UI.
- [Datadog Alert Integration](https://docs.mezmo.com/docs/datadog-alert-integration.md): Send Mezmo alerts to Datadog using the Datadog Metrics API by providing your API key and match and time-span criteria.
- [Docker](https://docs.mezmo.com/docs/docker.md): Send logs from Docker, Docker Cloud, ECS, and other Docker-based platforms to Mezmo using the Logspout-based Mezmo Docker container.
- [Edit Parsing Operations with the Mini-Map](https://docs.mezmo.com/docs/edit-parsing-operations-with-the-mini-map.md): Use the mini map's rule paths and nodes to navigate, inspect, and jump between operations in a Custom Parsing Template or Extract Fields.
- [AWS Elastic Beanstalk](https://docs.mezmo.com/docs/elastic-beanstalk.md): Configure the Mezmo agent on AWS Elastic Beanstalk by adding a .config file to your app's .ebextensions directory with your ingestion key.
- [Email Alert Integration](https://docs.mezmo.com/docs/email-alert-integration.md): Trigger presence and absence alerts from log lines and send emails to multiple recipients in your preferred timezone.
- [Enterprise SAML SSO](https://docs.mezmo.com/docs/enterprise-saml-sso.md): Set up SAML single sign-on for your Mezmo Enterprise organization through manual configuration or service provider metadata.
- [Exclude Log Data](https://docs.mezmo.com/docs/excluding-log-lines.md): Use Exclusion Rules to filter out unneeded log data by source, app, or query to manage storage costs and reduce usage.
- [Set Exclusion Rules](https://docs.mezmo.com/docs/exclusion-rules.md): Control which logs are stored by building exclusion rules from hosts, apps, and queries, using one or all three together.
- [Export Log Lines](https://docs.mezmo.com/docs/export-lines.md): Export a local copy of your log lines in JSON line format, delivered as a download link to your Mezmo user email address.
- [Export Logs to External Archive Storage](https://docs.mezmo.com/docs/export-logs-to-external-storage.md): Configure log archiving to external providers such as AWS S3, Azure Blob, Google Cloud Storage, IBM Cloud, Digital Ocean Spaces, and OpenStack Swift.
- [Extract Fields](https://docs.mezmo.com/docs/extract-fields.md): Parse additional fields from historical logs without re-ingesting them, using extractors, queries, and time ranges, then export results as CSV.
- [Feature Access Matrix](https://docs.mezmo.com/docs/feature-access-matrix.md): Reference table mapping Mezmo features to the Read, Member, Admin, and Owner roles that can access each one.
- [Fluent Bit](https://docs.mezmo.com/docs/fluentbit.md): Set up log ingestion to Mezmo using the Fluent Bit Mezmo output plugin and your Mezmo ingestion key.
- [Fluentd](https://docs.mezmo.com/docs/fluentd.md): Send Fluentd logs to Mezmo using the Mezmo plugin, set up ingestion in the Web App, and configure tailing in td-agent.conf.
- [Flynn](https://docs.mezmo.com/docs/flynn.md): Set up Flynn log ingestion to Mezmo by following the Web App instructions using your Mezmo ingestion key.
- [Format Log Lines with Custom Line Templates](https://docs.mezmo.com/docs/format-log-lines-with--custom-line-templates.md): Use custom %LINE templates to reformat log viewer output, display reserved fields, reference the original line, and return data as JSON.
- [GDPR Compliance](https://docs.mezmo.com/docs/gdpr-compliance.md): Understand GDPR obligations for logging and best practices for staying compliant with Mezmo, including data minimization, pseudonymization, and retention.
- [GitHub Events](https://docs.mezmo.com/docs/github-events.md): Connect the Mezmo GitHub integration to collect repository events, choose which event types to monitor, and filter them in the Web App.
- [Heroku Logs](https://docs.mezmo.com/docs/heroku.md): Ingest Heroku logs into Mezmo using the Heroku add-on or log drains, with notes on user roles, multi-app plans, and Private Space logging.
- [Heroku Template](https://docs.mezmo.com/docs/heroku-template.md): Explore the prebuilt Heroku Template of Views, Boards, and Screens for tracking app crashes, HTTP errors, response times, and security trends.
- [HIPAA Compliance](https://docs.mezmo.com/docs/hipaa-compliance.md): Understand your logging obligations under HIPAA and HITECH and how Mezmo helps you meet them with encryption, RBAC, retention, and monitoring.
- [Troubleshooting With Graphs and Log Data](https://docs.mezmo.com/docs/how-to-graph-logs-visualize-data-with-mezmo.md): Walk through real scenarios for using graphs and histograms to detect errors, spot unusual log volume, and analyze performance changes.
- [Import and Export Organizations](https://docs.mezmo.com/docs/import-and-export-organizations.md): Export an organization's views, boards, alerts, exclusion rules, and parsing templates as JSON and import them into another organization.
- [Index Rate Alerts Metrics](https://docs.mezmo.com/docs/index-rate-alerts-metrics.md): Learn how Mezmo calculates index rate, ingest rate, lines/s, z-score, and standard deviation to set thresholds for Index Rate Alerts.
- [Index Rate Alerts Overview](https://docs.mezmo.com/docs/index-rate-alerts-overview.md): Use Index Rate Alerts to track index and ingestion rates, spot volume spikes by source, and monitor anomalous flow with the alerts dashboard.
- [Mezmo Log Ingestion Methods](https://docs.mezmo.com/docs/ingestion.md): Compare ways to send logs to Mezmo, including the Mezmo Agent, client-side logger, platform integrations, code libraries, and the REST API.
- [Mezmo Log Ingestion Integrations](https://docs.mezmo.com/docs/ingestion-integrations.md): Browse the log ingestion integrations Mezmo develops and maintains for popular platforms.
- [Generate Service and Ingestion Keys](https://docs.mezmo.com/docs/ingestion-key.md): Create and manage Mezmo ingestion keys and IAM access keys (personal, service, and enterprise), with security best practices for handling tokens.
- [Mezmo Logging Agent](https://docs.mezmo.com/docs/introducing-the-agent.md): Learn how the Rust-based Mezmo Agent reads and uploads log files over HTTPS, plus configuration, host tags, hostnames, and release notes.
- [View Kubernetes Events and Metrics](https://docs.mezmo.com/docs/kubernetes-enrichment.md): Use Kubernetes Enrichment to view cluster events, pod and node metrics, and logs in the Log Viewer, and tag lines to distinguish clusters.
- [LaunchDarkly](https://docs.mezmo.com/docs/launchdarkly.md): Send and aggregate LaunchDarkly audit log events in Mezmo by configuring the integration with your Mezmo ingestion key.
- [Log Ingestion Delays](https://docs.mezmo.com/docs/log-ingestion-delays.md): Understand the two types of ingestion delays in Mezmo, Live Tail latency and indexing latency, and the typical timing for each.
- [Automatically Parsed Log Line Components](https://docs.mezmo.com/docs/log-parsing.md): Learn how Mezmo automatically parses log lines into string, source, application, JSON, and metadata components for search and analysis.
- [Manage Access](https://docs.mezmo.com/docs/manage-access.md): Manage users, permissions, discoverability, sign-in policies, two-factor authentication, and password rules for your Mezmo organization.
- [Manage Enterprise Organizations](https://docs.mezmo.com/docs/manage-enterprise-organizations.md): Use Enterprise Organization features to centrally manage access control, usage, and quotas across multiple Mezmo organizations from one dashboard.
- [Manage Groups](https://docs.mezmo.com/docs/manage-groups.md): Create, edit, and delete groups that restrict which logs members can access using search queries in your Mezmo organization.
- [Manage Members](https://docs.mezmo.com/docs/manage-members.md): Invite, edit, and remove members, assign roles and groups, and handle join requests for your Mezmo organization's team.
- [Manage Usage](https://docs.mezmo.com/docs/manage-usage.md): Explore tools to reduce and monitor log data usage, including the Usage Dashboard, trends, restoration, email digests, and usage alerts.
- [Manage Usage Quotas](https://docs.mezmo.com/docs/manage-usage-quotas.md): Set daily and monthly quotas to stop log storage, reduce volume with triggered exclusion rules, or alert when usage thresholds are reached.
- [Mezmo Agent Configuration for Kubernetes](https://docs.mezmo.com/docs/mezmo-agent-configuration-for-kubernetes.md): Configure the Mezmo Logging Agent in a Kubernetes cluster by editing the DaemonSet environment variables and applying a custom config file.
- [Mezmo Agent Supported Platforms](https://docs.mezmo.com/docs/mezmo-agent-support-matrix.md): Review the operating systems, architectures, and platform versions supported by the Mezmo Agent, including End of Life (EOL) policies.
- [Mezmo MCP](https://docs.mezmo.com/docs/mezmo-mcp.md): Connect AI assistants and IDE chat agents to Mezmo's remote MCP server for root-cause analysis, log queries, and pipeline management.
- [Welcome to Mezmo](https://docs.mezmo.com/docs/mezmo-quick-start-guide.md): Get started with Mezmo by creating an organization, adding log sources, parsing and searching logs, building views, alerts, boards, and archiving.
- [Mezmo Service Endpoints](https://docs.mezmo.com/docs/mezmo-service-endpoints.md): Reference the inbound and outbound IP addresses for Mezmo services to configure IP-based firewall rules and allowlists.
- [NGINX Ingress Controller Template](https://docs.mezmo.com/docs/nginx-ingress-controller-template.md): Use Mezmo's pre-built Views, Boards, and Screens plus a recommended log format to gain observability into NGINX Ingress Controller logs.
- [NXLog](https://docs.mezmo.com/docs/nxlog-for-windows.md): Configure NXLog on Windows to ingest Windows event and file logs into Mezmo using your syslog port and security certificate.
- [Okta SAML Setup](https://docs.mezmo.com/docs/okta-saml-setup.md): Configure Okta as a SAML identity provider for Mezmo single sign-on, including JIT provisioning and SSO enforcement behavior.
- [OneLogin SAML Setup](https://docs.mezmo.com/docs/onelogin-saml-setup.md): Configure OneLogin as a SAML identity provider for Mezmo single sign-on using a custom connector and downloaded SAML metadata.
- [OpenTelemetry Exporter](https://docs.mezmo.com/docs/opentelemetry-exporter.md): Send log data to Mezmo by adding the Mezmo exporter to an OpenTelemetry Collector pipeline, with a quick start config example.
- [OpsGenie Alert Integration](https://docs.mezmo.com/docs/opsgenie-alert-integration.md): Create OpsGenie alerts from Mezmo log data by configuring test, presence, and absence alerts with an OpsGenie API integration key.
- [Organization Management Overview](https://docs.mezmo.com/docs/organization-management-overview.md): Create, delete, join, switch, and manage Mezmo organizations, including ownership, default organization, and API key settings.
- [Organize Visualizations by Category](https://docs.mezmo.com/docs/organize-visualizations-by-category.md): Group Boards, Views, and Screens into Categories to organize your Mezmo visualizations and manage them under Settings.
- [PagerDuty Alert Integration](https://docs.mezmo.com/docs/pagerduty-alert-integration.md): Connect Mezmo alerts to PagerDuty so log-based alerts trigger incidents, including how to test, delete, and the 400 KB payload limit.
- [PagerDuty Auto-resolve Settings](https://docs.mezmo.com/docs/pagerduty-auto-resolve.md): Configure Mezmo to automatically resolve PagerDuty incidents based on log line volume within a specified time frame for an alert.
- [Parse Logs with Custom Templates](https://docs.mezmo.com/docs/parse-logs-with-custom-templates.md): Create custom parsing rules and templates to parse log formats Mezmo doesn't auto-parse, and manage template order and status.
- [Parsing Operators](https://docs.mezmo.com/docs/parsing-operators.md): Reference for the parsing operators used to extract, transform, and capture values when building custom parsing rules in Mezmo.
- [PCI Compliance](https://docs.mezmo.com/docs/pci-compliance.md): Understand how PCI DSS Requirements 3, 10, and 12 apply to your logging strategy and how Mezmo helps meet them as a PCI Level 1 Service Provider.
- [Role-Based Access Control](https://docs.mezmo.com/docs/rbac.md): Learn how Mezmo roles and groups control member privileges and restrict access to log data, and when to use each.
- [Read Archived Logs](https://docs.mezmo.com/docs/read-archived-logs.md): Re-ingest and parse archived JSON log files using Mezmo Data Restoration, Amazon Athena, Google BigQuery, IBM SQL Query, or jq.
- [Rsyslog](https://docs.mezmo.com/docs/rsyslog.md): Stream Rsyslog logs to Mezmo over TCP+TLS, TCP, or UDP, and configure host tags using the Mezmo Private Enterprise Number.
- [SaltStack](https://docs.mezmo.com/docs/saltstack.md): Set up the Mezmo Salt deployment integration to listen for Salt state events and send the event information to Mezmo.
- [Search and Filter Log Data](https://docs.mezmo.com/docs/search-and-filter.md): Learn how search terms and operators work in the Log Viewer, plus tips for resolving empty results, unexpected matches, and query warnings.
- [Search Log Fields](https://docs.mezmo.com/docs/search-json-fields.md): Search parsed and nested log fields using value, comparison, existence, term-match, and case-sensitive operators, plus metadata and line-size searches.
- [Search Tips](https://docs.mezmo.com/docs/search-tips.md): Troubleshoot vague queries, unexpected matches, symbol warnings, and case-sensitivity issues, and interpret Mezmo's search syntax feedback.
- [Search Log Contents](https://docs.mezmo.com/docs/searching-log-contents.md): Use terms, phrases, and AND/OR/NOT operators with grouping and precedence to search log contents, plus Time Search and special-character handling.
- [Server Analytics Screen](https://docs.mezmo.com/docs/server-analytics-screen.md): Build a Screen with Time Shifted Graph and Table widgets to monitor bytes sent to the server and the top response codes.
- [Server Security Screen](https://docs.mezmo.com/docs/server-security-screen.md): Build a Screen with widgets to track 401/403 errors and identify the top IP addresses generating forbidden requests.
- [Slack Alert Integration](https://docs.mezmo.com/docs/slack-alert-integration.md): Connect Mezmo log alerts to your Slack workspace, configure presence and absence alerting, and remove the integration.
- [SOC 2 Compliance](https://docs.mezmo.com/docs/soc-2-compliance.md): Understand the SOC 2 Trust Services Criteria and how Mezmo logging helps you meet and maintain SOC 2 compliance.
- [Enable Raw Line Storage](https://docs.mezmo.com/docs/store-and-show-raw-lines.md): Turn on storing and viewing raw, unparsed log lines for your account and understand the potential storage cost impact.
- [Sysdig Alert Integration](https://docs.mezmo.com/docs/sysdig-alert-integration.md): Configure Mezmo presence alerts that trigger events in your Sysdig Monitor instance using an API key and instance URL.
- [Syslog](https://docs.mezmo.com/docs/syslog.md): Set up Syslog log ingestion to Mezmo over TCP and UDP on a provisioned port, with RFC 5424 and RFC 3164 auto parsing.
- [Syslog-ng](https://docs.mezmo.com/docs/syslog-ng.md): Stream logs to Mezmo with syslog-ng over TCP+TLS, TCP, or UDP, including host tags and ready-to-use configuration examples.
- [Set Up System Cross-Domain Identity Management (SCIM)](https://docs.mezmo.com/docs/system-cross-domain-identity-management.md): Automate user and group provisioning in Mezmo from identity providers like Okta and Microsoft Entra ID using SCIM 2.0.
- [Terraform Provider for Mezmo](https://docs.mezmo.com/docs/terraform-provider.md): Manage Mezmo Views and Alerts as code with the Terraform provider, including setup, use cases, and an example HCL configuration.
- [The Enterprise Dashboard](https://docs.mezmo.com/docs/the-usage-dashboard.md): Review your organization's data usage with retained, restored, and ingested vs. retained graphs plus top app, source, and tag trends.
- [Create Usage Alerts](https://docs.mezmo.com/docs/usage-alerts.md): Set a usage limit and notify organization members when data usage exceeds your threshold before the end of the usage cycle.
- [Use the AI Assistant](https://docs.mezmo.com/docs/use-ai-assistant.md): Analyze logs and telemetry in natural language with the Mezmo AI Assistant using prompts, time expressions, context mentions, and slash commands.
- [Use Screens and Widgets to Monitor Log Data](https://docs.mezmo.com/docs/use-screens-and-widgets-to-monitor-log-data.md): Learn how Screens and the four widget types (Count, Gauge, Table, Time Shifted Graph) present log metrics for monitoring and analysis.
- [Templates for Views, Boards, and Screens](https://docs.mezmo.com/docs/using-templates.md): Browse, import, edit, and remove Mezmo's prebuilt templates to quickly add Views, Boards, and Screens for common queries.
- [Set Variable Retention](https://docs.mezmo.com/docs/variable-retention.md): Create rules that apply custom retention periods to specific log lines and track their impact in the Usage Dashboard and email digests.
- [Vector](https://docs.mezmo.com/docs/vector.md): Ingest observability data into Mezmo from Vector pipelines by installing Vector and configuring the Mezmo output sink.
- [Vercel](https://docs.mezmo.com/docs/vercel.md): Stream Vercel logs to Mezmo using the Vercel integration by locating or provisioning a syslog port in the Mezmo Web App.
- [VictorOps Alert Integration](https://docs.mezmo.com/docs/victorops-alert-integration.md): Trigger VictorOps incidents from Mezmo log alerts by configuring the URL to notify and routing key for the integration.
- [View Log Data](https://docs.mezmo.com/docs/view-log-data.md): Explore the Log Viewer to see your logs, apply Views, filter by tags, sources, apps, and levels, search, and use the timeline.
- [View Log Data by Timeline](https://docs.mezmo.com/docs/view-log-data-by-timeline.md): Use the Mezmo Timeline to spot trends, change time scales, scope into time frames, and jump to specific points in your logs.
- [Visualize Log Data with Graphs](https://docs.mezmo.com/docs/visualize-log-data-with-graphs.md): Use Boards and Graphs to chart log metrics over time with operations, plots, filters, and breakdowns like histograms and pie charts.
- [Web Analytics Screen](https://docs.mezmo.com/docs/web-analytics-screen.md): Build a Screen with widgets to track week-over-week traffic and your most popular pages from web server logs.
- [Web Server Template](https://docs.mezmo.com/docs/web-server-template.md): Get pre-configured Views, Boards, and Screens for HTTP web servers to monitor response codes, errors, traffic, and security.
- [Webhook Alert Integration](https://docs.mezmo.com/docs/webhook-alert-integration.md): Send Mezmo alerts to third-party services with a custom webhook, configuring method, URL, headers, body, and tokens, using Jira as an example.
- [Widget Use Cases](https://docs.mezmo.com/docs/widget-use-cases.md): Step-by-step examples of using Count, Time Shifted Graph, and Table widgets to monitor log counts, errors, apps, and authentication attempts.
- [Windows Security Template](https://docs.mezmo.com/docs/windows-security-template.md): Gain visibility into Windows security events with prebuilt Views, Boards, and Screens, plus the required NXLog configuration.
- [1 - Introduction](https://docs.mezmo.com/guide-to-pipeline-architecture/1--introduction.md): Workshop overview and prerequisites for optimizing OpenTelemetry logs, metrics, and traces with Mezmo Pipelines.
- [2 - Create Shared Sources](https://docs.mezmo.com/guide-to-pipeline-architecture/2---shared-sources.md): Create OpenTelemetry log, metric, and trace shared sources in Mezmo for use in later pipeline steps.
- [4 - Analyze the Source Data](https://docs.mezmo.com/guide-to-pipeline-architecture/3---configure-and-build-the-demo.md): Build a Log Explorer pipeline with a Script Execution and Data Profiler processor to analyze your OTel source data.
- [3 - Build the OTel Demo Source](https://docs.mezmo.com/guide-to-pipeline-architecture/4---profile-log-data.md): Clone the OpenTelemetry Demo, configure it with your Mezmo shared source credentials, and build it locally.
- [5 - Create an OTel Log Handler Pipeline](https://docs.mezmo.com/guide-to-pipeline-architecture/5---optimize-logs.md): Build a responsive log pipeline that parses custom Apache logs, reduces flood events, and routes data by operational state to Log Analysis.
- [6 - Create an OpenTelemetry Metric Handler Pipeline](https://docs.mezmo.com/guide-to-pipeline-architecture/6---optimize-metrics.md): Build a responsive metric pipeline that aggregates metrics and limits tag cardinality, routing data by operational state.
- [7 - Create an OTel Trace Handle Pipeline](https://docs.mezmo.com/guide-to-pipeline-architecture/7---optimize-traces.md): Build a pipeline that samples OpenTelemetry traces during normal operation and routes data by operational state.
- [8 - Test the Responsive Pipelines](https://docs.mezmo.com/guide-to-pipeline-architecture/8---optimize-responsibly.md): Use the switch-state script to toggle pipeline states and observe how responsive pipelines adjust fidelity during incidents.
- [Basic Configuration of a Pipeline with In-Stream Alerts](https://docs.mezmo.com/guide-to-pipeline-architecture/basic-configuration-of-a-pipeline-with-in-stream-alerts.md): Walk through a pipeline that uses in-stream alerts to flag change conditions on individual components before data is indexed.
- [Basic Data Optimization Pipeline](https://docs.mezmo.com/guide-to-pipeline-architecture/basic-data-optimization-pipeline.md): Explore the Demo Pipeline's Route, Filter, and Encrypt processors for handling transaction errors and encrypting credit card data.
- [Basic Data Rehydration Pipeline](https://docs.mezmo.com/guide-to-pipeline-architecture/basic-data-rehydration-pipeline.md): Build pipelines to archive telemetry data to S3 and restore it to Mezmo Log Analysis using a restoration task.
- [Basic Log Analysis Pipeline](https://docs.mezmo.com/guide-to-pipeline-architecture/basic-log-analysis-pipeline.md): Configure and use the Mezmo Log Analysis Destination with a Demo Logs Source to stream telemetry data into the Log Analysis viewer.
- [Build a Basic Data Rehydration Pipeline](https://docs.mezmo.com/guide-to-pipeline-architecture/build-a-basic-data-rehydration-pipeline.md): Archive telemetry data to an S3 bucket and restore it to Mezmo Log Analysis using the Archive Destination, Pipeline Data Restoration Source, and a restoration task.
- [Convert Events to Metrics](https://docs.mezmo.com/guide-to-pipeline-architecture/convert-events-to-metrics.md): Reduce log volume by routing routine 200 events through Event to Metric and Aggregate Processors, with example Processor configurations.
- [Kafka Data Optimization Pipeline](https://docs.mezmo.com/guide-to-pipeline-architecture/kafka-data-optimization-pipeline.md): Parse, route, and convert Kafka logs to metrics so routine events are summarized while errors and warnings reach storage at full fidelity.
- [Kubernetes Data Optimization Pipeline](https://docs.mezmo.com/guide-to-pipeline-architecture/kubernetes-data-optimization-pipeline.md): Transform Kubernetes telemetry into metrics with Filter, Route, Event to Metric, and Aggregate Processors while retaining original data in storage.
- [Mezmo Log Analysis Source Pipeline](https://docs.mezmo.com/guide-to-pipeline-architecture/log-analysis-source-pipeline.md): Overview of the four-step Pipeline that Mezmo Log Analysis customers use to optimize log data, including each Processor and its configuration.
- [Mask and Encrypt Data](https://docs.mezmo.com/guide-to-pipeline-architecture/mask-and-encrypt-data.md): Build a data compliance processor group that routes events through Redact and Encrypt Field Processors to obfuscate PII such as user IDs and credit card numbers.
- [Responsive OTel Pipeline Workshop](https://docs.mezmo.com/guide-to-pipeline-architecture/responsive-otel-pipeline-tutorial.md): Hands-on workshop for building responsive OpenTelemetry pipelines that route full-fidelity data during incidents and optimize for cost during normal operations.
- [Route Data](https://docs.mezmo.com/guide-to-pipeline-architecture/route-data.md): Use a Route Processor with conditional statements to direct financial, JSON, and Apache data from multiple sources through specialized processing chains to different destinations.
- [Types of Telemetry Data Pipelines](https://docs.mezmo.com/guide-to-pipeline-architecture/types-of-telemetry-data-pipelines.md): Compare Mezmo pipeline patterns for ingestion, optimization, archiving and rehydration, and responsive processing, with example pipelines for each.
- [Understanding Your Data to Optimize It](https://docs.mezmo.com/guide-to-pipeline-architecture/understanding-your-data-to-optimize-it.md): Use the Mezmo Data Profiler to analyze streaming telemetry through Message Templates, Field Summaries, and Log Metrics before deciding how to optimize it.
- [Welcome](https://docs.mezmo.com/index.md): Build, optimize, and act on telemetry data with Mezmo.
- [HTTP Source for Mezmo Edge](https://docs.mezmo.com/mezmo-edge/http-source-for-mezmo-edge.md): Configure any source to send data to a Mezmo Edge Pipeline via a RESTful POST over an allocated HTTP port.
- [Mezmo Edge Deployment Planning](https://docs.mezmo.com/mezmo-edge/mezmo-edge-deployment-planning.md): Sizing, scaling, durability, and performance guidance for planning a Mezmo Edge telemetry pipeline deployment in your own environment.
- [Mezmo Edge Pipelines for Local Data](https://docs.mezmo.com/mezmo-edge/mezmo-edge-pipelines-for-local-data.md): Run telemetry pipelines locally with Mezmo Edge to access local sources, process data within your network, and use Rust-based regex.
- [Set Up Mezmo Edge in a Docker Container](https://docs.mezmo.com/mezmo-edge/set-up-mezmo-edge-in-a-docker-container.md): Run a single Mezmo Edge instance as a Docker container using Docker Compose, including the compose and processor config files.
- [Set Up Mezmo Edge in Kubernetes](https://docs.mezmo.com/mezmo-edge/set-up-mezmo-edge-in-kubernetes.md): Install Mezmo Edge in a Kubernetes cluster with the Mezmo Helm chart, then create, deploy, and monitor an Edge Pipeline.
- [Syslog Source for Mezmo Edge](https://docs.mezmo.com/mezmo-edge/syslog-source-for-mezmo-edge.md): Send syslog events to a Mezmo Edge Pipeline through a specified port using the Syslog over HTTP source within your own network.
- [Tap and View Mezmo Edge Pipeline Data on Premises](https://docs.mezmo.com/mezmo-edge/tap-and-view-mezmo-edge-pipeline-data-on-premises.md): Inspect data flowing through a local Mezmo Edge Pipeline using the vector tap CLI or GraphQL, without sending data to the Mezmo Web App.
- [Getting Started with the Mezmo Pipeline API](https://docs.mezmo.com/pipeline-api-quickstart/getting-started-with-the-mezmo-pipeline-api.md): Walk through curl examples to create a pipeline, add an HTTP source and access key, attach a transform and S3 destination, then publish.
- [Analysis of Telemetry Data Optimization Techniques](https://docs.mezmo.com/practioner-guide-data-optimization/analysis-data-reduction-techniques.md): Summary results and findings from testing data reduction techniques on Priority 1 sources, showing 50%+ volume cuts without quality loss.
- [Introduction: Telemetry Data Optimization with Mezmo Pipelines](https://docs.mezmo.com/practioner-guide-data-optimization/data-optimization-introduction.md): How Mezmo helps SREs understand, optimize, and reduce overwhelming telemetry volume, with an overview of what this practitioner's guide covers.
- [Demo Pipeline Overview](https://docs.mezmo.com/practioner-guide-data-optimization/demo-pipeline-guide8ke.md): Tour the trial Demo Pipeline's sources, Route and Filter processors, and Encrypt Field processor for handling credit card transaction data.
- [Optimize Your Observability Data in Six Steps](https://docs.mezmo.com/practioner-guide-data-optimization/optimize-your-observability-data-in-six-steps.md): A platform-agnostic approach to cutting log volume by 50%+ via archiving, filtering, parsing, merging, metric conversion, and responsive pipelines.
- [Pipeline Example: Kafka Telemetry Data Optimization](https://docs.mezmo.com/practioner-guide-data-optimization/pipeline-architecture-for-data-reduction.md): An example pipeline that parses, routes, reduces, and converts Kafka logs to metrics while preserving errors and warnings at full fidelity.
- [Pipeline Example: Kubernetes Telemetry Data Optimization](https://docs.mezmo.com/practioner-guide-data-optimization/pipeline-architecture-for-kubernetes-data-optimization.md): An example pipeline that filters, converts to metrics, aggregates, and routes Kubernetes container logs while archiving originals for compliance.
- [Tutorial: Convert Events to Metrics](https://docs.mezmo.com/practioner-guide-data-optimization/pipeline-example--convert-200-events-to-metrics.md): Build a pipeline that routes Status 200 events through Event to Metric and Aggregate processors to reduce volume while keeping trend data.
- [Tutorial: Route Data](https://docs.mezmo.com/practioner-guide-data-optimization/pipeline-module--route.md): Build a routing group that uses a Route Processor and conditional statements to send financial, JSON, and Apache data down separate processing chains.
- [Tutorial: Mask and Encrypt Data](https://docs.mezmo.com/practioner-guide-data-optimization/pipeline-module--security-and-compliance.md): Build a compliance processor group that routes events to Encrypt Field and Redact processors to protect PII like card numbers and user IDs.
- [Pipeline Examples and Tutorials](https://docs.mezmo.com/practioner-guide-data-optimization/reference-architectures-for-data-optimization-pipelines.md): Index of example Mezmo Telemetry Pipelines and data optimization tutorials, including processor configuration settings.
- [About Mezmo Flow](https://docs.mezmo.com/telemetry-pipelines/about-mezmo-flow.md): Learn how Mezmo Flow profiles your telemetry data and recommends Processors to build a volume-reducing Pipeline in four steps.
- [About Mezmo Telemetry Pipelines](https://docs.mezmo.com/telemetry-pipelines/about-mezmo-telemetry-pipelines.md): Overview of how Mezmo Telemetry Pipelines ingest, process, route, and monitor telemetry data across diverse sources and destinations.
- [About Mezmo Trial Accounts](https://docs.mezmo.com/telemetry-pipelines/about-mezmo-trial.md): What the free 30-day Mezmo trial includes, how to select a plan when it ends, and where to start building your first Pipeline.
- [Aggregate Processor](https://docs.mezmo.com/telemetry-pipelines/aggregate-processor.md): Aggregate metric and log fields over tumbling or sliding windows and trigger threshold or change alerts when conditions are met.
- [Alert Message](https://docs.mezmo.com/telemetry-pipelines/alert-message-destination.md): Send Pipeline-triggered alerts to Slack, PagerDuty, or a Webhook based on event thresholds over a configurable time window.
- [API References](https://docs.mezmo.com/telemetry-pipelines/api-references.md): Links to the Mezmo Log Analysis and Telemetry Pipelines API documentation.
- [Archive and Restore Telemetry Data](https://docs.mezmo.com/telemetry-pipelines/archive-restore-data.md): Use the Mezmo Archive Destination and Pipeline Data Restoration Source to store events in S3 or Azure and restore them later.
- [Tutorial: Create a Basic Data Archiving and Restoration Pipeline](https://docs.mezmo.com/telemetry-pipelines/archive-restore-data-tutorial.md): Step-by-step guide to build archive and restoration Pipelines using an S3 bucket, demo logs, and the Mezmo Log Analysis Destination.
- [AWS CloudWatch Logs](https://docs.mezmo.com/telemetry-pipelines/aws-cloudwatch-logs.md): Use a Lambda function with an HTTP Source to bring AWS CloudWatch logs into your Mezmo Pipeline.
- [Azure Blob Storage](https://docs.mezmo.com/telemetry-pipelines/azure-blob-storage-destination.md): Send Mezmo Pipeline log data to an Azure Blob Storage container with configurable batching, encoding, compression, and prefixes.
- [Azure Event Hub](https://docs.mezmo.com/telemetry-pipelines/azure-event-hub-source.md): Ingest data from an Azure Event Hub into Mezmo Pipelines via the Kafka interface, including prerequisites and configuration options.
- [Blackhole](https://docs.mezmo.com/telemetry-pipelines/blackhole-destination.md): A Destination that drops all data sent to it, useful for testing Pipeline data processing in a simulation without billable egress.
- [Build and Deploy a Mezmo Telemetry Pipeline](https://docs.mezmo.com/telemetry-pipelines/build-deploy-mezmo-pipeline.md): Step-by-step instructions to build a Pipeline from Sources, Destinations, and Processors in the Mezmo Web App, then deploy and view it.
- [Build a Mezmo Telemetry Pipeline with Terraform](https://docs.mezmo.com/telemetry-pipelines/build-pipelines-terraform.md): Use the Mezmo Terraform provider to define, version, and manage your telemetry data Pipelines as infrastructure-as-code.
- [Checkly](https://docs.mezmo.com/telemetry-pipelines/checkly.md): Ingest Checkly OTLP data into your Pipeline using the OpenTelemetry Traces Source with a URL endpoint and authorization token.
- [Checkly](https://docs.mezmo.com/telemetry-pipelines/checkly-destination.md): Send Checkly-related spans to Checkly via the OpenTelemetry Destination, using a Route Processor to filter the correct traces.
- [AWS CloudWatch Logs](https://docs.mezmo.com/telemetry-pipelines/cloudwatch-logs-destination.md): Send Pipeline logs to AWS CloudWatch for monitoring, with options for credentials, encoding, compression, log group, and stream.
- [AWS CloudWatch Metrics](https://docs.mezmo.com/telemetry-pipelines/cloudwatch-metrics-destination.md): Send Pipeline metrics to AWS CloudWatch for monitoring, with configuration for credentials, compression, namespace, and region.
- [Compact Fields Processor](https://docs.mezmo.com/telemetry-pipelines/compact-fields-processor.md): Recursively remove empty arrays and objects from a specified field to clean up null values and empty spaces in messages.
- [Configure Responsive Pipelines](https://docs.mezmo.com/telemetry-pipelines/configure-responsive-pipelines.md): Pre-configure Pipelines to switch between normal and incident states automatically, balancing high-fidelity data with cost reduction.
- [Set Surge Detection Alerts](https://docs.mezmo.com/telemetry-pipelines/configure-surge-detection-alerts.md): Configure Surge Detection alerts in the Data Profiler Processor to be notified of significant data volume spikes by app, host, level, or label.
- [Create Processor Groups](https://docs.mezmo.com/telemetry-pipelines/create-processor-groups.md): Bundle related Processors into a reusable, shareable group to simplify your Pipeline Map and manage their configuration together.
- [Data Profiler Processor](https://docs.mezmo.com/telemetry-pipelines/data-profiler-processor.md): Analyze Source data to surface the most common message patterns and the apps and hosts driving log volume, with field mapping options.
- [Create a Data Profile](https://docs.mezmo.com/telemetry-pipelines/data-profiling.md): Use the Data Profiler to get a granular view of your log data through Message Templates, Field Summaries, and Log Metrics reports.
- [Datadog Agent V2](https://docs.mezmo.com/telemetry-pipelines/datadog-agent-v2-source.md): Receive logs, metrics, and traces from a Datadog Agent on separate output ports so each telemetry type can be routed independently.
- [Datadog Logs](https://docs.mezmo.com/telemetry-pipelines/datadog-logs-destination.md): Send Pipeline log data to Datadog, configuring the API key, compression, and Datadog site region.
- [Datadog Metrics](https://docs.mezmo.com/telemetry-pipelines/datadog-metrics-destination.md): Send metrics data to Datadog as Custom Metrics, supported with Datadog Agent, HTTP, and Prometheus Remote Write sources.
- [Datadog Traces](https://docs.mezmo.com/telemetry-pipelines/datadog-traces-destination.md): Send Pipeline trace data to Datadog, configuring the API key, compression, and Datadog site region.
- [Decrypt Field Processor](https://docs.mezmo.com/telemetry-pipelines/decrypt-fields-processor.md): Decrypt an encrypted string field using a secret key and initialization vector, reversing the Encrypt Field Processor.
- [Dedupe Processor](https://docs.mezmo.com/telemetry-pipelines/dedupe-processor.md): Remove duplicate log records across a set of events using Match or Ignore comparison on specified fields to reduce log chatter.
- [Demo Logs](https://docs.mezmo.com/telemetry-pipelines/demo-logs-source.md): Ready-to-use demo log sources in formats like NGINX, Apache, syslog, JSON, and metrics for building and testing your Pipelines.
- [Demo Pipeline Overview](https://docs.mezmo.com/telemetry-pipelines/demo-pipeline-guide.md): Walk-through of the auto-created Demo Pipeline showing Route, Filter, and Encrypt Processors handling JSON and financial data.
- [Remove Fields Processor](https://docs.mezmo.com/telemetry-pipelines/drop-fields-processor.md): Drop specified JSON fields from each record in the data stream before sending it to storage or other processors.
- [Edit or Delete a Pipeline](https://docs.mezmo.com/telemetry-pipelines/edit-a-pipeline.md): Edit Pipeline components and names, compare and roll back revisions, and delete Pipelines through the Mezmo Web App.
- [ElasticSearch](https://docs.mezmo.com/telemetry-pipelines/elasticsearch-destination.md): Send indexed log data to an ElasticSearch destination, with options for authentication strategy, compression, endpoints, and indices.
- [Encrypt Field Processor](https://docs.mezmo.com/telemetry-pipelines/encrypt-fields-processor.md): Apply an encryption algorithm and key to a specified field to protect sensitive log data before sending it to storage.
- [Error Code Reference](https://docs.mezmo.com/telemetry-pipelines/error-code-reference.md): Reference of processor, source, and general error codes and their messages for the Mezmo Telemetry Pipeline.
- [Event to Metric Processor](https://docs.mezmo.com/telemetry-pipelines/event-to-metric-processor.md): Create a counter, sum, or gauge metric event from a log message, drawing the metric values from event fields or static values.
- [Example In-Stream Alert Configurations](https://docs.mezmo.com/telemetry-pipelines/example-in-stream-alert-configurations.md): Example configurations for setting up in-stream telemetry data alerts in Mezmo Pipelines.
- [Filter Processor](https://docs.mezmo.com/telemetry-pipelines/filter-processor.md): Pass or drop events using conditional statements with content, string, comparison, and type operators to reduce forwarded data.
- [Flatten Fields Processor](https://docs.mezmo.com/telemetry-pipelines/flatten-fields-processor.md): Recursively collapse nested JSON objects into a single level, joining parent and child keys with a configurable delimiter.
- [FluentD and FluentBit](https://docs.mezmo.com/telemetry-pipelines/fluent-source.md): Stream FluentD and FluentBit logs and metrics to Mezmo Pipelines using HTTP output plugins for SaaS or Forward plugins for Edge.
- [Google Cloud Monitoring](https://docs.mezmo.com/telemetry-pipelines/gcp-cloud-monitoring-destination.md): Send metric events to Google Cloud Monitoring, configuring project ID, resource type and labels, and JSON service account credentials.
- [Google Cloud Operations](https://docs.mezmo.com/telemetry-pipelines/gcp-cloud-operations-destination.md): Send log events to Google Cloud Operations, configuring log ID, project ID, resource type and labels, and JSON credentials.
- [Google Cloud PubSub](https://docs.mezmo.com/telemetry-pipelines/gcp-cloud-pubsub-destination.md): Send events to Google Cloud Pub/Sub, configuring encoding, project ID, topic, and JSON service account credentials.
- [Google Cloud Storage](https://docs.mezmo.com/telemetry-pipelines/gcp-cloud-storage-destination.md): Send Mezmo Pipeline log data to a Google Cloud Storage bucket with configurable encoding, compression, batching, and credentials.
- [Getting Started with Mezmo Telemetry Pipelines](https://docs.mezmo.com/telemetry-pipelines/getting-started-with-mezmo-telemetry-pipeline.md): Learn the core concepts of Mezmo Pipelines, including sources, processors, destinations, ingress/egress usage metrics, and how to create an account.
- [Getting Started with the Mezmo Platform](https://docs.mezmo.com/telemetry-pipelines/getting-started-with-the-mezmo-platform.md): Walks you through setting up your organization, building your first telemetry pipeline, creating alerts, and using Mezmo Log Analysis search and visualization.
- [High Error Rate](https://docs.mezmo.com/telemetry-pipelines/high-error-rate.md): Example threshold alert configuration that triggers when a high number of HTTP 5xx errors per application is detected in metric events.
- [Honeycomb Logs](https://docs.mezmo.com/telemetry-pipelines/honeycomb-logs-destination.md): Send log data to a Honeycomb dataset by configuring your Honeycomb API key and target dataset name.
- [How to Convert an Existing Source into a Shared Source](https://docs.mezmo.com/telemetry-pipelines/how-to-convert-existing-source-to-shared.md): Step-by-step instructions for converting an existing pipeline source into a reusable Shared Source without rebuilding it.
- [How to Create a Shared Source from Scratch](https://docs.mezmo.com/telemetry-pipelines/how-to-create-shared-sources.md): Step-by-step instructions for configuring a new Shared Source, including key management, so it can be reused across multiple pipelines.
- [How to Use a Shared Source in a Pipeline](https://docs.mezmo.com/telemetry-pipelines/how-to-use-shared-source-in-pipeline.md): Step-by-step instructions for adding an existing Shared Source to a new pipeline so it inherits all data transmitted through it.
- [HTTP Endpoint](https://docs.mezmo.com/telemetry-pipelines/http-destination.md): Send Mezmo Pipeline log data to any HTTP endpoint, with options for encoding, compression, authentication, headers, proxies, and TLS.
- [HTTP](https://docs.mezmo.com/telemetry-pipelines/http-source.md): Send data to a Mezmo Pipeline via a RESTful POST when a native source type isn't supported, then parse it in-stream to extract fields.
- [In-Stream Alerts](https://docs.mezmo.com/telemetry-pipelines/in-stream-alerts.md): Set threshold, change, and absence alerts on pipeline data to detect and respond to conditions within seconds, before data is indexed or routed.
- [Script Execution Processor](https://docs.mezmo.com/telemetry-pipelines/js-script-processor.md): Transform events using a subset of JavaScript to filter, drop, map, and cast data within a single script, with supported functions and operators.
- [Azure Event Hub](https://docs.mezmo.com/telemetry-pipelines/kafka-aeh.md): Send Mezmo Pipeline data to Azure Event Hubs through its Kafka endpoint, with broker, topic, TLS, and SASL/SCRAM configuration options.
- [Kafka](https://docs.mezmo.com/telemetry-pipelines/kafka-destination.md): Send Mezmo Pipeline data to Kafka, with options for encoding, compression, TLS, and SASL/SCRAM authentication.
- [Kafka](https://docs.mezmo.com/telemetry-pipelines/kafka-source.md): A pull source that collects events from Kafka-compatible brokers, with configurable topics, consumer group, TLS, and SASL/SCRAM authentication.
- [AWS Kinesis Data Firehose](https://docs.mezmo.com/telemetry-pipelines/kinesis-firehose-destination.md): Publish logs from your Mezmo Pipeline to AWS Kinesis Data Firehose streams using AWS credentials, encoding, and compression settings.
- [AWS Kinesis Firehose](https://docs.mezmo.com/telemetry-pipelines/kinesis-firehose-source.md): Stream near real-time data into your Mezmo Pipeline from AWS Kinesis Firehose by configuring the HTTP endpoint and API key on your delivery stream.
- [AWS Kinesis Streams](https://docs.mezmo.com/telemetry-pipelines/kinesis-streams-destination.md): Publish logs from your Mezmo Pipeline to AWS Kinesis Streams using AWS credentials, encoding, compression, and a partition key field.
- [Mezmo Log Analysis Ingestion](https://docs.mezmo.com/telemetry-pipelines/log-analysis-ingestion-source.md): Redirect data sent to the logs.mezmo.com Log Analysis endpoint into a Pipeline Source, supporting agent, ingest, syslog, and Heroku endpoints.
- [Mezmo Log Analysis](https://docs.mezmo.com/telemetry-pipelines/log-analysis-source.md): A deprecated source that forwards logs from your Log Analysis account into a Pipeline, including the metadata query fields it attaches to each event.
- [Logstash](https://docs.mezmo.com/telemetry-pipelines/logstash-source.md): Send data from your Logstash instance to Mezmo Pipelines using the HTTP output plugin with string or JSON formatting.
- [Loki](https://docs.mezmo.com/telemetry-pipelines/loki-destination.md): Send logs from your Mezmo Pipeline to any Loki destination, such as Grafana Logs, with configurable endpoint, auth strategy, codec, and labels.
- [Map Fields Processor](https://docs.mezmo.com/telemetry-pipelines/map-fields-processor.md): Move or copy fields within an event, including nested fields, with options to drop the source field or overwrite an existing target.
- [The Pipeline Metric Data Model](https://docs.mezmo.com/telemetry-pipelines/metric-data-within-the-pipeline.md): Defines the standard metric data model fields required for processing metrics in a Pipeline, with JSON examples and ways to transform metrics.
- [Tag Cardinality Limit Processor](https://docs.mezmo.com/telemetry-pipelines/metrics-tag-cardinality-limit-processor.md): Cap the number of unique tag values per metric using exact or probabilistic matching, dropping the offending tag or the entire event when the limit is reached.
- [Mezmo Agent](https://docs.mezmo.com/telemetry-pipelines/mezmo-agent-source.md): Stream log data from the Mezmo Agent directly into a Pipeline, including configuration variables, migration from Log Analysis, and Helm installation.
- [Mezmo Archive Destination](https://docs.mezmo.com/telemetry-pipelines/mezmo-archive-destination.md): Archive telemetry data to S3 or Azure Cloud Storage in a date-partitioned folder structure so it can later be restored into a Pipeline.
- [Datadog Agent](https://docs.mezmo.com/telemetry-pipelines/mezmo-datadog-source-source.md): Receive logs and metrics directly from the Datadog Agent over HTTPS into a Mezmo Pipeline, with setup, configuration, and Docker/host examples.
- [Mezmo Log Analysis](https://docs.mezmo.com/telemetry-pipelines/mezmo-destination.md): Send Pipeline data to a Mezmo Log Analysis account for search, views, and alerts, with configuration options for ingestion, query, and message fields.
- [Monitor Pipeline Data Volume](https://docs.mezmo.com/telemetry-pipelines/monitor-data-pipelines.md): Use the Pipelines dashboard to track aggregated and per-source/destination Ingress and Egress volume, top 10 sources and destinations, and per-Pipeline metrics.
- [New Relic](https://docs.mezmo.com/telemetry-pipelines/new-relic-destination.md): Send logs and metrics to a New Relic instance, configuring the account ID, logs or metrics endpoint, US or EU region, and license key.
- [OpenTelemetry Logs](https://docs.mezmo.com/telemetry-pipelines/open-telemetry-logs-source.md): Send logs to a Mezmo Pipeline from any OTLP-compliant sender over HTTP, using a unique endpoint URL and Bearer Token authentication.
- [OpenTelemetry Metrics](https://docs.mezmo.com/telemetry-pipelines/open-telemetry-metrics-source.md): Send metrics to a Mezmo Pipeline from any OTLP-compliant sender over HTTP, using a unique endpoint URL and Bearer Token authentication.
- [OpenTelemetry Traces](https://docs.mezmo.com/telemetry-pipelines/open-telemetry-traces-source.md): Send traces to a Mezmo Pipeline from any OTLP-compliant sender over HTTP, including the per-span event data structure Mezmo produces.
- [OpenTelemetry Collector](https://docs.mezmo.com/telemetry-pipelines/otel-collector.md): Export log, metric, and trace data to Mezmo with the OpenTelemetry Collector, including a quick-start config and Helm chart installation.
- [Parse Processor](https://docs.mezmo.com/telemetry-pipelines/parse-processor.md): Convert incoming data of a known format into parsed values using parsers like CSV, Grok, JSON, Regex, and timestamps, plus AI-assisted pattern matching.
- [Parse Sequentially Processor](https://docs.mezmo.com/telemetry-pipelines/parse-sequentially-processor.md): Configure multiple parsers on a single node that are tried in order, applying the first parser that matches the incoming data.
- [Percentage Volume Increase](https://docs.mezmo.com/telemetry-pipelines/percentage-volume-increase.md): Example Change Alert configuration that fires when data volume rises by a set percentage compared to the prior tumbling window period.
- [Pipeline Example: Kubernetes Telemetry Data Optimization](https://docs.mezmo.com/telemetry-pipelines/pipeline-architecture-for-kubernetes-data-optimizationzlz.md): Walk-through of a Pipeline that transforms Kubernetes telemetry into metrics for observability tools while retaining original data in storage.
- [Pipeline Data Restoration](https://docs.mezmo.com/telemetry-pipelines/pipeline-data-restoration-source.md): Source that lets you restore telemetry data from an archive location into a Pipeline, with no configuration options required.
- [Pipeline Event Data Model](https://docs.mezmo.com/telemetry-pipelines/pipeline-event-data-model.md): How events move through a Pipeline via the event envelope, including the message, metadata, and timestamp fields and how to reference them.
- [Set Threshold Alerts for Pipeline Data Volume](https://docs.mezmo.com/telemetry-pipelines/pipeline-threshold-alerts.md): Create Absolute, Relative, and Absence threshold alerts to be notified when Pipeline ingress or egress volume meets criteria over a time frame.
- [Presence of Personally Identifying Information (PII)](https://docs.mezmo.com/telemetry-pipelines/presence-of-personally-identifying-information--pii-.md): Example alert that triggers when the Redact Processor detects PII such as SSNs, email addresses, or custom patterns in telemetry data.
- [Prometheus Remote Write](https://docs.mezmo.com/telemetry-pipelines/prometheus-remote-write-destination.md): Send metrics to any destination that accepts the Prometheus Remote Write protocol, such as Grafana, with authentication and endpoint options.
- [Prometheus Remote Write](https://docs.mezmo.com/telemetry-pipelines/prometheus-remote-write-source.md): Send metrics to a Mezmo Pipeline using the Prometheus Remote Write source, with a unique endpoint URL and Bearer Token authentication.
- [Redact Processor](https://docs.mezmo.com/telemetry-pipelines/redact-processor.md): Identify and redact PII such as SSNs, emails, credit cards, and phone numbers in your data stream using pattern detection, hashing, or replacement.
- [Reduce Processor](https://docs.mezmo.com/telemetry-pipelines/reduce-processor.md): Combine multiple log events into a single event over a time window using group-by fields and configurable per-field merge strategies.
- [Required Schema for Mezmo Log Analysis Destination](https://docs.mezmo.com/telemetry-pipelines/required-schema-for-mezmo-log-analysis-destination.md): Reference for the message schema, required fields, and display names data must conform to when restoring to the Mezmo Log Analysis destination.
- [Route Processor](https://docs.mezmo.com/telemetry-pipelines/route-processor.md): Separate events from a single stream into multiple streams using conditional statements, so you can send events to different processors or destinations.
- [AWS S3 Storage](https://docs.mezmo.com/telemetry-pipelines/s3-destination.md): Send pipeline data to an AWS S3 bucket for long-term storage, with options for encoding, compression, storage class, and required IAM permissions.
- [AWS S3 via SQS](https://docs.mezmo.com/telemetry-pipelines/s3-source.md): Use log data stored in Amazon S3 as a pipeline source via Amazon SQS to rehydrate, parse, and route archived data for analysis or compliance.
- [Sample Processor](https://docs.mezmo.com/telemetry-pipelines/sample-processor.md): Filter incoming events at a configurable 1/N rate to reduce event volume, with conditional rules to always forward matching events.
- [Set In-Stream Alerts for Pipeline Nodes](https://docs.mezmo.com/telemetry-pipelines/set-in-stream-alerts.md): Configure threshold, change, or absence alerts on any source or processor node, with evaluation windows and payloads sent to Slack, PagerDuty, or webhooks.
- [Set Pipeline Access](https://docs.mezmo.com/telemetry-pipelines/set-pipeline-access.md): Grant organization members access to the pipelines you create by assigning them the Member + Pipeline role.
- [Set Timestamp Processor](https://docs.mezmo.com/telemetry-pipelines/set-timestamp-processor.md): Override an event's timestamp with a field and parser of your choice, trying multiple fields and formats until one parses successfully.
- [Set Up and Test an HTTP Endpoint Source](https://docs.mezmo.com/telemetry-pipelines/set-up-and-process-http-endpoint-data.md): Walk-through for configuring an HTTP endpoint pipeline source, sending test data with cURL, adding a processor, and routing the data to a destination.
- [Set Up Pipeline Destinations](https://docs.mezmo.com/telemetry-pipelines/set-up-pipeline-destinations.md): Add and connect a destination to your pipeline, and learn how buffering controls when batched events are flushed to the destination.
- [Set Up Pipeline Processors](https://docs.mezmo.com/telemetry-pipelines/set-up-pipeline-processors.md): Insert processors between a connected source and destination to reduce, reformat, or extract information from log data in your pipeline.
- [Set Up Pipeline Sources](https://docs.mezmo.com/telemetry-pipelines/set-up-pipeline-sources.md): Create a pipeline and add a source to begin ingesting log data from one of the supported telemetry pipeline sources.
- [Shared Sources](https://docs.mezmo.com/telemetry-pipelines/shared-sources.md): Configure a source once at the global level and reuse it across multiple pipelines, transmitting the same data only once to reduce volume and management.
- [What Are Shared Sources?](https://docs.mezmo.com/telemetry-pipelines/shared-sources-overview.md): Shared Sources are global configurations that transmit the same data across multiple pipelines at once, reducing redundancy and configuration effort.
- [Simulate and Test Pipeline Data Streams](https://docs.mezmo.com/telemetry-pipelines/simulate-pipeline-data-flows.md): Use Simulation mode to test data flow through processors and destinations with sample data, compare input and output with diff view, and add custom samples.
- [Splunk HTTP Event Collector](https://docs.mezmo.com/telemetry-pipelines/splunk-hec-logs-destination.md): Send Mezmo Pipeline log data to Splunk via the HTTP Event Collector, configuring endpoint, token, encoding, compression, and indexed fields.
- [Splunk HEC](https://docs.mezmo.com/telemetry-pipelines/splunk-hec-source.md): Use the Splunk HTTP Event Collector as a pipeline source to route, reduce, and process events before forwarding them on to Splunk or a SIEM.
- [AWS SQS](https://docs.mezmo.com/telemetry-pipelines/sqs-destination.md): Publish observability events from a pipeline to an Amazon SQS queue, configuring access keys, encoding, region, and queue URL.
- [AWS SQS](https://docs.mezmo.com/telemetry-pipelines/sqs-source.md): Stream log data from an Amazon SQS queue as a pipeline source, including SQS setup, the required access policy, and IAM permissions.
- [Stringify Processor](https://docs.mezmo.com/telemetry-pipelines/stringify-processor.md): Render an entire event's JSON object into a single text string for downstream steps that require string input, such as the Encrypt processor.
- [Sudden Increase in Source Volume](https://docs.mezmo.com/telemetry-pipelines/sudden-increase-in-source-volume.md): Configure an alert that triggers when a source's data volume rises 60% or more compared to a prior tumbling window, including the custom aggregation script.
- [Sumo Logic Logs](https://docs.mezmo.com/telemetry-pipelines/sumo-logic-logs-destination.md): Send logs from a pipeline to your Sumo Logic instance, configuring the collector endpoint, compression, and category.
- [Supported Processors](https://docs.mezmo.com/telemetry-pipelines/supported-processors.md): Browse the processors Mezmo supports for telemetry data, with links to detailed configuration information for each.
- [Supported Telemetry Data Destinations](https://docs.mezmo.com/telemetry-pipelines/supported-telemetry-data-destinations.md): Browse the destinations Mezmo supports for sending telemetry data out of a pipeline.
- [Supported Telemetry Pipeline Sources](https://docs.mezmo.com/telemetry-pipelines/supported-telemetry-pipeline-sources.md): Browse the sources Mezmo supports for ingesting telemetry data into a pipeline.
- [Syntax for Editing Pipeline Component Configuration Values](https://docs.mezmo.com/telemetry-pipelines/syntax-for-editing-pipeline-component-configuration-values.md): Learn the syntax for data fields, data references, static values, and metadata when editing source, processor, and destination configuration values.
- [Syslog over HTTP](https://docs.mezmo.com/telemetry-pipelines/syslog-over-http-pipeline-source.md): Send Syslog events to Mezmo Pipelines through an HTTP endpoint over TLS, including an example rsyslog om-http configuration.
- [Primary Ingestion Pipeline](https://docs.mezmo.com/telemetry-pipelines/the-log-analysis-source-data-pipeline.md): Overview of the optimized log data management Pipeline given to Mezmo Log Analysis customers, including its four processing steps and component configuration.
- [Throttle Processor](https://docs.mezmo.com/telemetry-pipelines/throttle-processor.md): Apply rate limiting to an event stream to protect downstream destinations, throttling globally or per key field within a configurable time window.
- [Trace Sampling Processor](https://docs.mezmo.com/telemetry-pipelines/trace-sampling-processor.md): Sample OpenTelemetry traces at a given rate using the Trace ID, supporting both head-based and conditional tail-based sampling strategies.
- [Tutorial: How to Build a Telemetry Pipeline with Terraform](https://docs.mezmo.com/telemetry-pipelines/tutorial--how-to-build-a-telemetry-pipeline-with-terraform.md): Video tutorial on building a Mezmo Telemetry Pipeline with Terraform, including configuring access to Shared Sources with AWS Secrets Manager.
- [Unroll Processor](https://docs.mezmo.com/telemetry-pipelines/unroll-processor.md): Convert a JSON object array within a field into individual objects, commonly used when a source packages multiple events in a single JSON object.
- [Grok Pattern Reference](https://docs.mezmo.com/telemetry-pipelines/using-grok-to-parse.md): Learn how to use Grok patterns in Mezmo to extract structured data from unstructured text, including Mezmo-specific patterns, rules, and worked examples.
- [View Event Metrics](https://docs.mezmo.com/telemetry-pipelines/view-event-metrics.md): View historic event volume and trends per app, host, level, and label for a Pipeline over a selected time window.
- [View and Sample Pipeline Data](https://docs.mezmo.com/telemetry-pipelines/view-pipeline-data.md): Use a Pipeline Tap to view data streaming between nodes of a deployed Pipeline and capture samples for simulating and testing your processors.
- [View Pipeline Errors](https://docs.mezmo.com/telemetry-pipelines/view-pipeline-errors.md): Find processing errors in a Pipeline using error indicators, the Error History view, and per-error log lines, plus error retention details.
- [Webhook (WebSub)](https://docs.mezmo.com/telemetry-pipelines/webhook-source.md): Accept RESTful webhook messages using the WebSub protocol, verifying payloads with an HMAC signature based on a configured signing key.

## OpenAPI Specs

- [pipeline](https://docs.mezmo.com/pipeline.yaml)
- [log-analysis](https://docs.mezmo.com/log-analysis.json)

## Optional

- [About](https://www.mezmo.com/about)
- [Blog](https://www.mezmo.com/blog)