- Elastic integrations
- Integrations quick reference
- 1Password
- Abnormal Security
- ActiveMQ
- Active Directory Entity Analytics
- Admin By Request EPM integration
- Airflow
- Akamai
- Apache
- API (custom)
- Arbor Peakflow SP Logs
- Arista NG Firewall
- Atlassian
- Auditd
- Auth0
- authentik
- AWS
- Amazon CloudFront
- Amazon DynamoDB
- Amazon EBS
- Amazon EC2
- Amazon ECS
- Amazon EMR
- AWS API Gateway
- Amazon GuardDuty
- AWS Health
- Amazon Kinesis Data Firehose
- Amazon Kinesis Data Stream
- Amazon MQ
- Amazon Managed Streaming for Apache Kafka (MSK)
- Amazon NAT Gateway
- Amazon RDS
- Amazon Redshift
- Amazon S3
- Amazon S3 Storage Lens
- Amazon Security Lake
- Amazon SNS
- Amazon SQS
- Amazon VPC
- Amazon VPN
- AWS Bedrock
- AWS Billing
- AWS CloudTrail
- AWS CloudWatch
- AWS ELB
- AWS Fargate
- AWS Inspector
- AWS Lambda
- AWS Logs (custom)
- AWS Network Firewall
- AWS Route 53
- AWS Security Hub
- AWS Transit Gateway
- AWS Usage
- AWS WAF
- Azure
- Activity logs
- App Service
- Application Gateway
- Application Insights metrics
- Application Insights metrics overview
- Application State Insights metrics
- Azure logs (v2 preview)
- Azure OpenAI
- Billing metrics
- Container instance metrics
- Container registry metrics
- Container service metrics
- Custom Azure Logs
- Custom Blob Storage Input
- Database Account metrics
- Event Hub input
- Firewall logs
- Frontdoor
- Functions
- Microsoft Entra ID
- Monitor metrics
- Network Watcher VNet
- Network Watcher NSG
- Platform logs
- Resource metrics
- Spring Cloud logs
- Storage Account metrics
- Virtual machines metrics
- Virtual machines scaleset metrics
- Barracuda
- BeyondInsight and Password Safe Integration
- BitDefender
- Bitwarden
- blacklens.io
- Blue Coat Director Logs
- BBOT (Bighuge BLS OSINT Tool)
- Box Events
- Bravura Monitor
- Broadcom ProxySG
- Canva
- Cassandra
- CEL Custom API
- Ceph
- Check Point
- Cilium Tetragon
- CISA Known Exploited Vulnerabilities
- Cisco
- Cisco Meraki Metrics
- Citrix
- Claroty CTD
- Cloudflare
- Cloud Asset Inventory
- CockroachDB Metrics
- Common Event Format (CEF)
- Containerd
- CoreDNS
- Corelight
- Couchbase
- CouchDB
- Cribl
- CrowdStrike
- Cyberark
- Cybereason
- CylanceProtect Logs
- Custom Websocket logs
- Darktrace
- Data Exfiltration Detection
- DGA
- Digital Guardian
- Docker
- DomainTools Real Time Unified Feeds
- Elastic APM
- Elastic Fleet Server
- Elastic Security
- Elastic Stack monitoring
- Elasticsearch Service Billing
- Envoy Proxy
- ESET PROTECT
- ESET Threat Intelligence
- etcd
- Falco
- F5
- File Integrity Monitoring
- FireEye Network Security
- First EPSS
- Forcepoint Web Security
- ForgeRock
- Fortinet
- Gigamon
- GitHub
- GitLab
- Golang
- Google Cloud
- Custom GCS Input
- GCP
- GCP Audit logs
- GCP Billing metrics
- GCP Cloud Run metrics
- GCP CloudSQL metrics
- GCP Compute metrics
- GCP Dataproc metrics
- GCP DNS logs
- GCP Firestore metrics
- GCP Firewall logs
- GCP GKE metrics
- GCP Load Balancing metrics
- GCP Metrics Input
- GCP PubSub logs (custom)
- GCP PubSub metrics
- GCP Redis metrics
- GCP Security Command Center
- GCP Storage metrics
- GCP VPC Flow logs
- GCP Vertex AI
- GoFlow2 logs
- Hadoop
- HAProxy
- Hashicorp Vault
- HTTP Endpoint logs (custom)
- IBM MQ
- IIS
- Imperva
- InfluxDb
- Infoblox
- Iptables
- Istio
- Jamf Compliance Reporter
- Jamf Pro
- Jamf Protect
- Jolokia Input
- Journald logs (custom)
- JumpCloud
- Kafka
- Keycloak
- Kubernetes
- LastPass
- Lateral Movement Detection
- Linux Metrics
- Living off the Land Attack Detection
- Logs (custom)
- Lumos
- Lyve Cloud
- Mattermost
- Memcached
- Menlo Security
- Microsoft
- Microsoft 365
- Microsoft Defender for Cloud
- Microsoft Defender for Endpoint
- Microsoft DHCP
- Microsoft DNS Server
- Microsoft Entra ID Entity Analytics
- Microsoft Exchange Online Message Trace
- Microsoft Exchange Server
- Microsoft Graph Activity Logs
- Microsoft M365 Defender
- Microsoft Office 365 Metrics Integration
- Microsoft Sentinel
- Microsoft SQL Server
- Mimecast
- ModSecurity Audit
- MongoDB
- MongoDB Atlas
- MySQL
- Nagios XI
- NATS
- NetFlow Records
- Netskope
- Network Beaconing Identification
- Network Packet Capture
- Nginx
- Okta
- Oracle
- OpenAI
- OpenCanary
- Osquery
- Palo Alto
- pfSense
- PHP-FPM
- PingOne
- PingFederate
- Pleasant Password Server
- PostgreSQL
- Prometheus
- Proofpoint TAP
- Proofpoint On Demand
- Pulse Connect Secure
- Qualys VMDR
- QNAP NAS
- RabbitMQ Logs
- Radware DefensePro Logs
- Rapid7
- Redis
- Rubrik RSC Metrics Integration
- Sailpoint Identity Security Cloud
- Salesforce
- SentinelOne
- ServiceNow
- Slack Logs
- Snort
- Snyk
- SonicWall Firewall
- Sophos
- Spring Boot
- SpyCloud Enterprise Protection
- SQL Input
- Squid Logs
- SRX
- STAN
- Statsd Input
- Sublime Security
- Suricata
- StormShield SNS
- Symantec
- Symantec Endpoint Security
- Sysmon for Linux
- Sysdig
- Syslog Router Integration
- System
- System Audit
- Tanium
- TCP Logs (custom)
- Teleport
- Tenable
- Threat intelligence
- ThreatConnect
- Threat Map
- Thycotic Secret Server
- Tines
- Traefik
- Trellix
- Trend Micro
- TYCHON Agentless
- UDP Logs (custom)
- Universal Profiling
- Vectra Detect
- VMware
- WatchGuard Firebox
- WebSphere Application Server
- Windows
- Wiz
- Zeek
- ZeroFox
- Zero Networks
- ZooKeeper Metrics
- Zoom
- Zscaler
Azure App Service Integration
editAzure App Service Integration
editVersion |
0.6.0 [beta] This functionality is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features. (View all) |
Compatible Kibana version(s) |
8.13.0 or higher |
Supported Serverless project types |
Security |
Subscription level |
Basic |
Level of support |
Elastic |
The Azure App Service logs integration retrieves different types of logs categories from Azure App Service. Azure App Service provides different logging to help you track, monitor, and debug your web application.
- HTTPLogs help monitor application health, performance and usage patterns.
- AuditLogs provide insights when publishing users successfully log on via one of the App Service publishing protocols.
- IPSecAuditLogs are generated through your application and pushed to Azure Monitoring.
- PlatformLogs are generated through AppService platform for your application.
- ConsoleLogs are generated from application or container.
- AppLogs are generated through your application (ex. logging capabilities)
Data streams
editThis integration currently collects one data stream:
- App Service Logs
Requirements
editCredentials
editeventhub :
string
Is the fully managed, real-time data ingestion service.
consumer_group :
string
The publish/subscribe mechanism of Event Hubs is enabled through consumer groups. A consumer group is a view (state, position, or offset) of an entire event hub. Consumer groups enable multiple consuming applications to each have a separate view of the event stream, and to read the stream independently at their own pace and with their own offsets.
Default value: $Default
connection_string :
string
The connection string required to communicate with Event Hubs, steps here https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-get-connection-string.
A Blob Storage account is required in order to store/retrieve/update the offset or state of the eventhub messages. This means that after stopping the filebeat azure module it can start back up at the spot that it stopped processing messages.
storage_account :
string
The name of the storage account the state/offsets will be stored and updated.
storage_account_key :
string
The storage account key, this key will be used to authorize access to data in your storage account.
resource_manager_endpoint :
string
Optional, by default we are using the azure public environment, to override, users can provide a specific resource manager endpoint in order to use a different azure environment.
Ex:
https://management.chinacloudapi.cn/ for azure ChinaCloud
https://management.microsoftazure.de/ for azure GermanCloud
https://management.azure.com/ for azure PublicCloud
https://management.usgovcloudapi.net/ for azure USGovernmentCloud
Users can also use this in case of a Hybrid Cloud model, where one may define their own endpoints.
App Service Logs
editECS Field Reference
Please refer to the following document for detailed information on ECS fields.
Exported fields
| Field | Description | Type |
|---|---|---|
@timestamp |
Event timestamp. |
date |
azure.app_service.category |
The category of the operation. |
keyword |
azure.app_service.container_id |
Application container id |
keyword |
azure.app_service.event_ip_address |
IP address of the event |
keyword |
azure.app_service.event_primary_stamp_name |
Primary name of the service |
keyword |
azure.app_service.event_stamp_name |
Name of the service |
keyword |
azure.app_service.event_stamp_type |
Values that the service supports |
keyword |
azure.app_service.host |
Host where the application is running |
keyword |
azure.app_service.level |
Verbosity level of log |
keyword |
azure.app_service.log |
Details about the event depending on level |
keyword |
azure.app_service.operation_name |
The operation name. |
keyword |
azure.app_service.properties.client_ip |
IP address of the client. |
ip |
azure.app_service.properties.client_port |
IP address of the client. |
long |
azure.app_service.properties.computer_name |
The name of the server on which the log file entry was generated. |
keyword |
azure.app_service.properties.cookie |
Cookie on HTTP request. |
keyword |
azure.app_service.properties.cs_bytes |
Number of bytes received by server. |
long |
azure.app_service.properties.cs_host |
Host name header on HTTP request. |
keyword |
azure.app_service.properties.cs_method |
keyword |
|
azure.app_service.properties.cs_uri_query |
URI query on HTTP request. |
keyword |
azure.app_service.properties.cs_uri_stem |
The target of the request. |
keyword |
azure.app_service.properties.cs_username |
The name of the authenticated user on HTTP request. |
keyword |
azure.app_service.properties.details |
Additional information |
keyword |
azure.app_service.properties.protocol |
Authentication protocol. |
keyword |
azure.app_service.properties.referer |
The site that the user last visited. This site provided a link to the current site. |
keyword |
azure.app_service.properties.result |
Success / Failure of HTTP request. |
keyword |
azure.app_service.properties.s_port |
Server port number. |
keyword |
azure.app_service.properties.sc_bytes |
Number of bytes sent by server. |
long |
azure.app_service.properties.sc_status |
HTTP status code. |
long |
azure.app_service.properties.sc_substatus |
Substatus error code on HTTP request. |
keyword |
azure.app_service.properties.sc_win32status |
Windows status code on HTTP request. |
keyword |
azure.app_service.properties.service_endpoint |
This indicates whether the access is via Virtual Network Service Endpoint communication |
keyword |
azure.app_service.properties.source_system |
The source system |
keyword |
azure.app_service.properties.time_generated |
Time of the Http Request |
keyword |
azure.app_service.properties.time_taken |
Time taken by HTTP request in milliseconds. |
long |
azure.app_service.properties.type |
The name of the table |
keyword |
azure.app_service.properties.user |
Username used for publishing access. |
keyword |
azure.app_service.properties.user_agent |
User agent on HTTP request. |
keyword |
azure.app_service.properties.user_display_name |
Email address of a user in case publishing was authorized via AAD authentication. |
keyword |
azure.app_service.properties.xazurefdid |
X-Azure-FDID header (Azure Frontdoor Id) of the HTTP request |
keyword |
azure.app_service.properties.xfdhealth_probe |
X-FD-HealthProbe (Azure Frontdoor Health Probe) of the HTTP request |
keyword |
azure.app_service.properties.xforwarded_for |
X-Forwarded-For header of the HTTP request |
keyword |
azure.app_service.properties.xforwarded_host |
X-Forwarded-Host header of the HTTP request |
keyword |
azure.app_service.result_description |
Log message description |
keyword |
azure.correlation_id |
Correlation ID |
keyword |
azure.resource.authorization_rule |
Authorization rule |
keyword |
azure.resource.group |
Resource group |
keyword |
azure.resource.id |
Resource ID |
keyword |
azure.resource.name |
Name |
keyword |
azure.resource.namespace |
Resource type/namespace |
keyword |
azure.resource.provider |
Resource type/namespace |
keyword |
azure.subscription_id |
Azure subscription ID |
keyword |
azure.tenant_id |
tenant ID |
keyword |
data_stream.dataset |
Data stream dataset name. |
constant_keyword |
data_stream.namespace |
Data stream namespace. |
constant_keyword |
data_stream.type |
Data stream type. |
constant_keyword |
dataset.name |
Dataset name. |
constant_keyword |
dataset.namespace |
Dataset namespace. |
constant_keyword |
dataset.type |
Dataset type. |
constant_keyword |
geo.city_name |
City name. |
keyword |
geo.continent_name |
Name of the continent. |
keyword |
geo.country_iso_code |
Country ISO code. |
keyword |
geo.country_name |
Country name. |
keyword |
geo.location |
Longitude and latitude. |
geo_point |
geo.name |
User-defined description of a location, at the level of granularity they care about. Could be the name of their data centers, the floor number, if this describes a local physical entity, city names. Not typically used in automated geolocation. |
keyword |
geo.region_iso_code |
Region ISO code. |
keyword |
geo.region_name |
Region name. |
keyword |
Changelog
editChangelog
| Version | Details | Kibana version(s) |
|---|---|---|
0.6.0 |
Enhancement (View pull request) |
— |
0.5.0 |
Enhancement (View pull request) |
— |
0.4.2 |
Enhancement (View pull request) |
— |
0.4.1 |
Bug fix (View pull request) |
— |
0.4.0 |
Enhancement (View pull request) |
— |
0.3.0 |
Enhancement (View pull request) |
— |
0.2.1 |
Bug fix (View pull request) |
— |
0.2.0 |
Enhancement (View pull request) |
— |
0.1.0 |
Enhancement (View pull request) |
— |
0.0.1 |
Enhancement (View pull request) |
— |