Type to search.

Miniflux integration

Serverless Observability

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Serverless Security

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Stack 9.1+

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Generally available since 9.1

    This functionality is generally available and ready for production usage.

Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

Version 1.4.0 (View all)
Managed integration release status GA
Subscription level
What's this?
Basic
Developed by
What's this?
Elastic
Ingestion method(s) API
Minimum Kibana version(s) 9.1.4
9.0.7
8.19.4
Important - Managed integrations on Elastic Cloud Hosted The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability Generally available since 9.5 This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

You can use this integration as an Elastic Managed integration on Elastic Cloud Hosted deployments running this version or later.

The Miniflux integration allows you to extract data from Miniflux. Miniflux is an RSS feed reader.

Use the Miniflux integration to extract RSS feed content. Then visualize that data in Kibana, create alerts to notify you if something goes wrong.

For example, if you wanted to be notified for a new feed entry you could set up an alert.

Elastic Managed integrations are only supported on Elastic Cloud Serverless and Elastic Cloud Hosted deployments. An Elastic Managed integration lets you ingest data from a cloud source while avoiding the orchestration, management, and maintenance associated with standard ingest infrastructure. Elastic runs the collector for you, so you can focus on your data instead of the infrastructure that collects it.

For more information, refer to Elastic Managed integrations and the Elastic Managed integrations FAQ.

This integration collects the following logs:

  • Entries - Retrieves feed entries from the Miniflux application.

You need Elasticsearch for storing and searching your data and Kibana for visualizing and managing it. You can use our hosted Elasticsearch Service on Elastic Cloud, which is recommended, or self-manage the Elastic Stack on your own hardware.

Each data stream collects different kinds of logs data, which may require dedicated permissions to be fetched and may vary across operating systems. Details on the permissions needed for each data stream are available in the Logs reference.

Before sending logs to Elastic from your Miniflux application (self-hosted or SaaS), you must create a Miniflux API key by following Miniflux's documentation

After you've configured your device, you can set up the Elastic integration.

Feed Entry

This is the feed_entry dataset.

