Python 中的 Azure Function App 计时器触发器不起作用

Question

I can't get an Azure Function App to run my Pyhton script (timer trigger function) inside of Azure. Locally, the script works just fine. My script is a simple operation which copies data from a PostgreSQL-database to an Azure SQL Database. (script is also listed below).

After creating a function with the TimerTrigger template in VS Code, I get this __ init __.py file, looking like this:

import logging

import azure.functions as func


def main(mytimer: func.TimerRequest) -> None:
    utc_timestamp = datetime.datetime.utcnow().replace(
        tzinfo=datetime.timezone.utc).isoformat()

    if mytimer.past_due:
        logging.info('The timer is past due!')

    logging.info('Python timer trigger function ran at %s', utc_timestamp)

So, as I understand correctly from the (standard generated) function.json file, the init.py file will be the fired at the desired trigger. The function.json file looks like this:

{
  "scriptFile": "__init__.py",
  "bindings": [
    {
      "name": "mytimer",
      "type": "timerTrigger",
      "direction": "in",
      "schedule": "* */10 * * * *"
    }
  ]
}

When I paste in my own script in the __ init __.py file, it works like a charm locallly , but once uploaded to Azure nothing happens, at all . After pasting my own script, the init.py file looks like this (I hid my credentials of course):

import datetime
import logging
import azure.functions as func
from flask import Flask
from flask import render_template
import psycopg2
import pandas as pd
import pyodbc

def main(mytimer: func.TimerRequest) -> None:
    utc_timestamp = datetime.datetime.utcnow().replace(
        tzinfo=datetime.timezone.utc).isoformat()

    if mytimer.past_due:
        logging.info('The timer is past due!')

    logging.info('Python timer trigger function ran at %s', utc_timestamp)

# Start of script
# Connect PostgreSQL
pg_host = "###"
pg_port = "###"
pg_dbname = "###"
pg_user = "###"
pg_pw = "###"
db_conn = psycopg2.connect(host=pg_host, port=pg_port, dbname=pg_dbname, user=pg_user, password=pg_pw)
pg_cursor = db_conn.cursor()

# Query PostgreSQL
pg_sql = 'select "_id", "minute", "hour", "day", "month", "year", "action", "dashlaneRid", "href", "id", "ip", "roleType", "sessionId", "tag", "textContent", "toggle", "url", "userId", "userPib", "utcEpochMillis", "xtag" from click'
pg_cursor.execute(pg_sql)
query = pg_cursor.fetchall()

# Fetch PostgreSQL query in Pandas DataFrame
click_df = pd.DataFrame(query, columns=[
    '_id'
    ,'minute'
    ,'hour'
    ,'day'
    ,'month'
    ,'year'
    ,'action'
    ,'dashlaneRid'
    ,'href'
    ,'id'
    ,'ip'
    ,'roleType'
    ,'sessionId'
    ,'tag'
    ,'textContent'
    ,'toggle'
    ,'url'
    ,'userId'
    ,'userPib'
    ,'utcEpochMillis'
    ,'xtag'])

# Azure SQL connect
az_server = '###'
az_db = '###'
az_user = '###'
az_pw = '####'
cnxn = pyodbc.connect('DRIVER={SQL Server};SERVER='+az_server+';DATABASE='+az_db+';UID='+az_user+';PWD='+ az_pw)
az_cursor = cnxn.cursor()

# Truncate table click
az_cursor.execute("TRUNCATE TABLE stage.click;")
cnxn.commit()
print('Table succesfully truncated')

# Fill table click with values
for index, row in click_df.iterrows():
    az_cursor.execute("INSERT INTO stage.click"
    "(_id, minute, hour, day, month, year, action, dashlaneRid, href, id, ip, roleType, sessionId, tag, textContent, toggle, url, userId, userPib, utcEpochMillis, xtag) VALUES(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?);"
    ,row._id, row.minute, row.hour, row.day, row.month, row.year, row.action, row.dashlaneRid, row.href, row.id, row.ip, row.roleType, row.sessionId, row.tag, row.textContent, row.toggle, row.url, row.userId, row.userPib, row.utcEpochMillis, row.xtag)
    cnxn.commit()
az_cursor.close()
pg_cursor.close()
print('Table successfully filled')

I configured CORS for the Function App to allow all domains, because when I Test/Run the function, I was getting HTTP error 413 Request entity too large. That's solved: I now get HTTP response 202 Accepted. However: nothing happens on the SQL Database.

I probably forgot to mention a few important things, so please ask away.

Answer 1

Thank you Anupum Chand for your suggestions, Based on the discussion in comment section we understood issue got resolved so we are converting the above comments to Answer for this thread to help other community members.

Post enabling the application insights metrics understood that issue is related to the psycopg2 library. After adding the psycopg2-binary to the requirements.txt file & adding ODBC Driver 17 for SQL Server successfully resolved your issue issue.