Describes metric reporting capabilities provided by Philter.
Philter collects metrics while running to provide insights into its operation and the text being processed. The metrics collected include a count of the documents processed by Philter, counts of the types of sensitive information identified per type, and the entity confidence values of entities extracted by non-deterministic natural language processing methods. These metrics can be reported via JMX, and to external services Prometheus, Amazon CloudWatch, and Datadog.
To enable Philter metric reporting to Prometheus modify Philter's Settings to enable the Prometheus metrics. When enabled, the metrics HTTP endpoint will be
Enable scraping of Philter's metrics in Prometheus' settings:
- job_name: philter
- targets: ['10.0.2.104:9100']
You may need to make port
9100accessible to Prometheus. For example, if you launch Philter in AWS you will need to modify Philter's security group to permit inbound network traffic on port
To enable Philter metric reporting to Amazon CloudWatch modify Philter's Settings to set the AWS properties. Metrics will be published to CloudWatch every 60 seconds, by default, when enabled.
The AWS IAM user or role being used should have
The metrics will be published to the Amazon CloudWatch namespace provided in Philter's settings. Amazon CloudWatch can then be used to visualize the metrics, set performance alarms, or perform other integrations with AWS services.
Philter metrics reported and visualized in Amazon CloudWatch.
Metrics will be published to Datadog every 60 seconds when enabled.
Metrics published to Datadog will have a
Philter metrics in Datadog's Metrics Summary.
The metrics can be used to make graphs and dashboards.
Example Datadog graphs of select Philter metrics.
The listing below shows an example of the metrics Philter collects and writes to standard out while running. The metrics reported to supported services such as JMX, Amazon CloudWatch and Datadog will contain the same metrics but may be represented or visualized differently between the services.
The metrics collected include:
- A cumulative count of each type of sensitive information across all contexts and documents.
- The total count of documents processed.
These metrics will be reset when Philter is stopped and restarted.