Example
JSON
{
    "@timestamp": "2025-05-13T01:30:56.695Z",
    "agent": {
        "ephemeral_id": "3221ee48-0fe2-46e1-a34b-07909a00265e",
        "id": "ba6fa1eb-0b15-4523-83b2-12b2b68add1c",
        "name": "elastic-agent-34183",
        "type": "filebeat",
        "version": "8.18.0"
    },
    "data_stream": {
        "dataset": "miniflux.feed_entry",
        "namespace": "27883",
        "type": "logs"
    },
    "ecs": {
        "version": "8.17.0"
    },
    "elastic_agent": {
        "id": "ba6fa1eb-0b15-4523-83b2-12b2b68add1c",
        "snapshot": false,
        "version": "8.18.0"
    },
    "event": {
        "agent_id_status": "verified",
        "category": [
            "web"
        ],
        "dataset": "miniflux.feed_entry",
        "ingested": "2025-05-13T01:30:59Z",
        "kind": "enrichment",
        "type": [
            "info"
        ]
    },
    "input": {
        "type": "cel"
    },
    "miniflux": {
        "changed_at": "2023-09-02T20:30:13.118Z",
        "content": "<p></p>\n\n<h1>Exploit for Code Injection in Vmware Spring Framework CVE-2022-22965</h1>\n<p>2023-09-02 | CVSS 7.5 </p>\n\n\n\n\n\nCopy\nDownload\nSource\n<a href=\"#share-url\">Share</a>\n\n<pre><code>## https://sploitus.com/exploit?id=5C9561BE-D9BB-58D0-8E51-09DDD257BC72\n# Spring4Shell: CVE-2022-22965 RCE\n\n## Java Spring framework RCE vulnerability\nThese vulnerabilities affects a component &#34;Spring Core&#34; —  the heart of the framework \n\n**Current conditions for vulnerability:-**\n\n- JDK 9+\n- A vulnerable version of the Spring Framework (&lt;5.2 | 5.2.0-19 | 5.3.0-17)\n- Apache Tomcat as a server for the Spring application, packaged as a WAR\n- A dependency on the spring-webmvc and/or spring-webflux components of the Spring Framework\n\n## The exploit\n\n```python\nuser@attacker:~$ ./exploit.py --help\nusage: exploit.py [-h] [-f FILENAME] [-p PASSWORD] [-d DIRECTORY] url\n\nSpring4Shell RCE Proof of Concept\n\npositional arguments:\n  url                   Target URL\n\noptional arguments:\n  -h, --help            show this help message and exit\n  -f FILENAME, --filename FILENAME\n                        Name of the file to upload (Default tomcatwar.jsp)\n  -p PASSWORD, --password PASSWORD\n                        Password to protect the shell with (Default: thm)\n  -d DIRECTORY, --directory DIRECTORY\n                        The upload path for the file (Default: ROOT)\n```\n\n```python\nuser@attacker:~$ ./exploit.py http://MACHINE_IP/\nShell Uploaded Successfully!\n\n\n# OUTPUT= Your shell can be found at: http://MACHINE_IP/tomcatwar.jsp?pwd=thm&amp;cmd=whoami\n```</code> </pre>\n\n",
        "created_at": "2023-09-02T20:17:02.689Z",
        "feed": {
            "allow_self_signed_certificates": false,
            "category": {
                "hide_globally": false,
                "id": 25000,
                "title": "2-Production",
                "user_id": 4426
            },
            "checked_at": "2025-05-02T12:25:58.524Z",
            "crawler": true,
            "disable_http2": false,
            "disabled": false,
            "feed_url": "https://sploitus.com/rss",
            "fetch_via_proxy": false,
            "hide_globally": false,
            "icon": {
                "external_icon_id": "dadd95d716e12dbdc58fabdd0f38f48e8d7eab88",
                "feed_id": 355593,
                "icon_id": 60476
            },
            "id": 355593,
            "ignore_http_cache": false,
            "next_check_at": "0001-01-01T00:00:00.000Z",
            "no_media_player": false,
            "ntfy_enabled": false,
            "ntfy_priority": 0,
            "parsing_error_count": 0,
            "pushover_enabled": false,
            "pushover_priority": 0,
            "site_url": "https://sploitus.com/rss",
            "title": "Sploitus.com Exploits RSS Feed",
            "user_id": 4426
        },
        "feed_id": 355593,
        "hash": "fab2dc0ad7ba85e40595d197da245cb2602ce93c6a2c2deca340ce909c9a4a13",
        "id": 83721716,
        "published_at": "2023-09-02T10:41:05.000Z",
        "reading_time": 1,
        "starred": true,
        "status": "read",
        "title": "Exploit for Code Injection in Vmware Spring Framework exploit",
        "url": "https://sploitus.com/exploit?id=5C9561BE-D9BB-58D0-8E51-09DDD257BC72&utm_source=rss&utm_medium=rss",
        "user_id": 4426
    },
    "related": {
        "hash": [
            "fab2dc0ad7ba85e40595d197da245cb2602ce93c6a2c2deca340ce909c9a4a13"
        ]
    },
    "tags": [
        "forwarded",
        "miniflux-feed_entry"
    ],
    "url": {
        "domain": "sploitus.com",
        "full": "https://sploitus.com/exploit?id=5C9561BE-D9BB-58D0-8E51-09DDD257BC72&utm_source=rss&utm_medium=rss",
        "original": "https://sploitus.com/exploit?id=5C9561BE-D9BB-58D0-8E51-09DDD257BC72&utm_source=rss&utm_medium=rss",
        "path": "/exploit",
        "query": "id=5C9561BE-D9BB-58D0-8E51-09DDD257BC72&utm_source=rss&utm_medium=rss",
        "scheme": "https"
    }
}
Exported fields
Field Description Type
@timestamp Date/time when the event originated. This is the date/time extracted from the event, typically representing when the event was generated by the source. If the event source has no original timestamp, this value is typically populated by the first time the event was received by the pipeline. Required field for all events. date
data_stream.dataset The field can contain anything that makes sense to signify the source of the data. Examples include nginx.access, prometheus, endpoint etc. For data streams that otherwise fit, but that do not have dataset set we use the value "generic" for the dataset value. event.dataset should have the same value as data_stream.dataset. Beyond the Elasticsearch data stream naming criteria noted above, the dataset value has additional restrictions: * Must not contain - * No longer than 100 characters constant_keyword
data_stream.namespace A user defined namespace. Namespaces are useful to allow grouping of data. Many users already organize their indices this way, and the data stream naming scheme now provides this best practice as a default. Many users will populate this field with default. If no value is used, it falls back to default. Beyond the Elasticsearch index naming criteria noted above, namespace value has the additional restrictions: * Must not contain - * No longer than 100 characters constant_keyword
data_stream.type An overarching type for the data stream. Currently allowed values are "logs" and "metrics". We expect to also add "traces" and "synthetics" in the near future. constant_keyword
input.type Type of filebeat input. keyword
miniflux.author Author of the feed entry keyword
miniflux.changed_at date
miniflux.comments_url keyword
miniflux.content keyword
miniflux.created_at date
miniflux.enclosures keyword
miniflux.feed.allow_self_signed_certificates boolean
miniflux.feed.apprise_service_urls boolean
miniflux.feed.blocklist_rules keyword
miniflux.feed.category.hide_globally boolean
miniflux.feed.category.id long
miniflux.feed.category.title keyword
miniflux.feed.category.user_id long
miniflux.feed.checked_at date
miniflux.feed.cookie keyword
miniflux.feed.crawler boolean
miniflux.feed.description keyword
miniflux.feed.disable_http2 boolean
miniflux.feed.disabled boolean
miniflux.feed.etag_header keyword
miniflux.feed.feed_url keyword
miniflux.feed.fetch_via_proxy boolean
miniflux.feed.hide_globally boolean
miniflux.feed.icon.external_icon_id keyword
miniflux.feed.icon.feed_id long
miniflux.feed.icon.icon_id long
miniflux.feed.id long
miniflux.feed.ignore_http_cache boolean
miniflux.feed.keeplist_rules keyword
miniflux.feed.last_modified_header keyword
miniflux.feed.next_check_at date
miniflux.feed.no_media_player boolean
miniflux.feed.ntfy_enabled boolean
miniflux.feed.ntfy_priority integer
miniflux.feed.ntfy_topic keyword
miniflux.feed.parsing_error_count integer
miniflux.feed.parsing_error_message keyword
miniflux.feed.password keyword
miniflux.feed.proxy_url keyword
miniflux.feed.pushover_enabled boolean
miniflux.feed.pushover_priority integer
miniflux.feed.rewrite_rules keyword
miniflux.feed.scraper_rules keyword
miniflux.feed.site_url keyword
miniflux.feed.title keyword
miniflux.feed.urlrewrite_rules keyword
miniflux.feed.user_agent keyword
miniflux.feed.user_id long
miniflux.feed.username keyword
miniflux.feed.webhook_url keyword
miniflux.feed_entry_split keyword
miniflux.feed_id long
miniflux.hash keyword
miniflux.id long
miniflux.published_at date
miniflux.reading_time integer
miniflux.share_code keyword
miniflux.starred boolean
miniflux.status keyword
miniflux.tags keyword
miniflux.title keyword
miniflux.url keyword
miniflux.user_id long

This integration includes one or more Kibana dashboards that visualizes the data collected by the integration. The screenshots below illustrate how the ingested data is displayed.

Sample screenshot
Changelog
Version Details Minimum Kibana version
1.4.0 Enhancement (View pull request)
Update Elastic Managed integration documentation to the current wording and docs links.
9.1.4
9.0.7
8.19.4
1.3.0 Enhancement (View pull request)
Add tags to ingest pipeline processors.
9.1.4
9.0.7
8.19.4
1.2.1 Enhancement (View pull request)
Set agentless deployment mode release field to ga.
9.1.4
9.0.7
8.19.4
1.2.0 Enhancement (View pull request)
Use new release field for agentless deployment mode to establish as beta.
9.1.4
9.0.7
8.19.4
1.1.0 Enhancement (View pull request)
Enable Agentless deployment.
9.1.4
9.0.7
8.19.4
1.0.1 Bug fix (View pull request)
Add missing request trace enabled default option.
9.0.0
8.17.4
1.0.0 Enhancement (View pull request)
Release package as GA.

Enhancement (View pull request)
Add dashboard.
9.0.0
8.17.4
0.3.0 Enhancement (View pull request)
Use terminate processor instead of fail processor to handle agent errors.
9.0.0
8.17.4
0.2.1 Bug fix (View pull request)
Fix minor spelling mistakes.
9.0.0
8.17.4
0.2.0 Enhancement (View pull request)
Update Kibana constraint to support 9.0.0.

Enhancement (View pull request)
Add uri_parts pipeline parsing on field miniflux.url.
9.0.0
8.17.4
0.1.0 Enhancement (View pull request)
Initial draft of the package
8.17.4